1. MASTER PAGES FOR ALL AGES Presented by George Solomon of Vibe Commerce

3. Fundamental differences between AspDotNetStorefront using Master Pages vs. using Skins

5. Have a .master extension

6. Predefined layouts which can contain

7. HTML Elements

8. Static Text or Images

9. .NET Server Controls

11. They make it easy to create one set of controls and code and apply the results to a set of pages.

12. They give you fine-grained control over the layout of the final page by allowing you to control how the placeholder controls are rendered.

14. App_Templates

15. Provides a location for Master Pages and stylesheets that should be applied selectively rather than globally

17. App_Themes

18. Provides a location for stylesheets that should be applied globally for a theme

20. The .NET standard for applying a set of styles across a site

21. All stylesheets belonging to a theme are applied to the site regardless of whether or not they are declared in the page or the Master Page

23. No longer is a recursive loop required to re-parent and reassign controls nor look through those controls for locale strings to string replace

25. .NET developers that work with UI know Master Pages and don’t have to learn AspDotNetStorefront skins

26. UI layout and structure separate from UI styles

27. Can work simultaneously with designers

28. Flexibility

30. Add stylesheets directly to App_Themes without any changes to Master Pages

31. Separation of design and structure

32. Can work simultaneously with developers

33. Theme switching

35. Design, layout, and modifications are much easier to implement, saving days or even weeks

36. $$

37. Time is money, and when changes can be implemented quicker, they can be implemented for less money

38. Consistency

40. Easily create your own methods for dynamically selecting data for display in .NET controls

43. Easily segment different sections of a page into separate files that can be developed and designed individually and independent of each other