Master Pages for All Ages - George Solomon, Vibe Commerce

1,513 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,513
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Master Pages for All Ages - George Solomon, Vibe Commerce

  1. 1. MASTER PAGES FOR ALL AGES<br />Presented by George Solomon <br />of Vibe Commerce<br />
  2. 2. MASTER PAGES FOR ALL AGES<br />Agenda<br /><ul><li>Master Pages: What they are and why they are important
  3. 3. Fundamental differences between AspDotNetStorefront using Master Pages vs. using Skins
  4. 4. How Master Pages and the AspDotNetStorefront changes are beneficial to designers, developers, and end-users</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />What Are Master Pages<br /><ul><li>.NETs way of allowing you to create a consistent layout for the different pages of an application
  5. 5. Have a .master extension
  6. 6. Predefined layouts which can contain
  7. 7. HTML Elements
  8. 8. Static Text or Images
  9. 9. .NET Server Controls
  10. 10. Contain an asp:ContentPlaceHolder control which is replaced with the contents of the page that is being loaded</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Why Are Master Pages Important<br /><ul><li>They allow you to centralize the common functionality of your pages so that you can make updates in just one place.
  11. 11. They make it easy to create one set of controls and code and apply the results to a set of pages.
  12. 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.
  13. 13. They provide an object model that allows you to customize the master page from individual content pages.</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Fundamental AspDotNetStorefront Differences<br /><ul><li>Directory Structure
  14. 14. App_Templates
  15. 15. Provides a location for Master Pages and stylesheets that should be applied selectively rather than globally
  16. 16. Allows for a separation of layout and structure elements from style and design elements</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Fundamental AspDotNetStorefront Differences<br /><ul><li>Directory Structure
  17. 17. App_Themes
  18. 18. Provides a location for stylesheets that should be applied globally for a theme
  19. 19. Allows for a separation of style and design elements from layout and structure elements </li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Fundamental AspDotNetStorefront Differences<br /><ul><li>Themes
  20. 20. The .NET standard for applying a set of styles across a site
  21. 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
  22. 22. Themes can be easily applied on a page by page basis</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Fundamental AspDotNetStorefront Differences<br /><ul><li>Performance – much quicker to render compared to skins
  23. 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
  24. 24. Using Expression Builder tokens prevents the page from being converted entirely to a string before a string replace is used to find all skin token instances</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />What Does This Mean For Developers<br /><ul><li>Decreased learning curve and familiarity
  25. 25. .NET developers that work with UI know Master Pages and don’t have to learn AspDotNetStorefront skins
  26. 26. UI layout and structure separate from UI styles
  27. 27. Can work simultaneously with designers
  28. 28. Flexibility
  29. 29. 3rd party controls and add-ons</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />What Does This Mean For Designers<br /><ul><li>Ease of applying styles
  30. 30. Add stylesheets directly to App_Themes without any changes to Master Pages
  31. 31. Separation of design and structure
  32. 32. Can work simultaneously with developers
  33. 33. Theme switching
  34. 34. Simple to apply an entire library of styles from a separate theme</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />What Does This Mean For End-Users<br /><ul><li>Time
  35. 35. Design, layout, and modifications are much easier to implement, saving days or even weeks
  36. 36. $$
  37. 37. Time is money, and when changes can be implemented quicker, they can be implemented for less money
  38. 38. Consistency
  39. 39. Maintain a consistent look and feel across the site exactly where it’s needed with minimal platform experience</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Expression Builder Extension<br /><ul><li>New tokens can be extended in much the same way as XSLT Extension functions
  40. 40. Easily create your own methods for dynamically selecting data for display in .NET controls
  41. 41. One web.config addition and a class that inherits the System.Web.Compilation.ExpressionBuilder class</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Expression Builder Extension<br /><ul><li>public class CustomTokens : ExpressionBuilder { }
  42. 42. <compilation defaultLanguage="c#" debug="true"> <expressionBuilders> <add expressionPrefix="Tokens" type="AspDotNetStorefrontCore.Tokens, AspDotNetStorefrontCore" /> <add expressionPrefix=“CustomTokens” type=“Namespace.CustomTokens, App_Code”/></li></li></ul><li>MASTER PAGES FOR ALL AGES<br />Nested Master Pages<br /><ul><li>.NET allows for nested Master Pages
  43. 43. Easily segment different sections of a page into separate files that can be developed and designed individually and independent of each other
  44. 44. Flexibility allows you to easily change part of a page by swapping out a Master Page without having to re-work the entire structure of the page</li></li></ul><li>MASTER PAGES FOR ALL AGES<br />

×