TinaCMS Documentation and Website

Self-hosting TinaCMS allows you to run your own CMS backend instead of using TinaCloud. This gives you full control over your database, authentication, and Git integration.

When self-hosting, you configure an API function to serve as your backend service. This function exposes a GraphQL endpoint for your content and handles all aspects of authentication and authorization. The backend is designed to be compatible with any Node.js serverless environment, such as Vercel or Netlify.

The TinaCMS CLI provides several commands to manage your development environment, build your site, and maintain your schema.

Core Commands:

• dev: Compiles the schema and starts a local GraphQL server for development.
• build: Compiles/validates the schema and generates client/types for production.
• init: Initializes TinaCMS in an existing project (installs dependencies and creates a basic schema).
• audit: Checks files for schema errors and incorrect extensions.
• search-index: Builds and uploads the search index to TinaCloud.
• doctor: Checks if your installed TinaCMS packages are up to date.
• help: Displays help information.

$ tinacms <command>

The starter project follows a standard Next.js structure with additional directories for data and components:

• components/: Stores React components used throughout the blog.
• data/: Contains blog configuration and other data (e.g., config.json).
• pages/: Contains the file-based routes for the application.
• public/: Holds static assets like images that are accessible from the base URL /.
• styles/: Contains CSS files, including component-level CSS modules.

my-nextjs-blog
├── components/
├── data/
├── pages/
├── public/
└── styles/

If you are developing or deploying TinaCMS projects from mainland China without a VPN, the following service availability applies:

While the core TinaCMS tools (CLI, Cloud, and Documentation) work as expected, the primary challenge is that standard static hosting platforms like Vercel or Netlify cannot be reached by users in China.

Pricing

TinaCloud is currently free until the public release. A 'forever free' plan for personal use is planned. Users with large-team use cases may be contacted regarding paid plans.

Support and Feedback

• Documentation: Check the official docs for answers.
• Community: Join the Discord server.
• Email: Contact support@tina.io for help or to schedule a chat.
• Dashboard: Use the chat widget located at the bottom left of the TinaCloud dashboard.

The starter project follows a standard Next.js structure with additional directories for data and components:

• components/: Stores all React components used by the blog.
• data/: Contains blog configuration and other data files (e.g., config.json).
• pages/: Contains the file-based routes for the application.
• public/: Holds static assets like images that are accessible via the root URL (e.g., /image.jpg).
• styles/: Contains CSS modules and global styles.

TinaCMS's default 'Basic Editor' is compatible with a wide range of frameworks because it reads and writes file-based content such as Markdown, MDX, and JSON.

Key Framework Details:

• Astro is the recommended default framework for new projects. You can start there if you have no specific framework preference.
• Visual Editing (real-time preview of changes) is supported in React-based frameworks (Next.js, React, etc.) and is also available in Astro via specific configurations even without a React page tree.