What is Tina CMS?

Tina CMS is “The Markdown CMS”. It is an open-source, Git-backed content management system that provides real-time visual editing for static sites and React-based frameworks. Originally developed by Forestry.io, Tina evolved from an inline editing toolkit into a full-featured CMS.

Tina is designed for development teams who want to give content editors a visual, intuitive interface while keeping all content stored in Git. This approach maintains the benefits of version control and developer workflows while removing the friction of editing Markdown files directly.

The platform offers both self-hosted options (open-source) and Tina Cloud for managed Git synchronisation.

Architecture and Technology

Tina combines a Git-based content layer with a React-powered editing experience.

Core Components

Tina Schema: TypeScript-defined content models
Content API: GraphQL API for content queries
Visual Editor: Inline, contextual editing interface
Git Backend: Content stored as files in your repository
Tina Cloud: Managed service for Git sync and auth

How It Works

Define schemas in TypeScript configuration
Content stored as Markdown/JSON in your Git repository
GraphQL API provides typed queries for your frontend
Visual editor enables in-context content changes
Changes committed back to Git automatically

Typical Use Cases

Tina is commonly used for:

Documentation sites: Developer docs with team editing
Marketing websites: Jamstack sites with content workflows
Blogs: Markdown-based publishing with visual editing
Component-driven sites: React/Next.js projects
Open-source project sites: Community-editable content

Strengths

Visual editing: True inline, contextual editing experience
Git-native: Full version history via Git
TypeScript schemas: Type-safe content modelling
GraphQL API: Flexible, typed content queries
Open source: Self-host with full control
Framework integration: Deep Next.js support
MDX support: React components in Markdown

Limitations and Trade-offs

React-focused: Best with React-based frameworks
Setup complexity: Configuration requires TypeScript knowledge
Git limitations: Large binary media can bloat repositories
Tina Cloud dependency: Some features need cloud service
Newer ecosystem: Smaller community than established CMSs
Build times: Content changes require site rebuilds

SEO, Performance, and Content Governance

SEO

Content includes frontmatter for meta tags and SEO fields. Static generation ensures fast, crawlable pages with full SEO control at the framework level.

Performance

Git-based approach with static generation provides excellent performance. Content is fetched at build time, resulting in fast static pages.

Content Governance

Git history provides complete audit trail. Branch-based workflows enable content staging. Tina Cloud adds authentication and access control.

Tips and Best Practices

Use Tina Cloud for easier authentication and team workflows
Design schemas carefully,changes require migration effort
Leverage MDX for dynamic content within Markdown
Consider media hosting externally for large media libraries
Set up preview deployments for content review before merge

Who Should (and Should Not) Choose Tina

Best Fit For

Next.js and React developers
Teams wanting visual editing with Git benefits
Documentation and marketing sites
Projects already using Markdown content

Not Ideal For

Non-React projects (limited framework support)
Teams needing traditional CMS experience
Media-heavy sites with large file needs
Non-technical content teams

Common Alternatives

Netlify CMS (Decap): Similar Git-based, less visual editing
Pages CMS: Simpler Git-based editing
Sanity: Hosted backend, more features
Contentful: Full-featured SaaS headless CMS

Tina CMS excels for React developers wanting Git-based content with a polished visual editing experience.