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 » SharePoint 2010

SharePoint Publishing Site Templates

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

In SharePoint 2010 there are 3 predefined site templates which use the SharePoint Server Publishing Infrastructure feature:

  • Publishing Site
  • Publishing Site with Workflow
  • Enterprise Wiki

The easiest things to observe when we create a publishing site are the built in lists and libraries: Documents, Images, Pages, Workflow Tasks.
Please be aware that the internal name of the Images library actually is “PublishingImages”. Anyway, you can find all technical details of the publishing infrastructure on MSDN.

But, what I would really like to point in this post are some differences between these 3 site templates:

Step by Step: Customize a SharePoint Article Page Layout

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

In a previous post I have tried to display some SharePoint pages examples built with the standard Article Page Layouts. With this one I’m going to show you how to add a custom column to the Article Page content type and how to use it on the sites pages.

So, let’s create a site column. Please go to Site Setting -> Site Columns (below Galleries).

Click the Create button. On the new page please complete the column details (name, description, type etc.) and the click Ok. 

Content Rollup Web Parts

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

I want in this post just to give 2 basic graphic examples of how to use the standard content rollup web parts available in SharePoint. I think this is content aggregation made easy :).

Table of Contents Web Part

Content Query Web Parts

I don’t want to transform this post into another Content Query Web Part technical post, a great example can be found on the Microsoft Technet – How to: Customize the SharePoint Content By Query Web Part by Using Custom Properties (ECM).

Regarding Content Query Web Part, my open question is: how deep is this rabbit hole? I personally find it the most powerful out of the box web part existing in SharePoint 2010.

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

SharePoint Publishing Feature Page Content Types Overview

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

When we speak about content types I think there are some common general principles:

  • all the content types are children of  the visible Item content type (there is also a Parent for this, called _System but is hidden).
  • you should look at the content types as they are Business Entities (with the columns being the fields). By design they have a parent and they inherit all the columns defined within the parent.
  • a great advantage provided by the content types is that you have the possibility to enforce the data structure throughout the site collection. For example if you want to add a new column which must be pushed throughout all the Page Layout Content Type, you could add it in the Page content type.
  • you can define documents templates and page layouts and attach them to the content types. Every time when you are going to use that content type in a library the templates will be available too.

You can find detailed information on the Content type and workflow planning (SharePoint Server 2010) article on TechNet.
In the image below you can see how the publishing feature page content types are defined as children of the system content types (each child content type shows only the incremental differences from the parent):


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 3203