Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Perfect CMS: Brass Ring, or Unattainable Goal

2,025 views

Published on

This is my presentation for LavaCon 2011. We talk about evaluating Content Management Systems.

Published in: Technology
  • Be the first to comment

The Perfect CMS: Brass Ring, or Unattainable Goal

  1. 1. The Perfect CMS Brass Ring, or Unattainable Goal Robert Rhyne Armstrong November 16, 2011
  2. 2. The Intro.
  3. 3. Hi! I’m Rhyne. <ul><li>Or Robert…whatever. </li></ul><ul><li>Thanks for choosing this session. </li></ul>
  4. 4. I screw up, so you don’t have to.
  5. 5. We have a lot to talk about. <ul><li>Starting the task </li></ul><ul><li>Identifying potential products </li></ul><ul><li>Choosing the right one for you </li></ul><ul><li>Putting the product to work </li></ul>
  6. 6. I’m ready to begin.
  7. 7.
  8. 8. 1200 CMS listed on CMSMatrix.org
  9. 9. 134 Wikis listed in Wikimatrix.org
  10. 11. Oh crap.
  11. 12. Relax. You can do this. <ul><li>Limit your options </li></ul><ul><li>Build your selection criteria </li></ul>
  12. 13. Ask tactical questions that cut the list down.
  13. 14. How are you going to use it?
  14. 15. Who is going to host it?
  15. 16. What platform will it live in?
  16. 17. Where will your data be stored?
  17. 18. Will you need to connect to other systems?
  18. 19. What are people used to?
  19. 20. Is there a CMS already in your organization?
  20. 21. What can you do with legacy content?
  21. 22. What is your budget? Do you have one?
  22. 23. Hold on…
  23. 24. Open Source vs. Commercial Products
  24. 25. Open Source DOES NOT mean free <ul><li>Necessarily… </li></ul>
  25. 26. Pros <ul><li>Usually less expensive </li></ul><ul><li>Large community </li></ul><ul><li>Open source code </li></ul><ul><li>More flexible </li></ul><ul><li>Usable API </li></ul><ul><li>Usually high quality and well thought out </li></ul>
  26. 27. Cons
  27. 28. <ul><li>No ‘real’ support </li></ul><ul><li>Plug-ins can be slow to upgrade </li></ul><ul><li>Can get expensive with add-ons </li></ul><ul><li>Usually has poor documentation </li></ul><ul><li>The number of options in a space can lead to a fractured community </li></ul>
  28. 29. Evaluate on their merits, not on their origins.
  29. 30. Game on.
  30. 31. Use your list to narrow the field.
  31. 32. Identify 3 that you really like.
  32. 33. Get started with your evaluation.
  33. 34. Look at the product from three viewpoints.
  34. 35. The consumer…
  35. 38. The author…
  36. 41. The administrator…
  37. 44. Work in reality.
  38. 45. It eventually comes down to one thing:
  39. 46. Your preference.
  40. 47. Now you have to live with it.
  41. 48. Look beyond the ‘puppy period.’
  42. 50. Put the time to good use.
  43. 51. Work through all use cases. Don’t take anything for granted.
  44. 52. Don’t assume things work on your system the same way they work somewhere else.
  45. 53. Work on core features first.
  46. 54. You may never have to go beyond that step.
  47. 55. If you do, try one thing at a time.
  48. 56. Join the support community.
  49. 57. Enlist your developers.
  50. 58. Use the tool to plan the tool.
  51. 59. Involve everyone who is going to work on it.
  52. 60. Be careful with upgrades and 3 rd party plug-ins.
  53. 61. A mini case study.
  54. 62. 3 different CMS in use.
  55. 63. Author-it for our documentation.
  56. 64. Wordpress for our website and Customer Care portal.
  57. 65. Confluence for our Intranet.
  58. 66. Isn’t that overkill?
  59. 67. It works for us.
  60. 68. Can you please answer the question?
  61. 69. Nothing is perfect…
  62. 70. … but it could be perfect for you.
  63. 71. Good luck! <ul><li>Robert Rhyne Armstrong </li></ul><ul><li>@ninety7 </li></ul><ul><li>facebook.com/rhyne </li></ul><ul><li>[email_address] </li></ul>

×