►
From YouTube: Backdrop Design & UX - Dec 20
Description
Today’s design agenda: http://bit.ly/2Ej7OJU
A
A
By
are
enough
time,
so
I'm
gonna
try
and
get
to
that
again.
This
week,
oh
and
since
last
week,
I
have
got
a
couple.
People
who
are
offering
to
help
me
test
it.
So
thanks
in
advance.
Yes,
I'll
definitely
need
help
with
that.
I,
don't
think
we
have
a
beta
site
or
a
dev
site
for
puck
drop,
CMS
org
up
anywhere.
A
That
might
be
the
kind
of
thing
that
would
be
good
to
test
not
on
my
site,
so
I'll
see
I'll
see
what
we
have
available
in
terms
of
getting
that
tested,
someplace,
safer,
okay,
moving
on
to
backdrop,
the
product
itself,
we're
going
to
talk
about
user
experience,
issues
the
first
and
probably
one
of
the
oldest
issues
in
Arceus
issues
around
37,
and
this
is
about
speaking
of
module
search,
the
modules
page
in
the
product
itself,
trying
to
improve
the
user.
Experience
of
that
page
issue.
A
Number
37
is
a
subset
of
sort
of
the
end
goal
of
a
bunch
of
various
different
features
that
a
bunch
of
different
people
want.
All
it
does
is
add
tags,
so
all
of
the
info
files
and
Courtois
tags,
and
then
it
makes
the
modules
page
search
box
search
those
tags
in
addition
to
all
the
stuff
that
it
currently
searches.
So
it's
a
very
minor
improvement
of
that
modules
page,
but
I
think
it
would
be
nice
to
get
that
done
in
conjunction
with
this
issue.
That
diploma
is
working
on
it's
issue
number
487.
A
In
the
backdrop,
CMS
org
queue,
which
would
allow
contributed
projects
to
add
tags
in
the
same
way,
so
that,
if
you
have
a
module
that
fits
in
multiple
categories
like
administration
and
e-commerce,
or
something
like
that
it'll
make
people
find
that
module
more
easily,
and
this
is
not
only
gonna
affect
the
search
on
the
modules.
Page
is
what
issue
37
is
for,
but
it
could
also
affect
the
search
on
backdrop,
semester,
org
and
in
the
installer,
which
is
relates
back
to
issue
number
442
and
the
backdrop
CMS
to
argue
about
making
that
process
better.
A
A
Okay,
next
up
is
issue
number
566
and
the
backdrop
stamp
and
backdrop
queue
itself
factor,
officiers
queue,
and
this
is
about
making
the
submit
buttons
performs
sticky
at
the
bottom
of
the
window.
We're
thinking
this
would
only
happen
on
desktop,
but
there
is
I
believe
a
couple
of
examples
there
and
a
pull
request
you
can
play
with
what
we
really
need
for
that
issue
is
feedback,
so
that
means
they
want
people
to
go
and
play
with
the
sandbox.
A
Next
issue
is
number
thirteen
83.
This
is
to
change
the
text
on
the
submit
button.
So,
in
the
last
version
of
backdrop,
we
added
the
ability
to
create
a
draft
version
of
content
or
to
schedule
content
for
later.
So
what
we
want
to
do
is
based
on
the
value
of
the
option
for
how
you
want
to
have
this
content
saved.
We
would
change
the
text
on
the
button,
so
it
doesn't
just
say
save
it
would
say,
save
and
schedule,
or
save
and
publish
or
save
and
create
draft.
A
So
there
are
a
couple
of
options
for
texts
and
language
in
there.
Do
we
go
to
get
that
updated?
We
have
another
issue.
We
talked
about
last
design
meeting
separating
help
text
for
those
different
status
options,
social
in
their
progress
on
that.
But
if
you're
passionate
about
that
the
issue
there
is
3122
I'm
doing
the
dependency
message
looks
like
we
have
a
pull
request
there.
That
needs
a
review.
A
This
is
just
to
make
it
clear
when
you're
updating
from
Drupal
7,
if
there's
a
problem,
exactly
what
the
problem
is
on
the
Installer,
we
wanted
to
make
it
clear
that
we
have
some
modules
that
we
are
recommending
more
heavily
than
others.
So
we
wanted
to
be
able
to
take
advantage
of
the
promoted
checkbox,
and
this
is
issue
number
31
93.
It
looks
like
we
could
use
some
feedback
on
how
that
should
look
as
well
as
how
it
should
work.
I
guess,
I
haven't
looked
at
that
recently,
but
we'll
be
good
to
review.
A
That,
in
conjunction
with
all
of
this
other
module
stuff,
so
I'll
take
a
look
at
that
today
as
well
and
I.
Look
like
we
just
need
some
feedback
on
that
to
anyone
who
can
review
that
and
wants
to
wait
and
would
be
great
here's
a
new
one,
I,
don't
think
we
talked
about
the
last
design
meeting
3389
or
maybe
we
did
this
is
so
on
when
you
go
to
edit
your
user
profile
or
your
user
account
on
a
backdrop
site,
it
has
to
password
fields
and
it
requires
the
password.
A
If
you
do
something
like
change
your
email
address,
we
wanted
to
clean
it
up
a
little
bit
so
that,
if
you're
changing
something
on
that
form
that
it's
not
your
email
address,
it's
not
going
to
show
you
the
field
to
enter
your
password.
So
it
will
only
prompt
you
to
reenter
your
password
when
you're
doing
something
that
requires
a
new
password,
so
that
form
will
be
slightly
less
overwhelming.
I,
don't
think,
there's
been
any
progress
on
this
last
week,
but
there's
a
pork
was
there.
A
So
anyone
who
can
take
a
look
at
that
pull
request
and
confirm
or
deny
its
improvement
would
be.
Great
next
issue
is
adding
a
dashboard.
Decor
I
would
love
to
see
this
get
into
112
I
think.
Currently
it's
just
a
layout,
but
we
need
some
feedback
on
what's
on
it
currently
in
the
Melinda
to
wants
to
get
some
feedback
on
it.
We'll
probably
need
to
do
a
couple
of
iterations
on
that
one.
A
C
A
Ok,
let's
see
views,
we
cleaned
up
the
views
listing
page
to
add
the
machine
name
and
to
show
all
over
the
opal
displays.
There's
really
five.
It
looks
like
they've
got
a
question
each
of
you
I've
taken
a
look
that
account
I'm
I
love
that
I
think
the
huge
improvement
and
I
would
love
to
see.
I
could
I
want
to
I
have
an
interface
consistency,
so
this
is
actually
number
3402
and
it
came
from
our
work
on
3395
about
cleaning
up
the
piece
interface.
A
We
were
trying
to
look
at
other
places
in
core
that
had
similar
displays
of
both
human
readable
name
and
the
machine
name,
and
we
realized
that
there's
a
whole
bunch
of
different
listings
all
over
core.
They
do
it
different
different
ways,
and
so
what
we
wanted
to
do
is
create
a
theme
function
that
included
both
the
human,
readable
name
and
the
machine
name.
So
anytime
we're
doing
anything.
We
could
just
call
the
theme
function
and
pass
in
both
of
them
and
it
would
display
it
the
same
way
in
all
places
really
interesting
conversation
there.
A
We
got
some
feedback
from
people
that
on
interfaces
where
the
machine
name
has
its
own
column
and
a
big,
bold
title
at
the
tack
are
at
the
top.
It
gives
the
impression
that
this
interface
is
intended
for
developers
or
people
who
understand.
You
know
what
machine
names
are,
gives
more
importance
to
that
and
in
the
interfaces
where
it
just
so
named
and
I
had
a
human
name
and
then
parentheses
and
small
text
said,
oh
by
the
way,
here's
the
machine
name
it
made.
It
feel
like
that.
A
C
A
I
think
this
external
microphone
and
gotten
plugged
in
somehow
but
I,
don't
know
right.
It's
not
working
anymore
anyway,
they're
good,
something
rattled.
This
is
that
round
internal
speaker,
so
it
won't
be
as
good
so
I
got
that.
But
yes,
you
can
hear
me
you.
A
Okay,
anyway,
we
were
on
I'm
interfaced,
consistently
3402
I
would
love
some
feedback
on
whether
the
decision
we've
landed
on
there
is
gonna,
be
good
improvement
for
all
interfaces
or
not,
and
so
there's
proud
of.
We
know
if
there's
a
poor,
processor
or
not,
but
I,
think
there's
a
screen
shot
if
nothing
else,
all
right.
A
Moving
on
to
issues
that
are
specifically
about
the
design
of
specific
pages
issue
number
3209
about
putting
in
a
bunch
of
predefined
color
schemes
for
the
basis
theme
needs,
we
just
need
to
run
all
those
colors
through
an
accessibility
checker
to
make
sure
that
out
of
the
box,
we're
not
creating
in
an
accessible
color
palette.
For
someone
like
there's
enough
contrast
between
the
two
but
employer
cross
itself
looks
pretty
good.
The
sets
of
colors
they're
putting
integrate
a
3309
needs
some
feedback.
A
A
We
need
to
think
that
through
clearly
so
I'm
guessing
that
probably
won't
get
in
for
one
two,
because
we
need
enough
time
to
do
it
and
then
test
it
with
King
trim
and
I'd
be
a
little
bit
nervous
about
doing
that
now.
But
I
would
definitely
love
some
feedback
on
ways
that
we
can
handle
that
kind
of
situation
like
should
we
automatically
throw
all
those
links
until
like
bulleted
lists
on
that
page
or
something.
A
Still
navigate
from
one
place
to
another
and
then
style
it
specifically.
If
you
wanted
to
look
like
caps,
you
could
do
that
too.
Okay,
let's
see
next
up
we're
moving
Oh
No
installer
design
on
mobile,
so
issue
2873.
We
have
a
screenshot
there
and
what
it
should
look
like.
We
just
need
someone
to
implement
it,
so
we
have
to
sign
just
need
to
get
it
done.
I
think
it's
just
CSS,
but
maybe
some
changes.
It's
really
that
table
works,
thesis,
design
and
theme
the
maintenance
page.
A
So
we
have
a
fantastic
convenience
agents
on
the
far
other
core
themes,
but
the
basis
page
is
sort
of
on
the
themed.
It
would
be
great
if
we
could
get
the
very
least
some
style
on
it
before
112,
but
in
a
perfect
world
we
would
get
someone
with
some
design
skill
to
do
something
really
fun
with
that
page.
It's
a
great
place
where
we
can
add
a
little
character
show
a
little
bit
of
the
fun
side
of
backdrop,
and
that
is
it
for
all
of
the
design
and
user
experience
issues
we've
highlighted
for
112.
A
A
Okay,
we
only
have
one
other
section
on
the
web
on
the
agenda
for
today
and
that
is
under
print
design.
We've
had
sort
of
a
long-standing
request
for
a
Kate.
Would
it
be
neat
if
we
had
a
pop-up
banner
that
we
could
use
at
events
to
put
next
to
a
backdrop
table
or
in
a
training
classroom
or
in
a
summit
and
we'd
realize
that
would
take
design
skills?
So
it's
on
our
design
wish
list
here.
If
somebody
wants
to
work
on
a
pop-up
there,
that
would
be
great.
A
Obviously,
it's
not
necessary,
but
it's
a
good
place
for
it.
I
think
someone
who
wants
to
contribute
design
to
help
us
out
in
a
way
that
doesn't
involve
using
the
issue
queue
all
right.
That's
all
that's
on
the
agenda
for
today,
I
don't
know
if
either
of
you
want
to
add
anything
in
particular
about
any
of
those
issues
or
any
other
issues.
A
B
A
Okay,
this
is
stuff
that
got
in
this
is
the
stuff
we
need
clean
up
on
or
whatever,
and
then,
when
we
have
the
final
wreath
release,
we
go
back
to
the
full
agenda,
so
I.
Think
next
week
will
be
the
art
first
hyper
focused
meeting,
and
so
we'll
do
that,
and
if
people
can
make
the
Minx
that's
great,
but
if
not,
it
still
be
good
to
have
that
as
a
resource
for
them
to
review
later.
No
all
right!
Well,
we
have
another
meeting
in
about
20
minutes.
A
We're
just
gonna
talk
about
other
backdrop,
issues
not
necessarily
what
they
did
to
use
your
experience
and
design
the
thinks
they're
on
the
list
for
law
and
12th.
So
if
you
guys
can
come
to
that,
that
would
be
great,
if
not
other
people
probably
come
to
the
same
sort
of
meeting,
but
thanks
you
guys
for
coming
today
and
pointing
out
that
my
microphone
stuff.