Static Content & Publishing
Docs sites, blogs, handbooks and knowledge bases built on a Markdown/MDX pipeline that non-developers can write in.
Build
If your team writes a lot — documentation, release notes, a blog, an internal handbook — the publishing pipeline matters as much as the design. I set up a content workflow where writing is Markdown, review is a merge request, and publishing is automatic.
- Markdown / MDX content pipeline with front-matter schema and validation
- Full-text client-side search (no search service to pay for)
- Automatic navigation, table of contents, and cross-links from the file tree
- Draft previews on every branch, publish on merge to main
- Optional headless CMS layer for browser-based editing
- RSS/Atom feed and social preview images generated at build time
Writing should not require a developer
Authors work in Markdown with a small set of custom components (callouts, code tabs, embeds). A schema check runs in CI so a missing title or a broken internal link fails the build instead of shipping.
If some authors will never touch Git, I add a headless CMS on top — they edit in a browser, it commits for them, the same build runs.
Search that costs nothing to run
Search index is built at deploy time and shipped as a static asset, then queried entirely in the visitor's browser. No Algolia bill, no Elasticsearch cluster, and it keeps working offline.
Migrating existing content
I can bulk-convert an existing WordPress, Notion, Confluence, or GitBook export into the new Markdown structure, preserving URLs with redirects so you do not lose search rankings.
FAQ
Have a project in mind?
Tell me what you are building. You get a scoping call and a fixed quote — no obligation.