Including meta tags for pages on Internet-facing websites is very important. Additional information included in meta tags makes it easier for search engines to find and classify the content. Still many websites either don’t use meta tags at all or don’t provide content editors with a simple mechanism for managing the meta tags making managing the meta tags a one-time process. In many situations meta tags are not even a part of the information architecture for Internet-facing websites and are easily being forgotten in the development process. Additionally, as they are not being displayed on the screen, they are not a part of the branding what makes it challenging for the developers to provide an intuitive editing interface for. Mavention Meta Fields is a turn-key solution that allows you to easily add support for managing page-level meta tags even if your website is almost ready to go on-line.
The new Visual Studio 2010 SharePoint Developer Tools ship with Replaceable Parameters which allow you to provide values for SharePoint solution items whose actual values are not known at the design time. And while the Replaceable Parameters are without a doubt a great improvement in the development process, there is one problem with them: there are quite a few of them and looking up the right one might get you out of element when developing. And this is exactly where Mavention Replaceable Parameters Snippets come in.
Proper usage of headings is very important on the web. It helps you structure your content making it more readable, it makes it easier for visually challenged readers to navigate through the content and helps you optimize your content for search engines. And while it’s so important, it’s quite surprising that there is no standard mechanism available within SharePoint that would allow you to quickly verify that your page has a valid headings structure. However thanks to the great extensibility of SharePoint it’s history: proudly presenting Mavention Scan Page Headings!
What is Mavention Scan Page for Broken Links?
Defining custom Site Columns and Content Types is the very basis of almost every SharePoint project. Using Site Columns and Content Types you can define the information architecture of your Solution. And although this process is something that is very important and something you do very often, it is surprising how little support there is for it from the development point of view that would allow you to do it in a productive manner. CKS:DEV has already had some support around Content Types and Site Columns but still it was far from ideal, so including some improvements in that area was something we couldn’t really leave behind…