Defaulting To Scripts & Templates#
| Field | Label |
|---|---|
| Date | 2025-05-01 |
| Project | Personal-Site |
| Update | Streaming Usage |
It really is true that with ease comes use. I have in fact uploaded to my personal site a bit more than I did a few months ago. To improve upon this, I've added a script to install & setup a local static site instance and another to deploy to Github. They are 5 liners each but it removes more friction. Now, I can run my scripts and have it deploy with ease. Before, I would have to read my README.md and copy paste commands I wrote there. Now, I don't need to do that. Considering I intend to write indefinitely, this should save me time. I've also updated my Nvim's init.lua config to inject templates to help write my entries. This is where my key-value tables are coming from. I'm hoping that maybe in the future I can use these tables but for now they serve as a way to view metadata about my entries. I've also added a markdown formatter and visualizer in my Nvim' init.lua. They will be helpful in viewing and editing text.
Kerfuffle in Last Deployment#
| Field | Label |
|---|---|
| Date | 2025-04-22 |
| Project | Personal-Site |
| Update | Deleted By Accident |
I had unintentionally deleted my project site files haha. No, it is not due to rm -rf being misplaced. It is due to how mkdocs gh-deploy will overwrite whatever directory it is in. This wasn't too bad as it took a few minutes to copy the file contents from the site back into markdown. It does make me want to update the mkdocs command to not overwrite without letting the user know what is going to be overwritten. I doubt many people have workflows in which they are intending to do that. It would help on the usability front.
50% Done w/ Personal Site#
| Field | Label |
|---|---|
| Date | 2025-04-11 |
| Project | Personal-Site |
| Update | Massive Improvements |
Previously, my personal site had a single README.md with all my
aspirations. During this update, I used mkdocs to make it nicer.
Originally, my intentions were to use Golang to setup a static site but mkdocs does the job just fine. No reason to let perfect or a narrowed focus get in the way of making something useable.
I suppose one barrier to making progress on this site was scheduling a regular time to make updates. I think there was some friction to update it as well. Now that I've reach a mostly editable and deployable state, I can proceed more easily. Hopefully with more edits.
Eventually, I'll have to update this to use Docker instead of python's venv as I abhor installing local packages onto my development machine. No practical consequences will come from leaving it as is, but I don't prefer it.