Glossary

A row or column of links for sharing an asset.

A relationship a visitor creates with an asset. Examples of affinities include the following:

• Visitor follows an asset
• Visitor bookmarks an asset
• Visitor shares an asset
• Visitor purchases an asset

Archiving has two effects:

• If the content has a URL, archiving removes the URL from the published site so visitors can no longer view it.
• Removes the content from search results within Brightspot so editors can no longer reference it on another page, asset or module.

You can restore or permanently delete archived content. For details, see Archiving and deleting content.

A piece of content, such as an article, image, or video. Assets can also be components of other assets—an author can be an asset that is part of an article. You can see the types of assets you can create by opening the Create list in the search panel. An asset can also be referred to as an item.

A request for items associated with a pitch. Assignments often have a lead editor, an assignee generating the content, and a due date.

A group of visitors to which tailored content can be delivered at specified times to specified devices.

A schedule that includes the earliest date and time when all of an editor’s new and modified content will be published.

A utility for determining all classes in the code base based on their Java hierarchy or inheritance.

The Styleguide component that generates Java interface files for the view from template and JSON files.

A group of assets. Actions on multiple assets such as archiving, sharing, and opening work streams are often easier to do with Collections.

The widget for picking a color's hex value in Brightspot CMS.

Component of a Tomcat configuration entry that identifies a configuration. The configuration key is typically the third component of a path. The following illustration is an example of a configuration key for Storage Items. The configuration key for databases and image editors is in a similar format.

A network architecture that delivers content from a server that is geographically close to a visitor. When you publish an item in Brightspot, the item may be stored on various servers to ensure rapid delivery to all your visitors.

Area of the content edit page where editors develop content. A content edit form typically consists of several fields, and can vary depending on the content type.

The content edit page contains the forms, widgets, and editorial toolbar for developing, managing, and publishing content. The available widgets can vary depending on the content type.

A widget opened from a selection field that displays assets that you can select for the list. For example, the content edit form for an article may have a field for selecting an author. When you click the author field, Brightspot displays a content picker listing the existing authors you can select.

A search for assets in Brightspot. You perform content searches in the search panel.

A mechanism for automatically populating a Content Edit Form for a given content type. For example, you can create a content template that automatically populates an article’s headline, body text, and image. You can define content templates at the role level, user level, and site-specific combinations for roles and users.

A type of content, such as article, image, blog, or video.

The process of rendering content differently depending on a template’s context. For example, Brightspot can render an author’s image one way in the context of a bio page, and a different way in the context of a byline on an article’s page.

An object persistence library and data-modeling tool used to build complex content types and persist them to one or more databases. Dari enables developers to query databases, as well as to create and modify custom data structures from within the same access layer. For example, a data model can be altered by modifying the Java classes that define it, without regard to database schema or other configurations.

A Dari tool that keeps track of all events that occur within a specific time frame.

The top-level Brightspot page containing links for managing content, work streams, and scheduled events. The dashboard is the landing page users see after logging in to Brightspot. Developers can customize the dashboard to fit an organization’s needs. The following image is an example of a typical dashboard; your version of Brightspot may have a different dashboard.

The URL Brightspot uses when sending notifications that include links, such as emails or text messages. Default tool URLs are often similar to the URLs for published content. For example, if published content appears at http://www.neanderthalrecipes.com/, the corresponding default tool URL may be http://editors.neanderthalrecipes.com/.

The method by which Brightspot delivers a subscription’s messages. Brightspot can send messages through the browser, email, Slack, and text messaging.

In the editorial context, a dictionary is a list of names, technical terms, acronyms, or other nomenclature that you do not want to be flagged as spelling errors.

In the visitor-search context, a dictionary is a list of terms and associated variants. When a visitor searches for a term in the dictionary, Brightspot includes in the search results a spotlight.

A pre-published version of an asset that is labeled with the Draft status in the Revisions Widget. If the asset participates in a Workflow, the workflow status is indicated, for example, Submitted, Approved, or Rejected.

After the initial publication of the draft, all subsequent updates to the asset are revisions, that is, post-published versions.

An Internet-based API for image resizing.

An object field annotated with @Embedded. The object set on the field is then embedded within the containing object.

An object embedded in the rich-text editor, such as media, a promo, pull quote, external content, and many other assets in Brightspot CMS.

A content template that appears as its own content type. For example, if you have a content type Article, you can create an extra template Blog Post that has the same structure as Article.

An in-CMS search of a third-party content provider, such as Getty Images.

Configuration settings that apply to all users of a Brightspot application, unless some or all of the settings are overridden by a system level that’s of higher precedence than global, for example, Site Settings

A Sub-Navigation that contains groups of Navigation Items.

An item that appears above a published page’s header. Hats are typically very brief messages.

A widget for editing images on the Content Edit Form for editing images.

A database index that enables searching in a Brightspot application. Both fields and methods can be targeted for indexing with the @Indexed annotation.

A method that returns a value and is a target for indexing. Indexing methods is a way to index and query values that are not directly set by users, but are generated from other values stored in an object.

The identifier Brightspot uses to refer to an object.

An asset visitors see typically after a headline and before the body text. Depending on your version of Brightspot, leads can be images, videos, or modules.

