I Write Markdown in the Editor… and Watch the Site Update: Tools for Busy Builders
Low-friction edits mean more posts; picking an editor and a workflow matters more than hunting a mythical perfect tool.
If every tweak to a post means a long manual ritual, writing slows down even when ideas are ready. I believe a simple Markdown workflow—a solid editor, a fast preview, maybe one build command—removes more friction than any “magic” utility. The goal is for writing to stay the heavy lift, not fighting the interface.
Editor plus preview: the real minimum
Start with whatever feels easy on the eyes. Some folks live in VS Code with a preview pane, others prefer Obsidian or a lighter editor. The point is to see headings, lists, and code blocks roughly the way they will render. If your stack runs through Vite or a Laravel asset pipeline, keep dev mode beside the editor; even if it is not instant, you still feel close to the shipped page.
Lightweight file hygiene inside the repo
Use clear filenames and keep dates in front matter when you need chronological sorting. A content/ folder (or similar) gives you a single source of truth—skip scattered notes that compete with published drafts. When your brain knows where “home” is, publishing becomes a small decision after writing, not the other way around.
When Markdown stops being enough
If you need multi-user permissions, complex scheduling, or lots of dynamic fields, a CMS might be the next step. For a personal portfolio with a blog, Markdown usually stays enough and keeps maintenance light.
Quick list:
- Comfortable editor + preview or a fast build
- One obvious content directory
- One deploy command you know by heart
Parting question: Which step in your current workflow annoys you most whenever you start a new post?