·¬ÇÑÉçÇø

Brightspot CMS User Guide

Understanding the importation of external assets


Some Brightspot integrations give you access to external assets, typically images and videos. You can import those assets into Brightspot, and then include them in parent assets such as articles and galleries. The following sections describe the differences between importing videos and images.

Importing external videos

When you import a video, you typically retrieve the title, description, and other metadata as available. You do not retrieve the actual video. There are two implications to this architecture:

  • The metadata (such as title and description) are now local to Brightspot. You can modify the metadata in Brightspot, and those changes are not sent to the video provider. Similarly, a change to the metadata on the service provider is not automatically imported into Brightspot.
  • Brightspot renders the video from the service provider's server. If someone updates the video, Brightspot uses the new copy.

Example

Olivia is creating an article about filing for a patent. For the article's lead, she found a nice video on YouTube.

YouTube video import YouTube video import
YouTube video import


When Olivia clicks Import, Brightspot retrieves the video's title, description, thumbnail, ID number, and other metadata. At this point, Olivia can modify some of the metadata within Brightspot; those changes do not carry back to YouTube. Furthermore, any changes to the metadata within YouTube are not automatically imported into Brightspot.

Olivia then completes her article about patents, adds the lead video, and publishes. A visitor to the article sees content rendered from two sources: Brightspot and YouTube.

Rendering an external video Rendering an external video
Rendering an external video

Synchronization with external images

When you import an external image, you retrieve the title, caption, other metadata as available, and the image itself. After you import the image, you can modify any part of it (title, caption, image, and any other field in an image). These modifications are local to Brightspot, and are not communicated back to the image provider. Similarly, a change to the image on the service provider is not automatically imported into Brightspot.

Example

Adam is creating an article about space exploration. For the article's lead, he found a nice image of a space shuttle launch on Getty Images.

Getty Image import Getty Image import
Getty Image import

When Adam clicks Import, Brightspot retrieves the image and associated metadata. At this point, Adam can modify any part of the image; those changes do not carry back to Getty Images. Furthermore, any changes to the image within Getty Images are not imported into Brightspot.

Adam then completes his article about space exploration, adds the lead image, and publishes. A visitor to the article sees content rendered from Brightspot.

Rendering an imported image Rendering an imported image
Rendering an imported image

Previous Topic
Performing integrated searches in Brightspot
Next Topic
User settings
Was this topic helpful?
Thanks for your feedback.
Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

•
•
•
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

• Content types
• Modules
• Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

• Dashboards
• Publishing
• Workflows
• Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

• Field types
• Content modeling
• Rich-text elements
• Images
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

• Google Analytics
• Shopify
• Apple News