In this information intensive world, it sometimes gets difficult for organizations to facilitate a web-site with the home page containing all important information. If there is too much content on the page entered directly, it creates a vertical (or horizontal) scrollbar. Normal Users like to see the content right on the page or with very few obvious clicks. This generates the idea of creating widgets/controls which help content owners to deliver the content in more user-friendly way. There are two very important gadgets worth mentioning: Accordion and Tabs.
In this information intensive world, it sometimes gets difficult for organizations to facilitate a web-site with the home page containing all important information. If there is too much content on the page entered directly, it creates a vertical (or horizontal) scrollbar. Normal Users like to see the content right on the page or with very few obvious clicks. This generates the idea of creating widgets/controls which help content owners to deliver the content in more user-friendly way. There are two very important gadgets worth mentioning: Accordion and Tabs. Let us understand a Tabs widget here.
By default, MOSS 2007 configures every 1st level sub-site to have a tab (with link) on the horizontal navigation bar at the root level of the site collection. I would like to be able to nest some or all of these links under one tab heading, saving space for other tabs.
For site navigation, SharePoint provides a Top navigation menu and a Left navigation menu, but sometimes this is not sufficient. If you have 100 sites or pages underneath your Site Collection and you want to look at it alphabetically, anything out of the box is not going to work. You need something custom, but you don't want to write complex C# code or spend a lot of time coding and deploying it, so what can you do?
Enterprise level systems consist of huge amounts of data which is likely interrelated. All data stored in SharePoint has a specific metadata. Until SharePoint 2007, there was no way of storing the metadata in an organized and hierarchical format.
With evolution of search, different kinds of requirements arise for searching content. One of the requirements we came across was that they wanted to search for content from external locations (i.e. like Google, YouTube and other public facing internet applications).
Targeted email notification is a basic need in today's business process automation. Using SharePoint workflow, this can be achieved using SharePoint Designer 2007 (MOSS 2007 or WSS3) whenever a document is uploaded. The content of the email can be improved by including a link in the body of the email to the document item in process.
There are numerous solutions out there in the web to create a Slideshow web part. But finding one with jQuery was a tough job for me when I started working on this. JQuery was chosen based on the requirement given.
A common requirement for publishing sites on SharePoint is to personalize and target content, menu links, and other site features, based on attributes of the user. For example, the latest company news and events for Sales Associates in California may not be all that relevant to Shipping Agents in South Carolina.
SharePoint content types are created and managed in the Content Type Gallery of a specific SharePoint site, and are inherited by all sub-sites within the same site collection. In SharePoint 2007, to use the same content type across multiple site collections required duplicating the content type manually, or deploying a custom developed feature. In SharePoint 2010, the Managed Metadata Service provides the ability to publish content types from a central location.
One of the most general requirements we come across is to make enterprise search more compact and effective, providing quick and more accurate results. One of the major problems is to provide the right filters to find a particular record. For instance in a large enterprise environment, searching for a person called Jeffry from the Finance department, is not always a feasible option. Filters may not provide the accurate results for what users are expecting.
The site template for "Site Directory" was an interesting navigation feature in MOSS 2007. When I went to look for it in SharePoint 2010, I could not find it. After doing a few searches, I found the answer...