This is not a newsflash. Anyone who has dealt with internet content, whether it is for search engine marketing purposes or just generally on their site, will know that people read in a different way on the internet. It’s really not new knowledge.

So why on earth are people still publishing poor online content?

Bad internet content is everywhere, even on business sites. A lot of these sites should know better, but the mistake usually is made that writing is writing. Businesses that are used to presenting information in one way tend to be reluctant to change their habits. When it comes to online content, this tends to translate into text on pages that really doesn’t suit the net.
Read the rest of this entry »

SharePoint Server 2010 is the trending topic these days. And when talking about SharePoint 2010, how can I miss to mention one of the most valuable interface changes provided in it, i.e., the new Ribbon Menu. SharePoint Ribbon Menu is a contextual interface that allows users to execute any action related to ribbon controls depending upon the context the user is currently dealing with. Simply put, Ribbon Menu helps to add or replace buttons, groups, tabs or even the whole ribbon. You also remove the custom button from the ribbon. However¸ the designers and web developers, who until now were quite comfortable with designing master pages for SharePoint Server, are somewhat puzzled now with this thing called Ribbon Menu in the middle of their page. But there’s nothing to get confused about because the SharePoint 2010 API allows developers to extend and customize the ribbon using SharePoint features on site/site collection level.

There are several types of controls which can be deployed to SharePoint Ribbon, which are as follows:
• Button
• CheckBox
• DropDown
• FlyoutAnchor
• ToggleButton

The above given controls can be collected for usability purposes to containers such as Group and Tab. Consequently, it is possible to add controls with custom functionality not only to existing containers, but deploy new tabs and groups, and then add necessary controls to them. However, any ribbon customization should be mounted within XML in-feature declaration.

If you have deployed some ribbon customization XML and later have to provide some changes into it then it might be necessary to change the Feature ID for SharePoint feature where your customization belongs. For simple modifications (i.e. changing button titles, image URLs, etc.) this is not necessary, but if you change the Feature ID, every time you change anything in XML, it might save a lot of time and effort.

To conclude, the Ribbon is a new concept with SharePoint Server 2010 and SharePoint Foundation 2010, and another advance over Microsoft Office SharePoint server. Also do not forget the free SharePoint web parts or templates that come with SharePoint.