• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Choosing the right Content Management System
 

Choosing the right Content Management System

on

  • 5,511 views

My talk from the Highland Fling Conference 2011

My talk from the Highland Fling Conference 2011

Statistics

Views

Total Views
5,511
Views on SlideShare
5,278
Embed Views
233

Actions

Likes
11
Downloads
77
Comments
0

15 Embeds 233

http://lanyrd.com 67
http://thesmu.tumblr.com 62
http://paper.li 52
url_unknown 11
http://www.pinterest.com 7
http://ayudamutuapadresenprocesodeduelo.blogspot.com 6
http://dev.springcorp.co.uk 6
http://pinterest.com 5
http://twitter.com 5
https://twitter.com 4
http://zootool.com 3
http://newsrivr.com 2
http://www.tumblr.com 1
http://us-w1.rockmelt.com 1
http://www.slideshare.net 1
More...

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

    Choosing the right Content Management System Choosing the right Content Management System Presentation Transcript

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