State of the inline debate
•
6 j'aime•2,810 vues
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
Recommandé
Contenu connexe
Similaire à State of the inline debate
Similaire à State of the inline debate (20)
Plus de Rasmus Skjoldan
Plus de Rasmus Skjoldan (11)
Dernier
Dernier (20)
State of the inline debate
- 1. State of the inline debate A.K.A: “WYSIWTFFTWOMGROFL” Rasmus Skjoldan @ Jboye CMS Experts Europe, Oracle – october 2013
- 3. I’m a UX’er. Not technical and very bad at numbers (80% out of 5500 and you’ve lost me – and who is this JSON guy really?)
- 4. How on earth did we start debating inline?
- 5. Mobile changed desktop web from 1 – to many
- 6. The WYSIWYG editing dream turned into a nightmare when embracing COPE
- 8. WYSIWYG inline editing makes users forget metadata (oh no!)
- 9. “The era where we privilege the desktop web interface above all others is over”
- 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
- 17. Karen says hi...
- 19. Is preview even possible?
- 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
- 26. Previewing is no fun when it’s an after-thought
- 27. From edit to preview and back “oh no, I have to go back and fix that typo”
- 28. The first Neos workflow from editing to previewing:
- 29. The state of the inline debate is… *Drumroll*
- 30. It’s not about inline editing!
- 31. It’s about tailoring the authoring experience on a whole new level
- 32. Examples...
- 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.
- 34. How will this look on Little Printer?
- 35. Integrator decides on editing and previewing together with client:
- 37. Customized backend template for simple content variant:
- 38. User can customize preview presets:
- 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