Did you know that SharePoint 2010 ships with a brand new menu control, which allows you to render the menu as an unordered list (UL)? Using that control makes branding your menus extremely simple! Unfortunately this control is available only with SharePoint 2010. If you’re still working with Office SharePoint Server 2007 projects, you have to either brand the tables rendered by the standard SharePoint menu or create a custom control that would generate semantic markup. But wait: code no more! Proudly introducing the Mavention Simple Menu control!
Recently I was presenting for a group of colleagues at Imtech ICT Integrated Solutions about new publishing features in SharePoint 2010. One of the questions that I got was: how can we leverage the Rich Text Editor for anonymous users on Internet-facing websites?
Body id is a cool webdesign trick that allows designers to easily alter the layout of a page using nothing more than a single property and some CSS styling. Using the body id you can define one HTML page structure for the whole site and then, by changing the single value of the body id attribute, you can create new experiences by styling the different pieces of the page in a totally different way. While it sounds very easy and it is very easy with HTML, this trick can get very challenging when used with SharePoint.
Recently I published a new extended version of the Content Query Web Part. I extended the SharePoint 2010 version of CQWP with support for paging the results which is one of the things that our customers ask for very often. But that’s not the end of the extensibility possibilities of the CQWP. In this version I extended the Imtech Content Query Web Part even further by adding additional capabilities which make working with the CQWP even easier. Introducing: Imtech Content Query Web Part v14.2!
One of the coolest and probably most frequently used Web Parts in SharePoint 2007 was the Content Query Web Part (CQWP) – a great control that allowed you to display content aggregations to the users. Although it was pretty awesome, it had some serious drawbacks like for example the lack of a paging mechanism – something that almost every single Web Content Management project that I worked on required. Three years later in SharePoint 2010 the CQWP got a facelift and shipped with some seriously cool features like slots and the Content to Content concept. Unfortunately still no sign of paging. So what if you want to create an aggregation of your content and page the contents? Do you have to create a custom and bad performing Web Part? Not really… Introducing Imtech Content Query Web Part v14!