CMS framework integrations: choose your frontend guide
Find the CMS connection guide for your frontend. Each route separates content access, preview, publication and the checks that keep store guidance current.
- Published
- Last updated
Choose the CMS guide for the framework that publishes your storefront’s public pages. A content management system (CMS) holds editorial content, such as buying guides and delivery policies. Your frontend determines how that content reaches a customer.
Choose the framework you publish with
Start with the application that renders the page. A JavaScript runtime can run a content service while a different application reads its content. Knowing that the stack uses JavaScript doesn’t identify its rendering or publication workflow.
For a Next.js storefront, use the Next.js guide. Choose Astro or Nuxt when that framework publishes the public pages. Use the JavaScript guide when you first need to separate the content service from its frontend client.
Keep content access and publication separate
A successful content request proves that your application can read a record. Draft preview checks whether an editor can inspect an unpublished change without exposing it to customers. Publication checks whether the approved version reaches the public page through the configured build or refresh process.
For example, preview a revised delivery policy, then publish it and compare the customer-facing wording with the approved record. Keep product prices and stock in the commerce system that owns them. Private order records stay with their order system.
Use the framework-specific checks
The directory below groups the CMS guides by the stack you maintain. The JavaScript guide separates the server and frontend roles. Next.js covers draft preview and public refresh. Astro examines content sourcing and build or request-time delivery, while Nuxt covers content loading and the publication path.
Choose your framework’s guide before copying configuration from another stack. Follow its checks through to the public version of a changed answer.
Explore this topic
18 guides
Start here
- CMS for Astro: content, previews and updates in 2026Publish CMS content through Astro with a clear update model. Compare local files and external sources, validate records and check the deployed policy page.
- CMS for JavaScript: server and frontend roles in 2026Choose a JavaScript CMS by the role it plays. Distinguish a Node-hosted editor from a frontend client, then check typed content and published updates.
- CMS for Next.js: preview and publication in 2026Connect a CMS to Next.js with a clear draft and publication flow. Compare content access, previews and cache refresh before relying on updated store pages.
More guides
- CMS for Nuxt: content routes and publishing in 2026Choose a CMS route for Nuxt without mixing editing and delivery. Compare content files and APIs, preview a change and verify the published store guidance.
- Best React CMS options for retail frontendsCompare CMS approaches for a React retail frontend by their editorial workflow, content delivery, preview and responsibility for the published version.
- CMS for an ASP.NET website: compare the content workflowChoose a CMS for an ASP.NET retail website by checking the supported runtime, editorial workflow and ownership of publication and maintenance.
- CMS for Gatsby: content, builds and previewsConnect a CMS to a Gatsby retail site through the documented content, build and preview path, then verify the approved version customers receive.
- Laravel CMS: choose and maintain the content workflowChoose a Laravel CMS approach for retail content, comparing the editor, application and published page while keeping commerce records clearly assigned.
- CMS for Hugo: editing files and publishing contentChoose a CMS editing path for Hugo retail content, from stored files and previews to a successful build and the approved page customers see.
- Java CMS: content choices for a maintained retail siteChoose a Java CMS approach around the supported runtime, editorial task and public delivery, with clear commerce boundaries and maintenance owners.
- PHP CMS: choose the editorial and operating dutiesChoose a PHP CMS for retail content by checking the supported runtime, editing workflow, publication and maintenance rather than the language label alone.
- CMS for Svelte: content access, preview and publicationConnect a CMS to a Svelte retail frontend using its actual rendering setup, with draft previews, public refresh and clear product-record ownership.
- CMS for Remix: content, previews and public deliveryConnect a CMS to a Remix retail site through its actual supported release, content reads and previews, then verify the approved public version.
- Golang CMS: choose a content workflowChoose a Go-compatible CMS approach for retail content, comparing editorial needs, API delivery and application maintenance before connecting the store.
- Python CMS options for retail publishingCompare Python CMS approaches for guides and policies, checking editors, delivery, maintenance and the retail application’s actual content boundary.
- Ruby on Rails CMS: editorial and delivery choicesChoose a Rails CMS approach around the actual editor, content model and publication path, with retail transactions kept in their owning system.
- Rust CMS: content editing and delivery optionsAssess a CMS arrangement for a Rust retail application, comparing actual editor needs, content APIs and maintenance rather than the language label alone.
- Vercel CMS options: content, previews and deploymentChoose a CMS for a Vercel-hosted retail site, separating the editor and content API from previews, builds and the public deployment.