Configuring OS2Loop

All OS2Loop settings can be found Administration › Configuration › OS2Loop (/admin/config/os2loop).

After installing OS2Loop you should run through all the module settings below and make sure that everything is set up as needed.

The basic idea behind site configuration of OS2Loop is that all available OS2Loop modules (and their dependencies) are installed and all have reasonable standard configuration. Using the settings outlines below some tweaks to the default configuration can be made.

Important post-installation configuration

Right after installing OS2Loop, go to /admin/config/os2loop/settings and define the site name, email address and front page url. Also decide on which content types and taxonomies should be available for use on the site.

Taxonomies

In order to make the media library work, go to /admin/structure/taxonomy/manage/os2loop_media_library/overview and define the media categories for the site.

Go to /admin/structure/taxonomy and make sure that the Profession and Subject taxonomies contain the terms needed for the content. Users can dynamically create new terms in the Tag taxonomy, but any default terms can be added if needed.

All taxonomy terms are added and edited on /admin/structure/taxonomy

Category: Is used for overall grouping of content e.g. "Vejledning" or "Instruks"
Subject: Is used for grouping content related to similar themes (subjects) e.g. "Support" or "Administration".
Tags: Is used as inspirational words for similar content e.g. "Ernæringsindsats" or "Hjælpemidler". As opposed to the other taxonomy terms these can also be defined by end users when submitting questions and/or answers.

Menu items

By default the main menu contains only one item, the user menu, but any new items (and sub-items) can be created on Administration > Structure > Menus (/admin/structure/menu) by editing “Main navigation” and adding menu items.

Technical details

Behind the scenes the configuration for all modules is stored in (and may be imported from) the config/sync folder and the Config Ignore module is used to prevent overwriting site specific configurations when updating the OS2Loop core.