The Future of Content Management
Upcoming SlideShare
Loading in...5
×
 

The Future of Content Management

on

  • 502 views

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

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

Statistics

Views

Total Views
502
Views on SlideShare
502
Embed Views
0

Actions

Likes
2
Downloads
8
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

The Future of Content Management The Future of Content Management Presentation Transcript

  • 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 images, crazy content? Id love toknow your stories.”Thursday, 2 May 13
  • 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.Thursday, 2 May 13
  • 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 thatexperience?Thursday, 2 May 13
  • 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 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
  • 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 need to create.Thursday, 2 May 13
  • 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.Thursday, 2 May 13
  • 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 ownfolder of images.Thursday, 2 May 13
  • 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
  • RequirementsProvide a browseable library of images on the website,direct from the archive, that again could be regeneratedif the templates changedThursday, 2 May 13
  • 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
  • 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 May 13
  • 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 problemThursday, 2 May 13
  • 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
  • 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 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
  • 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 any other bug.Thursday, 2 May 13
  • 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/Thank you@rachelandrewhttp://rachelandrew.co.uk/presentations/smashing-confThursday, 2 May 13