Configurations Guide

General json structure

The Writer and plugins config file is a .json file, so when reading the file an add-on for json-formatting is a good help.

A object in json consists of {"key":"value"} pair. The objects in the config file are separated by curly brackets, the {-sign.

The object can consist of the {"key":"value"} pair in different levels and also of a list of objects. The list are written with the straight brackets[xx]

``

First sections in the config file

{
"newsItemTemplateId": "30eae1c0-c640-4053-b114-05c64e28bbe7",
"language": "en_EN",
"labelLanguage": "en",
"conceptServiceConfig": {
//...   
//...
//...
//...

"propertyMap": {
///
}        
},

“newsitemTemplateId”

From the top of the writer-config.json file you find “newsitemTemplateId”, which stores the article template that is stored in Open Content. There is only one template. The template is presented with a UUID, and can be viewed in Open Content, if you search via the UUID.

Example:

"language"

The "language" and "labellanguage" sets the Writer language for the plugins, not the language to be used when you write the content.

"conceptServiceConfig"

"conceptServiceConfig" is the service for the Concept plugin that sets the configuration for Open Content. The searches in Open Content are run through the BA-proxy and the "PropertyMap"-key sets the Writer property to map Open Contents properties.

Plugin section in the config file

The plugin section contain a list of all the plugins that are included in the Writer setup. To be able to find if a certain plugin/function is included in the configuration, a search in the browser is recommended.

The Link plugin as an example of a simple plugin configuration:

{
    "id": "se.infomaker.link",
    "name": "link",
    "url": "https://plugins.writer.infomaker.io/releases/7.8.5/im-link.js",
    "style": "https://plugins.writer.infomaker.io/releases/7.8.5/im-link.css",
    "enabled": true,
    "mandatory": false
},

Explanation of the keys in the example plugin above.

Id: only uniqe names (if there is duplicates, only the first one will be read, see example below)

Name: name of the plugin

Url: check the plugin version (there can be different versions dev (higher), stage, prod)

Style: the ux for the plugin (please, observe it also follows the version)

Enabled: enable the plugin or not (true or false)

Mandatory: if true, it is a mandatory plugin

Importance of Plugin order

The plugins are listed after each other, in an unspecified order. It is important to notice that the config is read from top to bottom. As they are read from top to bottom the plugin that is read first will be the one that execute a task. If two plugins can do the same operation, the first will do the task. An example is configuration of the Iframely plugin and the social embed plugin, where Iframely then will manage the instagram etc, video etc, instead of the social media embed plugin if that is placed below.

{
    "id": "se.infomaker.ximconcept.story",
    "name": "ximconcept",
    "url": "https://plugins.writer.infomaker.io/releases/7.8.5/im-ximconcept.js?concept=story",
    "style": "https://plugins.writer.infomaker.io/releases/7.8.5/im-ximconcept.css?concept=story",
    "enabled": true,
    "mandatory": false,
    "data": {
        "label": "Story",
        "name": "x-im/story",
        "enableHierarchy": true,
        "editable": true,
        "placeholderText": "Search stories"
    }
},
{
    "id": "se.infomaker.ximconcept.contentprofile",
    "name": "ximconcept",
    "url": "https://plugins.writer.infomaker.io/releases/7.8.5/im-ximconcept.js?concept=contentprofile",
    "style": "https://plugins.writer.infomaker.io/releases/7.8.5/im-ximconcept.css?concept=contentprofile",
    "enabled": true,
    "mandatory": false,
    "data": {
        "label": "Functiontags",
        "name": "x-im/content-profile",
        "enableHierarchy": true,
        "editable": true,
        "placeholderText": "Search functiontags"
        }
},

This is a general configuration guide and each configuration must be tested in a test environment before it is implemented in any production environment.

Configuration details

When you want learn more about config, the user guide is a start. The functions are described for a normal set up of Writer. In most cases the configuration documentation is found in the documentation of each plugin and the Writer User Guide provides you with links to each plugin documentation.

Version dependencies

The Writer version has dependencies to the plugin versions (or vice versa). This dependency is stated in the so called manifest-part of the plugin documentation of each plugin. This must be checked carefully.