BRIDGING THE GAP BETWEEN THE COMMUNITY AND THE END USER. THE STORY OF SPARK.

7/30/2019 BRIDGING THE GAP BETWEEN THE COMMUNITY AND THE END USER. THE STORY OF SPARK.

1/23

CONNECTING THEAUTHOR & THECOMMUNITY

The story of Spark


2/23

You dont need a Drupal.org IDto be part of the com

project lead

site admiD.O members

community

Admins

Authors


3/23

JESSE BEACH

DRIES BUYTAERT

KEVIN OLEARY

ANGELA BYRON

GABOR HOJTSY

PRESTON SO

THE SPARKTEAM

DHARMESH MISTRY


4/23

WHAT IS SPARK?

SPARK IS A PROJECT TO IMPROVE THE

AUTHORING EXPERIENCE IN DRUPAL 8Initiated at Acquia by Dries Buytaert with the goalof accelerating feature improvement in Drupalspecifically around the content authoring for the nontechnical user.


5/23

DRUPAL IS ACONTENT MANAGEMENT

OUR COMPETITORS WERE EATING OUR

1.

2.

WHYCONTENT

AUTHORING?


6/23

STRENGTHS &WEAKNESSES

0

1

2

3

4

5

6

7

8

Sitecore

CQ5

Plone

Squiz

Wordpress

Joomla

Drupal

Open Text

Technical strength

0

1

2

3

4

5

6

7

8

Sitecore

Wordpress

Joomla

Drupal

Open Text

Authoring experience


7/23

PEER

TOPE

ER

DEVELO

PEREXPE

RIEN

CE

INSTALLATIO

N

THEM

ING

LAYO

UT

DRAG

DRO

PFIELDS

FORMBUILDER

UI

MULTIP

LEFILE

UPL

OAD

DRUP

ALCOM

MER

CE

WHAT WE COULD HAVE DONE(WITH UNLIMITED TIME)

INF

ORMATIONAR

CHITEC

TURE

MODULEUS

ABILITY

RE-DES

IGNE

DFIELDUI

ORGANICGR

OUPS

ICON

FONTS

CONT

ENTSTRA

TEGY

RESP

ONSIVE

VIDEO

HTML5

CANVA

S

SEMANTICMARK U

USER

WORKFLO

W S

MU L

SABILIT

Y

TSTAGING

XONO

MYAC

CESCONT

ROL

DESIGN

INTHE

BRO

WSER


8/23

IN PLACE EDIT EVERYTHING

RESPONSIVE TOOLS EVERYWHERE

ACESSIBILITY

WHAT WE DID IN DRUPAL 7(IN ABOUT A YEAR)

WYSIWYG IN CORE

DRAG-DROP LAYOUTS

EMBER ADMIN THEME

WHAT IS IN DRUPAL 8(QUITE A BIT)

MULTILINGUAL

DRAG-DROP LAYOUTS

EMBER ADMIN THEME

MULTILINGUAL


9/23

COGNITIVE BIAS

Not invented here.The tendencypeople to prefer their own ideas

those of others, regardless of the

actual validity.


10/23

THE SOLUTION

First arrive at consensus on a toolthen figure out how to make it work

for the user in a sensible, semantic,

responsive and accessible way.

WYSIWYG INCORE

THE PROBLEM

Out-of-the-box we did not have a

way for users to format content

apart from writing HTMLandthe

process of installing a WYSIWYG

was really hard.

How do I format my cThis is what I wa

And th


11/23

WHO CONTRIBUTED

sun BojhanTwoD quicksketch

Falcon03

EverZufe

mgifford


12/23

WHAT WE DID

We had to disappoint some

awesome people who spent a

great deal of time and effort

working with us.

Be open to idea

the team. Disco

that present po

stealth launch o

We were able to re-examine our

initial assumptions about what

the right approach was and

turn around a good solution.

WHAT WENT RIGHT WHAT WENT WRONG WHAT WE LEA


13/23

COGNITIVE BIAS

The curse of knowlege effect.

The closer you get to a problem

greater your risk of overlooking a

obvious solution.


14/23

THE SOLUTION

Design a best-of-breed solution that

meets the expectations of the user

and overcome the technical hurdles

of altering content that has theme

styles applied to it.

EDIT IN PLACE

THE PROBLEM

In Drupal 7 the ONLY place to edit

anything is in an administrative

form. Editing content in place was

considered by many to be

impossible, but for the content

author this was a big need.want to ed

No


15/23

WHO CONTRIBUTED

sun Bojhanquicksketchyched

Catch David

Rothstien


16/23

BUT WAIT

ISNT EDIT-IN-PLACE

BAD FOR STRUCTURED CONTE


17/23

WHAT WE DID

If anything we underestimated

the complexity of the

implementation especially when

it comes to things like views.

We overlooked issues around

multiple contexts which we will

address in future version.

User testing an

great but we ne

all of the person

organization.

Users only tell y

want not what i

for them.

We were able to iterate on a

problem and produce designs

that worked well in testing.

Our implementation caused us

to fundamentally rework big

parts of Drupal to the benefit

of everyone.



18/23

COGNITIVE BIAS

Sunk loss fallacy.The resistance

abandoning existing work and st

from scratch even if all evidence

that it makes sense and would ta

less time to complete.


19/23

THE SOLUTION

Make the Drupal toolbar responsive,

simpler and easier to use, with

understandable iconography, fewer

options and larger touch targets.

RESPONSIVETOOLBAR

THE PROBLEM

The toolbar in Drupal 7 not

responsive, which made it close to

unusable on a phone. Configuring a

site on a phone is an edge case but

authoring content on a phone is

becoming increasingly common

very


20/23

WHO CONTRIBUTED

SunBojhanLewisNyman

EverettZufelt

BenjiFisher

yoroy useradvocate


21/23

WHAT WE DID

We waited too long to ask for

help and get designs in front of

people who had a vested

interest in participating.

We failed to successfully

separate the design process

from implementation.

Get buy in as ea

Abstract desig

development pr

We were able to consolidate

several divergent approaches

into a unified solution that will

serve us well into the future.



22/23

THANK

YOU

www.sparkdrupal.com


23/23

BY THE WAY

ACQUIA IS HIRING

Visit our booth or www.acquia.com for more information

BRIDGING THE GAP BETWEEN THE COMMUNITY AND THE END USER. THE STORY OF SPARK.

Documents

Transcript of BRIDGING THE GAP BETWEEN THE COMMUNITY AND THE END USER. THE STORY OF SPARK.