Using your own content in the Editor

Concept

CHILI Publisher's API consists of three large areas:

• The SOAP WebServices for server to server communication
• The JavaScript bridge for client-side communication
• The possibility to connect to External Data through configuration in BackOffice and Editor

While WebServices and JavaScript definitely are a push-model (where your application tells CHILI what to do and how to behave), the various links to External Data pull in data from an external XML feed (almost always through an HTTP GET command). The URLs themselves can be entered in the relevant areas inside CHILI, and influence the behavior of the interface and logic. Some examples are:

• Pulling in assets from an external asset repository: ?External Assets XML
• Combining snippets with variable data: ?External Snippets XML
• Providing the data for a DataSource: ?External DataSources XML

Security and Context

When embedding an editor in a portal, you get its URL through the ?Webservice Functions - DocumentGetEditorURL call. You can add your own query string variables to this editor URL, which can be referenced in the configured XML URLs: ?External XML URL replacement

Using such (and other) configuraton, you can include setting applying to your currently logged in user, template, customer, ...