Configuration files
See the info in the Configuration file
A Writer without the plugins is a very empty area in your web browser. So in order to get a working envirnment you need plugins of different kind. The plugins are configured to get the Writer functionality and specializations that are needed in different workflows.
Writer + Writer Plugins = Installation
The Writer and plugin configuration can bee inspected via the Writer's endpoint, via the API. To show the configuration file in your browser you should add /api/config to the Writer's URL.
As stated many times now, almost everything you see in Writer is run with plugins and the plugins are configured with the json-file: Xxxx-writer-config.json. A Json formatter makes the reading of the file easier (more admin guiding here). That may be down-loaded to the web browser as an Add-on.
The unique name of the plugins are written in this format, on the first line under "plugins" “id”: “se.infomaker.archivesearch” to be followed by next plugin “id”: “se.infomaker.contentrelations” etc.
More details of the different sorts of plugins and how to understand the anatomy of the different plugins is clearly described in the section Plugin overview, that is a part of the developer guide. If you think of how to read the configure, you can get help in this section.
Other important configuration files
There are also Imageflow and Serversetting config files, besides the writer-config.json-file, that are configured in the setup of the Writer environment. The configuration files are all stored in the installation in AWS. The writer-config.json file is possible for Naviga setup admins and customer admins to change. The Imageflow and Serversettings are configured by Naviga devops.
Last updated