The document discusses how SharePoint public websites include unnecessary markup that is not compliant with HTML standards and degrades accessibility. It proposes using page filters to remove this markup from the output delivered to anonymous users, producing lightweight, compliant HTML. The filters can be customized and reduce page weight by up to 95% while giving full control over the published output. A downloadable open source filter is available to achieve this clean, compliant SharePoint markup for public websites.

1. Clean, Compliant SharePoint
Producing HTML Compliant Markup for Public Websites in SharePoint 2013
Tobias Lekman

2. The Issue
• SharePoint uses script libraries and assets to support collaboration and content editing
capabilities
• Public websites has anonymous visitors
• Anonymous users cannot, and should not, use collaboration and editing tools
• SharePoint does not, by default, remove these functions for anonymous visitors
10/12/2013
Tobias Lekman
2

3. 10/12/2013
Tobias Lekman
3

4. Unnecessary Markup in SharePoint 2013
FILES MEASURED IN
KILOBYTES
JavaScript
CSS
CSS images
150
348
110
HTML
• 20 (!) JavaScript files, total of 3.3 mb
• 3 CSS files, total of 110 kb
• 8 CSS images, total of 348 kb
• ~600 lines of redundant rows of HTML
3300
10/12/2013
Tobias Lekman
4

5. Unfiltered code is not compliant
• HTML markup is not valid
• Markup cannot be recognized by nonMicrosoft browsers
• Invalid markup leads to issues for screen
readers and degrades compatibility for
accessibility (WCAG)
• Scripts cause performance degradation
10/12/2013
Tobias Lekman
5

6. The Solution
• Page filters
• Light weight
• Developer full control
SharePoint page
publishing output
• Custom master pages
• Use public starter pages
• Open source
Page filter amends
output using regular
expressions
• Available for download today
• http://lek.mn/htmlfilter
10/12/2013
Filtered HTML is
delivered in the server
response to the end user
Tobias Lekman
6

7. Customizing the solution
• Edit master pages, place “filter comments”
around areas that should be hidden from
end users
• Install the filter by referencing the control
in the master page or within a control
delegate
• Add extended regular expressions to
handle custom scenarios
10/12/2013
Tobias Lekman
7

8. Filtered output results
PERCENTAGE WEIGHT
Your Code
5%
SharePoint
95%
10/12/2013
• You can reduce the page weight by up to
95%
• You can completely control the output of
the publishing page
• You can create 100% compliant code
• You can easier support accessibility
requirements
• You can maximize cross browser
compatibility
Tobias Lekman
8

9. http://lek.mn/htmlfilter
Tobias Lekman