In a previous post view briefly went through the Navigation model best practices from a Portal perspective, lets look at the next natural step. The use of the navigation model has two main purposes:
- To enable friendly navigation and memorable links that can be used when cross referencing or for Search Engine Optimizations purposes (even though we still have some work to be done, with aspect of mandatory URL parameters for the ADF control state)
- To generate a predictable user interface where the navigation can automatically decorate the page with accessible navigation links.
This post will go into how to create page templates that leverages the navigation model to render dynamic page links depending on what is in the navigation model, users previous navigation actions and current navigation selections state including navigation parameters.
To minimize complexity and maximize the use of the Oracle WebCenter Portal and Framework, ATEAM recommends that the Page Template follow these simple rules:
- Use ADF Layout managers rather than using HTML DIVs and SPANs
- If the site is a public facing, or you want to enable search engine optimization, ATEAM strongly recommends that the navigation and page links are added using
af:goLink with the navigation model goLinkPrettyUrl method
- Styling, decorative images and geometry should be managed via the CSS style (Skin) framework
- Selection of the Page Templates should be controlled by the Portal framework either through the default template settings in the adf-config.xml, or in the navigation model for each navigation link:
portal:preference id="oracle.webcenter.portalapp.navigation.model" desc="Default Navigation Model" value="/oracle/webcenter/portalapp/navigations/default-navigation-model.xml" resourceType="navigation" display="true"/>
For more information on Page Templates, see following links:
- Introduction – Introduction to the series of posts and what to expect at the end of the series