Content Items enable you to create any type of user-facing content. They are not by default forms which require the user to submit information or take an action, though they can be coded to behave as such. (Image 1)
Content items' potential uses are as manifold as the potential pages on your web site. Some of the more common uses in the Salsa community include:
Configuring a Salsa content item is a simple three-step process, described below. You'll also notice a box in the corner of the screen (Image 2), which enables you to:
Throughout Salsa, Reference Name fields provide an internal reference for you to identify the page; it is not shown on the user-facing pages.
The public name of the event will appear as a banner headline atop the page (in h2 HTML style). This will also set the HTML "title" element of the web page, meaning that the name you place here will generally appear as the page's name in most browser tabs or panes.
You won't see the "Status" selector when you initially create a Content page.
After you've saved the page, however, you have the additional option to set your Content page to Active, Inactive, or Archived.
Pages set to Inactive or Archived (currently, those two statuses are synonymous) no longer display their content to end-users who might follow the View Page link you've published. Instead, visitors will see the page's template with no further content. Active pages display their content as usual. (All new pages are Active by default.)
The Status option gives you the ability to "turn off" outdated pages. You might also consider building a special template for use with Inactive/Archived pages that explicitly directs users to other parts of your site.
This field, the "meat" of the content item, appears after the Title, and can be HTML-styled using the WYSIWYG editor, including images, links, and video embeds. At any time, you can click the "Source" button of the WYSIWYG (see Image 4) to access the page's HTML code.
To use content items for advanced customization of other Salsa forms:
You'll need to have some comfort working with HTML (and perhaps CSS) to do this, and you'll need to troubleshoot your own results. Unfortunately, we are generally unable to provide HTML support on custom pages, including customized content items.



