26. A CMS is not a website
design tool.
Thursday, 2 May 13
27. If you wouldn’t give the client a copy of
Dreamweaver & their site files, why give
them a CMS that attempts to mimic that
experience?
Thursday, 2 May 13
28. Your CMS should be entirely focussed
around creating great quality content.
Thursday, 2 May 13
29. Content editors are often the forgotten
users when we deploy a CMS.
Thursday, 2 May 13
39. 3. The CMS protects the design and
architecture decisions made for the site
Thursday, 2 May 13
40. When we stop trying to give content
editors a web design tool, we can focus on
a system tailored to the type of content
they need to create.
Thursday, 2 May 13
41. If content editors are not worrying about
how it looks. They can add better content
more quickly.
Thursday, 2 May 13
42. You keep control of document semantics -
can add Aria Roles, HTML5 elements,
format dates for international audiences.
Thursday, 2 May 13
43. Content is stored based on what it means
rather than how it looks.
Thursday, 2 May 13
44. Structured content can be easily
repurposed - on the site or for email,
RSS, social media, another website.
Thursday, 2 May 13
45. A big textarea to fill in page content is a
terrible user experience.
Content editors are our users too.
Thursday, 2 May 13
50. Requirements
Make it easy for content editors to explore the archive
and choose images without needing to maintain their own
folder of images.
Thursday, 2 May 13
51. Requirements
When an image is used, if the template changes, we need
to be able to regenerate the image at the new size.
Thursday, 2 May 13
52. Requirements
Provide a browseable library of images on the website,
direct from the archive, that again could be regenerated
if the templates changed
Thursday, 2 May 13
53. Requirements
Leave the door open to provide a range of image assets
for any one use of an image in a template - to enable
retina images or different images for screen widths/
bandwidths.
Thursday, 2 May 13
66. Trying to make the CMS behave ‘like
Word’ is solving the wrong problem.
Thursday, 2 May 13
67. Pouring energy into solutions that tie the
content to one design or one output is
solving the wrong problem.
Thursday, 2 May 13
68. Turning a content management system into
a site building tool rather than a content
creation tool is solving the wrong problem
Thursday, 2 May 13
69. Seeing ourselves as the user, or the visitors
to the website as the user and ignoring
content editors means we will continue to
try and solve the wrong problems.
Thursday, 2 May 13
71. Karen McGrane - http://karenmcgrane.com/2011/12/14/mobile-content-strategy/
“If we’re going to succeed in publishing
content onto a million different new
devices and formats and platforms, we
need interfaces that will help guide content
creators on how to write and structure
their content for reuse.”
Thursday, 2 May 13
76. If your CMS falls short tell the maker.
Report user experience issues to open
source projects & CMS vendors just as
you would any other bug.
Thursday, 2 May 13