Getting All Your Web Apps To Wear The Company Brand


Published on

Cross-platform theming! No matter what the platform/language, you can seamlessly apply 1 theme across all your disparate web applications. The technology is called Deliverance and Tim Knapp will demonstrate how to use this powerful tool to theme your web applications.

Published in: Technology, Design
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • There's 1 company theme but many different web applications with different theming approaches, for e.g. mailing list software, issue tracking software, CMS, blogging s/w, etc. The company may wish to use for e.g. WordPress to manage their blog rather than whatever comes native with their CMS. Management may decide for e.g. to move to a new CMS platform. Upgrades do tend to also mean rewriting applications to work on the new version and this can be a long drawn out process. And usually by the time you've completed it the new version of the software has been released.
  • Uses standard HTML and CSS. No need to integrate the theme into the web application technology. Can use it as is. - Can either be run as a separate proxy server, as WSGI middleware or using an XSLT inline transformation hence allowing for better performance and flexibility.
  • Also using PyQuery.
  • Getting All Your Web Apps To Wear The Company Brand

    1. 1. Getting All Your Web Apps To Wear The Company Brand Tim Knapp
    2. 2. Introductions <ul><li>Plone developer since 2003 </li></ul><ul><li>Vice-President of the NZPUG </li></ul><ul><li>Member of the Plone Foundation </li></ul>
    3. 3. The Problem
    4. 4. The Problem <ul><li>Multiple web apps with different theming technologies </li></ul><ul><li>Wanting to use best-of-breed web apps </li></ul><ul><li>Migrations </li></ul><ul><li>Upgrades </li></ul>
    5. 5. The Solution
    6. 6. Deliverance
    7. 7. 1 2
    8. 8. 1 2
    9. 10. How Difficult Was This?
    10. 11. Why Use Deliverance? <ul><li>Web designers don't need to learn a new theming technology </li></ul><ul><li>Can use an existing theme </li></ul><ul><li>Works with any web framework </li></ul><ul><li>Performance and flexibility </li></ul>
    11. 12. Sites Using Deliverance
    12. 13. - Before
    13. 14. - Deliveranced
    14. 15. - Deliveranced
    15. 16.
    16. 17.
    17. 18.
    18. 19. - Before
    19. 20. - Deliveranced
    20. 21. How Does It Work? <ul><li>Move elements from your content </li></ul><ul><li>Into placeholders in your theme </li></ul><ul><li>Without touching either of them </li></ul>
    21. 22. The Nuts and Bolts <ul><li>An XML rules file defines the actions you wish to perform on the content and theme </li></ul><ul><li>4 available actions </li></ul><ul><li>Select the items you wish to operate on via CSS selectors or XPath expressions </li></ul>
    22. 23. 4 Deliverance Actions <ul><li>replace </li></ul><ul><li>append/prepend </li></ul><ul><li>drop </li></ul>
    23. 24. replace <ul><ul><li>“ replaces something in the theme with something in the content ” </li></ul></ul>
    24. 25. append and prepend <ul><ul><li>“ append puts things from the content after things in the theme , and prepend puts things from the content before things in the theme ” </li></ul></ul>
    25. 26. drop <ul><ul><li>“ remove problematic elements from a theme or content” </li></ul></ul>
    26. 27. More Advanced Usage (PyQuery, etc)
    27. 28. Deployment Options <ul><li>Proxy </li></ul><ul><li>WSGI middleware using repoze </li></ul><ul><li>collective.xdv </li></ul>
    28. 29. Q & A
    29. 30. Contact Details <ul><li>e : [email_address] </li></ul><ul><li>w : </li></ul>
    30. 31. Presentation URLs <ul><li> </li></ul><ul><li> </li></ul>
    31. 32. More info <ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>
    32. 33. Image Credits <ul><li> </li></ul><ul><li> </li></ul>