Content and Experience Cloud - Component, Template, Theme and Content Layout Development
To learn about developing components for Content and Experience Cloud, see the links below:
Test to Production – Use the OCE toolkit for Test to Production
- Make sure
npmare in your
PATH. Use NodeJS 8.0.0 or later.
- Download the OCE Toolkit - e.g. from GitHub - link
- Install the dependencies
cd <download-path>/content-and-experience-toolkit/sites npm install
cecon your path:
sudo ln -s $PWD/content-and-experience-toolkit/sites/node_modules/.bin/cec /usr/local/bin/cec
SystemPropertiesAdvanced.exe, edit Environment Variables and add
<your download path>\content-and-experience-toolkit\sites\node_modules\.bin to the
PATH variable, replacing
<your download path> as appropriate.
- Run the command line utility
cecto get help about the commands.
Create an initial
Create an initial src directory in any location on your local file system to contain your CEC source.
package.json some dependencies, and src will be created. You can use this a your starting point for CEC source and dependency inclusion.
mkdir cec-src cd cec-src cec install
- Start the local test harness to allow disconnected development of components, themes, templates, and content layouts:
the runtime test harness can be accessed from the browser using address: http://localhost:8085
Your components, themes, templates, layouts can all be found in
Using a Content and Experience Cloud instance for local testing
The CEC instance can be used for the following things:
- Testing components like Sample-File-List which access content
- Generating Content Layouts from content types stored in CEC
- Rendering Content Layouts using content from CEC
- Exporting and Importing templates, and components from / to CEC into local file system
The steps are as follows:
cec.propertiesfile to point to your CEC instance. Note for internal compute CEC instances, use
cec_url=https://<documents-hostname>:443 cec_username=your.username cec_password=your.password cec_env=pod_ec
cec.properties file will be loaded from your current working directory. Alternatively, you can use an environment variable to specify the location. E.g.:
# optional export CEC_PROPERTIES=~/my.properties