State of the inline debate presented at Oracle, Utrecht at a J.Boye CMS Experts Europe meeting.
More info:
http://jboye.com/groups/group-list/cms-expert-group
http://rasmusskjoldan.com
12. So I asked @eaton on his take on the State of the inline debate and gave him
write-access to these slides. Here’s what he wrote:
“Visual layout tools will always be with us, but the
explosion of channels and devices means that
many organizations will have to find a different
way.
Short-lived marketing content and page-focused
tools are an easy fit. But for businesses that treat
their content as a long-term asset, tools that
prioritize the underlying meaning are critical.”
Jeff Eaton
13. Ugly arrow points
to important part
http://buytaert.net/wysiwyg-and-in-place-editing-for-structured-
14. Leisa Reichelt told me:
“Commit to
multi-channel”
PS: “You will fail. Miserably.”
15. Where to draw the lines?
Long-lived content /
Known channels /
Purified content /
Content stays /
Short-lived content
Unknown channels
Social updates
Templates die
20. How do you preview
content in an unknown
or future channel?
21. “Creators need an immediate
connection to what they create”
http://vimeo.com/36579366
22. My own principle building TYPO3 Neos:
Creators need
to experiment
with content
in different
contexts
23. * Breaking * Breaking * Breaking *
Preview is not
just about
devices
24. Previewing is many
different things...
● Content in one particular context
● Same content via different templates
● Same content on different websites
● Same content on entirely different channels
● Search appearances
● Social media appearances
● Personalized, differentiated versions
● A/B testing variants
● Different workflow previews
● Languages
● …and yes, devices & responsive widths
33. Let user experiment with
editing and previewing in different ways
Experiment, fail, fail, fail, succeed...
Here you have inline editing but in an abstract view.
No in-page editing but inline in a backend mode.
39. To Inline or not to Inline
is not the question
/ In many cases you’ll have to include possibilities of both
WYSIWYG inline and more abstract interfaces
/ Tailor the authoring experience on project-basis
/ Sometimes you need inline, in-page editing
– sometimes you don’t