SharePoint Standards
This is the table of contents for SharePoint Standards. This is an ongoing project and anyone is welcome to participate.
Below are links to pages we am working on where you can find collated information on SharePoint Standards.
- SharePoint Access Standards
- SharePoint Accessibility Standards (In Progress)
- SharePoint Communication Standards
- SharePoint Content Standards (Updated for 2013)
- SharePoint Deployment Standards (In Progress)
- SharePoint Development Standards (Updated for 2013)
- SharePoint Graphic Standards
- SharePoint Installation Standards (In Progress)
- SharePoint Legal, Compliance and Accountability Standards (In Progress)
- SharePoint Media Standards
- SharePoint Navigation Standards
- SharePoint Security Standards (In Progress)
- SharePoint Social Standards (Updated for 2013)
Know of some standards we don’t have listed or want to help outline some others? Let us know via the comments.
Richard Harbridge
{ 5 trackbacks }
{ 9 comments… read them below or add one }
Not sure if should be standard or not but all wsp’s in this environment are deployed using SharePoint Solution Installer.
Oops – posted that comment to the wrong place
For a single WSP I don’t know if I would mandate that. Though I could see benefits there is more flexibility with just the WSP on it’s own.
For multiple WSPs how about…
“When a collection of WSPs or dependant WSP files are contained in a solution they should be deployed using a Solution Installer or SharePoint Solution Installer (http://sharepointinstaller.codeplex.com/) to simplify the installation and upgrade process.”
Can’t think of any drawbacks so far. What do you think?
I like how the content is evolving here Richard. Just wondering if you might want to put up a wiki for this to let everyone contribute to it? It can still be controlled/moderated but having more peoples input might move things along. For example there are several navigation statndards I’d like to add (relative paths vs. absoute for example) but have no way of doing it (other than comments or emails). Something to think about. Jeremy has the spdev wiki setup so maybe this could be a section on there?
Agreed Bil.
Was hoping to use the NBSP platform for this. Currently there are some delays in getting the SharePoint Business Community area up. I was going to have this live in that area as a wiki format (along with other governance related initiatives).
Alternatively I can always break aspects of this out and distribute management and ownership of it – like ensuring the development standards were in NBSP’s development wiki (evolved version of SPDevWiki). Let me coordinate with Jeremy on that one – as I am not sure where he is in the ‘transition’ process from SPDevWiki to the new NBSP dev wiki. 🙂
P.S – If you send me the other parts now via email (richard@rharbridge.com or twitter or any other method I promise I will update them as soon as possible here). Also if you have any other advice/ideas for where this could be hosted/provide better benefit feel free to let me know. I don’t care/need to own any of it. Just trying to ensure changes are validated/discussed. 🙂
Hi Richard, I met you at the SharePoint Summit. Currently I have been tasked to suggest a modified SDLC approach for our SharePoint inhouse. However the dilema I am faced with is, all references I am finding, are heaviliy biased towards the developer-centric approach to SharePoint development, whereas I use the Author-centric approach to development and do not even venture forth into Visual studio or codeland for anything. I am finding though, the way a development shop is set up, developer, author, coder, out of box, front-end or hybrid would have direct bearing on the process and the types of deliverables and deployments. Is there anywhere you can point me for a best practice author-centric (codeless and useing SharePoint designer) development process, or hybrid author/developer, that utilizes a development, UAT and Prod environments with changes always always progressing through the three environments with no production modifications. An Ideal development environment for us would be a combined Author-centric focused (using SharePoint Designer and declaritive workflow)s, and the developer-centric (using Visual Studio and .NET coding), with even an ability for 3rd party off-site development also.
Richard,
Would definitely love to contribute if you don’t mind. Some of the other areas I think are:
0: Infrastructure / Change Control
1. Managed Metadata Standards
2. User Profile Standards
3. Authentication (NTLM, Kerberos, FBA, Single Sign On) (Other auth providers) (Claims)
4. Training
5. BI Standards
6. ECMA / JavaScript / jQuery (though this might fall more in the development standards)
Let me know.
Best Regards,
Nilesh Mehta
Great job starting to document these standards. I look forward to your next version. I find them very helpful in my work. Minor thing to note is the use of apostrophes when not needed: e.g., it’s instead of its, sites instead of site’s
I transposed my comment about possessive pronouns:
e.g., it’s instead of its, site’s instead of sites, I suppose it will be more helpful if I identify exactly where I saw the edits. I will do that and get back to you.