Building Internet-facing on the SharePoint platform is different than building portal solutions. Although in both cases you’re working on the SharePoint platform, building Internet-facing websites introduces a number of challenges. In this presentation I want to show you what those challenges are and how you can deal with them.

1. SharePoint 2010 WCM challenges made easy Waldek Mastykarz

2. About: Waldek Mastykarz mvp: SharePoint Server work: Mavention blog: http://blog.mastykarz.nl mail: waldek@mavention.nl twitter: @waldekm

3. Why this session Improved WCM capabilities in SharePoint 2010 Increasing demand for SharePoint WCM solutions WCM solutions are different than portals

4. 90% SharePoint Internet-facing websites suck* and it’s not because of SharePoint * 90% of Dutch Internet-facing websites built on SharePoint 2010

5. What’s in it for you Learn why WCM solutions are different and why you should care Learn what the common challenges are and what you can do about them Be able to focus on the cool stuff instead reinventing the wheel

6. Let’s suck less!

7. custom User Experience Challenge

8. UX challenges

9. UX challenges

10. HTML is the center of the universe

11. How to deal with it

12. Alternative: Mavention Flex Layout* * But that’s cheating

13. building for the internet Challenge

14. The Internet Experience Demo

15. Building for an intranet

16. The Challenge Intranet Internet

17. Building for the Internet challenges

18. Building for the Internet challenges

19. Accessibility & cross-browser support Demo

20. HTML is the center of the universe

21. How to deal with it

22. mobile wcm Challenge

23. Out-of-the-box SharePoint 2010 mobile experience Demo

24. 75% SharePoint Internet-facing websites can’t be opened on a mobile device* * 75% of Dutch Internet-facing websites built on SharePoint 2010

25. Mobile challenges

26. Mobile challenges (2)

27. How to deal with it

28. Fixing the out-of-the-box SharePoint 2010 mobile experience Demo

29. web assumptions Challenge

30. Common assumptionsfor Internet-facing websites XML sitemap robots.txt hierarchical titles meta tags 404/error page short URLs resizing images web analytics SEO (X)HTML strict accessibility performance consistent authoring anonymous audiences

31. How to deal with it

32. content aggregations Challenge

33. Content aggregationschallenges

34. 9/10 custom made content aggregations suck* * a general yet true assumption

35. Content Query Web PartShow-off Demo

36. How to deal with it

37. pretty urls Challenge

38. Forget it! Pretty URLs in SharePoint

39. Pretty URLs in SharePoint

40. Pretty URLs in SharePoint

41. 10/10 pretty URLs suck* * hard reality. It’s just a matter of time

42. How to deal with it Try to understand why your customer want it Try to explain why it’s a bad idea Removing Pages and .aspx doesn’t change much Migration: URL redirection Purity vs. scalability

43. internet-facing website performance Challenge

44. WCM performance challenges

45. How to deal with it

46. How to deal with it (2)

47. Dynamically loading debug/release JS & CSS Demo

48. Mavention Flex Layout* * But that’s cheating

49. Summary Internet-facing SharePoint is not obvious but great results can be achieved Know what you are doing know the platform know your toolbox know the boundaries Don’t forget non-functional requirements!

50. Thank you!