Marketing and SEO
FumaDocs for documentation and blog. MD/MDX content, landing pages, and SEO. Ship content that converts and ranks.
What this system covers
Documentation site
FumaDocs powers the docs: MD/MDX content, structure, and navigation. Ship a professional docs site that onboarding and trust rely on.
Blog
Blog content and feed, with optional MDX. Keep marketing and product updates in one place, consistent with the rest of the app.
Landing and marketing pages
Routing, CTAs, and layout aligned with the app. One codebase for product and marketing so messaging stays consistent.
SEO
Meta tags, structure, and sitemap. Docs and blog support authority and long-tail search so you rank for what you document.
Why a dedicated docs and blog system?
Good documentation and content improve onboarding, trust, and SEO. We ship one provider per category (FumaDocs for docs) with a clear swap guide so you can replace it if needed. MD and MDX let you write in a format that version control and non-developers can work with.
Decisions & trade-offs
We chose FumaDocs so you get a docs site and blog from the same content pipeline (MD/MDX). We wanted one provider per category with a clear swap guide: ship fast with defaults, replace when your needs outgrow them. SEO and long-tail content are first-class so your docs and blog support acquisition and trust.
Pros
- Docs and blog in one stack; MD/MDX is version-control and writer-friendly.
- FumaDocs is lightweight and fits TanStack Start; no heavy static site generator.
- Meta, structure, and sitemap support SEO without extra tooling.
- Swap path is documented so you can move to Docusaurus or similar if needed.
Trade-offs
- FumaDocs is less widely adopted than Docusaurus or Nextra; we trade ecosystem for fit.
- Advanced doc features (versioned docs, i18n) may require custom work.
- Blog is basic; high-volume content teams might want a headless CMS later.