Thoughts on my workflow

I’m not fully happy with my workflow for creating and publishing these posts. At the moment I keep everything in a git repository and version and publish from the command line.

But I’m not really using sophisticated versioning. It is nice to fix a typo or so, or to keep posts and their assets and design changes together, but that’s about it.

When drafting posts it is actually a hassle. I’m using different devices so I have to make sure to commit/push/pull all the time just to keep things in sync. Which in turn clutters version history unnecessary.

In addition, using two branches to distinguish what I draft (”dev”) from what I publish (“main”) makes it a multi-step procedure to actually publish something.

Let’s summarize the requirements:

• Drafts should be kept in sync across devices
• Published posts should be versioned
• Publishing a draft should be take exactly one simple action

Yes, I could just go with an established platform, say WordPress, but that feels counter to one of the reasons I started this blog, namely to have a setup that I can fully control without too much headaches.

Having put these thoughts into words I leave them now for subconscious processing.