Case Study - How We Built joomlagov.info (Dwight Barnard))

558 views

Published on

Joomla Day Cape Town South Africa, August 2011

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
558
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Case Study - How We Built joomlagov.info (Dwight Barnard))

  1. 1. Case Study - How we built the http: //joomlagov.info/ website
  2. 2. The White House site is built on Drupal. Can you top that? wiki http://joomlagov.info Response to the question posed to Ryan Ozimek in March 2011
  3. 3. 1. Visual representation of all government websites using Joomla!2. Easy updates, quick addition of new listings and Minimal Maintenance3. Site speed and performance
  4. 4. Joomla! Extensions ● Joomlaworks K2 ● Editor - JCE Editor ● Chronoforms ● Disqus comment system ● NoNumber! Extension Manager ● XMap ● XCloner Backup and Restore
  5. 5. 3rd Party Apis ● Google Maps Api version 3 ● Disqus comment system
  6. 6. Challenges Faced ● Capturing a huge volume of data ● Simplifying the management of new data records and updates ● No budget ● Tight deadline
  7. 7. Solutions ● Automation (Selenium IDE / Python scripts) ● Old fashioned manual labour (community workforce)
  8. 8. Workflow
  9. 9. Project scope ● 253 categories ● 2847 articles ● 2847 screen captures ● 261 menu items
  10. 10. Getting content into Joomla ● Scraping wiki doc and customizing output (long, lat, coutry) ● Automating screen captures, resizing and renaming ● Creating content by merging text and images
  11. 11. Hit Replay Button
  12. 12. Design and template ● fresh clean look ● map focal point ● room for growth
  13. 13. Integration ● K2 extra fields with Google Maps Api ● Chronoforms with K2
  14. 14. K2 Extra Fields - HTML Overrides
  15. 15. K2 Category Map clustering
  16. 16. K2 Article - HTML Overrides
  17. 17. Chronoforms submissions directly into K2
  18. 18. Performance enhancements ● re-order code ● compression (css, js, html) ● caching on
  19. 19. Data is Boring - Maps are fun
  20. 20. Data is Boring - Maps are fun

×