Creating Custom Templates

OrchestraCMS content templates for use with the Lightning components can be created in one of two ways:

Content Template Creator

Any account defined as an OrchestraCMS Administrator can use the Content Template Creator (CTC), a GUI interface to create the editor interface and the rendering markup for content templates.  All content templates created with the CTC can be authored, edited and loaded by the OrchestraCMS Lightning components. 

More information on the CTC can be found in the Content Template Creator Guide found here.

Lightning Components

Content templates created with the CTC are static markup. No Apex or Lightning logic can be included.  To extend a content template to use your own code, you can develop separate Lightning components for both the rendering and/or authoring/editing of content.  To use your own code, after you have created your own lightning components following the guidelines given, you can create or edit a Content Layout record in Salesforce to use that code.  The Content Layout record would require the fields to be setup as listed:

Name (cms__Name__c): The name you want to use for the content template.

Label (cms__label__c): The label you want content editors/authors to see for the content template.

Component Name (cms__Component_Name__c): The name of the Lightning component that will be used as the editor interface for content authors. Only required if not using CTC created content template.

Visualforce Edit (cms__Visualforce_Edit__c): The value LightningOutContentEditor. This is only required if the content template was not created with the Content Template Creator.

Visualforce View (cms__Visualforce_View__c): The name of the Lightning component used to provide the rendering for the content template.

Render Context (cms__Render_Context__c): Needs to be include the value LIGHTNING in order to use the content template in a Lightning environment.