💾 Archived View for rawtext.club › ~mieum › relog › 2020-10-26-jfm-draft_strategy.gmi captured on 2023-09-28 at 17:36:17. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-12-03)
-=-=-=-=-=-=-
gemini://carcosa.net/journal/20201025-drafts-branching.gmi
My first thought is to keep my gemlog under version control (which it already was, just like my blog), and use branches for drafts. I initially tried using a single "draft" branch, but then I got commits entangled between multiple in-the-air drafts. Now I'm trying one branch named "drafts/article-name" per draft article, merge to main and delete when it's ready to publish. But I'm afraid I'm overthinking it.
I can see how things could get messy trying to use git branches to manage drafts. Why not just keep a non-world-readable drafts folder in the repo and move posts out when they are ready to publish? You could also include the drafts folder in the .gitignore file if you are working locally and pushing changes to the server. In that case, you could alternatively just keep drafts unstaged.
Even though gemini is stylistically minimal and doesn't really NEED a statitc site generator in the way a blog would, I think it would be helpful to use one for the sake of managing drafts, tags, and other metadata. Lately I've been trying to build something like this for my own use as a way to learn more about programming. It's an after-the-kids-are-asleep project, so it's slow moving. But I'm also interested to hear about others' ideas and solutions.
_________
CC-BY-NC-SA 4.0 mieum(at)rawtext.club