Home
Blog
Showcase
Community
Introduction
Overview
Introduction To TinaCMS
Getting Started
Using the Tina Editor
FAQ
Core Concepts
Content Modeling
Data Fetching
Visual Editing
Querying Content
Overview
Writing custom queries
Editing
Overview
Markdown & MDX
Block-based editing
Single Document Collections
Customizing Tina
Overview
Validation
Custom Field Components
Custom List Rendering
Format and Parse Input
Filename Customization
Before Submit function
Going To Production
Overview
Tina Cloud
Self-Hosted
Drafts
Overview
Draft Fields
Editorial Workflow
Guides
Overview
Framework Guides
Separate Content Repo
Querying Tina Content at Runtime
Internationalization
Migrating From Forestry
Overview
Setting up Tina
Common Errors & Fixes when Migrating to TinaCMS
Comparing Forestry & Tina Concepts
Accessing the CMS
Local Workflow
Previews
Content Modelling
Drafts
Data Files
Media
Missing Forestry Features
Reference
Overview
Config
Schema
The "tina" folder
The TinaCMS CLI
Media
Search
Content API
Tina's edit state
The "tinaField" helper
Self-Hosted Components
Table of Contents

CMS Hosting

One of the main differences between Forestry.io and TinaCMS is how you access the CMS. In Forestry, you access the CMS via our hosted environment (app.forestry.io).

In TinaCMS, the CMS frontend is hosted alongside your site. This pattern is comparable to Forestry's "remote-admin" feature, which allows you to access the CMS from your site's URL.

To set this up, your site's build script will change to something like:

- build: hugo
+ build: tinacms build && hugo

The tinacms build step outputs the TinaCMS dashboard SPA in your site's build directory.

Once TinaCMS is setup, your editors will access the CMS via (<your-site-url>/admin)

Extra flexibility

By having the CMS-frontend hosted within your site, you have more flexibility/control over your CMS behaviour. Write custom field components, create custom field validations, reuse your schema models, etc.

For example, here's how you might go about creating a custom "read-only field"

//config.js
// ...
const ReadonlyTextField = wrapFieldsWithMeta(({ input }) => {
return <input type="text" disabled className={textFieldClasses} {...input} />
})
export default defineSchema({
collections: [
{
label: 'Post',
name: 'post',
path: 'posts',
fields: [
{
label: 'Title',
name: 'title',
type: 'string',
},
{
label: 'identifier',
name: 'identifier',
type: 'string',
ui: {
component: ReadonlyTextField,
},
},
],
},
],
})

Product

Showcase
Tina Cloud
Introduction
How Tina Works
Roadmap

Resources

Blog
Examples
Support
Media

Whats New
TinaCMS
TinaCloud
Use Cases
Agencies
Documentation
Teams
Jamstack CMS
Benefits
MDX
Markdown
Git
Editorial Workflow
Customization
SEO
Comparisons
TinaCMS vs Storyblok
TinaCMS vs Sanity
TinaCMS vs DecapCMS
TinaCMS vs Contentful
TinaCMS vs Builder.io
TinaCMS vs Strapi
Integrations
Astro
Hugo
NextJS
Jekyll