You have content created in the Content interface and all ready to publish it on the website that you own. You may be maintaining your website outside of Content.
It does not matter where your website is hosted, Content's rendering feature automatically generates HTML markup for content that is managed in Content. To render the content in your own website:
- Create HTML templates to define the specific markup format that you want to generate for a specific type of content.
- Create layouts and layout mappings to define how to render formatted content in a site. You associate a template to a content type through the layout mappings. Content types are created in Acoustic Content.
- Upload the corresponding rendering templates to Content with the wchtools command-line interface or the public REST API of Content.
The generated HTML documents or fragments are automatically published to the CDN for efficient worldwide delivery.
Now you can reference these rendered web assets through a command-line interface with relative URLs. You can control the URL format for the generated documents and fragments with the URL templates.
Note: If updates are made to the ready versions of your content, the Content auto-publish feature re-renders the updated content to overwrite the rendered content.
You can pre-render parts of your content into HTML documents or fragments that can either directly or indirectly be used on your website or JavaScript applications.
Note: The prerender field in the layout must be set to true for the content to be pre-rendered. By default, the content layout is ignored and the content is not pre-rendered.
For more information on how to manage web assets, layouts, and layout mappings, go to wchtools documentation and the Layout service REST API documentation.