Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

State of the inline debate


Published on

State of the inline debate presented at Oracle, Utrecht at a J.Boye CMS Experts Europe meeting.

More info:

Published in: Technology

State of the inline debate

  1. 1. State of the inline debate A.K.A: “WYSIWTFFTWOMGROFL” Rasmus Skjoldan @ Jboye CMS Experts Europe, Oracle – october 2013
  2. 2. 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?)
  3. 3. How on earth did we start debating inline?
  4. 4. Mobile changed desktop web from 1 – to many
  5. 5. The WYSIWYG editing dream turned into a nightmare when embracing COPE
  6. 6. COPE this dude!
  7. 7. WYSIWYG inline editing makes users forget metadata (oh no!)
  8. 8. “The era where we privilege the desktop web interface above all others is over”
  9. 9. WYSIWTF
  10. 10. Jeff Eaton
  11. 11. 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
  12. 12. Ugly arrow points to important part
  13. 13. Leisa Reichelt told me: “Commit to multi-channel” PS: “You will fail. Miserably.”
  14. 14. Where to draw the lines? Long-lived content / Known channels / Purified content / Content stays / Short-lived content Unknown channels Social updates Templates die
  15. 15. WYSIFTW
  16. 16. Karen says hi...
  17. 17. Mark Boulton said:
  18. 18. Is preview even possible?
  19. 19. How do you preview content in an unknown or future channel?
  20. 20. “Creators need an immediate connection to what they create”
  21. 21. My own principle building TYPO3 Neos: Creators need to experiment with content in different contexts
  22. 22. * Breaking * Breaking * Breaking * Preview is not just about devices
  23. 23. 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
  24. 24. Editing and previewing are intimately connected
  25. 25. Previewing is no fun when it’s an after-thought
  26. 26. From edit to preview and back “oh no, I have to go back and fix that typo”
  27. 27. The first Neos workflow from editing to previewing:
  28. 28. The state of the inline debate is… *Drumroll*
  29. 29. It’s not about inline editing!
  30. 30. It’s about tailoring the authoring experience on a whole new level
  31. 31. Examples...
  32. 32. 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.
  33. 33. How will this look on Little Printer?
  34. 34. Integrator decides on editing and previewing together with client:
  35. 35. Variations are endless
  36. 36. Customized backend template for simple content variant:
  37. 37. User can customize preview presets:
  38. 38. 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
  39. 39.