When a developer is working on a site, the changes are usually made on their local machine. At some point, you will want to host an "editing environment" where editors can log in and make changes.
Tina's flexibility means that there's several ways that you can setup an editing environment.
With a dedicated /admin section on your site, your Tina environment deploys with your site, but editing is constrained to /admin pages.
When users navigate to your /admin page, they will usually be prompted to log-in.
With modern build-time features like code-splitting, your production pages can load without Tina's javascript.
With this approach, your pages will have both a "production-mode" and an "editing-mode". Typically, there will be a link for a user to enter edit-mode (where the user will be prompted to log-in). Once logged in, Tina's editing features will be enabled within the same page.
This can be accomplished with a react site, with frontend conditionals that toggle edit-mode.
It can also be accomplished by using NextJS & preview-mode.
With this approach, your editing environment is a separate deployment from your site.
Examples coming soon.
This is the recommended way for editing a Gatsby site with Tina. With Gatsby, build transformations require a dev-server, so when the user makes changes the dev-server will do a re-build.