Brightspot CMS Developer Guide

File Storage


Most high-profile websites deliver binary files to the client, such as graphics, video, audio, and PDFs. Regardless of the file type, the minimal HTML pattern for delivering the files is one of the following:

<!-- internal image, video, or audio file -->
<img src="url-to-image.png" />
<video src="url-to-video.mpeg" />
<audio src="url-to-audio.mp3" />

<!-- external file -->
<a href="url-to-spec.pdf">Download the specification"</a>

(There are other attributes for the <img><video><audio>, and <a> tags.)

In the first three cases, the client renders or plays the media within the web page; in the last case, the client downloads the file external to the web page. In either case, at a minimum the client must receive the file’s URL, and the file must exist in the location implied by the URL. Through Interface StorageItem and associated interfaces and classes, Dari provides high-level functions for maintaining file URLs and locations, as well as other functions for file processing.

Previous Topic
Alterations
Next Topic
Creating StorageItems
Was this topic helpful?
Thanks for your feedback.
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
Modules
Landing pages
Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

Dashboards
Authoring content
Workflows
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
Images