Your SlideShare is downloading. ×
0
The Future ofContent ManagementRachel Andrew: Smashing Conference 2012Thursday, 2 May 13
edgeofmyseat.comThursday, 2 May 13
grabaperch.comThursday, 2 May 13
Question.Who here generally develops sites using some form ofcontent management system?Thursday, 2 May 13
Why don’t we talk aboutthis more?Thursday, 2 May 13
The trouble with contentmanagement systems.Thursday, 2 May 13
http://storify.com/rachelandrew/cms-horrors“Has your client ever done somethingreally odd using a CMS? Font horrors,giant ...
Thursday, 2 May 13
Thursday, 2 May 13
Thursday, 2 May 13
Thursday, 2 May 13
Thursday, 2 May 13
Clients love to do a littlebit of web-designing.Thursday, 2 May 13
“Make the logo bigger!”No.Thursday, 2 May 13
“I want to use 24 pointComic Sans”No.Thursday, 2 May 13
“I want to edit my site inMicrosoft Word!”oh go on then ...Thursday, 2 May 13
Web designing.Just one of mymany skills.Thursday, 2 May 13
Why are we doing this?Thursday, 2 May 13
We should not be giving content editors atool to use to destroy their site.Thursday, 2 May 13
If you provide something better than theWord experience of website content-editing. Your users stop asking for Word.Thursd...
Thursday, 2 May 13
Thursday, 2 May 13
We cannot expect non-developers anddesigners to make sane decisions aboutdocument semantics.Thursday, 2 May 13
Thursday, 2 May 13
Thursday, 2 May 13
A CMS is not a websitedesign tool.Thursday, 2 May 13
If you wouldn’t give the client a copy ofDreamweaver & their site files, why givethem a CMS that attempts to mimic thatexpe...
Your CMS should be entirely focussedaround creating great quality content.Thursday, 2 May 13
Content editors are often the forgottenusers when we deploy a CMS.Thursday, 2 May 13
This is not a new problem.Thursday, 2 May 13
This is why we can’t have nice thingsThursday, 2 May 13
(probably not) Henry Ford.“If I had asked people what they wanted,they would have said faster horses.”Thursday, 2 May 13
What should the CMSuser experience be like?Thursday, 2 May 13
1. The CMS helps content editors makegood decisions.Thursday, 2 May 13
A CMS is often as much an enemy of goodcontent as it is of good design.Thursday, 2 May 13
- Karen McGranehttp://www.uie.com/brainsparks/2012/08/08/karen-mcgrane-content-strategy-for-mobile/“Let’s try to make the ...
2. The CMS allows the designer to makesemantic decisions so the editor doesn’thave to.Thursday, 2 May 13
Thursday, 2 May 13
3. The CMS protects the design andarchitecture decisions made for the siteThursday, 2 May 13
When we stop trying to give contenteditors a web design tool, we can focus ona system tailored to the type of contentthey ...
If content editors are not worrying abouthow it looks. They can add better contentmore quickly.Thursday, 2 May 13
You keep control of document semantics -can add Aria Roles, HTML5 elements,format dates for international audiences.Thursd...
Content is stored based on what it meansrather than how it looks.Thursday, 2 May 13
Structured content can be easilyrepurposed - on the site or for email,RSS, social media, another website.Thursday, 2 May 13
A big textarea to fill in page content is aterrible user experience.Content editors are our users too.Thursday, 2 May 13
An example.a structured content approach to image managementThursday, 2 May 13
greenbelt.org.ukThursday, 2 May 13
greenbelt.org.ukThursday, 2 May 13
greenbelt.org.ukThursday, 2 May 13
RequirementsMake it easy for content editors to explore the archiveand choose images without needing to maintain their own...
RequirementsWhen an image is used, if the template changes, we needto be able to regenerate the image at the new size.Thur...
RequirementsProvide a browseable library of images on the website,direct from the archive, that again could be regenerated...
RequirementsLeave the door open to provide a range of image assetsfor any one use of an image in a template - to enableret...
Greenbelt Media ServerThursday, 2 May 13
Greenbelt Media ServerThursday, 2 May 13
greenbelt.org.ukThursday, 2 May 13
Structured Contentnot a silver bullet.Thursday, 2 May 13
strong, emphasis, links, blockquotes,lists, inline images and filesThursday, 2 May 13
Avoid raw HTML being inserted into yourcontent at all costs.Thursday, 2 May 13
Your CMS should actively be removingHTML elements added by content editors(unless you really love 1997 markup)Thursday, 2 ...
MarkdownThursday, 2 May 13
markitup,jsalvat.comThursday, 2 May 13
We are solving thewrong problems.Thursday, 2 May 13
Our customers ask forfaster horses.Thursday, 2 May 13
Our customers ask for abetter WYSIWYG.Thursday, 2 May 13
Trying to make the CMS behave ‘likeWord’ is solving the wrong problem.Thursday, 2 May 13
Pouring energy into solutions that tie thecontent to one design or one output issolving the wrong problem.Thursday, 2 May 13
Turning a content management system intoa site building tool rather than a contentcreation tool is solving the wrong probl...
Seeing ourselves as the user, or the visitorsto the website as the user and ignoringcontent editors means we will continue...
The future of CMS?Thursday, 2 May 13
Karen McGrane - http://karenmcgrane.com/2011/12/14/mobile-content-strategy/“If we’re going to succeed in publishingcontent...
Use structured content wherever possibleThursday, 2 May 13
Avoid directly inserting HTML into contentThursday, 2 May 13
Treat content editors as your mostimportant user.Thursday, 2 May 13
Craft better experiences for content editorswithin the tools you useThursday, 2 May 13
If your CMS falls short tell the maker.Report user experience issues to opensource projects & CMS vendors just asyou would...
Difficult problemsThursday, 2 May 13
Hoe can we create a more elegant layeron top of structured content?Thursday, 2 May 13
Can we enable offline editing?Thursday, 2 May 13
Multilingual content?Internationalized sites.Thursday, 2 May 13
Let’s talk about this.Thursday, 2 May 13
Photo credits:http://www.flickr.com/photos/boston_public_library/7018116723/http://www.flickr.com/photos/jk_too/3300092780/T...
Upcoming SlideShare
Loading in...5
×

