In the last post I gave you a small tour how you can create your context-aware configuration. And you always used CRXDE Lite to do changes on your configuration. Which is ok for testing and during development, but as this configuration is made to be changed (otherwise we might have put it into OSGI, do you remember?), we need to provide a better way to do it. Something suited also for less-technical users.
Steffen Seifert (of the Adobe partner Pro!Vision) started the project wcm.io and contributed there a lot of interesting stuff and extensions for AEM. And they also developed an editor for CA-Config (http://wcm.io/caconfig/editor/index.html).
Ok, so let’s use it. The integration is very simple:
- Add the dependency to the io.wcm.caconfig.editor.page package and add it as subpackage to your ui.apps package.
- Add a static template which uses “wcm-io/caconfig/editor/components/page/editor” as resourceType.
- And use this template.
(I added these steps to my github example code at https://github.com/joerghoh/cqdump/tree/master/ca-config-example).
When you open this page at /content/ca-config/en/configuration.html, you see all available configurations for this bucket and when you click on the configuration you can edit it (including saving back to the correct location in the repository).
Cases like “the user does not have the permission to write this configuration” are also handled gracefully.
So the WCM.io configuration editor gives you a nice way to let users edit configuration without using CRXDE Light.
In the next blog post I want to introduce configuration inheritance which can help you to reduce the amount of configuration work.