Web Content Assets are used for entering HTML-formatted text or media items. They are created and edited via a mini-WYSIWYG Editor. Web Content Assets support Dependency Manager tags and linking. This type of asset is available across all sites within an account unless Lock to Site is selected. By default, users Level 4 and above can create assets. However, users with custom permissions may also access this screen.
Web Content Mini WYSIWYG Editor
When a user creates or edits a Web Content Asset, a mini-WYSIWYG editor will appear in the Asset Content panel on the asset's configuration screen. Similar to the Page WYSIWYG Editor, this mini editor allows users to insert text or media and create styling options for how each of these elements is displayed. The following tools are available in the Web Content Mini WYSIWYG Editor:
- Cut, Copy, Paste, and Paste as Plain Text: Allows users to Cut, Copy, Paste, or Paste as Plain Text content into the new asset. Mozilla Firefox and Google Chrome disable some of these buttons; if using those browsers, use keyboard shortcuts instead.
- Undo/Redo: Allows users to revert or repeat the last action performed.
- Spell Check: Allows users to perform a spell check in the asset. Clicking the drop-down button will reveal the languages available for spell check.
- Remove Formatting: Removes previously applied formatting to the tune of bold, italic, underline, and strikethrough
- Text Styling Options: Allows users to add bold, italicize, underline, or strike-through styling to contextual strings in the content.
- Insert or Remove List: Creates either a bulleted (unordered) or numbered (ordered) list of the currently selected text.
- Help: Clicking this button will show a guide to the toolbar icons in a pop-up window.
- Increase/Decrease Indent: Increase the spacing at the beginning of a paragraph.
- Create Block Quote: Allows users to create a block quote.
- Alignment: Allows users to select the content's alignment to the margins of the editor.
- Unlink: Remove the selected hyperlink.
- Insert/Edit Image or Media: Allows users to insert and edit images or media by entering the URL, dependency tag, or browsing to the location of the image/media in the file structure.
- Insert Special Character: Provides the dialog for inserting special characters into the asset, which includes the symbol, as well as the entity reference for the character.
- Cleanup Messy Code: Attempts to remove any bad code from the asset.
- Insert Predefined Snippet Content: Allows users to insert snippet content into the asset. For more information, refer to the Snippets page.
- Edit HTML Source: Allows a user to edit the source code of a Web Content Asset. Clicking this option opens a new dialog that displays a text field for entering code. Once finished, clicking the Update button saves the changes and returns the user to the asset configuration screen.
Creating a Web Content Asset
1. Navigate to the Assets list view by selecting Content > Assets from the global navigation bar.
3. Select Web Content from the menu to display the Web Content Asset screen.
4. Fill out the required fields to create the asset. The Asset Content panel is where users will use the mini-WYSIWYG editor to create the asset.
5. After configuring the items click Create.
6. Once the asset has been created, Publish the asset.
Like pages, created and saved assets can be immediately published, scheduled to publish, or sent to user for approval. An unpublished asset can even be inserted onto pages; however, the asset will not render on a page on the production server until it has been published.
Inserting a Web Content Asset onto a Page
Web Content assets are placed on a page either from the WYSIWYG Editor or the Source Editor, just like all other assets. For detailed information about adding an asset to a page, visit the Inserting Assets page.
When a user adds a Web Content Asset to a page, it is usually unavailable for preview in the WYSIWYG editor unless the content contains only plain text. Instead, a grey box is displayed as a placeholder.
In order to view the asset correctly, it must be viewed either on the preview screen or on the live page on the production server after publishing the asset.