The Future of Content Management

636

Published on

Talk originally given at the Smashing Conference. Resources can be found at http://www.rachelandrew.co.uk/presentations/future-of-cms

Published in: Technology
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total Views
636
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
14
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "The Future of Content Management"

  1. 1. The Future ofContent ManagementRachel Andrew: Smashing Conference 2012Thursday, 2 May 13
  2. 2. edgeofmyseat.comThursday, 2 May 13
  3. 3. grabaperch.comThursday, 2 May 13
  4. 4. Question.Who here generally develops sites using some form ofcontent management system?Thursday, 2 May 13
  5. 5. Why don’t we talk aboutthis more?Thursday, 2 May 13
  6. 6. The trouble with contentmanagement systems.Thursday, 2 May 13
  7. 7. http://storify.com/rachelandrew/cms-horrors“Has your client ever done somethingreally odd using a CMS? Font horrors,giant images, crazy content? Id love toknow your stories.”Thursday, 2 May 13
  8. 8. Thursday, 2 May 13
  9. 9. Thursday, 2 May 13
  10. 10. Thursday, 2 May 13
  11. 11. Thursday, 2 May 13
  12. 12. Thursday, 2 May 13
  13. 13. Clients love to do a littlebit of web-designing.Thursday, 2 May 13
  14. 14. “Make the logo bigger!”No.Thursday, 2 May 13
  15. 15. “I want to use 24 pointComic Sans”No.Thursday, 2 May 13
  16. 16. “I want to edit my site inMicrosoft Word!”oh go on then ...Thursday, 2 May 13
  17. 17. Web designing.Just one of mymany skills.Thursday, 2 May 13
  18. 18. Why are we doing this?Thursday, 2 May 13
  19. 19. We should not be giving content editors atool to use to destroy their site.Thursday, 2 May 13
  20. 20. If you provide something better than theWord experience of website content-editing. Your users stop asking for Word.Thursday, 2 May 13
  21. 21. Thursday, 2 May 13
  22. 22. Thursday, 2 May 13
  23. 23. We cannot expect non-developers anddesigners to make sane decisions aboutdocument semantics.Thursday, 2 May 13
  24. 24. Thursday, 2 May 13
  25. 25. Thursday, 2 May 13
  26. 26. A CMS is not a websitedesign tool.Thursday, 2 May 13
  27. 27. If you wouldn’t give the client a copy ofDreamweaver & their site files, why givethem a CMS that attempts to mimic thatexperience?Thursday, 2 May 13
  28. 28. Your CMS should be entirely focussedaround creating great quality content.Thursday, 2 May 13
  29. 29. Content editors are often the forgottenusers when we deploy a CMS.Thursday, 2 May 13
  30. 30. This is not a new problem.Thursday, 2 May 13
  31. 31. This is why we can’t have nice thingsThursday, 2 May 13
  32. 32. (probably not) Henry Ford.“If I had asked people what they wanted,they would have said faster horses.”Thursday, 2 May 13
  33. 33. What should the CMSuser experience be like?Thursday, 2 May 13
  34. 34. 1. The CMS helps content editors makegood decisions.Thursday, 2 May 13
  35. 35. A CMS is often as much an enemy of goodcontent as it is of good design.Thursday, 2 May 13
  36. 36. - Karen McGranehttp://www.uie.com/brainsparks/2012/08/08/karen-mcgrane-content-strategy-for-mobile/“Let’s try to make the job for our contentcreators as easy as possible, and let’s buildthe tools and the infrastructure that weneed to support them in creating greatcontent.”Thursday, 2 May 13
  37. 37. 2. The CMS allows the designer to makesemantic decisions so the editor doesn’thave to.Thursday, 2 May 13
  38. 38. Thursday, 2 May 13
  39. 39. 3. The CMS protects the design andarchitecture decisions made for the siteThursday, 2 May 13
  40. 40. When we stop trying to give contenteditors a web design tool, we can focus ona system tailored to the type of contentthey need to create.Thursday, 2 May 13
  41. 41. If content editors are not worrying abouthow it looks. They can add better contentmore quickly.Thursday, 2 May 13
  42. 42. You keep control of document semantics -can add Aria Roles, HTML5 elements,format dates for international audiences.Thursday, 2 May 13
  43. 43. Content is stored based on what it meansrather than how it looks.Thursday, 2 May 13
  44. 44. Structured content can be easilyrepurposed - on the site or for email,RSS, social media, another website.Thursday, 2 May 13
  45. 45. A big textarea to fill in page content is aterrible user experience.Content editors are our users too.Thursday, 2 May 13
  46. 46. An example.a structured content approach to image managementThursday, 2 May 13
  47. 47. greenbelt.org.ukThursday, 2 May 13
  48. 48. greenbelt.org.ukThursday, 2 May 13
  49. 49. greenbelt.org.ukThursday, 2 May 13
  50. 50. RequirementsMake it easy for content editors to explore the archiveand choose images without needing to maintain their ownfolder of images.Thursday, 2 May 13
  51. 51. RequirementsWhen an image is used, if the template changes, we needto be able to regenerate the image at the new size.Thursday, 2 May 13
  52. 52. RequirementsProvide a browseable library of images on the website,direct from the archive, that again could be regeneratedif the templates changedThursday, 2 May 13
  53. 53. RequirementsLeave the door open to provide a range of image assetsfor any one use of an image in a template - to enableretina images or different images for screen widths/bandwidths.Thursday, 2 May 13
  54. 54. Greenbelt Media ServerThursday, 2 May 13
  55. 55. Greenbelt Media ServerThursday, 2 May 13
  56. 56. greenbelt.org.ukThursday, 2 May 13
  57. 57. Structured Contentnot a silver bullet.Thursday, 2 May 13
  58. 58. strong, emphasis, links, blockquotes,lists, inline images and filesThursday, 2 May 13
  59. 59. Avoid raw HTML being inserted into yourcontent at all costs.Thursday, 2 May 13
  60. 60. Your CMS should actively be removingHTML elements added by content editors(unless you really love 1997 markup)Thursday, 2 May 13
  61. 61. MarkdownThursday, 2 May 13
  62. 62. markitup,jsalvat.comThursday, 2 May 13
  63. 63. We are solving thewrong problems.Thursday, 2 May 13
  64. 64. Our customers ask forfaster horses.Thursday, 2 May 13
  65. 65. Our customers ask for abetter WYSIWYG.Thursday, 2 May 13
  66. 66. Trying to make the CMS behave ‘likeWord’ is solving the wrong problem.Thursday, 2 May 13
  67. 67. Pouring energy into solutions that tie thecontent to one design or one output issolving the wrong problem.Thursday, 2 May 13
  68. 68. Turning a content management system intoa site building tool rather than a contentcreation tool is solving the wrong problemThursday, 2 May 13
  69. 69. Seeing ourselves as the user, or the visitorsto the website as the user and ignoringcontent editors means we will continue totry and solve the wrong problems.Thursday, 2 May 13
  70. 70. The future of CMS?Thursday, 2 May 13
  71. 71. Karen McGrane - http://karenmcgrane.com/2011/12/14/mobile-content-strategy/“If we’re going to succeed in publishingcontent onto a million different newdevices and formats and platforms, weneed interfaces that will help guide contentcreators on how to write and structuretheir content for reuse.”Thursday, 2 May 13
  72. 72. Use structured content wherever possibleThursday, 2 May 13
  73. 73. Avoid directly inserting HTML into contentThursday, 2 May 13
  74. 74. Treat content editors as your mostimportant user.Thursday, 2 May 13
  75. 75. Craft better experiences for content editorswithin the tools you useThursday, 2 May 13
  76. 76. If your CMS falls short tell the maker.Report user experience issues to opensource projects & CMS vendors just asyou would any other bug.Thursday, 2 May 13
  77. 77. Difficult problemsThursday, 2 May 13
  78. 78. Hoe can we create a more elegant layeron top of structured content?Thursday, 2 May 13
  79. 79. Can we enable offline editing?Thursday, 2 May 13
  80. 80. Multilingual content?Internationalized sites.Thursday, 2 May 13
  81. 81. Let’s talk about this.Thursday, 2 May 13
  82. 82. Photo credits:http://www.flickr.com/photos/boston_public_library/7018116723/http://www.flickr.com/photos/jk_too/3300092780/Thank you@rachelandrewhttp://rachelandrew.co.uk/presentations/smashing-confThursday, 2 May 13
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×