A language-region pair that characterizes language, currency symbol, date and time format, and other conventions used in a particular geographical region.

A utility that displays a preview of the item currently in the content edit form. You can use Looking Glass to preview content on different devices.

A template Brightspot uses to generate the body of a notifications. For example, an email message formatter typically specifies the notification’s subject line and the body.

A Dari feature to add new fields to existing classes.

A container for content that supports or supplements the main asset on a page, like an article. There are several types of modules, such as ad, list, promo, and search.

A site logo that complies with width and height restrictions for AMP.

A mechanism for sending messages to editors and administrators when events occur. For example, you can receive notifications when you are mentioned in a conversation or when content is published.

An object associated with only one other object. Examples include the following:

• An editor creates a one-off dashboard; no other editors can use that dashboard.
• An editor assigns a one-off image to an article; no other editor can use that image.

A collection of assets grouped together under a common theme, often for a limited time. Examples include the following:

• Grouping recipes into a Christmas cookies package.
• Grouping pages, articles, and listings into a Fall TV package.
• Grouping articles, slideshows, and videos into an election package.

A subset of query results as specified by a limit and offset. A paginated result prevents all results from being returned at one time and potentially exceeding system memory.

A visibility icon on the Editorial Toolbar that displays the Preview Pane.

A Dari tool for querying single aggregated or multiple SQL and Solr databases.

A widget on the dashboard that provides quick access to creating new content types and editing existing assets.

A component that allows Brightspot to update content as it is edited in real time.

A widget that displays a list of assets containing the current asset. For example, if you are viewing an author in the Content Edit Page, the References widget lists articles written by that author.

A web application that, after changes in a Brightspot source project, automatically rebuilds and redeploys the application.

A post-published version of an asset that, when published, replaces the live version of the asset. Prior to publication, assets are in the draft state.

A widget on the content edit page that lists all current and previous revisions of an asset.

A version of a published asset that will be visible on a website at a future time.

Widget in the content edit page listing results of most recent search. By default, the search carousel is disabled in the Settings for the Global Site.

A collection of episodes organized by a time frame.

A field for selecting an item, either from an abbreviated list or the Content Picker.

Object that can be initialized by Settings.

An object available for use with other objects. Examples include the following:

• An editor creates a shared dashboard; other editors can use that dashboard.
• An editor creates a shared image for an article; other editors can use that image.

A collection of seasons, episodes, or specials that can have a franchise as a parent.

A website to which Brightspot publishes content.

A user-defined category of sites. For example, a medical supplies company could associate its websites with one or more categories, like retail sales, physician offices, and hospitals. A website can belong to more than one category.

An identifier for an asset , typically used in the asset’s permalink. Brightspot automatically generates slugs from an asset’s headline or title.

A Navigation Item that links to a post on a social network.

A Dari feature that enables rapid web application development by making source code changes immediately available.

A video asset that is typically a one-off production of a show.

A promo associated with a search term. Brightspot displays the spotlight when displaying results for the search term.

An asset that provides authentication settings for visitors to log in to your site.

A module that provides the most recently available stock price from a specified listing exchange.

File-based data in a Brightspot application that is referenced by objects persisted to the database.

A tool for building a library of front end components for Brightspot applications.

In the editorial context, a visitor who has a login to a site. Subscribers typically log in with a username and password, or with a social networking account. Traditionally, subscribers have access to extended content and site features compared to other visitors.

A combination of topic and delivery method. Brightspot periodically runs a job that delivers a topic’s messages to subscribers using the requested delivery method.

A data source for a report, typically isolated for a specific event. For example, a page-view supplier is a data source containing a log of visitors’ page views.

A palette of seven colors recommended by a site designer to use in a publication.

A collection of layouts, color schemes, animations, and image sizes.

Protocol and domain name editors use to access Brightspot, such as http://editors.brightspot.com/.

A menu of actions available for an asset on the content edit page. To display the tools menu, click settings on the Editorial Toolbar. The available actions depend on the state of the asset version (draft, revision, live) that is currently selected.

A widget providing miscellaneous information and settings for editors, and technical information for developers. To open the widget, click Tools on the Tools Menu.

The unique ID assigned to a class stored in the database.

A widget in the content edit page listing an asset’s URLs. Clicking a link in this widget opens the asset (if published) in your web browser.

The Brightspot mechanism for associating back-end model classes with front-end components.

The Brightspot component that generates Java interface files from front end files created in the Styleguide.

The class that binds a model to a view. It receives raw data from the model and transforms that data to produce a view.

The Brightspot system that controls presentation of data on the front end.

An editor who opened an asset in the content edit page.

A graph showing the frequency of a video’s percent completion as watched by visitors.

In the previous illustration, approximately 43,000 visitors watched the first 10 percent of a video, and approximately 4,000 visitors watched the entire video.

A component of a Brightspot page that provides links or fields for entering, viewing, and updating information. The following image is an example of the Recent Activity widget.

A widget for navigating through the steps of a workflow. To open the widget, click Workflow on the Editorial toolbar.

An assignment for one or more assets. For example, an editor can create a work stream to fact-check a group of articles, and then assign that work stream to the copy-edit department.