Tina CMS backend adapter for Fumadocs content management

[fazi-gondal]

What problem will this feature address?

As a senior developer maintaining a growing documentation ecosystem, I’d love to see a native integration with Tina CMS for both Fumadocs and Fumapress.

Why Tina CMS?
Tina is a fully open‑source, Git‑backed headless CMS that aligns perfectly with Fumadocs’ Markdown/MDX workflow. It provides:

• Visual, real‑time editing – content creators get a live preview without needing to run a local dev environment.
• Git‑backed version control – all content stays as plain Markdown/MDX in your repository; no proprietary database.
• GraphQL API – query structured content effortlessly (e.g., post.author.firstName).
• Zero‑database architecture – simpler hosting, instant rollbacks, and full developer control.

Describe the solution you'd like

Given that Fumadocs already offers official integrations for Sanity, and community examples exist for Payload CMS, a first‑party Tina adapter would be a massive win for teams that prefer a lightweight, Git‑native content pipeline. This would benefit both fumadocs (documentation sites) and fumapress (content‑driven websites), making the entire ecosystem far more accessible to non‑technical editors.

Describe alternatives you've considered

Pagescms

Additional context

No response

[coderabbitai[bot]]

🔗 Related PRs

#2820 - docs: add Takumi integration [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[fuma-nama]

feel free to create community adapter for Fumadocs, we can link it from the official docs.

[fazi-gondal]

feel free to create community adapter for Fumadocs, we can link it from the official docs.

Thanks for the quick reply @fuma-nama! I'll get started on a community adapter for Tina CMS. A couple of quick questions if you have a moment:

• Are there any existing adapter examples (like the Sanity or Payload CMS ones) you'd recommend as a reference for the preferred structure and patterns?
• Any specific requirements or conventions the adapter should follow to be eligible for linking from the official docs?

Once the repo is up, I'll share it here for feedback and hope to see it listed in the docs soon. Really looking forward to bringing Tina's visual editing to the Fumadocs ecosystem.

[fuma-nama]

would recommend the Sanity CMS adapter if you need a reference, the conventions are all baked into Source API at type-level.

[fazi-gondal]

would recommend the Sanity CMS adapter if you need a reference, the conventions are all baked into Source API at type-level.

Sounds great, thanks @fuma-nama! I'll build the community adapter for Tina CMS and share the repo once it's ready. Looking forward to seeing it linked in the docs.

[fazi-gondal]

Hi Hark / TinaCMS team,
@tinacms
Thanks for reaching out and for the offer to collaborate.

After thinking it over, I realized that your team has significantly deeper expertise in both TinaCMS and Next.js internals than I do. Given that, it genuinely makes more sense for the TinaCMS team to take the lead on building this integration—you'll be able to architect it properly from the start.

Rather than me driving the development, I'd be happy to step back and contribute in a supporting role instead. For example, I can help with:

· Beta testing the adapter once you have a working version
· Writing documentation or examples from a user's perspective
· Providing feedback on the DX (developer experience)

That way, the core work is handled by the experts, and I still get to help where it counts.

Let me know if that works for you, and feel free to share progress updates here.