FirstSpirit Tagging Editor

(FS_TAGGING)

Fragments and variants are created and managed regardless of context (e.g., a website or navigation structure) (see Fragments: from fixed structures to modular content).

Instead, tags are used to organize and sort fragments and variants (regardless of a navigation or folder structure) based on specific topics. Tags are additional information that is saved on a variant. For example, instead of storing all variants relating to “FirstSpirit” in a specific folder, it is sufficient to give the corresponding variants the “firstspirit” tag. The tagged content is then extremely easy to filter later on using FragmentCreator, no matter where it is located.

Tags are created and edited in FragmentCreator via the FS_TAGGING input component.

The component is not a standard FirstSpirit input component and therefore has to be installed separately via a module (.fsm). Installation using the ServerManager is described here.

Module file

tagging-editor-[version].fsm

Installing the module

The module is installed using the FirstSpirit ServerManager, in the “Server properties / Modules” dialog using the “Install” button:

(For more information about installing modules, see also Modules (→Documentation for Administrators).)

Use in projects

Once the module has been installed successfully, the input component can be used in all fragment projects on this server. The input component must be added in the form area of the page template for this purpose. The input component is normally used in the metadata template.

In order to be able to use the input component in ContentCreator, the “FS_TAGGING for ContentCreator” web component must be added to the relevant project in the “ContentCreator” area (“FirstSpirit ServerManager / Project properties / Web components”):

(For more information on configuring web components, see also Web components (→Documentation for Administrators).)

For general information on FirstSpirit standard input components, see BUTTON (→FirstSpirit Online Documentation).

For information on configuring the input component in the project, see FS_TAGGING configuration.

FS_TAGGING restrictions

Restrictions when using the FS_TAGGING input component:

• Not released for SiteArchitect:
  The input component is not (yet) released for use in SiteArchitect.
• No language-dependent content:
  The input component does not support any language-dependent content within FragmentCreator; the useLanguages parameter must be set to no (... useLanguages="no"...).