The document discusses author experience in content management systems. It argues that the purpose of a CMS is to facilitate managing content through its entire lifecycle from creation to archiving. It emphasizes that author experience needs to consider the needs of authors, businesses, workflows and end-users. Key aspects of good author experience include consistent and easy-to-use interfaces, domain-modeled processes, and producing personalized and adaptive content for end-users across all channels and devices.
2. Rick Yagodich
17 years in the web
Founder of Excolo
Author of:
AUTHOR EXPERIENCE:
bridging the gap between people and
technology in content management
Twitter: @think_info
@think_info
3. What we will cover
Quiz?
For authors
For business For workflow
For end-users
What?
@think_info
10. Quiz
What is the purpose of a CMS?
To be the butt of a bad joke?
There’s a reason they call it a
@think_info
11. Quiz
What is the purpose of a CMS?
The purpose of a content management system is
to facilitate the human process
of managing the communication content lifecycle
from creation, through use, to archiving
@think_info
12. Communication
Facilitate the human
process of managing
content
For authors
For business For workflow
For end-users
Creating content
for the end-user
experience
@think_info
14. If there’s only one output, store in the output format, and input directly to that format too.
Communication
@think_info
15. To output to multiple channels, you need a translation layer, and adaptive-optimised storage.
Communication
@think_info
16. Adaptive-optimised storage is complex. A translation layer is needed to manage it cleanly.
Communication
@think_info
17. Author experience for authors
Facilitate the human
process of managing
content
For business For workflow
For end-users
Creating content
for the end-user
experience
For authors
@think_info
18. Author experience for authors
Defining author
An author is anyone who uses
the author environment
of the content management system
@think_info
19. Author experience for authors
Fit-for-purpose
language
Constent
decoupling
Design
patterns
• Domain-modelled
interface copy
• Consistent
terminology
• Consistent
paradigms
• Content only
• No presentation
• One context at a
time (by default)
• No access to source
code
• Ease of learning;
occasional use effort
• Consistent
approaches
• Domain-modelled
interface logic
• Tools that help
@think_info
20. For authors
Author experience for the business
Facilitate the human
process of managing
content
For workflow
For end-users
Creating content
for the end-user
experience
For business
@think_info
21. Author experience for the business
Frustration erodes
quality
Consistency and
reuse
Multi-channel
content
• Poor systems
frustrate
• Frustrated users pay
less attention
• Distracted users
make mistakes
• No per-channel
content
• Content model
designed for
repurosing
• The same message
everywhere
• Adaptive content
• Contextual delivery
@think_info
22. For authors
Author experience for the business
Facilitate the human
process of managing
content
For end-users
Creating content
for the end-user
experience
For business For workflow
@think_info
23. Author experience for workflow
More than
approvals
Domain-modelled
process
Holistic
systems
• Work flows
between content
variants
(SME, edited,
segmented, etc)
• Modelled
business
processes
• Designed for the
specific business’
needs
• Enhancing off-line
processes
• The entire
content
ecosystem
considered
• A model for
different
environment to
communicate
Bridging comms
silos
• Highly structured
content
• Distributed
authoring
responsibility
• Repurposed
content
@think_info
24. For authors
Author experience for the end-user
Facilitate the human
process of managing
content
For workflow
Creating content
for the end-user
experience
For business
For end-users
@think_info
25. Author experience for the end-user
Personalised &
adaptive content
Any channel,
any device
Content
consistency
• Granular content
adapts
• Behaviour- and
context-based
profiling
• More intelligent
content delivery
• Reduction of page
parity
• Optimised journeys
• Appropriate
interaction models
• End-user choice
• All content
everywhere (but
different sized
chunks)
• No channel
penalties
@think_info
26. In summary
Facilitate the human
process of managing
content
Creating content
for the end-user
experience
For authors
For business For workflow
For end-users
@think_info
27. Author Experience
• Available 13 October 1014
• Published by XML Press
• Part of the Content Wrangler series on
Content Strategy
• http://theAXbook.com/
@think_info
28. Questions?
Facilitate the human
process of managing
content
Creating content
for the end-user
experience
For authors
For business For workflow
For end-users
@think_info
Notes de l'éditeur
Ease of use – meta-documentation. What is the platform you use to create documentation like? Do you need to refer to its documentation?