+ All Categories
Home > Technology > Gilbane 2013: To WYSIWYG or not WYSIWYG

Gilbane 2013: To WYSIWYG or not WYSIWYG

Date post: 08-May-2015
Category:
Upload: tom-wentworth
View: 354 times
Download: 3 times
Share this document with a friend
Description:
Presentation from Gilbane 2013
36
1 To WYSIWYG or Not WYWIWYG That is the Question Tom Wentworth Chief Marketing Officer, Acquia @twentworth12
Transcript
Page 1: Gilbane 2013: To WYSIWYG or not WYSIWYG

1

To WYSIWYG or Not WYWIWYGThatis the Question

Tom WentworthChief Marketing Officer, Acquia@twentworth12

Page 2: Gilbane 2013: To WYSIWYG or not WYSIWYG

2

About Me

• 14 years in CMS– CMO at Acquia– Prior CMO at Ektron– Led Technical Sales at

HP/Autonomy/Interwoven

• World Record Holder in CMS Editor demos– *Verification Pending

• @twentworth12 for CMS industry thoughts and general hilarity on Twitter

Page 3: Gilbane 2013: To WYSIWYG or not WYSIWYG

3

Page 4: Gilbane 2013: To WYSIWYG or not WYSIWYG

4

Page 5: Gilbane 2013: To WYSIWYG or not WYSIWYG

5

Page 6: Gilbane 2013: To WYSIWYG or not WYSIWYG

6

Content Strategists like Karen McGrane

CMS Vendors, Products, and

Usersvs.

Page 7: Gilbane 2013: To WYSIWYG or not WYSIWYG

7

Page 8: Gilbane 2013: To WYSIWYG or not WYSIWYG

8

“We allow content creators to embed layout and styling information directly into their content.

Unfortunately, the code added by content creators can be at odds with the style sheet, and it’s difficult for developers to parse what’s style and what’s substance.

When it comes time to put that content on other platforms, we wind up with a muddled mess.”- Karen McGrane

Page 9: Gilbane 2013: To WYSIWYG or not WYSIWYG

9

Page 10: Gilbane 2013: To WYSIWYG or not WYSIWYG

10

Page 11: Gilbane 2013: To WYSIWYG or not WYSIWYG

CMS Product Selections are

made on Usability

And that usually means WYSIWYG

Editor Demos

Page 12: Gilbane 2013: To WYSIWYG or not WYSIWYG

12

Page 13: Gilbane 2013: To WYSIWYG or not WYSIWYG

13

We’ve Come to Expect Content and Presentation to be Combined

Page 14: Gilbane 2013: To WYSIWYG or not WYSIWYG

14

But This Approach Came With Tradeoffs

Page 15: Gilbane 2013: To WYSIWYG or not WYSIWYG

15

“Make it as Easy as Word!”

• Formatting• Styling• Layout• and Comic

Sans MS!

Page 16: Gilbane 2013: To WYSIWYG or not WYSIWYG

16

“And Let Me Preview the Page When I’m Done!”

Page 17: Gilbane 2013: To WYSIWYG or not WYSIWYG

17 Source: geocitiesizer

So, What’s Wrong with Making Things Easy?

Page 18: Gilbane 2013: To WYSIWYG or not WYSIWYG

18

Page 19: Gilbane 2013: To WYSIWYG or not WYSIWYG

19

…My Name is Tom

…Her name is Blake

… And I’m a Glasshole

Page 20: Gilbane 2013: To WYSIWYG or not WYSIWYG

20

Page 21: Gilbane 2013: To WYSIWYG or not WYSIWYG

21

Content as an API

Page 22: Gilbane 2013: To WYSIWYG or not WYSIWYG

22

Page 23: Gilbane 2013: To WYSIWYG or not WYSIWYG

23

Page 24: Gilbane 2013: To WYSIWYG or not WYSIWYG

content strategy is to copywriting as information

architecture is to design

Source: http://boxesandarrows.com/content-strategy-the-philosophy-of-data/

Page 25: Gilbane 2013: To WYSIWYG or not WYSIWYG

25

The Current State of Content Authoring• Structured Authoring– Separation of content from presentation e.g.

“chunks”

• WYSIWYG Authoring– Mixed content and formatting e.g. “blobs”– Embedded Rich Text Editors

• Inline Editing– Content editing within page layout– Can be structured or WYSIWYG

• WYSIWYG Page Layout– Visual page layout

Page 26: Gilbane 2013: To WYSIWYG or not WYSIWYG

26

Structured Authoring

• Complete separation of content from presentation

• Encourages users to think only about content

• Defines content and metadata

• Small design changes require developers

Ektron SmartForms

Page 27: Gilbane 2013: To WYSIWYG or not WYSIWYG

27

Structured with WYSIWYG

• Content types with a mix of “chunks” and “blobs”

• Simple (Title + Body) or complex

• Rich Text Editors– Aloha, CKEditor,

TinyMCE, EditLive, … Drupal

Page 28: Gilbane 2013: To WYSIWYG or not WYSIWYG

28

Inline Editing in Drupal:“Chunks” and “Blobs”

• Allows users to make changes right on the page

• Appeals to less technical authors

• Can be confusing, since a single in-context edit can update lots of pages

Drupal

Page 29: Gilbane 2013: To WYSIWYG or not WYSIWYG

29

WYSIWYG Page Layout

• Let’s the users manage both content and design

• Drag+Drop Page Assembly• Can complete break brand

consistency

Page 30: Gilbane 2013: To WYSIWYG or not WYSIWYG

30

Adobe AEM

Page 31: Gilbane 2013: To WYSIWYG or not WYSIWYG

31

HP/Autonomy TeamSite SitePublisher

Page 32: Gilbane 2013: To WYSIWYG or not WYSIWYG

32

Sitecore

Page 33: Gilbane 2013: To WYSIWYG or not WYSIWYG

The editing interfaces we offer to users send them important

messages, whether we intend it or not.

They are affordances, like knobs on doors and buttons on telephones.

If the primary editing interface we present is also the visual design seen by site visitors, we are saying: “This page is what you manage! The things

you see on it are the true form of your content.”

- Source: Jeff Eaton, Lullabot

Page 34: Gilbane 2013: To WYSIWYG or not WYSIWYG

34

Solution: Let’s Make Smarter Authors and Pick the Right Tool for the Job

1. To WYSIWYG or not WYSIWYG

– Structured content authoring is the best way to future proof your content strategy

– There are valid use cases combined content and formatting. Brochure-ware websites aren’t going away.

– Editors used to stink, and now they don’t. It’s much easier to enforce clean markup.

2. In-line Editing is Okay. But be Smart About It

3. We Need to Reset Expectations about Content Preview

– WYISWYMGTOPIOC

4. Be very Careful when Using Visual Page Assembly

Page 35: Gilbane 2013: To WYSIWYG or not WYSIWYG

35

and When Selecting Your Next CMSEvaluate Usability, Not Curb Appeal

Page 36: Gilbane 2013: To WYSIWYG or not WYSIWYG

36

Thanks!

Tom WentworthChief Marketing Officer, Acquia@twentworth12


Recommended