Adventures in Content Management

717 views

Published on

Trying to implement content management at work? Thinking about it? Here are some of the issues you need to be aware of.

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

No notes for slide

Adventures in Content Management

  1. 1. Adventures in Content Management Joomla, WordPress, Contribute & More Mark Farmer
  2. 2. Who the heck this is for • Implementing a CMS at work • Trying to decide whether or not to implement a CMS at work • Trying to manage content better, CMS or not
  3. 3. Take-aways • Better insight into the choice of platform • Managing content & contributors • Some of the “gotchyas,” platform-specific or related to CMSs in general
  4. 4. • Anyone attend my 2009 talk? • How many developers? • How many designers? • Content managers? • WordPress • Joomla • Drupal • Contribute • Not using one, but planning to in next 6 months Quick survey
  5. 5. SECTION 1 – The Software • Help! I have too much stuff! • Only ever encountered one reason people implement a CMS:  Too much content  Web team can’t keep up • Implementing a CMS is disruptive.
  6. 6. Picking the Right Platform • First question is likely “what platform?” • The right questions: A. What’s it going to be used for? B. Who’s going to use it? • “A” is important & straightforward.  Blog? Portal? Other?
  7. 7. Picking the Right Platform
  8. 8. Picking the Right Platform
  9. 9. Picking the Right Platform
  10. 10. Picking the Right Platform
  11. 11. Picking the Right Platform • “B: Who’s going to use it” is just as important  WYSIWYG  Interface • Don’t assume that just because you build it, they’ll use it • Stay tuned for a couple of websites that will help you decide which to choose
  12. 12. CMS varieties • It’s tricky to rock a rhyme... and Joomla  Don’t believe the hype  Don’t overpromise on timelines • The learning curve / frustration curve • The good news  You can make it do pretty much anything, with enough elbow grease  So don’t let the curves hold you back
  13. 13. CMS varieties • It’s all about the extensibility  Behold the power of WordPress!
  14. 14. CMS varieties
  15. 15. CMS varieties • (E-mail me to a link for more examples of sites like this)
  16. 16. CMS varieties • My focus: Joomla, WordPress & Contribute
  17. 17. Comparison shopping • The CMS Matrix  cmsmatrix.org • Open-source CMS ratings  php.opensourcecms. com/general/ratings. php
  18. 18. #1: Contribute • Completely different metaphor • Template-based (or not) • Apply retroactively to a site • $199 – but discount for non-profits  techsoup.org  adobeprograms.giftsinkind.org • I love you, WYSIWYG/Window • EDC, yeah you know me • EcoKids
  19. 19. #1: Contribute
  20. 20. #1: Contribute • The importance of a friendly (inter)face • A control issue  Dev/pub  Security  Q/A  Time saver • This is important, because of the number of clients who implement CMSs and then don’t use them
  21. 21. #2: Joomla • The obvious comparison: Drupal  Extensibility  Pre-installation  The App Store of CMSs  Do you need that many...?
  22. 22. Joomla • Deceptively simple & template-driven... • ...but counter-intuitive  Menus drive the content • Blank slate? • Many files in WP vs... one in Joomla
  23. 23. Joomla – gotchyas • The wonderful world of extensions: extensions.joomla.org  Don’t believe the hype  The Black Box concept  Graphical nav bar woes  My recommendation? Get someone else to pay you to learn how to do it.  Like much of web design, most of this is 25% IQ & 75% brute force/persistence
  24. 24. Joomla – more gotchyas • Couple more quickies:  Don’t forget to turn on the cache after primary development is over  Enable user/SEO-friendly URLs  GoDaddy is weird
  25. 25. • Joomla vs. Drupal: not a make-or-break decision Drupal: sounds like RuPaul, but not
  26. 26. Drupal: sounds like RuPaul, but not
  27. 27. • Like Joomla, play by the rules and no one gets hurt • Joomla does a better job up front, Drupal better behind the scenes, faster. • Big changes on the front-end in ver. 7 • Weird science: taxonomy, blocks Drupal: sounds like RuPaul, but not
  28. 28. WordPress • Layout very different, again • Easier to produce a custom layout • Templates & themes
  29. 29. WordPress • But test, test, test! • Plugins less buggy, easier to activate than Joomla/Drupal
  30. 30. WordPress & Language • Setting the language & uploading the language plug-in a no-go • Required customization of the PHP • Skinning not too hard ;customizing on the PHP level is  Plug: Super Finder
  31. 31. SECTION 2 – The Peopleware • The biggest challenge in content management isn’t the software, it’s the people • You are going to spend a lot of time educating your client. Accept this.
  32. 32. Build it, but they won’t come • Clients that have CMSs but don’t use them. Why?  Lack of education  Intimidating  Too much work/time  Doesn’t get used
  33. 33. Play • Play. It’s important  Sandbox: demo.joomla.org/1.5  Dev/pub
  34. 34. Secret Weapon #2: Funnels
  35. 35. Secret Weapon #2: Funnels
  36. 36. Resources • Web:  cmsmatrix.org  php.opensourcecms.com/general/ratings.php • Books: • Groups:  groups.drupal.org/toronto  toronto.joomla.ca  wordcamptoronto.com
  37. 37. Thank you • E-mail: markfarmer@webness.biz • Site: webness.biz • Blog: webheresies.com • Twitter: markus64 • Facebook: markus64 • LinkedIn: markfarmer64 Feedback: spkr8.com/t/2047

×