Tags are a way for content teams to add additional metadata to an asset, and they can be used in two ways:

  • A tag can be applied to assets.
  • A tag can be its own page that lists associated assets.

Tags are a useful way to group content both internally and externally. If you want to use a tag to only group content internally, you may opt to hide the tag from public pages and modules.

To create a tag:

  1. In the header, click add.
  2. From the Create list, select Tag. A blank content edit page appears.
  3. In the Display Name field, enter the tag’s title.
  4. In the Internal Name field, enter a label Brightspot uses for the tag in widgets (or retain the default, which is populated from the Display Name field).
  5. In the Description field, enter the tag’s description.

    Tag example.png

  6. If you are creating a hierarchy of tags, from the Parent selection field, select a parent tag. If the parent tag is not listed, do the following:
    1. Click search to open a content picker.
    2. Search for an existing tag or, from the Create widget, click New Tag to create a new one. You return to the content edit form.
  7. Toggle on Hidden to hide the tag on all public pages.
  8. Under Lead, select Page Heading (or retain the default None value). For more information, see Page headings.
    1. Under Content, click into the selection field and choose one of the following (or retain the default Inherit value):
    2. Repeat to include additional items.
    3. Complete your site’s workflow and publish the tag.
    4. As necessary, add associated content to this asset. For details, see Creating associated content.
    The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

    Content types
    Landing pages
    Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

    Admin configurations
    A guide for installing, supporting and administering code on the Brightspot platform, including integrations requiring developer support to use.

    Field types
    Content modeling
    Rich-text elements