Customize web content delivery
Although web content viewers and page templates provide the basis for delivering web content, we can customize the environment to provide users with a better experience.
For example, we can create custom objects like page templates and web content viewers. We can also provide users with conveniences like customized error messages and friendly URLs that reference web content.
- Create web content page templates
Create web content page templates to quickly deploy new pages containing web content. With a template, we can define the layout and presentation of the page, including adding web content viewers configured to render web content.
- Add predefined web content to the customization shelf
To make web content easier to find, the customization shelf provides categories to organize components that we can add, such as portlets, iWidgets, and web content. By default, the Web Content category includes four sample content items, but we can also add the own content to the Web Content category.
- Customize error messages for web content viewers
If an error occurs during rendering, the web content viewer shows an error screen. We can customize the default error screen, and we can create the own custom JSP file used to display error messages.
- Friendly URLs and web content viewers
Friendly URLs provide a way for you to define a custom address for a portal page that is easy to remember and share. The web content viewer expands on friendly URL support by enabling you to specify additional path information in the friendly URL.
- Set up a web content fallback page
Set up a web content fallback page to be used when a web content viewer cannot determine which page to use to display a content item. The fallback page can also be used when users do not have sufficient privileges to view the page originally associated with the content item.
- Enable page-based access control for web content pages
Typically, when you render content items in a web content viewer, access control enforcement on those content items is handled by Web Content Manager. However, we can use page-based access control to delegate access control enforcement to the web content page used to display the content.
- Previewing content on web content pages
When working with content in the authoring portlet, we can preview content items in a portal environment as part of a web content page. To preview content items, there must be a web content viewer on the associated web content page, and the viewer must be configured to receive links.
- Add HTML meta tags for Search Engine Optimization
Search engine optimization (SEO) focuses on improving the visibility of a page or website in search engine results. A basic technique of SEO is adding HTML title and meta tags to the page source. These meta tags are used to define keywords and other metadata that search engines and crawlers can use when creating search indexes and collections. When including content in a page with a web content viewer, we can improve the SEO of the page by adding title and meta tags with values derived from the web content itself.