Documentation Center

Embed Xopus in your system

There are three different ways to embed this editor in your system.

There are three ways to embed SDL LiveContent Create in to your system:
  • Keep SDL LiveContent Create in a persistent iframe.
  • Wrap SDL LiveContent Create around the whole site.
  • Let SDL LiveContent Create take control over a single webpage.

Persistent iframe

A persistent iframe gives you the best way to communicate with SDL LiveContent Create . You can load new documents for example, using Editor.setURL(href); from the JavaScript API.

This kind of implementation also allows SDL LiveContent Create to cache schema files, which speeds up the startup time for documents that use the same schema. It doesn’t mean that the whole site is editable. Only the part that you define as editable will be editable. This part is the ‘island’.

Wrap around a website

By placing SDL LiveContent Create around the site you also have a lot of control and access to SDL LiveContent Create but clients can get confused about what software they are working with. We sometimes hear from clients that don’t realize what software they work with. This works best for situations where authors only need to edit text in a website with little or no extra functionality.

Single webpage

By placing SDL LiveContent Create on its own webpage, you will most likely be restarting SDL LiveContent Create for every loaded document. This may make the whole editing experience slow.