SharePoint 2010

Recently I’ve released the Mavention Meta Fields SharePoint 2010 solution that allows you to easily add meta tags to Publishing Pages. While the first version was a great improvement of the user experience for managing meta tags of Publishing Pages, it had a minor flaw when using multiple Content Types in a single Pages Library with different sets of meta tags fields. This issue has been fixed in this release.

In my last article I wrote about how deep links can help you point to specific pieces of the page making it easier to discover the right content. I showed you how SharePoint supports creating deep links out of the box and how you can enrich the default experience using the Mavention Deep Links solution. While writing that article I noticed one thing: deep links are not as discoverable as you would want them to. So what’s exactly the problem and what to do about it?

Hyperlinks are the very base of the Web as we know it. They link relevant information to each other making it easier for the visitors to find the resources they are looking for. By linking different resources to each other content authors can create more complete resources. One of the challenges in linking to other pages is the relevance: sometimes instead of linking to a whole article you might want to point to a specific part of it. And this is exactly where deep links become very handy. Find out how you can easily create deep links with Mavention Deep Links.

Content Query Web Part is probably the best solution for creating dynamic content rollups in SharePoint 2010. It’s lightning fast and because it’s using XSLT it allows you to easily change layout without touching your data. And although changing the presentation in Content Query Web Part is a matter of a few mouse clicks, it gets quite inconvenient when you start using custom XSLT files.

SharePoint 2010 ships with the great ability of adding Web Parts to content areas. This allows you to easily extend your content with dynamic elements providing your users with richer experience. Similarly to using Web Parts with Web Part Zones you should include Web Parts in Rich Content in your structured and repeatable deployment. There are however a few differences in how you provision Web Parts to Rich Content and knowing how it all works can make your life easier.