I liked the imagery of creating a steering mechanism or guide for SharePoint development, so I’ve named my solution the “Rudder.” The foundations for the Rudder are based on an ingenious Scripting Resource Center that Mark Miller first introduced on EndUserSharePoint.com in January 2010. With the addition of Microsoft’s OneNote and few other site assets, Mark’s resource center can easily be expanded into a configuration management system.
The addition of OneNote is the only significant change made to Mark’s suggestions, so an overview of “Building a SharePoint Scripting Resource Center” on EndUserSharePoint.com would be of benefit to anyone interested in creating this solution. Mark’s original post uses a wiki site to meet the documentation needs and certainly is the best option for those without a user license for OneNote.
As with every SharePoint solution, there are hundreds of possible options. Those outlined here are meant to get the beginner started. These concepts can be expanded upon depending on the level of development and the needs of the organization.
Like Mark’s Resource Center, the Rudder should sit at the top of the site collection. My solution is contained in one document library. The location of the library and/or the need for it to be a separate subsite is entirely dependent upon the architecture and permission structure of the site. The library/site permissions must be set to read-only for all staff, granting elevated ...