Organizing content templates
Brightspot organizes content templates using a hierarchy from the site, then role, and then user levels. When a user opens the dashboard, Brightspot examines the user's ID, role ID (if any), and the site the user is working on. Brightspot then looks for content templates matching those criteria, and adds them to the Quick Start widget. Below are some examples.
- All editors working on the site
Brightspotcan write articles highlighting software features. Using a site-level content template, they can pre-populate their articles' headlines with an introductory phraseFeature review.
Feature review template (applied at site level) - A special group of editors covers the company's annual user conference. For those articles, they use the role
Reporteron theBrightspotsite, and, using a role-level content template, pre-populate their articles' headlines with an introductory phraseSession summary.
Session summary template (applied at site and role level) - Olivia is the only editor providing code samples on the developer site
API Reference. For those articles, she uses a user-level content template to pre-populate her articles' headlines with an introductory phraseCode sample.
Code sample template (applied at site level and user)
The following diagram illustrates the logic Brightspot uses to determine which content templates are available in the previous scenarios.
These examples show how you can design content templates in a wide variety of combinations:
- Any user working on a specific site.
- Any user working in a specific role.
- Any user working in a site-role combination.
- A specific user working on a specific site.
- A specific user working in a specific role.
- A specific user working on any site or role.
Think about how your publications re-use text at different combinations of sites, roles, and users, and design content templates to pre-populate your assets accordingly.
See also: