On the verge of launching a new release of a public SharePoint website and I came across this list (from shanselman’s twitter actually).
Here’s how we fared:
- Favicon – checked and done!
- Titles and Meta data – checked! Actually SharePoint comes with quite a bit of baggage, but we started with a clean masterpage so this is not too bad.
- Cross-Browser Checks – checked! IE6, 7, 8, FireFox, Chrome, Safari + iPhone. RichHTML editing is limited to IE for now – but there’s a release soon afterwards to upgrade to Telerik’s RadEditor Lite.
- Proofread – not enough :-(
- Links – checked - using both SharePoint’s internal reports and SSW Link Auditor – hopefully the content editors don’t put in bad links from now til launch…
- Functionality Check – checked! My biggest fears are that in the sprint until launch, if we accidentally break an existing feature that was working previously, so far my fears have been unfounded.
- Validation – no - it’s SharePoint. This is going to be a tough one to tick off.
- RSS Link – checked – may be. One of the features of this release, unless we have to cut it.
- Analytics – checked – both the SharePoint reports, as well as Google Analytics that was used for the old site
- Sitemap – checked – SharePoint does this naturally
- Defensive Design – checked. SharePoint allows for 404 to be customized
- Optimize – not enough. We’re utilizing quite a few performance tricks we have up our sleeves, but ultimately there’s just not the level of control in SharePoint vs. say a custom ASP.NET application
- Back Up – checked
- Print Style Sheet – need to check again. This was working previously but we’ve had some work done on the site in the last two releases and I’m a bit worried about our good ol’ print css.
So we scored 10/15. Ticked off most of the easy ones. Have quite a few really tough ones left. Wish us luck!