►
From YouTube: Backdrop Design/UX May 10th
Description
Today’s Design/UX agenda: https://bit.ly/2I2cwNq
A
A
If
you're
on
a
browser
with
a
smaller
screen
or
a
computer,
with
a
smaller
screen
and
you're
trying
to
install
backdrop,
you
can
get
into
a
situation
where
it
looks
pretty
ugly
issue
number
is
two:
eight
seven,
three
and
I
think
it
looks
pretty
good,
but
the
proposed
solution,
but
it
would
be
good
to
get
someone
else's
eyes
on
that.
If
you
have
any
feelings
on,
what
that
should
look
like
could
use
reveal
Sanrio
the
other
one.
The
next
one
is
a
database
long
message
page.
So
this
is
lovingly
known
as
watchdog
Interpol.
A
There
was
a
whole
bunch
of
feedback
about
how
this
page
is
a
little
bit
weird,
and
we
made
some
recommendations
on
how
to
change
it,
and
nobody
could
agree
on
whether
their
recommendations
are
an
improvement
or
not
so
the
whole
thing
sort
of
been
tabled
until
we
can
actually
get
some
consensus.
There
were
two
very
small
changes
that
had
been
made
in
been
committed
for
the
database
blog
page
for
backup
110.
A
One
of
them
is,
we
add,
a
button
dangerous
class
right
before
you
delete
all
the
messages
so
that
you
know
that
delete
action
is
dangerous
rather
than
it
just
being
harmful
button
and
then
the
other
one
is
we.
There
are
two
field
sets
at
the
top
of
page.
One
of
them
is
filters,
and
one
of
them
with
the
delete
button
and
the
delete
button
was
between
the
filters
and
the
list
and
we
just
swapped
them
so
now
the
delete
buttons
at
the
top
and
the
filters
are
next
to
the
list.
A
They're
filtering
there's
a
whole
bunch
of
discussion
about
controlling
the
way
those
field
sets
work
about
moving
the
delete
button
somewhere
else
about
having
a
different
pH
or
the
bottom
or
wherever
and
that's
the
stuff
we
couldn't
agree
on.
So
if
you
have
feelings
on
how
to
handle
the
field
sets
and
the
delete
button,
we
definitely
could
use
some
feedback.
I,
don't
think
we're
going
to
get
any
of
that
in
for
10,
but
it
is
something
that
we
should
think
about
improving,
maybe
in
110
1.
A
Ok,
because
these
are
experience
issue,
we
could
probably
get
it
anytime,
user
experience
issues.
Our
longest-standing
UX
issue
is
issue
number
37,
which
is
improving
the
way
that
modules
page
works
back.
Job
already
has
a
search
box
on
the
modules
they
would
like
to
type
in
the
module
you're
searching
for
you
can
enable
it
and
when
it's
done,
enabling
the
lists
its
filtered
based
on
your
search
criteria.
A
A
I
know,
I
already
has
a
lot
of
comments,
but
more
feedback
specifically
about
the
currently
recommended
change.
If
that's
going
to
be
an
improvement
or
not,
the
next
one
is
issue
29
23,
which
is
adding
settings
to
the
search
box
form.
So
right
now
you
can
drop
a
search
box
onto
any
page
in
your
site
using
the
block
in
in
any
layout,
and
it's
not
configurable
at
all.
A
It
gets
a
title:
it
gets
a
label,
it
gets
a
button
and
it's
a
search
a
lot
of
times
by
default,
and
so
this
issue
will
let
you
turn
off
the
search
button
label.
Let
you
turn
off
the
text
in
the
button
and
it
will
let
you
add,
placeholder
text
if
you
rather
have
that
these
are
three
things
that
I
do
on
almost
every
site
that
I
add
I
almost
always
remove
the
button
label.
I
almost
always
add
placeholder
text.
A
They
must
always
remove
the
field
label
for
the
field
itself,
as
well
as
block
leave
also,
except
that
to
default
to
be
empty
instead
of
on,
and
so
the
question
remaining
now
is
in
that
law
request.
If
we
allow
people
to
remove
the
label,
do
we
also
want
to
leave
the
label
on
the
page
and
mark
it
as
element
invisible
or
not?
There's,
like
an
accessibility
question
there,
and
if
we
leave
it
on
the
page
in
market
its
element,
invisible,
do
we
Oh
require
customized
text
in
it.
A
So
we
don't
leave
an
empty
label
or
do
we
like
default
easing
search,
and
how
is
that
are
the
changes
that
we
have
now
sufficient
for
the
80%
use
case.
Or
do
we
want
to
include
a
customized
label?
That's
hidden
from
display,
that's
still
visible,
to
screen
readers
for
that
search
element,
because
placeholder
text
is
not
great
for
screen
readers
as
an
alternative
to
the
label,
so
just
trying
to
figure
out
how
much
we
need
to
get
in
this
form
for
the
initial
floor
request
or
if
what
we
have
is
sufficient.
A
A
Next,
one
I
just
want
to
say
I
would
love
to
get
the
missing
tabs
added
back
when
we
added
View
mode
support
on
the
manage
display
sub
pages
the
tabs
have
disappeared.
This
is
issue
a
2681.
It's
something
that
someone
who
uses
the
manage
display
pages
a
lot.
Orcs
me
every
time.
You
know
the
concerts
a.
A
Think
that
has
a
pork
bust
yet,
but
if
we
could
get
that
in
for
one
ton
or
one
night,
six
or
110
one,
that
would
be
fantastic.
The
update
dependency
message,
so
this
is
issue
28:25.
This
is
something
that
happens
when
you're
running
database
updates
so,
for
example,
you're
updating
from
hide
ripples
up
into
backdrop.
A
If
you
hit
a
module
that
you
haven't
had
a
few
latest
version
and
Drupal
seven
before
you
get
to
backdrop,
this
is
someone
throws
a
message
saying:
I
can't
update,
because
this
module
hasn't
met
its
requirement
in
order
to
do
so
and
the
language
it
previously
used
to
do.
That
was
confusing
and
not
very
useful,
didn't
tell
you
which
module
it
was
or
what
updated
wasn't
able
to
do?
A
So
we
could
definitely
use
some
feedback
on
the
update
dependency
error
messaging
to
make
it
more
useful
to
people
the
next
one
is
issue
number
twenty.
Seventy
two.
This
is
a
new
feature
that
went
in
for
1:10.
It's
the
ability
to
upload
a
file
from
the
link
dialog
button.
So,
for
example,
you
were
editing
piece,
content,
you're
pasting
in
some
text
from
somewhere,
and
you
realize
you
want
to
link
the
text
to
a
PDF
file.
A
So
you
can
highlight
the
text,
so
you
can
click
the
link
button
and
you
can
click
a
little
file,
tab
and
upload
a
file
right
in
that
interface.
I
would
just
love
to
get
some
more
people
to
test
that
and
make
sure
that
the
process
of
adding
a
file
has
a
nice
clean
user
experience.
All
the
language
makes
sense.
There's
anything
you
know
that's
confusing.
That's
already
in.
We
could
just
use
some
user
experience
improvements
before
we
release
110
if
any
are
needed.
So
it's
a
fantastic
new
feature
in
courage
alone.
A
And
then
there's
another
one
here
on
these
exposed
filters,
if
you're,
if
you
have
a
view
where
you're
exposing
a
filter
for
the
user
name
for
the
user,
account,
it
just
says
name
and
that
can
be
really
cute
confusing,
especially
on
a
site
where
you
are
actually
collecting
somebody's
real
name
as
opposed
to
their
user
name
having
a
field
that
says
name
and
helpful.
So
this
is
just
a
recommendation
to
change
the
label
from
name
to
user
name.
A
A
A
Alright,
196
and
there's
also
a
label
in
our
issue,
queue
for
audience
design
and
those
are
usually
issues
that
specifically
need
design,
review
or
actual
designs
posted
to
the
issue
before
we
can
proceed
and
then
any
issue
that
its
user
experience
related
to
just
put
square
brackets
in
the
title
us,
because
there
could
be
a
number
of
issues
that
I
really
attend.
Other
things
also
have
user
experience
focus.
So
those
are
two
ways
you
can
search
the
issue
cube
for
design,
her
user
experience,
specific
issues,
so
that's
all
I
have
for
those.
C
A
So
the
problem
right
now
is
they
give
them
one
sentence
that
says:
like
problems
happened,
and
it's
not
very
useful.
You
tell
them
what
problems
happened
and
so
the
current
poor
request,
I
think
itemizes.
Every
crisis,
Hey
problems
happened,
and
then
it's
like
this
problem
happened.
This
problem
happen
this
probably
happened
and
then
at
the
end
it
says
no
problems
happened.
So
we
need
to
figure
out
how
to
minimize
the
amount
of
noise
so
that
people
can
actually
get
the
information
they
need
out
of
it.
A
So
I
think
if
we're
gonna
itemize
each
problem
that
happen,
we
might
not
people
used
to
say,
hey
problems,
happen
and
then
the
very
end.
We
should
probably
say
like
no
additional
problems
happened
rather
than
just
say
no
problems.
Have
you
just
told
them
about
problems,
but
that's
really
hard,
because
the
last
message
has
already
been
generated.
We
would
need
to
alter
it
somehow,
which
is
really
tricky
or
catch
it
before
it
gets
added
to
the
page
and
I.
A
Don't
know
if,
like
somehow
check
for
weather
problems
happened
before
we
tell
people,
no
problems
happened
and,
if
we're
honest
often
we
could
say
no
other
problems
happened,
so
it's
just
a
little
tricky
just
so
that
we
don't
have
like
you
know
so
much
text
people
are
like.
Oh,
my
god,
everything
is
completely
broken.
I
give
up
that's
the
impression
I
would
like
to
avoid
being
able
to
say
we
had
this
one
problem
right
here.
This
is
how
you
fix
it.
That
would
be
most
useful.
A
A
We
should
list
each
problem,
but
we
don't
need
to
say,
there's
problems
and
then
there's
three
problems
and
then
there's
no
problems.
It
would
be
five
messages.
We
could
get
it
down
to
three
messages
or
four
would
even
be
better
than
five
and
if
each
one
word
very
concise,
like
this
problem,
have
them
with
this
module.
That
would
be
fine
or
if
we
wanted
the
last
one
rather
than
putting
how
to
fix
it.
Four
times
like
once
look
each
problem,
we
could
put
one
how
to
fix
it.
I
don't
know
they
do
we.
A
C
A
A
Think
it
just
needs
a
little
a
little
more
thought.
There's
a
lot
of
good
improvements
there,
but
I
was.
C
Looking
at
the
other,
the
other
one
with
the
design
of
the
installer,
the
installer
do
down
there,
but
a
mobile
version.
I
didn't
go
through
all
the
comments.
I'm
just
looking
at
the
screen:
ships,
real,
quick,
again
I,
really
like
the
mobile
version
territories.
They
have
the
other
rows,
expanding
on
tweak
or
something
or
you
just
I,
think.
A
C
A
C
A
Something
similar
for
the
module
installer,
where
it
has
the
same
problem
on
mobile,
where
you
don't
want
to
make
people
scroll
for
an
hour
to
get
to
what
they
immediately.
You
want
to
collapse
it.
So
if
we
could
come
up
with
some
on
patter
for
hiding
additional
information
in
a
table
on
mobile
devices
with
it
give
someone
like
a
plus
or
more
link
or
whatever
it
is.
We
use
on
the
modules
page
now
where
they
can
open
that
up
and
then
it'll
expand
and
show
them
more
information
in
hide.
That's
something
we
could
reuse
across.
C
The
other
authorities
for
consistency,
it's
okay!
It's
a
good
compromise
that
we
put
the
step
X
out
of
X
out
there,
but
if
we
could,
we
could
speak
there,
like
the
steps
in
the
world
actually
know
like
the
name
of
the
state
where
people
are
I'll,
come
up
with
a
design
dumb
things,
although
stairs
will
not
fit
there,
but
we
could.
We
could
do
the
same
thing
that
we
do
for
pages
like
have
the
parent
step
to
the
next
and
the
previous,
so
that
people
can
go
back
and
forth.
A
But
yeah
I
think
I
think
the
impermanence
dollar,
but
we've
already
done
a
lot
for
first
impressions
for
backdrop
in
110.
I
think
this
would
be
another
one
that
would
take
us
a
long
way
there
or.
A
A
Pages,
those
are
gonna,
probably
gonna,
get
implemented
after
a
release
of
115.
It's
a
no
point
on
to
my
chapter
because
we
have
hopefully
improvements
going
in
for
the
modules
page
to
110,
so
it
would
be
nice
to
get
those
working
in
conjunction
with
one
another
and
on
the
forum
site
I.
Have
my
local
I?
Have
a
search
box
took
me
a
little
bit
to
figure
out
where
to
add
it.
A
A
C
A
A
That's
still
up,
you
can
see
I
put
out
it
a
horse,
almost
roll
bar
to
the
pre-code
here.
So,
oh,
my
god.
Oh
that's
really
long.
It
won't
work,
that's
actually
how
I
started.
This
was
like.
Oh
that
looks.
Terrible
I
should
fix
that
and
I
was
like
wow.
While
I
was
in
here
I'm
mad
this
search
box,
hopefully
I'll,
get
both
of
these
pushed
up
today
and
then
we
won't
have
that
problem
anymore.
A
B
A
See
if
I
can
demonstrate
here
and
you
go
to
add
styles,
you
can't
read
the
names
of
the
styles,
because
the
Styles
drop-down
isn't
wide
enough,
and
this
problem
happens
on
backdrop.
Seeing
us
at
work
as
well
so
I
don't
know
how
CK
editor
works
if
it's
easy
to
make
this
drop
down
wider,
but
we
can
try
and
do
it
in
the
theme
and
see
if
we
have
any
control
over
that.
It's
a
good,
a
good
idea,
we'll
see
about
that.
And
then,
let's
see
the
last
issue
mentioned
number
50.
A
Okay,
so
like
on
a
list
of
the
forums
themselves,
each
one
of
these
rows
could
be
colored
based
on
its
status.
If
it
has
an
accepted
answer,
we
can
make
it
green
or
if
it
needed
help,
we
could
make
it
red
or
something
so
I
think
that's
a
good
idea.
Having
them
all
gray
is
a
little
boring
if
we
could
have
those
colors
have
meaning.
That
would
be
great
I
think
we
also
could
add
a
column
here,
because
the
color
by
itself
isn't
gonna,
be
super
super
useful
for
people
who
are
using
screen
readers.
B
C
Wondering
if
we
could
do
something
like
the
same
thing
that
did
have
does
with
tickets
in
their
tags
being
there
so
see
how
in
kidnap,
we
have
tags
for
needs
for
request,
and
these
are
like
fields
and
they
have
colors.
So
you
can
have
answer
it
or
not.
Let
me
see
if
I
can
explain
it's
mostly
the
backdrop.
C
B
Yeah
I'm,
a
fan
of
that
approach,
I
think
it's
less
visually
heavy
than
coloring
the
entire
row
and,
like
you
say
it's
like
Jim,
has
a
concern,
it's
also
accessible
because
as
the
texts
right
there
next
to
it,
you
know
apples
forms,
look
kind
of
like
that
as
well.
That
they've
got
just
like
written
in
green,
like
you
know,
has
accepted
answer
next
to
the
title
rather
than
making
like
a
new
column
or
coloring
the
entire
row,
both
of
which
kind
of
take
up
more
space
and
also
add
a
lot
of
visual
weight.