So, I've got an elaborate and highly manual process put together for rolling out this blog. Up until now, this has worked well because I'd author an entry every so often, and some time later I'd want to publish it, and I'd take the 5 or so minutes to jump through the hoops to get this out to the site. Now, I am using a site generator, so building is fairly quick, but I still have to move it to my remote host to get it out. I have some support bits, but I have to run all of them.

The other part here is that my entries are reaching the high double digits, and coming up with super interesting blog titles is becomimg a bit more challenging, and I'd like to have a bit better of a logical organization. In my hand-crafted blog, I did this with monthly directories. That works well for me logically, but I'm flexible and don't mind even doing things by year.

So, there is some cleanup and org to be done. I want to review my tags as well -- I've gotten lazy and everything is getting one category, where I have a bunch or categories. Also, I have to figure out if my tags should be generic like container, or be specific like Docker and Kubernetes. I've even started to use some more Markdown, figuring out the corrrect way to do a hard rule and remebering out how to use URL links again. And I'd like to have a spell checker, so I don't need to rebuild when I notice a mistake on the website.

This means learning a bit more about Pelican. I also need to check out what else is out there -- while I like Pelican, one of the advantages of using a site generator is flexibility, so I want to check out state of the art.

Along with using more features in my entries, like graphics and diagrams, I'm planning on streamlining the publishing process. I have a way to create a draft, signal the draft is ready for publishing. What I want is to have a script/process that spellchecks, builds the content, stages and then launches the content. I also want a "quick revert", so I can go back to a previous revision if I messed something up. Last but not least, should I use source control for the blog? Maybe, but I should figure this out.