Planning an OrchestraCMS Site Implementation

When it comes to publishing OrchestraCMS Content and Pages, it will likely be the site publishing team that handles these tasks rather than site developers. However, there are several considerations a developer can make to help improve how the publishers will be using the site. These include:

• Building page templates that are clear and concise, which provide not only the layout and resources for the live website, but also instructions that make it simple for the site publishing team to work with.
• Creating content templates in a way that provides ease of use and extensibility of configuration.

Salesforce is the platform on which OrchestraCMS runs.  Although OrchestraCMS provides the application interface for managing the pages and content in the site, the site itself is largely handled at the Salesforce level.  This means that site level management tasks such as configuring business process workflows, security and domain configurations need to be performed by a Salesforce Administrator.

The following items are intended as a broad outline to identify some of the processes involved in implementing a site with OrchestraCMS.

1. Collect Project Requirements
2. Design the Site
3. Isolate content markup from page markup
4. Convert page markup into templates
5. Convert content markup into templates
6. Build services to handle advanced functionality requiring server side processing using the OrchestraCMS RESTProxy
7. Build out code in Development Org / Sandbox
8. Build out pages and content in Production