Reusable Content is probably one of the few underestimated features in SharePoint 2010. Not surprisingly: the default samples give you not the best impression of what you could use it for – same as its management interface, and using it in a real life scenario is rather inconvenient. And it’s a shame, because Reusable Content allows you to move away from page-centric content management and make a step towards content-centric content management. And this is exactly where Mavention Create Reusable Content can help you with.
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.