Plan

Before you create content, administrators and developers need to decide how they plan to use CMS (SaaS).

1. Create a CMS (SaaS) architecture design – Plan the configuration of your CMS (SaaS) instance to meet your organization's content management needs. Determine
   1. the types of content you manage, such as articles, blog posts, products, and so on.
   2. your target audiences.
   3. your delivery platforms.
   4. how your architecture scales.
   5. how you plan for data security updates.
2. Review your instances – Decide how to divide up your production and non-production environments. CMS (SaaS) includes three instances out of the box. Use these instances to separate your production and non-production data. You can choose how to use your instances. See Configure environments.
3. Create a content model – Consider how you want to construct your content in CMS (SaaS). Because content can be used with any front end, it is important to architect your content in a platform-agnostic way. Identify the content types needed, including their fields and properties. The content type is the foundation for creating one or many experiences, pages, or block instances. The content type and properties must be mapped to the corresponding rendering to display content to visitors.
4. Review CMS (SaaS) user interface documentation – Read the documentation in the Content managers section to learn how the content types, content, and styles you define are reflected in the CMS (SaaS) UI.
5. Select a front-end stack – Choose the technologies and tools for the user interface and client-side functionality. Optimizely has partnered with Vercel and Netlify, which offer services for hosting the front end of your application.
6. Configure a repository – Select a version control system to track changes to your code.