Choosing the right Content Management System

  • 5,091 views
Uploaded on

My talk from the Highland Fling Conference 2011

My talk from the Highland Fling Conference 2011

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,091
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
83
Comments
0
Likes
11

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CHOOSING THE RIGHT CONTENT MANAGEMENT SYSTEMFriday, 8 July 2011
  • 2. RACHEL ANDREW @rachelandrew http://rachelandrew.co.uk http://edgeofmyseat.com http://grabaperch.comFriday, 8 July 2011
  • 3. WHAT IS A CMS? (for the purposes of this presentation)Friday, 8 July 2011
  • 4. A TOOL FOR CONTENT EDITING By non-technical users Via some kind of web-based adminFriday, 8 July 2011
  • 5. YOUR CMS IS AN IMPORTANT PART OF YOUR SOLUTIONFriday, 8 July 2011
  • 6. ONE-SIZE DOES NOT FIT ALL.Friday, 8 July 2011
  • 7. WHAT DOES THIS PROJECT NEED?Friday, 8 July 2011
  • 8. HOSTINGFriday, 8 July 2011
  • 9. LANGUAGE PHP, .NET, Ruby, Python ...Friday, 8 July 2011
  • 10. OTHER TECHNICAL REQUIREMENTS Working with existing software, user loginsFriday, 8 July 2011
  • 11. WHO WILL EDIT THIS?Friday, 8 July 2011
  • 12. HOW MANY EDITORS? and do they need protecting from each otherFriday, 8 July 2011
  • 13. SKILLS Not just technical skillsFriday, 8 July 2011
  • 14. PREFERENCES What do they love? What do they hate? Find and fix the pain points.Friday, 8 July 2011
  • 15. THE PROJECT SPEC What requirements does this site have?Friday, 8 July 2011
  • 16. SIMPLE PAGE-BASED An obvious hierarchical site mapFriday, 8 July 2011
  • 17. BLOG-CENTRIC Where a blog or blogs are the main featureFriday, 8 July 2011
  • 18. COMPLEX CONTENT STORAGE REQUIREMENT A huge amount of content - not necessarily page- basedFriday, 8 July 2011
  • 19. CMS SECONDARY TO MAIN APPLICATION Used for editing bits of content in an app.Friday, 8 July 2011
  • 20. OTHER FEATURES Galleries, news updates, e-commerce, calendars ... what else?Friday, 8 July 2011
  • 21. VISITOR NUMBERS How busy do we expect this site to be?Friday, 8 July 2011
  • 22. WHAT EDITING ENVIRONMENT DO YOU WANT TO PROVIDE?Friday, 8 July 2011
  • 23. WHAT BEST SERVES YOUR DESIGN AND YOUR EDITORS?Friday, 8 July 2011
  • 24. YOUR CLIENT IS (PROBABLY) NOT A COPYWRITERFriday, 8 July 2011
  • 25. YOUR CMS SHOULD SUPPORT THE CONTENT STRATEGYFriday, 8 July 2011
  • 26. YOUR CLIENT IS (PROBABLY) NOT A DESIGNERFriday, 8 July 2011
  • 27. YOUR CMS SHOULD MAINTAIN THE DESIGN & TYPOGRAPHYFriday, 8 July 2011
  • 28. DEFAULT TO THE SIMPLEST THING POSSIBLEFriday, 8 July 2011
  • 29. USERS SHOULD NOT NEED TO UNDERSTAND THE DATABASEFriday, 8 July 2011
  • 30. THE SOLUTION TO ONE PROBLEM IS NOT THE SOLUTION TO ALL.Friday, 8 July 2011
  • 31. THE CURSE OF WYSIWYGFriday, 8 July 2011
  • 32. YOUR CLIENT IS (PROBABLY) NOT A DESIGNERFriday, 8 July 2011
  • 33. ckeditorFriday, 8 July 2011
  • 34. Emoticons anyone?Friday, 8 July 2011
  • 35. Comic Sans pleaseFriday, 8 July 2011
  • 36. BUT CLIENTS NEED TO BE ABLE TO STYLE THEIR CONTENT!Friday, 8 July 2011
  • 37. DO THEY, REALLY?Friday, 8 July 2011
  • 38. WYSIWYG EDITORS FOCUS ON HOW CONTENT LOOKS.Friday, 8 July 2011
  • 39. WYSIWYG IS A FLAWED PREMISEFriday, 8 July 2011
  • 40. WYSIWYG CREATES NON-REUSABLE DATAFriday, 8 July 2011
  • 41. This looks like contact informationFriday, 8 July 2011
  • 42. But is it really?Friday, 8 July 2011
  • 43. WYSIWYG MIXES CONTENT AND PRESENTATIONFriday, 8 July 2011
  • 44. WYSIWYG PROMOTES STYLE OVER CONTENTFriday, 8 July 2011
  • 45. SO WHAT SHOULD WE DO?Friday, 8 July 2011
  • 46. STRUCTURED CONTENTFriday, 8 July 2011
  • 47. Contact information?Friday, 8 July 2011
  • 48. Add a contactFriday, 8 July 2011
  • 49. The Contact on a web pageFriday, 8 July 2011
  • 50. Contact mark-upFriday, 8 July 2011
  • 51. SUPPORT THE CONTENT STRATEGY WITH STRUCTURED CONTENTFriday, 8 July 2011
  • 52. MAINTAIN THE DESIGN - EDITORS ENTER CONTENT - NOT MARKUPFriday, 8 July 2011
  • 53. STRUCTURED CONTENT removes the need for editors to think about how it looks.Friday, 8 July 2011
  • 54. STRUCTURED CONTENT can promote the content strategy and offer help and advice in the form for novice copywritersFriday, 8 July 2011
  • 55. STRUCTURED CONTENT allows you to store data in a way that describes what it is - so it can be easily reusedFriday, 8 July 2011
  • 56. STRUCTURED CONTENT prevents a mess of html ending up in your database, making it easier to re-present that content elsewhereFriday, 8 July 2011
  • 57. SIMPLE FORMATTINGFriday, 8 July 2011
  • 58. MARKITUP http://markitup.jaysalvat.com/home/Friday, 8 July 2011
  • 59. WYSIWYM What You See Is What You MEANFriday, 8 July 2011
  • 60. PREVIEWFriday, 8 July 2011
  • 61. VIEW CHANGES IN CONTEXTFriday, 8 July 2011
  • 62. “IN-CONTEXT” EDITINGFriday, 8 July 2011
  • 63. ONLY WORKS FOR VERY SIMPLE SITESFriday, 8 July 2011
  • 64. PROMOTES THINKING ABOUT STYLE RATHER THAN CONTENTFriday, 8 July 2011
  • 65. REQUIRES JAVASCRIPT AND MAY CONFLICT WITH SITE JAVASCRIPTFriday, 8 July 2011
  • 66. USE WITH CAUTION http://allinthehead.com/retro/357/the-lure-of- on-page-editingFriday, 8 July 2011
  • 67. BE UNASHAMED TO BE THE EXPERTFriday, 8 July 2011
  • 68. BUT, WHAT IS THE RIGHT CMS FOR MY PROJECT?Friday, 8 July 2011
  • 69. A CMS THAT DOES NOT FORCE YOU TO COMPROMISEFriday, 8 July 2011
  • 70. A CMS THAT ENABLES EDITORS TO CONTINUE YOUR WORK.Friday, 8 July 2011
  • 71. A CMS THAT PROMOTES EFFECTIVE USE OF CONTENT.Friday, 8 July 2011
  • 72. A CMS THAT PREVENTS ACCIDENTAL DESTRUCTION.Friday, 8 July 2011
  • 73. A CMS THAT DOES THINGS IN THE SIMPLEST WAY POSSIBLE.Friday, 8 July 2011
  • 74. DEMAND MORE FROM YOUR CMS MAKERSFriday, 8 July 2011
  • 75. NEVER SETTLE FOR ‘GOOD ENOUGH’Friday, 8 July 2011
  • 76. HIGHLIGHT GOOD PRACTICE ...and file bugs and complain about outdated, crufty systemsFriday, 8 July 2011
  • 77. THANK YOU @rachelandrew Photos: http://www.flickr.com/photos/ongline/3131142818/ http://www.flickr.com/photos/ongline/3131143218/ http://www.flickr.com/photos/ongline/3131143024/ http://www.flickr.com/photos/ongline/3131142976/Friday, 8 July 2011