Using environments in the Frontastic studio

In the Frontastic studioFrontastic studio - The interface you use to manage, build, and edit all areas of your project and commerce sites. Previously known as `backstage`. there are 3 environments:

  • Production
  • Staging
  • Development

This article will go through the best practices when working with these environments and what can/can't be done.

If anything is already available in the production environment, you won't be able to view or edit this in staging or development.

There are 2 areas of the Frontastic studioFrontastic studio - The interface you use to manage, build, and edit all areas of your project and commerce sites. Previously known as `backstage`. that are the same across all 3 environments. They are: Teams, and Sandboxes.

Production

If you're a Content Editor or any kind of business usersbusiness users - A non-technical user of the Frontastic studio. They could be a marketeer, an SEO specialist, a translator, and so on., you should use the production environment.

Developers can also use this environment to do any tests with production data. Dynamic page schemas need to always be uploaded to the production environment.

If you make any changes to a Live page and publish these changes, they'll be visible to your customers.

If you want to create a new version of your current homepage, it's best to duplicate the default page version. Then you can work on the draft version without worrying that the changes will go live to your customers.

Staging

If you're using the Frontastic CLIFrontastic CLI - Our Commandline Interface (CLI) that you can use for frontend development., you should use the staging environment. Any changes you make in this environment will be visible to you on the test link provided in the Frontastic CLIFrontastic CLI - Our Commandline Interface (CLI) that you can use for frontend development..

If you override an existing Frontastic component schema, this will update in all environments including production.

Any page folderspage folders - A way of structuring the pages within a project and forms the URL structure – they can contain sub-folders. Known as `node` in code. in the production environment will be shown here, but you won't be able to edit them. This is also the same for page templatespage templates - A template of a page that can be used as a base to create new pages – they're created using the page template builder. Previously known as `blueprints`. and component groupscomponent groups - A group of Frontastic components saved in a reusable block – they’re created using the component group builder. Previously known as `kits`..

Development

If you're using a Frontastic sandboxFrontastic sandbox - A virtual machine hosted in the cloud that you can use for backend and some frontend development. They're provisioned from the developer area of the Frontastic studio., you should use the development environment. Any changes you make in this environment will be visible to you locally.

If you override an existing Frontastic componentFrontastic component - A customizable building block that's used together with other components to create a commerce site. Known as `tastic` for short in code. schema, this will update in all environments, including production.

Any page folderspage folders - A way of structuring the pages within a project and forms the URL structure – they can contain sub-folders. Known as `node` in code. in the staging or production environment will be shown here, but you won't be able to edit them. This is also the same for page templatespage templates - A template of a page that can be used as a base to create new pages – they're created using the page template builder. Previously known as `blueprints`. and component groupscomponent groups - A group of Frontastic components saved in a reusable block – they’re created using the component group builder. Previously known as `kits`..


Did this page help you?