Warning: Declaration of WarpMenuWalker::start_lvl(&$output, $depth) should be compatible with Walker_Nav_Menu::start_lvl(&$output, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::end_lvl(&$output, $depth) should be compatible with Walker_Nav_Menu::end_lvl(&$output, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::start_el(&$output, $item, $depth, $args) should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = Array, $id = 0) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::end_el(&$output, $item, $depth) should be compatible with Walker_Nav_Menu::end_el(&$output, $item, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678
Denis Stadler – SharePoint & Dynamics CRM Consultant » Built-in Publishing Page Layouts Examples

Built-in Publishing Page Layouts Examples

Written by Denis Stadler on . Posted in Publishing Feature, SharePoint 2010

When you create a publishing page, among the default page layouts you can find many layouts, from which the following layouts are bounded to the Article Page content type: Body Only, Image on Left, Image on Right, Summary links.

The Article Page Content Type inherits the Page content type and has the following specific fields:

  • Page Image – Publishing Image
  • Page Content – Publishing HTML
  • Summary Links – Summary Links
  • Byline – Single line of text
  • Article Date – Date and Time
  • Image Caption – Publishing HTML

These fields can be used to store the page related data (information, picture, links etc) offering two major advantages compared to a standard HTML page:

  • The information is “normalized” – even if this term is more common to the database design rather web pages. I would like to point that the main advantages of structuring the page information in this way are: the logical structure of the information and accessibility from search (for example you can define a search scope to filter the information based on the Byline – Author filed)
  • Standard page design

Now, let’s see how are these fields mapped in some layout examples:

Article Page – Image on Left

Let’s take a look at the same page in edit mode in the picture below.

You can see that this page layout uses the following fields: Page Image, Page Content, Byline, Article Date, Image Caption, Rollup Image.

Even if the Rollup Image  is not displayed in the page’s body, it is used by default by a Content Query Web Part (CQWP) displaying an item collection which includes this page.

Image on Right

This layout look almost identical with the previous one, the only difference is made by the picture’s positioning.

Summary links

In this layout the Page Image and Image Caption fields are removed but instead of the picture we can find the Summary links field which gives us the possibility to add links to other web sites.

Please take a took at the following articles which are related to the current topic:

Tags: , ,

Trackback from your site.

Denis Stadler

I'm a technology enthusiast, with more than 10 years of experience in SharePoint and Dynamics CRM projects. To find more details about, please visit the about me page.

Leave a comment


Warning: Parameter 1 to W3_Plugin_TotalCache::ob_callback() expected to be a reference, value given in /home4/x15denis/public_html/wp-includes/functions.php on line 3208