A presentation I did together with my colleague Anders Ganes at Norwegian Developers Conference 2011 (NDC2011). Abstract: SharePoint 2010 was chosen as the platform for the new public website for The Norwegian Defense , www.forsvaret.no, as one of the first large scale web sites built upon SharePoint 2010 for Internet Sites worldwide. By choosing SharePoint 2010 as a platform you get a powerful and feature rich foundation, but there are also some concerns. DIFI (Agency for Public Management and eGovernment) has defined many requirements that public websites have to fulfill. Soon, these requirements will also apply to all Norwegian websites. In this talk we will discuss how SharePoint 2010 fulfills these requirements. This also includes a closer look at SharePoint in regard to usability, how SharePoint 2010 relates to the Web Content Accessibility Guidelines (WCAG) 2.0 and what issues and experiences we have made related to these topics. We will also share our experiences with SharePoint as a large–scale Content Management System for Internet solutions, issues that has been dealt with as well as workarounds and solutions.

1.  www.steria.com
 SharePoint 2010 for Internet: Forsvaret.no
NDC 2011
Anders Ganes and Jan Maximilian Winther Kristiansen
© Steria

2.  Content
 1. The project and requirements for public websites
 2. SharePoint customizations
 3. Challenges using SharePoint 2010 for Internet
 www.steria.com 13/06/2011 2

3.  From mil.no…
 Screenshot of the old websites go here.
 www.steria.com

4.  Timeline
2010
March December
SharePoint 2010 beta Development
Launch!
 www.steria.com

5.  The Team
 Development  Usability
Bård Terje Fallan Anders Ganes Ishfaq Khan Eirik Brandtzæg Kjetil Ødegaarden Eli Toftøy-Andersen
 Frontend  Test Leader  Advisor/PM
 Plus graphical
designers, frontend
developers and other
resources from the
customer.
Jan Maximilian Jørgen Sundt Stina Braathen Ole Johan Heum
Kristiansen
 www.steria.com

6. 
 www.steria.com

7.  … to Forsvaret.no
 www.steria.com

8.  What did we develop?
 Around 30 custom webparts
 16 pagelayouts and over 20 content types
 Custom asp.net menu controller, custom master
pages, custom error pages
 Tons of css, javascript and xslt
 +++
 www.steria.com

9.  Web Accessibility
 Stortingsmelding 17 (2006-2007)
”INFORMATION AVAILABLE FOR
EVERYONE”
 www.steria.com 13/06/2011 9 Steria Templatev8_English_samples orange V003.ppt

10.  u
 www.steria.com
Flickr by Hatters! http://www.flickr.com/photos/hatters/4451459591/sizes/l/in/photostream/

11.  Tenk på tilgjengelighet fra starten
 www.steria.com
http://www.flickr.com/photos/17804775@N00/4335903569/sizes/l/in/photostream/

12. Web Content Accessibility Guidelines (WCAG)
 2.0
 Consists of 12 guidelines that covers a range of
recommendations for making Web content more
accessible
 Testable success criteria for each guideline
 Three conformance levels. Level A, AA and AAA
 www.steria.com

13.  Requirements for public websites
 Agency for Public Management and eGovernment
(DIFI) does every year a quality assessment of public
websites (http://kvalitet.difi.no/ )
 Has a set of criteria where you can score points for
each criteria
 From 1st of July 2011, all new public websites must
fulfill the WCAG 2.0 A and AA requirements.
 www.steria.com

14.  Content
 1. The project and requirements for public websites
 2. SharePoint customizations
 3. Challenges using SharePoint 2010 for Internet
 www.steria.com 13/06/2011 14

15.  SharePoint and accessibility
 SharePoint 2010 aims to be WCAG 2.0 AA compliant
out of the box.
 Meets most of DIFIs requirements
 Some adjustments had to be made
 www.steria.com

16.  Improving markup
 Issue: Webpartzones renders tables instead of div’s
 Solution: Use adapter to render div’s
 www.steria.com

17.  A page should be easy to load
 Reduce file size
 Reduce number of files
 www.steria.com

18.  Improving performance
1000s of lines of JavaScript
 www.steria.com

19.  Removing SharePoint JavaScript
 Created stubs of missing objects and functions
 www.steria.com

20.  Removing SharePoint JavaScript
Size in Megabytes
1,6
1,4
1,2
1
0,8
Size in Megabytes
0,6
0,4
0,2
0
Before After
 www.steria.com

21.  Loading necessary files
 Place content not needed for anonymous users in a
SPSecurityTrimmedControl
 www.steria.com

22.  Minifying CSS and JavaScript
 Minimize JavaScript and CSS files to minimize size
Normal:
Minimized:
 www.steria.com

23.  Improving accessibility
 Text size.
 Skip links
 Custom menu controller
 www.steria.com

24.  Text Size
 Browser zoom and text resize not sufficient
 Dedicated button in UI
 Adds new font styles on click
 www.steria.com

25.  Adding Skip Links
 A skip link is a link which points directly at specific
section of the page
 Added directly in the master page
 www.steria.com

26.  Custom Menu Controller
 www.steria.com

27.  Content
 1. The project and requirements for public websites
 2. SharePoint customizations
 3. Challenges using SharePoint 2010 for Internet
 www.steria.com 13/06/2011 27

28.  Use SharePoint for Internet vs Internal solution
Internal solutions Internet
 www.steria.com

29. 
Lines of CSS
6000
5000
4000
3000
Lines of CSS
2000
1000
0
All browsers IE7 IE6
 www.steria.com

30.  Prefixing CSS3 Properties
 Many properties are not stable
 Prefix special properties for all browsers, and leave the
property for compability in the future.
 www.steria.com

31.  Pages for mobile devices in SharePoint 2010
 www.steria.com

32.  Pages for mobile devices in SharePoint 2010
 www.steria.com

33.  Generate site structure manually??
No, thank you
 www.steria.com

34.  How to generate site structure
 www.steria.com

35.  How to generate site structure
Save the mind map as XML
 www.steria.com

36.  How to generate site structure
 Create site structure with SharePoint Object Model
with the XML map as input
 www.steria.com

37.  How to generate site structure
 Demo
 www.steria.com

38.  How to generate site structure
 Demo
 www.steria.com

39. 
 www.steria.com

40.  How to generate site structure
 Advantages
▬ User involvement
▬ Development purposes
▬ Lower time to market
▬ Saves a lot of clicks
 Disadvantages
▬ Content development
 www.steria.com

41.  Summary experiences
 SharePoint 2010 has been a stable and good product
to work with
 We succeeded building a website that mostly fulfills
requirements for public websites, but adaptions had to
be made
 Plan accessibility from the start
 www.steria.com

42. 
Terje Øfsdahl
Software Engineer
Avdeling: Microsoft
Thank you!
twitter.com/_Terje
to@steria.no
Anders Ganes Jan M. Kristiansen
Software Engineer Trainee Software Engineer
ang@steria.no jmk@steria.no
@_anders @jankristiansen
 www.steria.com 13.06.2011 42 Konfidensiell - Navn på presentasjon.ppt

43. 
Terje Øfsdahl
Software Engineer
Avdeling: Microsoft
Questions?
twitter.com/_Terje
to@steria.no
 www.steria.com