Extending the User Interface
It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired workflow. Chances are that it gets it mostly right. But it's also very likely that as you use Cloud CMS, you may find places where wish you could extend or adjust the configuration of screens, layouts, controls and other things.
Similarly, Cloud CMS lets you configure the user interface entirely via JSON. Using our client-side JSON configuration service, your custom extensions can register and override new JSON blocks to reset the order of menus, show or hide pages based on roles, turn on and off buttons based on user rights and authorities and much more. Once again, no server side changes required.
Register your Add-On
Note: To register your add-on, you must have Manager rights to your tenant. If you do not have Manager rights, you will either need to delegate the responsibility to someone who does or ask to be granted Manager rights by the person who set up your tenant.
Log in to your Cloud CMS tenant. Go to on Platform Settings and then select Modules from the submenu. You shouldn't see any modules listed if you haven't done this before.
Click on Register New Module. A dialog will appear like this:
Enter the required fields. The ID should match the ID of your module within source control. Provide
the GitHub (or BitBucket) URL for your module source code. If your module lives under a directory within
the root of the checkout, you can provide that path as well. Finally, provide a branch ID if you would
like to have your code checked out from a branch other than
For the Sample Add-On, we would do something like this:
Then click on Register. You will then see your add-on module listed.
Select your Add-on from the list and click on Deploy.
Cloud CMS, in all of its courtesy, will ask if you're sure you want to deploy the module.
Click Deploy to confirm. Your source code will be checked out and deployed to the Cloud CMS user interface.
The Cloud CMS user interface will reload and your AMD module will be loaded after the main Cloud CMS modules are loaded. As such, your AMD module has the ability to extend and override any configuration or components on the page, ahead of them being rendered.
The modules list will now show that your module is deployed.
Now click in a Project. You will see a new menu option on the left-hand side called Products:
Clicking on Products page will bring up a list of the
catalog:product instances in your Sample
Additional sample modules are available within the Cloud CMS SDK.
Use these as a basis for building out your own custom modules.