One of the best forms oflearning something is through experience. When you don’t have all the time and oppurtunity to experience everything, you can still learn heaps of stuff from others experiences. To learn from others experiences, ‘How we did it’ articles on the SharePoint Team Blog and other blogs are very nice media. I take this oppurtunity to present all the ‘How we did it’ here in this post. Please note that this post will be updated as and when I find a new article.
|
Article |
Snippet |
|
Nintex Reporting is all about content/collaboration analytics reports for anyone who owns/manages any SharePoint assets. It’s reporting about SharePoint farms, not reporting for SharePoint farms. |
|
|
How We Did It: blueKiwi SharePoint Connector and OfficeAssistant |
The blueWiki SharePoint Connector allows SharePoint customers to integrate blueKiwi’s complementary, highly specialised social software suite into their existing SharePoint environment, surfacing valuable social metrics, such as the most active discussions across the whole organisation, within a SharePoint portal. |
|
Have you ever needed to integrate an external system with SharePoint, showing content from each system within the other? What if you needed to integrate search between SharePoint and the external system? How do you keep the user experience seamless if the systems use different authentication mechanisms? Have you wondered if this can be done if the external system is written in Java? |
|
|
The PKS is an accelerator for social media, using podcasting and social networks to deliver the next-generation knowledge management solution. Built on top of Office SharePoint Server 2007 and using Silverlight 2, the PKS delivers an integrated experience with a wide variety of podcast-capable devices including computers, iPod mobile digital devices, Zune digital media players, and Windows Mobile-based phones. |
|
|
This blog entry describes how Spotlight Connect for SharePoint enhances SharePoint’s Enterprise Search and My Site capabilities by augmenting these native SharePoint features with enterprise social content from Connectbeam. This results in SharePoint users having a greater reach of “social discovery.” |
|
|
How we did it: Mission critical HawaiianAir.com website powered by MOSS 2007 |
About a year ago, when Hawaiian Airlines planned to redesign the look and feel of their website, http://www.HawaiianAir.com, they wanted a solution that would improve the authoring and management of the website’s content. After an evaluation, they decided to take advantage of MOSS 2007’s Web Content Management (WCM) features even though the product was still in beta. |
|
How we did it: PFGC.com — design, development, and go live in 10 weeks! |
The design of the website was accomplished by first understanding and defining the audience personas and then using that information to guide the information architecture and graphical design of the site. |
|
How We Did It – Automating Service Requests using InfoPath Forms Services |
The application addresses the need for enterprises to have a no-code way to quickly turn around service request based SharePoint sites |
|
How We Did It: Christian Children’s Fund extranet powered by SharePoint |
The purpose of this project was to develop and implement a new CCF extranet, known as “The Hub”, that would be used by all CCF employees worldwide as the single source for information, content and document storage, as well as a means for collaboration internally and externally. |
|
Tomoye Ecco and SharePoint Integration – How We Did It and What We Will Do Next |
In order to publish content from SharePoint into Ecco, we created an application page that is accessed from a custom menu action on SharePoint list items. The application page and custom action are deployed using a SharePoint solution (.WSP) file and then activated as a Feature. |
|
Academy Mobile was built entirely on SharePoint Server 2007. The videocasts and podcasts are stored in a customized document library that has been tested to scale upwards of 10,000 podcasts. |
|
|
MOSS Has Got Game – Glu Mobile’s Website (www.glu.com) – How We Did It – Part 1 of 3
MOSS Has Got Game – Glu Mobile’s Website (www.glu.com) – How We Did It – Part 3 of 3 |
Our design philosophy from the start was to integrate the best of ASP.NET 2.0 and MOSS 2007 to implement a highly functional, manageable, and scalable site within a short amount of time. |
|
|
The main aim of the project was to migrate and consolidate all existing web site content, which was in multiple languages and dispersed across several different web domain names, to a common SharePoint server farm. The initial driving force behind the project’s inception was the Live Earth concert series on July 7, 2007 |
|
How We Did It: Australia National Native Title Tribunal website – advanced web content management |
The Tribunal website needed to provide access to government records related to the native title process. The records have complex content types with thousands of pages based on each, and many pages also link to other images and documents that would be available to download. MOSS 2007, with its flexible support for content types and advanced web content management functionality, was a very suitable candidate for a tough job like this. |
|
The core requirements of the solution were to enable SSRS web parts in SharePoint Server 2007 to point to multiple SSRS environments, a capability available in SSRS web parts for SharePoint 2003, with parameterization capability with the filter framework in SharePoint Server 2007. In essence, combine the best qualities of SSRS web parts from 2003 with 2007, as well ensuring usability was easy for end-users with minimal or no training required. |
