A collection of Samples that extend the Authoring interface of Acoustic Content (formerly Watson Content Hub) with custom elements that have custom user interface extensions.
More information: Dropdown Song Selector
More information: Custom Category Selector
More information: Color element
More information: Google Maps Location Selector
More information: Custom CKEditor
More information: Email Address with Validation
More information: HTML Editor on file asset
More information: HTML Editor on text element
Install the latest version of wchtools-cli:
Windows: npm install -g wchtools-cli
Linux/Mac: sudo npm install -g wchtools-cli
Make sure that you have initialized wchtools with your user and tenant API URL using:
wchtools init
You will be prompted for your user password when deploying to the tenant. For more information, refer to https://github.com/acoustic-content-samples/wchtools-cli.
To install all the custom element user interface extensions, run:
chmod 777 ./install.sh
./install.sh
Enter you password at the prompts.
To create you own Custom elements with custom user interface extensions, copy the patterns shown in the samples.
Include the JavaScript library for the UI extensions in your index.html using:
<script src="https://content-eu.goacoustic.com/auth/acoustic-content-ui-extensions.js"></script>or
<script src="https://content-us.goacoustic.com/auth/acoustic-content-ui-extensions.js"></script>NOTE: For Acoustic Content developers - If testing UI extensions on an internal environment, the above URL should be modified to point to the correct domain:
<script src="https://<Acoustic Content Domain>/auth/acoustic-content-ui-extensions.js"></script>For information on how to use the JavaScript library, see https://www.npmjs.com/package/@acoustic-content/ui-extensions.
Write your Custom UI and push the assets into the hub, as per the above instructions for the samples. Finally, enable the Custom UI in the content type that is using it, again, as shown in the samples.
Whilst developing Customer user interfaces, we do not recommend that you push the user interface to the hub each time that you make an updates. A much faster way to run/testing/debugging your Custom UI is to run the Custom user interface extension locally (ie on localhost), and point the element in the Acoustic Content Authoring UI at the UI extension running on your localhost. To do this, follow these steps:
First create a self-signed certificate and fill in the given details:
openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem
Install http-server from npm and serve your files locally
npm install http-server -g
http-server <path> -p 3000 -S -C cert.pem -o
For example:
http-server content-artifacts/assets -p 3000 -S -C cert.pem -o
This will allow you to point to the custom user interface extension using the following url:
https://localhost:3000/dxauth/ui-extension-<extension_name>/index.html
For example:
https://localhost:3000/dxauth/ui-extension-email/index.html
Enter this URL in the Acoustic Content Authoring UI for the element for which wish to use a custom UI.
When you have completed development, push the custom UI files to the hub for final testing and use. The web files in the hub are cached by Akamai for 10 minutes, so you will not see these updates appear in the Acoustic Content Authoring UI for 10 minutes after they are pushed.
We have also developed a toolkit that provides a mock of the Acoustic Content Authoring Custom user interface extension environment that runs locally. The use of the toolkit is optional - use it only if you find it helpful. It allows a developer to write their extension, configure the input, inspect the output and test it in a local web page on their computer. In this way, an extension can be developer and tested without the requirement for a localhost server or pushing the files to a Acoustic Content hub. This can be accessed via the following link: UI Extension development toolkit. When development and testing of the custom UI extension is complete, the files can then be run from localhost as described above, and then push the files to the Acoustic Content hub for final testing and use.