►
From YouTube: Backdrop Design & UX - Apr 25
Description
Today’s design agenda: http://bit.ly/2U0TeyM
B
B
Windows
open,
but
then
let
me
first
start
with
the
jackhammer
okay,
so
hopefully
no
more
terrible
fixes
so
I've
put
a
whole
bunch
of
Drupal
7
upgrade
stuff
in
here,
which
I'm
not
entirely
sure
is
related
to
usability.
It's
more
documentation,
stuff
but
I
think
trying
to
figure
out
like
how
and
where
we're
gonna
put
the
documentation
in
places
or
people.
Gonna
I
mean
it's
useful
to
be
related,
so
we
can
talk
a
little
bit
about
that,
so
starting
with
vector
of
CMS
to
org.
B
We
have
this
huge
block
on
the
home
page
now
that
talks
about
upgrading
from
triple7,
with
a
number
of
watches
included
in
core
the
number
of
modules
that
are
ready
for
backdrop
and
some
other
statistics
which
I've
forgotten
right
now
and
last
week
we
talked
about
adding
links.
So
each
one
of
those
numbers
or
headings
will
take
you
to
the
page
on
Doctor
of
CMS
org,
where
more
information
can
be
found
about
each
of
those
statistics
which
I
think
is
good
and
then.
B
I
added
two
new
items
that
jammed
today
that
came
up
based
on
all
trying
to
use
our
documentation
instructions
on
how
to
upgrade
from
circle.
To
backdrop,
one
of
the
things
that
he
pointed
out
that
I
thought
was
really
interesting
was
that
we
have
mentioned
all
these
modules
are
included
in
core.
But
how
do
you
upgrade
them
might
vary
depending
on
the
module
like?
Sometimes
you
just
leave
out
the
module
and
you
wanna
run
the
upgrade
and
vegetable.
Can
the
data
for.
C
B
Sometimes
you
have
to
like
delete
and
uninstall
the
module
and
then
back
drop
ads
replacement
and
then
there's
no
settings
for
back
tabouleh
include
your
settings
or
sometimes
the
modules
like
merchant
do
something
else,
and
so
it
can
be
really
different
on
a
case-by-case
basis
and
so
trying
to
like
document,
because
we
have
all
of
these
modules
moved
in
the
core.
We
know
what
we
did
with
the
data
for
each
one.
We
need
to
document,
so
people
are
upgrading
in
this
case
to
remove
your
module
from
you
know.
B
What
we
could
also
do
is
on
this,
like
modules
included
from
core
page,
we
could
list
all
of
the
ones
that
have
placeholders
or
like
here
all
modules
are
included
and
here's
all
other
instructions.
So
if
somebody
went
to
the
upgraded
instructions
page,
there
could
be
a
button
that
would
be,
like
you
know,
review
modules
that
are
included
in
course
see.
If
you
have
any
of
these
on
your
Drupal
site.
Yes,
no,
we
have
kind
of
a
nice
cohesive
list
of
them
over
there,
so
I'm
not
really
sure
it
like.
B
B
That
would
be
part
of
like
step,
one
I'm
doing
an
upgrade
to
like
create
a
code
base
in
backdrop,
look
for
modules,
add
them
and
then
another
one
would
be
like
if
you
go
to
documentation
first
before
you
start
upgrading
to
see
what's
involved
in
upgrading,
that's
another
place
that
people
information
like.
Oh,
you
know
these
three
modules
I
need
to
remove.
That's
good,
that's
easy,
but
these
four
modules
I
have
to
like
put
content
back
in
the
database
or
whatever
it
is
that
you
need
to
do
a
person
like
so
I
think
yeah.
C
B
I
think
so
too,
and
that's
why
I
think
why
I
created
that
placeholder
page
first,
where
I
was
like
this,
is
going
to
be
useful
in
the
future,
but
we're
not
really
using
it
right
now
or
I.
Think
we've
identified
the
use
case
for
having
these
individual
pages,
where,
like
okay,
putting
upgrade
instructions
on
them
is
important,
but
also
a
story
might
be
really
valuable
or
like
screenshots
of
how
it
was
improved,
like
I
feel
like
there's
a
lot
of
like
really
good
potential
news
in
there.
C
It's
not
just
like
necessary.
It's
pretty
interesting
awesome
like
each
one
of
these
things
has
you
know
for
techies
that
like
this
though
it
this
is
fun,
I
mean
this
is
like
oh
cool.
That's
what
you
did.
That's
how
you
solved
it.
That's
that's
what
improved
you
know.
I
I
think
it
provides
a
lot
of
hooks
to
tell
the
story.
B
C
I
mean
I
mean
visually
each
of
these
cases,
being
you
know,
node
and
and
like
like
the
default
view,
would
be
you
know.
Obviously
you
know
a
view
of
the
nodes
with
like
the
list.
Here's
the
model,
here's
those
replaced,
which
would
that
would
make
sense,
have
an
o-type
just
for
this
or
does
this
piggyback?
Is
this
fields
on
like
an
existing
type
with.
B
It
already
happen
note
a
just
for
this,
but
they're
sort
of
one
for
each
module
was
the
way
it's
set
up
so
but
I
think
like
we're.
Gonna
keep
discovering
more
uses
for
this
know
type.
So
initially
it
was
just
like
what
version
of
backup
core
was
it
moved
into,
and
that's
all
those
in
there
and
it
looks
like
well,
here's
upgrade
instructions
because
we
forgot
that
last
time
and
I
think
in
the
future,
like
here's,
a
news
story
about
how
it
was
metier,
screenshots
about
how
it
was
improved.
B
B
C
B
You
could
take
a
stab
at
doing
one
like
I
think
doing
something
like
link
module
might
be
a
great
example.
That's
something
that,
like
it's
different
between
you're,
going
back
to
it
right
where
we
just
took
the
existing
link,
module
we
put
in
the
court
and
we
can
have
screenshots
of
like
it's
exactly
the
same.
Look
this
interface,
whereas
in
Drupal,
8,
they're
like
well,
we're
not
gonna,
give
you
a
link
module
because
that's
hard,
we're
gonna,
give
you
URL
module,
it's
just
a
simplified
version
of
what
you
had
in
Drupal
7.
B
So
if
you're
going
from
link
module
and
triplets
on
the
URL
module
and
chocolate
you're
loosening
both
functionality
and
data
that
you
have
in
your
zero
second
site
and
so
I
think
we
just
had
a
story
about
how
everything
is.
That
is
exactly
the
same.
Then
I
think
that
would
be
compelling
in
and
of
itself
and
if
those
screenshots
include
like
the
differences
in
our
administration
themes.
So
what
was
in
triple
salmon
you'll
also
see
like
some
of
usability
improvements
to
just
in
having
the
screenshots.
B
C
B
C
Since
you
brought
it
up
that
actually
brings
up
something
and
sorry
this
is
tangent
thing,
but
but
I
was
I
was
looking
at
our
homepage,
where
it
says
upgrade
from
Drupal,
7
and
I
was
wonder.
If
that's
gonna
rub
people
their
own
way
like,
like
maybe
like
because
upgrade
like
people
have
put,
you
know,
years
of
sweat
and
effort
into
Drupal
might
might
incorrectly
get
a
night.
You
know
the
thought
that
we
have
a
negative
impression:
first
Drupal
yeah,
migrating
or
moving
or.
B
B
But
I
think
I,
think
you're
I
understand
your
point
and
I
think
I
I'm
open
to
other
language,
especially
for
like
the
heading
on
the
homepage,
doesn't
have
to
get
into
the
nitty-gritty
great
detail
stuff
like
upgrade
versus
migration
different
kind.
It
could
just
be
something
like
come
from
purple
or
have
a
Drupal
7
site
or
something
that
doesn't
use
any
of
those
words.
That
would
maybe
be
less
offensive.
So
if
you
have
ideas
that
don't
include
the
word
migrate,
I'm
all
ears,
alright,.
D
I'll
just
say
that
I
think
that
your
loop
you're
right
to
be
concerned
about
it.
On
the
other
hand,
I
hear
more
and
more
group
alerts,
sort
of
recognizing
that
not
everybody's
gonna
go
to
Drupal
8
and
appreciating
this
option,
so
it's
I
think
less
controversial.
Maybe
that
would
have
been
a
two
years
ago,
but
it
still
it
will
probably
rub
some
people
the
wrong
way.
Yeah.
B
I
think
if
we
can
rub
the
least
people
the
wrong
way,
that
would
be
ideal,
but
we
also
want
to
make
sure
that
the
people
who
are
curious
about
backed
up
who
wanna
know
what
it's
like
to
come
from.
Drupal
7
should
be
able
to
understand
from
somewhere
that,
like
it's
an
upgrade,
it's
not
on
migration,
so
I
don't
know
where
that.
Maybe
that
just
goes
in
the
upgrading
from
Drupal
7
page
right,
it
doesn't
have
to
be
on
home
page.
That's
fine,
I'm!
Also
thinking
just
is
related
I'm.
B
Also
thinking
about
doing
an
upgrade
versus
migration
blog
post
that
we
talked
about
about
like
you
know,
when
is
it
better
for
you
to
migrate
versus
upgrade?
And
what
are
your
options
for
that
sort
of
thing
and
I
think
that
would
tie
in
really
well
to
all
of
this
other
stuff?
That's
going
on,
so
we
could
maybe
put
the
nitty-gritty
details
in
there
and
then
we
don't
even
need
it
on
our
anyway
links
for
home,
page.
A
D
If
having
some
sort
of
like
a
upgrade,
you
know
and
I'm
the
vents
guy
right,
Oh.
Some
kind
of
these
virtual
events
I
think
we're
starting
to
get
a
handle
on
and
getting
a
little
bit
better
at
and
what
if
there
was
a
monthly
you
know,
migration
upgrade
or
not.
Migration,
don't
use
that
word
upgrade
or
or
just
move
officer
horrors
and
or
you
know
we
did
some
live
sites
like
we
asked
people
to
volunteer
a
simple
blog
site.
That's
in
Drupal,
seven
and
say:
hey
we're
gonna!
Do
this
live
what.
B
Started
doing
some
outreach
to
people
I'm
working
with
saying,
like
hey
I'm
in
the
market,
for
upgrade
projects
like
sunny
or
heavier
your
week.
What
is
it
you
say
in
the
United
States?
We
have
that
thing
that
it
likes
like
the
handed
sites
that
people
aren't
really
interested
in
investing
in
I'm
like,
let
me
know
if
you
have
any
of
those,
because
I
don't
want
that
use
case
to
be
like
I,
don't
want
the
maintenance,
this
triple7
project,
if
I,
can
push
the
button
and
have
it
like
maintain
itself
and
how's
that
working
backdrop.
B
That
would
be
ideal,
so
those
are
kind
of
what
I'm
looking
for
and
those
would
be
perfect
for
a
live.
How
do
you
do
this
thing
now?
I'm,
not
sure
we
can
do
that
in
an
hour
no,
but
we
could
do
it
ahead
of
time
and
then,
like
summarize,
what
was
done
in
an
hour
and
go
through
some
of
those
steps.
I
think
you
know
able
to
like
saving.
You
know.
Different
points
in
the
process
is:
do
it.
This
was
hard.
Let's
go
through
this
together,
yeah
or.
D
A
small
group
of
people
could
do
it
over
a
longer
period
of
time
as
and
treat
it
almost
like
a
usability
study
here
in
upgrading
right,
where
it's
more
than
just
you
but
yeah,
there's
two
or
three
of
us
that
are
going
through
the
process
together
and
and
again,
creating
it
like
a
usability
study
watching
for
glitches.
Looking
for
places
where
you
know
the
directions
aren't
clear
or
whatever
it'll.
D
B
Started
with
two
or
three
people
and
solving
the
issues
that,
like
you,
know,
someone
like
you,
that's
already
familiar
with
cheerful
and
back
to
our
Institute.
That
would
be
like
all
the
low-hanging
fruit,
and
that
means
we
can
do
it
again
in
like
a
month
once
it
hit
all
the
terrible.
You
know
showstopper
issues,
then
we'd
be
working
on
like
the
little
tiny
like
nitty-gritty
issues,
and
we
could
do
it
over
and
over
again.
We
could
do
that
like
once
a
month,
we'd
have
like
a
upgrade
your
backdrops
a
weekend
or
something
and.
C
B
B
B
So
we
can
put
more
stuff
on
that
layout
and
it's
going
pretty
well
so,
hopefully
I'll
be
able
to
get
that
wrapped
up
today.
I
would
love
it
if
someone
else
could
help
me
test
that
so
I
was
thinking.
What
I
would
do
is
throw
it
up
on
the
new
server
I
think
right
now,
all
of
backdrop
sites
are
moved
to
the
new
server,
except
for
backdrop,
CMS
org.
So
if
we
can
test
that
on
the
new
server,
it
would
be
a
good
place
to
let
everybody
else
play
with
them.
B
Adjusting
some
layout
pages
just
to
make
sure
we
don't
make
sure
I
don't
break
that
before
we
like
it
might
be
good,
okay
and
then
sandbox
I
think
is
fixed.
I
know,
Nate's
been
some
time
fixing
the
code
on
that
I
haven't
tried
it
on
our
life
site
to
see
if
it
works,
but
I've
also
been
motivated
to
switch
that
try
demo
button
on
the
home
page
if
it
is
working
to
start
using
our
new
sandbox
thing.
So
let's
talk
about
that
Deb
meeting
all
right.
Let's
change
gears
and
talk
about
backdrop.
B
The
product
there
are
two
major
usability
features
going
in
backdrop:
1:13
one
of
them
is
dashboard,
which
I
think
is
ready,
but
we
needs
to
write.
I
need
to
write
some
automated
tests
for
it,
so
I'm
hoping
to
do
that
today
and
we'll
see
how
far
we
get
and
then
the
next
one
is
save
draft
in
core
and
I.
Don't
think
anyone's
done
any
work
on
this
save
draft
in
core
issue
in
quite
a
while,
so
I'm
a
little
concerned
that
it's
not
going
to
make
it
into
1:13.
B
B
Publishing
setting
this
vertical
tab
and
change
them
into
buttons
on
the
bottom
of
the
form,
so
that
when
you
click
a
button,
it'll
say
like
save
and
publish
or
save
draft,
or
you
know
so
you
know
what's
gonna
happen
when
you
hit
the
Save
button,
which
I
think
is
a
huge
improvement
and
then
also
does
some
I
think
it
like
removes
the
science
of
it's
just
some
cleanup
on
the
note
form.
So
in
theory
it
should
be
easy
to
get
that
into
core,
but
considering
no
one
started
on
it
increases
on
Wednesday
next
week.
D
B
Okay,
that's
it
for
core
usability.
There
are
two
issues
relating
to
design.
One
of
them
is
designing
the
maintenance
page.
That
issue
looks
like
it's
our
TBC,
so
things
that
really
for
helping
review
that
one
and
then
the
other
one
is
color
schemes
for
basis.
We
had
an
idea
about
how
to
solve
the
blocker
on
that
issue,
which
I
posted
as
a
comment
in
there
a
while
ago,
but
I
don't
think
it's
been
getting
any
attention
lately.
D
B
B
You
just
sort
of
it
granted
access
to
whatever
right,
yeah
I
set
you
up
visit
whatever
role
it
is
that
allows
you
to
create
and
send
emails,
and
so
you
should
have
access
to
all
of
our
previous
ones,
and
you
should
just
be
able
to
go
in
there
and
like
copy
a
template
which
it
has
all
the
like
black
white
blue
stuff
in
it
and
then
just
put
stuff
wherever
you
want,
so
don't
feel
limited
by
the
layout.
But
I
just
want
you
to
get
the
like
black
style
stuff
by
copying.
B
Existing
one,
yep
and
I
would
say:
I
have
a
meeting
with
the
folks
I
think
today
about
the
newsletter
stuff,
but
I'm
gonna
talk
to
them
about
content
and
not
about
sending
the
newsletters
just
like
I
would
much
rather
have
them
focus
on
like
doing
interviews
for
what
we
call
the
community
stoplight
and
writing
writing
the
content.
Worse
then,
sending
the
email
since
they
have
been
searching.