First Things First

These questions will help you, as Site Administrator, determine what first needs to be configured in Salesforce and OrchestraCMS.

Who will need access?

Decide who needs access to OrchestraCMS to create, edit, approve, and publish content. This determines how many and what types of OrchestraCMS user licenses you require. Once they have been allocated to you, you can create OrchestraCMS profiles and set specific permissions that determine what each profile can do.

What will you put on your website?

Before anything else, it is important to understand the types of content that will be on your site. This affects nearly every other consideration.

Do you need an approval process?

Do you have separate content creators and approvers in your organization, or are all content creators allowed to publish content? If you require an approval process, this needs to be structured in Salesforce and associated with OrchestraCMS before you can use approvals to control the publishing process.    

Do you need to control access to content or pages?

Do you need to restrict what some site users see compared to others? If you do, you can use private sharing, targeting, or both to control access to content and pages. (Private sharing and targeting each require an OrchestraCMS feature license.)

What are your storage requirements for media files?  

The storage limit for the default media library is based on the storage limits of your Salesforce organization. If you need additional storage, OrchestraCMS integrates with  Amazon Web Services and Google Cloud Storage. (Linking an Amazon Web Services or Google Cloud Storage account to OrchestraCMS requires a feature license.)

What pages do you need? How will users navigate to them?

Planning how users will navigate your site might be the single most important aspect of building a site that people enjoy visiting. Determine how users can quickly and logically reach the content they want—and the content you want them to see—whether it's through a primary navigation menu, header and footer links, taxonomy menus, or by other means.

Determining the initial pages that are required for your site should only happen after you have decided the types of content and features you want to include.

Using OrchestraCMS taxonomies to display content dynamically helps minimize the amount of pages required for your site.