My Blogging Workflow
My workflow for writing and publishing blog posts (blosts) has changed a lot over the years that I have been blogging (nearly 2 years). In this blost, I'll go through what I do to write then publish my blog posts.
IDEAS This is one of the hardest parts of the whole process for me, coming up with the ideas. Often my blost ideas come from random thoughts or from blosts/toots from some of my FediFriends. Sometimes they come in groups, other times they don’t come at all.
Writing
To write my blosts, I use Obsidian syncing between all my different devices using a community plugin called Remotely Save. I have it all saved to OneDrive (yes, bleh, but it’s what works for me, I don’t have the infrastructure to host storage myself). As Obsidian creates a local “Vault” directory on each device it’s installed and setup on, I can cd
into this directory and use Neovim to edit the files in the terminal on my Linux laptop, WSL on one of my Windows laptops or even iSH on my iPhone. Makes it a lot easier to edit blosts this way.
Publishing
Once I have finished writing my blosts, I turn on Source Mode in Obsidian and copy/paste the markdown into a new markdown file on either Codeberg web editor or into a local git
clone on one of my machines. Sometimes I put the front matter in Obsidian, other times I put it in the markdown file in git. Once I’m happy with all that, I commit and push to the main branch of my websites repo and let the automation do its thing. I use Codeberg’s Woodpecker CI to trigger a Vercel build where my site fets built and deployed.
Hopefully this blost has been informative and enjoyable, let me know your thoughts in the comments (aka my emails). Have a good one!
- Previous: Stormworks: Build & Rescue - Initial Thoughts
- Next: June Is Upon Us