CHOOSING THE RIGHT

CONTENT

MANAGEMENT SYSTEM

Friday, 8 July 2011

RACHEL ANDREW

@rachelandrew

http://rachelandrew.co.ukhttp://edgeofmyseat.comhttp://grabaperch.com

Friday, 8 July 2011

WHAT IS A CMS?(for the purposes of this presentation)

Friday, 8 July 2011

A TOOL FOR CONTENT

EDITINGBy non-technical usersVia some kind of web-based admin

Friday, 8 July 2011

YOUR CMS IS AN

IMPORTANT PART OF

YOUR SOLUTION

Friday, 8 July 2011

ONE-SIZE DOES NOT

FIT ALL.

Friday, 8 July 2011

WHAT DOES THIS

PROJECT NEED?

Friday, 8 July 2011

HOSTING

Friday, 8 July 2011

LANGUAGEPHP, .NET, Ruby, Python ...

Friday, 8 July 2011

OTHER TECHNICAL REQUIREMENTSWorking with existing software, user logins

Friday, 8 July 2011

WHO WILL EDIT THIS?

Friday, 8 July 2011

HOW MANY EDITORS?and do they need protecting from each other

Friday, 8 July 2011

SKILLSNot just technical skills

Friday, 8 July 2011

PREFERENCESWhat do they love? What do they hate? Find and fix the pain points.

Friday, 8 July 2011

THE PROJECT SPECWhat requirements does this site have?

Friday, 8 July 2011

SIMPLE PAGE-BASEDAn obvious hierarchical site map

Friday, 8 July 2011

BLOG-CENTRICWhere a blog or blogs are the main feature

Friday, 8 July 2011

COMPLEX CONTENT

STORAGE REQUIREMENTA huge amount of content - not necessarily page-based

Friday, 8 July 2011

CMS SECONDARY TO MAIN APPLICATIONUsed for editing bits of content in an app.

Friday, 8 July 2011

OTHER FEATURESGalleries, news updates, e-commerce, calendars ... what else?

Friday, 8 July 2011

VISITOR NUMBERSHow 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

COPYWRITER

Friday, 8 July 2011

YOUR CMS SHOULD

SUPPORT THE

CONTENT STRATEGY

Friday, 8 July 2011

YOUR CLIENT IS

(PROBABLY) NOT A

DESIGNER

Friday, 8 July 2011

YOUR CMS SHOULD

MAINTAIN THE

DESIGN & TYPOGRAPHY

Friday, 8 July 2011

DEFAULT TO THE

SIMPLEST THING

POSSIBLE

Friday, 8 July 2011

USERS SHOULD NOT

NEED TO UNDERSTAND

THE DATABASE

Friday, 8 July 2011

THE SOLUTION TO ONE

PROBLEM IS NOT THE

SOLUTION TO ALL.

Friday, 8 July 2011

THE CURSE OF

WYSIWYG

Friday, 8 July 2011

YOUR CLIENT IS

(PROBABLY) NOT A

DESIGNER

Friday, 8 July 2011

ckeditor

Friday, 8 July 2011

Emoticons anyone?

Friday, 8 July 2011

Comic Sans please

Friday, 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

PREMISE

Friday, 8 July 2011

WYSIWYG CREATES

NON-REUSABLE DATA

Friday, 8 July 2011

This looks like contact information

Friday, 8 July 2011

But is it really?

Friday, 8 July 2011

WYSIWYG MIXES

CONTENT AND

PRESENTATION

Friday, 8 July 2011

WYSIWYG PROMOTES

STYLE OVER

CONTENT

Friday, 8 July 2011

SO WHAT SHOULD WE

DO?

Friday, 8 July 2011

STRUCTURED CONTENT

Friday, 8 July 2011

Contact information?

Friday, 8 July 2011

Add a contact

Friday, 8 July 2011

The Contact on a web page

Friday, 8 July 2011

Contact mark-up

Friday, 8 July 2011

SUPPORT THE CONTENT

STRATEGY WITH

STRUCTURED CONTENT

Friday, 8 July 2011

MAINTAIN THE DESIGN -

EDITORS ENTER

CONTENT - NOT MARKUP

Friday, 8 July 2011

STRUCTURED CONTENTremoves the need for editors to think about how it looks.

Friday, 8 July 2011

STRUCTURED CONTENTcan promote the content strategy and offer help and advice in the form for novice copywriters

Friday, 8 July 2011

STRUCTURED CONTENTallows you to store data in a way that describes what it is - so it can be easily reused

Friday, 8 July 2011

STRUCTURED CONTENTprevents a mess of html ending up in your database, making it easier to re-present that content elsewhere

Friday, 8 July 2011

SIMPLE FORMATTING

Friday, 8 July 2011

MARKITUPhttp://markitup.jaysalvat.com/home/

Friday, 8 July 2011

WYSIWYMWhat You See Is What You MEAN

Friday, 8 July 2011

PREVIEW

Friday, 8 July 2011

VIEW CHANGES IN

CONTEXT

Friday, 8 July 2011

“IN-CONTEXT” EDITING

Friday, 8 July 2011

ONLY WORKS FOR VERY

SIMPLE SITES

Friday, 8 July 2011

PROMOTES THINKING

ABOUT STYLE RATHER

THAN CONTENT

Friday, 8 July 2011

REQUIRES JAVASCRIPT

AND MAY CONFLICT

WITH SITE JAVASCRIPT

Friday, 8 July 2011

USE WITH CAUTIONhttp://allinthehead.com/retro/357/the-lure-of-on-page-editing

Friday, 8 July 2011

BE UNASHAMED TO BE

THE EXPERT

Friday, 8 July 2011

BUT, WHAT IS THE RIGHT

CMS FOR MY PROJECT?

Friday, 8 July 2011

A CMS THAT DOES NOT

FORCE YOU TO

COMPROMISE

Friday, 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 MAKERS

Friday, 8 July 2011

NEVER SETTLE FOR

‘GOOD ENOUGH’

Friday, 8 July 2011

HIGHLIGHT GOOD PRACTICE...and file bugs and complain about outdated, crufty systems

Friday, 8 July 2011

THANK YOU@rachelandrewPhotos: 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