Custom Editors

Build and use custom editors to support your content editors.

How to write your own editor

Custom editors are enabling developers to replace the default editors with HTML5 applications so that the editing experience of the Squidex Web App can be customized.

Technically speaking a UI editor lives in a sandboxed iframe,which interacts with the web application through a small SDK using messaging. This SDK is a proxy of the Angular ControlValueAccessor, without having the dependencies to Angular itself.

Define Editor URL

Lets see how the code looks like:

<!DOCTYPE html>
<meta charset="utf-8">
<!-- Load the editor sdk from the local folder or -->
<script src="editor-sdk.js"></script>
<script src=""></script>
.ck-editor__editable {
min-height: 250px;
<textarea name="content" id="editor"></textarea>
var element = document.getElementById('editor');
.catch(error => {
.then(editor => {
// When the field is instantiated it notified the UI that it has been loaded.
var field = new SquidexFormField();
// Handle the value change event and set the text to the editor.
field.onValueChanged(function (value) {
if (value) {
// Disable the editor when it should be disabled.
field.onDisabled(function (disabled) {
editor.set('isReadOnly', disabled);
editor.model.document.on('change', function () {
var data = editor.getData();
// Notify the UI that the value has been changed. Will be used to trigger validation.
editor.ui.focusTracker.on('change:isFocused', function (event, name, isFocused) {
if (!isFocused) {
// Notify the UI that the value has been touched.

You just have to reference the editor SDK and handle the events. You also have to push the current value to the web application whenever it changes. Validation will happen automatically then.


The SquidexFormField class is the entry point to your editor.

Create a new instance when your editor is initialized.





Gets the current value of the field.


Gets the current context information. More about that later.


Gets the current value of the content form. Can be used to access the values of other fields.


Get the language of the field editor. If the field is not localized the master language is passed through.


Get the current disabled state of the field form. Disabled (true) or Enabled (false).


Get the current fullscreen state of the field form. Fullscreen on (true) or off (false).


Notifies the control container that the editor has been touched, must be called when your custom editor looses the focus.


Cleanup the editor. Usually it is not needed to call this method.


Register a function that is invoked when the messaging communication with the management UI is established. After the callback is invoked you get retrieve values with the get methods. The context object will be passed to the callback.


Register a function that is invoked whenever the editor should either be enabled or disabled. A boolean value will be passed with either true (disabled) or false (enabled).


Register a function that is invoked whenever the value of the field has changed. The value will be passed to the callback as argument.


Register a function that is invoked whenever the value of the content form has changed. The value will be passed to the callback as argument.


Register a function that is invoked whenever the language of the field is changed, because in same cases the editor is shared between languages. If the field is not localized the master language is passed through.


Register a function that is invoked whenever the fullscreen mode is changed. The function has one argument with the the fullscreen mode.


Navigates the Management UI to a new URL. Because the plugin is integrated as an iframe, you cannot use normal links as it would only change the URL within the iframe and not the URL of the Management UI.


Toggle the fullscreen mode and sends the current state to the management UI. The field editor is destroyed and recreated because it has to be moved inside the DOM. Therefore onInit is invoked again.


The context object contains application information, such as the username and access token.


"user": {
"user": {
"id_token": "TOKEN",
"session_state": "TOKEN",
"access_token": "TOKEN", // Access Token
"token_type": "Bearer", // Access Token Type
"scope": "openid profile email squidex-profile role permissions squidex-api",
"profile": {
"s_hash": "Wn3eHEjfi65aLx-KioJ53g",
"sid": "-S7htcpBlnhNKfBXLhl1rg",
"sub": "5dc32104ebc77a363cca0e0c", // User Id
"auth_time": 1573240790,
"idp": "Google",
"amr": [
"urn:squidex:name": "USERNAME",
"urn:squidex:picture": "URL",
"urn:squidex:permissions": "squidex.admin.*",
"email": "",
"email_verified": false
"expires_at": 1573405262
"apiUrl": "http://localhost:5000/api",
"appName": "my-app"

You can use apiUrl, access_token and token_type to retrieve additional information from the API, for example when you build a special editor to manage references or assets.

Example editors

Squidex contains a few example editors that can help you to understand the flow, for example:

All Examples

Also, we have more example you can use them on your apps.

1. Simple CKE Editor


CKE Editor

Clone the sample and configure the CKE editor as you need it.

2. Country selector


Country Selector

3. Product taxonomy


The data format is a list of URL like paths for each product category that will be converted to a tree structure.

Product taxonomy

4. JSON Tree


Create a visual tree for a JSON object.


5. JSON Schema Editor


This editor downloads json schema from the URL that is defined via the URL fragment (everything after #):

JSON Schema from external URL