Overview

aSaaSin uses TinaCMS as the content management system for landing pages, blog, and docs.

You can run the project locally without any TinaCMS environment variables. These variables become relevant when connecting to Tina Cloud for production editing.

Full instructions for registering with Tina Cloud, connecting your GitHub repository, and obtaining the credentials are provided in the Deployment section.

Add to env (optional for local)

# TinaCMS
NEXT_PUBLIC_TINA_CLIENT_ID=
TINA_TOKEN=
TINA_SEARCH_TOKEN=

You can leave these variables empty during local development. When you connect a production site to Tina Cloud, you will add real values here.

Save the file, then restart the dev server if it was running.

What each key is for

  • NEXT_PUBLIC_TINA_CLIENT_ID - Identifies your Tina Cloud project (safe to expose).
  • TINA_TOKEN - API token for authenticated editing (server-side).
  • TINA_SEARCH_TOKEN - Token used for content search.

In local development you can use dummy values or test keys.
When deploying, you’ll generate these values in Tina Cloud and connect them with your GitHub repo.