►
From YouTube: Backdrop Design & UX Oct 22nd, 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Now
we're
live
okay,
sure
you
want
to
kick
it
off.
B
I
guess
so
hi
everyone,
I'm
tim
erickson,
and
we
are
here
for
the
october
22nd
design
and
usability
meeting.
We
are
recording
lists,
so
please
turn
off
your
youtube
or
turn
off
your
video.
If
you
don't
want
to
be
recorded
and
or
mute
yourself,
but
we
welcome
everyone
to
participate
in
these
meetings
with
video
and
audio.
B
Let's
go
around
and
introduce
ourselves.
I'm
tim
erickson
coming
to
you
from
deerwood
minnesota.
B
A
herd
of
wild
turkeys
is
passing
my
window
right
now
and
I'm
here
to
talk
about
well,
I've
got
one
or
two
things
on
the
agenda
we'll
get
to
in
a
little
bit.
Gregory
go
ahead.
C
D
Hi,
I'm
leighton
clowmak
a
web
product
manager
in
san
ramon,
california.
I
also
saw
a
herd
of
turkeys
flock
of
turkeys.
I
guess
there
this
morning
and
I'm
here
to
talk
about
user
interface
issues
because
they're,
one
of
the
great
things
that
you
can
complain
bitterly
about
without
knowing
anything
everybody
likes
to
do
that.
So
I'm
happy
to
draw
them
joseph.
E
I'm
joseph
I'm
from
las
vegas
nevada
and
I'm
just
here
to
see
how
I
can
help.
Maybe
improving
theme,
settings
or
color
module
or
something
like.
E
A
I'm
in
oakland
california,
I
do
not
have
a
group
of
turkeys
outside
my
window.
I
just
googled
it.
Apparently
you
can
refer
to
a
group
of
turkeys
as
a
rafter
of
turkeys,
but
I
did
see
one
on
wednesday
yesterday
morning
in
the
pasture
near
my
horse,
so
that
was
exciting.
A
Let's
see
tim,
do
you
want
to
go
through
the
agenda
or
you
want
me
to
do
it.
B
You're
doing
the
theme
and
updates
yeah
yeah
great
luke,
so
the
first
thing
on
our
agenda
is
initiative.
The
theme
initiative
update
luke
update
us,
you're,
muted,
luke
yeah.
I
think
that's
intentional.
D
Agenda
right
all
right,
all
right,
yeah,
the
the
the
ready
to
wear
initially,
all
right
so
I'll
I'll
I'll,
just
spew
out
the
stuff
that
I've
been
intending
to
write
all
week,
which
is
that
which
is
that
it's
all
close.
But.
D
Well,
like
a
rainbow
they're,
just
just
always
just
slightly
out
of
reach
the
lately,
what
I've
been
noticing
is.
We
have
a.
We
have
a
a
ready-to-wear
demo
site
running
on
simplo,
where
we're
prototyping
a
bunch
of
sort
of
the
ideas,
including
a
switch
theme
and
the
style
module,
both
of
which
answer
the
question
and
and
then
and
then
betrayed
me
that
that
the
question
wasn't
wasn't
precisely
what
was
missing
but
but
they
they
come
kind
of
close
the
style
module
actually
stylesheet
modules.
They
had
it
right.
Oh.
B
D
Style
guide,
really,
it
really
kind
of
shows
shows
the
challenge,
because,
because
it
kind
of
unhelpfully
answers,
the
very
question
like
like
you
can
you
can
click
through
the
different
themes
which
is
great
and
then
it
shows
you
every
single
element
which
is
which
is
kind
of
not
great,
because
because,
unless
you're
like
a
theme
designer
that
knows
exactly
what
you
changed.
D
D
Is
it
that
kind
of
tabbed
interface,
where
the
first
page
of
content
is,
is
more,
is
more
configurable
and
designed
to
be
more
useful,
the
design
to
kind
of
concentrate
on
one
screen
enough
stuff
to
vary
so
that
between
the
things
that
you
tab
across,
you
can
see
differences
like
it
doesn't
help
if
you,
if
you
click
on
each
of
like
the
five
things
and
you
see
five,
you
know
displays
of
h1
through
h6
and
they
all
look
the
same,
tiny,
tiny
little
differences.
D
D
A
a
two-part
thing,
what
one
part
is,
is
a
display
demo,
which
would
include
that
kind
of
type
interface.
But
that
also
includes
some
kind
of
display
tabs
too,
which
could
be
layouts.
D
D
I
mean
I'm
looking
for
you
know
the
blue
suit
or
the
red
sea
kind
of
experience,
but
but
I
think
we're
kind
of
close
now
now
the
the
other
side
of
this-
and
this
is
actually
what
relates
to
the
documentation
thing
right
that
that
there
are
pieces
for
for
for
getting
an
initial
look
going
and
the
pieces
themselves
aren't
that
complicated
or
hard
to
figure
out,
if
you
can
find
them.
D
D
So
it
strikes
me
that
that's
you
know
what
like
the
hard
thing
is,
is
the
reimagine,
so
people
find
it
out
of
the
box,
but
the
easy
thing
I
think
I'm
gonna
try
to
do
like
today
is
is
a
little
step-by-step
guide.
Like
first
thing
you
do
is
and
then
give
them
that
long
path
to
find
that
thing
and,
like
you
know,
set
up
what
your
layout's
going
to
be,
and
you
know
that's
a
necessary
step
for
for
creating
things.
I
I
still
think
it's
it's
also
going
to
involve.
D
B
D
Yeah,
I
was
just
ranting
them
out
there.
Why
don't
I?
D
Why
don't
I
deliver
it
today?
I
I've
actually
got
a
relatively
open
thing
today,
so
so
here
after
the
meeting
like
like
by
five
o'clock
pacific
time,
I'll
I'll
set
out
a
list
of
steps
and
then
then
how
do
I?
D
B
So
yeah,
this
is
an
interesting
question
and
it's
one
I'm
struggling
with
a
bit
is
how
best
to
organize
these
initiatives.
We
have
an
issue
in
the
drupal
core
issue
queue
for
this,
but
we
also
at
one
point
and
we
should
decide
if
we
want
to
use
this.
We
set
up
a
separate,
separate
issue
queue
for
the
demo
site
where
we
could
create
issues
like
you
know,
create
a
content
model.
B
D
A
D
Think
I
think
today
what
I
can
commit
to
sure
is
is
there's
a
lot
of
comment
to
the
thread
on
the
on
the
forum
thing
saying
saying
what
I
think,
and
I
mean
at
this
point-
I
can
make
a
burn
down
list.
I
I
can
make
here's
the
steps
that
we
need
to
do
when
we've
done
all
these.
As
far
as
I
know
now
we
can
release
it
and
I
I
can
I
can
put
those
in
there
and
then
we
can
decide
how
to
burn
them
down
a
second.
D
A
Would
it
be
valuable
to
have
a
dedicated
repository
under
backdrop,
ops
for
initiatives
that
we
know
are
going
to
span
more
than
one
project,
or
is
that
tough,
because
people
look
in
the
core
queue
for
stuff
yeah?
I
know
until
you've
had
this
question
for
a
long
time,
but
I
don't
I
just
didn't
know.
F
A
D
D
B
E
A
B
It
would
the
I
mean,
I'm
I'm
struggling
with
the
same
thing
that
I
think
you
are
joseph,
but
which
is
for
the
ready
to
wear
initiative,
see
some
of
that.
There
might
be
some
things
that
are
drupal.org
related.
There
are
some
things
that
are
on
this
special
demo
site,
so
these
aren't
core
issues
and
we
want
to
be
able
to
discuss
so
like
creating
content
for
the
the
demo
site
is
not
a
core
issue,
it
doesn't
belong
in
the
core
issue
queue,
but
we
want
to
have
an
issue
for
it,
not
just.
D
Affects
me
so
before
I
I
know,
but
but
I'm
saying
as
as
a
first
thing,
I
can
make
the
the
list
of
the
issues
which
would
all
be
in,
like
the
you
know,
not
yet
started
column
of
the
kanban
board
and
and
I'll
put
that
in
the
forums
thing
and
then
from
there
we
can
decide.
You
know
if
we
I
I'd,
be
thrilled
to
have
a
comp
on
board.
I
find
those
like
super
useful
are.
A
A
D
E
B
A
A
F
D
B
B
C
I
have
a
usability
issue
that
I
don't
think
I
see
it
in
the
list
is
the
one
about
merging
the
different
date
pages,
the
update
modules
of
the
themes
and
update
layout
pages
okay.
So
I
would
like
to
move
that
forward.
I
will
add
it
there,
but
basically
the
the
remaining
issue
for
me
to
start
and
work
on.
It
is
a
decision
on
where
that
page
would
live
like
would
it
be
at
a
configuration
or
under
reports.
C
Yeah,
so
the
issue
number
is
two
seven
one:
four,
which
is
merge:
all
the
update
core
module
thin
layout
pages
into
a
single
page,
so
the
decision
has
been
made
because
it's
it's
a
bit
confusing.
So
the
update
themes,
page
includes
modules
and
vice
versa.
All
pages
include
backdrop
core
updates,
so
the
decision
was
made
that
we
need
a
central
place
where
we
update
everything
we
list
and
update
and
allow
people
to
update
everything.
C
C
C
Yeah
anyway,
I
just
need
feedback
on
where,
where
people
think
that
the
best
fit
would
be
so
that
people
intuitively
can
find
this
place-
and
I
mean
there's
workarounds
or
additional
ux
improvements
as
as
in
they
don't
need
to
know
where
the
place
is.
If
they
go
to
the
site
status
report,
they
would
say
that
there's
pending
updates,
they
will
click
a
button.
It
would
take
them
to
the
updates
page.
So
yeah
give
me
the
issue
number
again:
gregory,
sorry,
two,
seven
one,
four,
okay
and
I'll
provide
a
link
as
well.
Okay,.
B
B
Yeah,
so
I
had
two
things,
one
of
which
is,
and
I
don't
know
if
we
have
time
to
talk
about
either
of
them
I'll
mention
them
for.
Let
me
talk
about
them
later
issue,
four,
one,
one
three
gen.
I
think
that
is
the
was
better
defaults
for
breadcrumbs
and
you
have
jumped
in
and
said
you
have
a
better
idea
about
using.
A
B
I
was
primarily
concerned
with
basis,
and
I
think
that
some
of
the
discussion
indicated
that
it
would
be
better
if
we're
making
a
change
like
this
to
just
do
it
in
basis,
but
I
don't
there
could
be
a
case
for
doing
it.
Overall,
I
don't
know.
A
A
If
we
move
like
if
they'd
had
written
additional
css
that
had
targeted
something,
so
this
sort
of
goes
against
her
we're,
not
gonna
break
basis
thing
but
yeah.
I
don't
know
I'm
like
conflicted,
because
I
also
agree
with
you
that
it's
a
new,
better
location
is
your
current.
Is
the
current
approach
with
the
config?
Is
that
only
for
new
sites.
B
We
don't
have
to
resolve
this
today,
but
it's
one
thing
I
just
need
like.
I
wanted
to
go
back
and
look
at
this
issue
and
I'm
not
quite
sure
what
to
do
with
that
feedback.
This
is
a
big
topic
and
it
might
actually
tie
into
the
to
the
documentation,
but
I
forget,
if
it
was
john
franklin
or
graham,
but
somebody
recently
posted
a
suggestion
for
a
what
is
the
equivalent
of
a
help
module
right
a
little
and
then
I
found
an
existing
issue
that
jen.
B
I
think
you
started
a
long
time
ago,
3707
about.
Let
me
see
if
that
was
your
issue
yeah,
it's
basically
tool
tips
with
help
tips.
It
seems
to
me
I've
heard
during
previous
meetings,
where
somebody
said.
Oh,
this
sounds
like
we're
trying
to
rebuild
the
help
module
and
I
don't
remember
exactly
how
the
help
module
worked
and
I'm
just
wondering
like
what
the
history
has
been
around
like
did
we
take
that
out
for
a
reason,
do
we
want
to
rebuild
something
like
that
which
is
basically
contextual
sort
of
tool
tips
to
help
people?
A
So,
just
for
history,
the
help
module
in
drupal
7
was
never
really
very
helpful,
same
thing
with
drupal
6
and
every
version
before
there
was
another
module
in
contrib
called
advanced
help.
That
did
actually
make
help
helpful,
and
so
I
think
our
thought
with
backdrop
is
like.
Why
include
something
in
core?
That's
not
helpful
at
all.
Let's
leave
this
to
advanced
help
to
do
whatever
we
need
done
in
a
place
where
it
might
actually
get
done
better.
A
This
solution,
I
think,
was
one
of
greg's
ideas.
Was
it
your
idea
that
we
had
in
a
meeting
one.
C
B
A
B
A
C
Yeah,
so
there
are
a
few
yeah.
It
wasn't
my
idea,
it's
just
that.
I
noticed
that
if
we
reduced
all
help
text
in
certain
pages
into
smaller
question
mark
things-
and
I
have
a
side-by-side
comparison-
screenshot
there,
it
sort
of
like
reduces
the
scrolling
and
the
the
amount
of
text
that
the
user
has
to
pass
within
a
page.
So
it
makes
the
page
less
confusing.
C
But
having
said
that,
that's
for
inline
help
like
help
that
is
attached
to
specific
fields.
The
help
module
to
answer
your
question
team
was
providing
a
big
chunk
of
help
at
the
top
of
the
page,
or
it
would
link
you
to
another
page
where
it
would
provide
like
a
full
tutorial
or
user
guide.
On
this
specific
subject,
I
recently
checked
how
wordpress
are
doing
that
and
they're
doing
it
impressively
easy
and
intuitive.
So
there's
a
link
at
the
top,
which
indicates
that
there's
help
you
click
it.
C
Something
falls
down
and
then
sort
of
like
expands
over
the
page,
so
it
doesn't
push
content
over
it
just
expands.
It
explains
what
it
is
in
the
uk
and
they
hide
it.
So
it
doesn't
require
page
load.
It
provides
any
kind
of
information
and
yeah,
I'm
not
sure
if
it
should
be
part
of
or
or
not
like,
I'm
decided
and
I'm
not.
I
don't
have
any
hard
feelings
about
either
way.
C
So
the
way
that
team,
for
your
benefit,
the
way
that
things
worked
with
help
in
core
was
that
each
module,
contrib
or
core
could
provide
a
function
which
was
hook
help.
So
in
other
words,
it
would
be.
I
don't
know
web
form
underscore
health
and
then
it
would
add
a
bit
a
bit
of
text
and
that
would
show
up
as
the
help
text
for
that
specific
module.
Okay
configuration
well,
I
just
raised
this
because.
A
B
So
I
just
raised
this
issue
because
john
franklin,
two
weeks
ago
opened
this
issue.
Add
dragon
help
module,
which
I
think
is
the
same
as
its
issue
4680
and
I
think
it's
basically
the
same
as
3707
and
I
felt
like
I'd
heard
sort
of
skepticism
about
trying
to
build
this
kind
of
system
in
core
before,
but
I
wasn't
sure
so
I
guess
basically,
my
question
is:
is
this
something
we've
ruled
out
or
is
it
something
we
want
to
entertain?
Even
if
it's
not
like
a
short-term
priority.
C
So
the
the
idea
there
was
that
it's
better
to
provide
and
tutorials
outside
the
module
and
link
to
link
to
these
from
the
module,
if
need
be
so
in
order
to
help,
especially
because
adding
things
in
at
least
in
drupal
core
was
lengthy
time
consuming
for
changes
to
get
in
useful
texts
would
take
a
long
time
to
in
order
to
be
incorporated.
So
if
the
help
the
help
text
lived
as
a
tutorial
on
the
torque,
for
example,
it
was
easier
to
be
updated
by
the
community.
So
that
was
the
idea.
C
So,
instead
of
having
something
that
is
harder
to
update
within
the
core
within
core
itself,
you
would
allow
it
to
leave
yeah
somewhere
else
and
link
to
it.
That
was
the
idea
was
that,
what's
that
issue
number
again
4480,
you
said.
B
46.80
is
the
new
issue,
but
I
think
it's
basically
the
same
as
the
3707.
Both
of
them
are
basically
just
tool
tips.
I
think
john
franklin's
idea
was
that
there'd
be
a
little
dragon
icon
that
you
hover
over
to
get
tips
and
and
in
the
international
issue.
It
was
just
like
a
question
mark
so
other
than
that.
I
I
feel
like
they're
the
same
proposal.
C
Yeah
every
different
implementation
of
basically
the
same
idea
providing
inline
health
there's,
also
a
tooltip
module.
Maybe
it
was
an
experimental
model
that
they
tried
to
put
in
a
core.
Maybe
it
was
a
country,
then
I'm
not
sure
if
you
remember,
which
would
actually
provide
balloon
tips
like
contextually,
so
the
help
text
would
pop
up
it
was.
It
was
called
the
tour
module
yeah
which
would
have
next
next
next
thing,
so
yeah
so
yeah.
B
Again,
well,
I'm
interested
in
this
idea
there's
but
like
there's
so
many
other
things,
I'm
not
sure
it's
a
priority,
but
I
wanted
to
at
least
understand
the
history
and
like
whether
or
not
there's
even
support
for
something
like
this
or
if
it's
something
that
we
decided.
We
didn't
want
in
court
and
it
sounds
like
people
are
still
open
to
something
like
this.
But.
C
A
I
would
love
to
see
it
developed
and
contribute,
and
then
you
know,
because
it
is
a
standalone
thing-
it'll
be
pretty
straightforward
to
drop
in
later.
If
we
decide,
we
like
it,
but
my
concern
is
that
we'll
end
up
with
like?
Oh,
we
have
this
use
case,
for
it
we'll
put
in
these
two
pages
where
we
have
help
and
then
it
dies
there,
and
so
I
don't
think
it'll
ever
become
full-featured
enough
to
be
valuable
in
core,
which
is
what
happened
in
previous
journal.
So
if.
C
A
Yeah
I
mean
this
is
how
token
module
works
in
drupal
7
right.
It
provides
tokens
for
all
of
the
core
stuff
and
just
the
name
of
its
hooks
like
it
would
have
a
like
layout
underscore
help
and
then
that
when
we
move
it
to
core
that
function
gets
moved
into
layout
module.
So
you
can
call
the
hooks
from
a
contrib
module,
pretending
as
though
your
core,
and
it
would
work
exactly
the
same.
B
Right,
I
guess
what
I'm
thinking
about,
though,
is
like
I
think
john
franklin
brought
this
up
and
that
we
were,
you
know,
arguing
about
like
what
inline
text
help
we
were
going
to
provide
for
a
specific
feature
and
and
he's
like.
Well,
you
know
why
provide
that
inline
text?
Why
not
have
this
tool
tip,
and
it
seems
to
me
like
these?
If
we
did
this
in
contrib
we'd
end
up
with
both
right?
B
We
we
couldn't
depend
on
the
the
the
the
tool
tip,
because,
unless
what
the
tooltip
did
was
it
automatically
took
whatever
was
in
line.