Tina CMS: editing, Git and the published store site
Follow a Tina CMS content correction from the editor through storage, preview and the site build to verify what customers actually receive.
- Published
- Last updated
Tina CMS, styled TinaCMS, gives editors a content interface while storing content in files backed by Git version control. For a retailer, its fit depends on how an approved edit reaches the published site. Saving content, reviewing a preview and releasing a page are separate steps in a build-based setup.
Identify the content and hosting arrangement
Identify the TinaCMS version, backend service and frontend before assessing the proposal. TinaCMS separates content editing from the website that displays the content. The developer chooses the site’s framework and hosting arrangement.
The official introduction describes Markdown, MDX and JSON content files stored in Git. Git records changes in a repository, with branches holding separate versions of the work. A branch used for review can contain a correction that the production branch hasn’t received.
TinaCloud is the hosted backend service for content queries, repository integration and user management. Self-hosting involves a backend host, a Git provider, a database adapter and an authentication provider. Specify who maintains those components if the proposal uses them.
The proposal must also name how the public site reads content. A static site generates pages during a build. A site that fetches content when someone opens a page has a different publication path. Visual editing in the browser doesn’t establish which path the public site uses.
Record the installed TinaCMS package version and the framework version in the technical handover. Attach the relevant documentation to that arrangement. A general promise of visual editing leaves the developer’s hosting and release work undefined.
Follow a store-content edit
Follow one policy correction from its saved file to the page a signed-out customer receives. Use a fictional retailer whose return-policy page gives the wrong return-request period. The approved policy allows requests within 30 days, while the page says 14 days.
Assume this example uses TinaCloud’s Editorial Workflow with a protected production branch and a static frontend. The editor opens the policy record, replaces 14 days with 30 days and saves the correction to a review branch. TinaCMS records the change in the repository and creates a pull request, which is a request to merge that branch into production.
The reviewer opens the preview for that branch and checks the corrected policy. The developer must configure the preview link and make the preview read the review branch. A preview pointing at production can show the old wording even when the edit was saved correctly.
After approval, the team merges the change into the protected branch. The store’s build then reads the approved content and generates the public policy page. The hosting service must successfully release that output before a static page shows the correction. TinaCMS’s content API guidance distinguishes content updates from the rebuild a statically generated site needs.
Keep the product catalogue outside this editorial correction. A product description can reference a stable product identifier, while the commerce system owns its current price, availability and order records. Use a variant identifier where the guidance applies to one size or finish. Matching by display title alone becomes unreliable when staff rename the product.
Give connected customer assistance a defined policy source and update path. If it imports the public page, confirm the new page is available before refreshing the import. If it reads a separate document feed, confirm that feed uses the approved branch and excludes drafts.
Test the publication boundary
Test access and publication with the store’s configured accounts and a non-public copy of the site. TinaCMS documents both draft fields and branch-based drafts. A draft field needs the site’s content selection rules to exclude that document from public output.
The Editorial Workflow documentation describes protected branches and pull requests, with the feature available on selected paid plans. Decide who can merge changes and who can change the workflow configuration. An editor’s login alone doesn’t define the store’s approval rules.
Use the fictional return-policy correction for these acceptance checks.
- Save the 30-day wording without approval. Confirm the review preview shows it while the public page still says 14 days. Check that public content queries and connected assistance also retain the approved version.
- Try an editor account and a reviewer account. Confirm that each can perform only the actions assigned in the store’s approval process. Check access to the underlying repository as well as the CMS interface.
- Approve the correction and follow the build to its deployed output. Open the canonical policy URL signed out, then follow a product-page policy link to the same rule.
- In the test environment, make publication fail after the content is saved. Confirm which version stays public and who receives the failure notice. Give the developer responsibility for restoring a successful release.
- Recover the prior approved policy through a new corrective change and release it. Confirm the restored text and any linked media work on the recovery site. Retain the approved correction for the final test release.
The data layer and deployed pages also need separate checks. TinaCloud indexes repository content for queries. A successfully saved or indexed record doesn’t prove that a static page was rebuilt from it. For the final correction, confirm the deployed version and the policy source received by customer assistance, then ask a return-period question against that source.
Budget for the maintained site
Separate the CMS service charge from hosting and developer maintenance. TinaCMS’s pricing page sets out TinaCloud plans, while the site’s hosting and release arrangement remains a separate decision. Keep the selected plan’s written terms with the proposal, including its billing period and user allowance.
Ask for separate costs for the following work.
- The CMS service or self-hosted backend, including authentication and support.
- Website hosting and preview environments, plus the build service that releases approved content.
- Developer work on content fields, templates and commerce references.
- Ongoing package updates, publication failures and tested recovery, including media stored outside the repository.
Include the selected review workflow in the quote. A low service charge doesn’t price the developer’s work to configure previews or maintain publication. For a self-hosted arrangement, add ownership of backend updates and operational recovery.
Choose the proposal when your editors can correct a policy without developer help and the maintained release process carries that approved correction to customers. Name the person who handles a failed release before the store depends on it for time-sensitive policy changes.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.