►
From YouTube: Backdrop Design & UX - Oct 24th 2019
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).
B
B
A
B
Right
well
housekeeping
there
today
is
October
24th
in
California
October
25th
in
Australia,
as
I
just
mentioned,
and
this
is
our
meeting
on
backdrop,
design
and
usability
issues.
It
looks
like
this
week.
We
have
a
new
issue
on
the
API
website,
API
that
bike
trip
semester,
maybe
not
a
new
issue,
probably
very
long-standing
issue-
that
we
only
newly
discovered
where
it
says
the
site
menu
doesn't
look
great
on
phones.
B
That
is
not
surprising,
because
the
API
site,
I
think
uses
I,
don't
know
it
uses
it's
like
one
of
our
oldest
themes
that
we've
had,
and
so
it
would
not
surprise
me
at
that
side.
Menu
is
not
adequately
displayed
on
mobile
I
think
we
probably
need
to
at
least
add
hamburger
collapsing
thing
to
it.
I
haven't
that
it,
but
there's
probably
a
lot
of
love
than
it
needs
in
order
to
make
it
occur.
B
I
believe
that
Justin
has
set
us
our
weekly
sanitized
backups
of
the
API
site,
so
it
should
now
be
easier
for
other
people
to
work
on
our
public
facing
sites.
The
code
base
is
in
github
any
less
file
pull
requests.
B
I
expect,
though,
that
this
is
going
to
be
a
configuration
change,
so
the
way
that
that
would
work
as
you
would
set
up
the
site
locally
on
your
work
environment,
whatever
that
is
make
whatever
change
it
is
and
then
copy
the
configuration
file
or
files
that
have
been
changed
into
the
staging
directory,
commit
them
and
file
a
pull
request,
and
then,
when
we
do
a
sync
on
live
it'll,
sync
from
stage
into
the
production
and
we'll
get
the
change
in.
So
it's
a
fairly
straightforward
thing
technically,
but
it's
the
sort
of
complicated
workflow.
B
But
then,
let's
help
us
fix
the
menu
on
the
API
say
that's
a
good
test
that
I
think
is
possible
on
backed
up
CMS
to
org.
We
have
a
handful
of
outstanding
issues.
Some
of
them
are
related
to
content,
some
of
them
design,
some
of
them
organization
they're
all
listed.
In
the
backdrop
ops
backdrop
CMS
at
work,
queue
I,
don't
think
we
should
cover
any
of
them
this
week,
because
we
haven't
made
any
changes
to
any
of
those
issues
since
our
last
design
meeting
or
any
of
the
design
issues
anyway.
B
B
Thank
You
Justin
again
for
any
notes
going
next
up
is
backdrop
the
product,
and
we
have
two
sets
of
issues
we're
going
to
talk
about
today.
The
first
one
is
around
user
experience.
I
think
one
of
these
issues
we
talked
about
are
surf
rolling
sisters.
We
talked
about
last
week,
maybe
in
the
developers
meeting
I
remember
talking
about
them
recently.
Maybe
it
was
a
scientific
CEO,
but
the
first
one
is
to
change
the
drop-down
menu.
B
Behavior
and
part
of
this
is
were
using
the
standard,
smart
menus,
JavaScript
library,
which
would
look
at
what
they're
doing
see
if
we
need
to
do
any
updates
to
our
JavaScript
code
to
pull
in
any
improvements
they've
made.
But
we
have
noticed
that
user
experience
is
it's
often
that
someone
will
hover
over
links
all
the
way
down
to
the
bottom
before
they
click
on
them
and
they'll
miss
the
like
landing
page
links
at
the
top,
and
so
one
of
our
primary
suggestions,
which
is
just
duplicate.
B
So
that's
something
worth
thinking
about
changing
that
could
be
a
kind
of
a
hard
fix,
because
if
those
changes
are
not
in
the
smart
menus
library
which
I
expect
they're
not,
we
will
have
to
add
our
own
JavaScript
separate
from
the
smart
meetings
library
in
order
to
override
those
behaviors,
and
that
might
be
a
rather
complicated
technical,
jQuery.
Javascript
person
challenge
I'm,
not
trying
capable
of
doing
that.
So
we'd
have
to
roll
that
over
to
someone
who
knows
how
to
do
that.
B
D
B
For
help
on
that,
one
I
think
the
idea
is
great,
though,
to
try
and
clean
up
a
little
that
is
issue
1442
in
our
core
queue.
The
next
issue
number
four
zero.
Eight
one
is
about
cleaning
up
the
text
in
our
new
layout,
flexible
layout
creation
tool
where
we're
trying
to
describe
to
people
how
to
control
the
width
of
their
rows.
There
are
three
options:
there's
one
it
doesn't
put
any
classes
on
the
row
at
all
and
it
always
takes
the
full
width
of
the
page
and
then
there's
two
others
that
match
the
bootstrap
library.
B
One
of
them
is
adding
a
container
class
which
gives
it
a
fixed
width
at
each
size,
so
one
size
it
would
be
one
set
one
desk
like
desktop
would
be
one
size
tablet.
We
one
size,
no
only
one
size
and
then
the
other
one
is
that's,
not
a
fixed
width
but
a
max
width
at
each
size.
So
it
will
still
be
squishy,
but
it
will
be
squishy
to
a
point
and
that's
a
little
bit
different,
so
you
still
have
like
gutters
on
the
left
and
right,
but
rather
than
something
game-like,
always
one
size
I'm.
B
Eight
one
has
a
bunch
of
suggestions
in
it
about
perhaps
we're
placing
the
Select
list
with
radios,
which
I
really
like
adding
a
longer
description
for
each.
It
would
be
great
if
we
could
figure
out
some
way
to
add
a
visual
reference
in
there,
though
I'm
not
sure
I
could
come
up
with
something
that
was
clear
for
people,
but
it
definitely
needs
more
feedback.
B
So
if
you
have
been
confused
by
what
those
three
options
are
when
you're
setting
up
a
row-
and
you
want
to
jump
in
on
this
issue-
and
let
us
know
what
terminology
might
make
sense
to
you-
we've
got
some
good
suggestions
in
there
already.
We
just
need
to
figure
out
how
to
take
that
and
turn
it
into
a
pour
request.
That's
significantly
better
than
what
we
have
now.
A
B
A
A
B
Sounds
good.
The
next
issue
is
about
cleaning
up
the
Installer
user
experience.
This
is
issue
number
3975.
Sorry
I!
Think
you
open
this
quite
a
while
ago.
I
think
all
of
your
feedback
is
really
got
people
there.
I
tried
to
go
through
the
same
process.
More
recently
it
was
like.
Oh
my
gosh
you're,
so
right
this
is
really
confusing.
They're.
D
B
I
think
of
separate
issues
in
there
that
we
could
tackle.
There's
a
PR
I,
don't
know
how
many
of
those
that's
cleaning
up.
I
haven't
checked
it
for
a
while,
but
it
isn't
an
interview
State.
So
anyone
who's
really
passionate
about
cleaning
up
the
user.
Experience
of
installing
modules
using
installer
module
to
give
that
test.
So.
A
I
have
addressed
most
of
the
issues
there
most.
The
only
one
remaining
is
that,
because
the
I've
moved
the
whole
bulk
of
the
text
that
was
either
in
a
separate
step
into
a
field
set
by
default
field
sets
have
capitalized
uppercase
letters,
so
we
opened
a
separate
issue
to
fix
that
and
that
other
issue
is
with
me.
A
B
A
One
one
thing
that
I
need
feedback
for
is
that
I
made
it
so
in
order
to
avoid
extraneous
clicks,
it's
the
list
of
languages
that
is
added
is
like
up
to
three
long.
It
renders
it
as
a
series
of
Freddy's.
If
it
goes
more
than
that,
then
it
falls
back
to
a
check.
It's
sorry
to
a
select
list
like
a
drop-down.
It's.
A
A
B
A
B
A
great
idea:
okay,
let's
see
basically.
A
A
A
B
A
A
B
B
D
D
B
B
Okay,
there's
an
issue
here
that
says
fields
that
are
dependent
on
other
fields
should
be
indented,
I
guess
so.
A
Yes,
this
is
a
serious
of
three
issues.
One
of
them
has
been
committed
so
that
make
the
forms
look
a
bit
busy
in
case
so
one
that
was
recently
most
I
checked
with
114
one
was
making.
So
there
was
setting
a
CSS
setting
that
was
making
the
field
field
labels
not
be
both.
So
we
fixed
that.
But
now
this
does
this.
A
The
field
sits
thing
and
then
the
other
thing
is
that
if
you
have
too
many
options,
they're
all
in
the
same
vertical
I
should
say
so
like
aligned
vertically
again,
but
it
it
would
make
more
sense
if
you
have
them,
intend
them
so
that
the
grouping
of
what
you're
looking
at
is
obvious,
because
sometimes
you
have
a
set
of,
for
example,
very
options
and
they
have
a
label.
And
then,
if
you
add
a
checkbox,
a
single
check
box
after
it,
without
any
it
doesn't
have
a
label.
A
A
B
So
another
word
you
might
use
is
in
see
tools.
They
had
a
different
state
system
that
actually
added
the
indenting
that
our
state
system
doesn't
add
for
that
dependency
thing,
so
there
might
be
something
that's
like
add:
ctools
dependency,
whatever
that
those
might
be
words
you
could
look
for,
and
then
the
indenting
of
radio
options
I
think
that's
a
separate
issue
specifically
for
like
that
node
edit
form,
because
we
have
the
the
scheduling
options
are
now
radios
and
then
the
underneath
option
for
making
it
path
list.
B
This
I
think
what
gets
mixed
up
in
there
are
may
be
published.
There's
there's
something
in
there
that
gets
really
confusing
without
that
indentation.
So
that
might
have
been
part
of
that
issue
and
I'm
not
sure
it
was
ever
split
off
to
be
solved.
This
for
all
field
sets
I
think
we
just
mentioned
that
in
there,
but
if
it
was,
maybe
it
would
be
linked
from
there
I.
Don't.
A
B
B
I,
don't
remember
exactly
how
it
worked.
I
think
it
was
very
similar,
States
I,
know
added
an
add
agent.
Also
added
like
some
extra
validation
and
stuff,
like
you
know
how,
with
normal
states
they're
required
thing
like
you
can
add
the
indicator,
but
it
doesn't
change
the
form
validation.
So
there
are
some
stuff
that
this
each
was
version
fixed,
I
think
we
have
some
of
that
in
backtrack
or
but
I
know
we
don't
have.
The
indentation
in
part
sounds.
A
Be
speaking
again
about
related
things
with
form
elements,
there
was
a
UX
issue.
I
know
that
I'm
not
going
to
be
able
to
find
it
now
because
it's
difficult
to
even
describe
it
so
I
kind
of
wonder
what
words
it
gives,
but
I
have
initiatives
but
wait
for
it.
So
when
you
have
a
set
of
say
four
options,
you
know
in
radio
balance
in
each
one
of
them
has
a
dependent
States
option.
So
you
select
something
from
the
radio
option
and,
depending
on
what
you
have
checked,
then
more
options
appear
after
it.
A
A
A
B
Yeah
I
think
that
that
would
be
interesting
too
and
be
able
to
inject
one
for
a
moment
inside
another
element
that
could
be
really
hard
because
I,
don't
think
like
HTML
can
do
that.
But
I
think
we
could
do
something
clever
with
like
positioning
elements
in
a
certain
way.
I,
don't
know
figure
out
yeah.
A
Yeah,
this
is
one
interface,
so
each
time
that
I
try
to
work
with
a
form
API
I
just
come
with
come
across
in
the
assistances
and
I
check.
If
this
something
respective
luck
indeed
occurred.
So
this
does
sound
like
an
one
of
those
issues
that
I
filed
for
found
at
some
point
in
which
I'm
trying
to
find
that
other
issue.
It's
really
come
to
this,
but
yeah.
Please
got
him.
B
So
form
API
is
an
amazing
tools
developer.
It
is
a
little
kludgy
when
you're
trying
to
use
it
as
a
human
being
after
form,
so
I
love
that
every
time
you
use
it,
you
come
out
with
a
lot
of
good
ideas
for
how
to
improve
it
and
they're
things
that,
like
you
know,
as
someone
who
has
written
a
lot
of
forms,
I'm
always
like
I
wish
I
could
make
it
do
this
and
there's
not
know
like
developer
tool.
That
does
that,
but
I
think
like
you're,
always
in.
B
A
A
B
A
B
B
B
B
But
my
recommendation
was
to
do
sort
of
halfway
where
we
would
leave
the
color
as
it
is
now
on
mobile
and
just
remove
the
color,
make
it
transparent
when
we
go
back
to
desktop,
and
that
way
you
wouldn't
have
to
worry
about
trying
to
colorize.
Only
that
one
part
and
in
the
color
module
we
could
just
change
the
label,
for
that
particular
part
of
the
page
to
say,
like
mobile
background
color,
so
that
it
would
still
work
in
the
same
way.
B
D
B
A
B
A
So
I'll
show
you
a
less
common
just
a
few
minutes
ago
and
I
agree
that
that's
the
easiest
solution
to
go
with
the
only
cats
there
is
that
we
would
say
that
hey.
This
is
the
color
that
is
being
used
on
mobile,
but
the
preview
that
we
have
next
to
that
thing's
is
showing
the
desktop
version
of
the
mobile.
D
B
A
There
is,
there
is
a
link
at
the
top
of
the
preview
that
says
to
open
it
in
a
new
tab.
So
after
they
open
it
in
a
new
tab
that
they
can
squeeze.
It
then
and
then
see
it.
There
is
not
just
the
side
by
side
thing
that
I
mean
yeah.
It's
just
that
there
will
be
changing
a
thing
that
will
not
reflect
on
the
actual
preview.
That's
but,
as
you
say,
it
can
be
a
follow
up.
Yeah.
B
B
It
sounds
like
an
issue,
everybody
just
sort
of
wants
to
remove
the
margin,
and
my
thought
was
if
we
could
find
a
safer
place
to
add
the
margin,
even
if
we
were
targeting
only
the
basis
front
page
or
only
the
basis
boxed
in
layout.
That
might
be
a
better
way
to
do
it.
We
can
keep
the
margin
just
wouldn't
be
on
the
hero.
It
would
be
on
some
other
elements.
D
Right
so
I
think
under
most
when
you
first
install
backdrop,
it's
the
header
and
then
there's
the
hero
block
and
then
there's
the
page
title
and
I
think.
If
we
move
to
the
margin
from
rather
being
on
the
bottom
of
the
hero
being
on
the
top
of
the
page
title,
it
would
fix
it
and
not
change
anything
visually.
B
B
B
A
B
B
Here
is
that
core
uses
the
built-in
GD
image
library,
which
does
not
support
SVG's
last
recommendation
in
that
issue
was
just
there's
a
place
in
quarterly
hard
code
to
be
allowed
file,
types
for
images
and
I
think
the
last
recommendation
is
to
remove
that
that
way.
If
you
have
a
different
image
library
that
does
support
SVG,
so
you
can't
use
them
you're,
not
limited
by
backdrop,
but
I
would
also
like
to
find
some
way
to
support
SVG's
in
core.
B
Even
if
that
means,
we
don't
run
them
through
image,
styles
or
any
of
the
processing
that
GD
needs
to
do,
and
we
can
put
some
kind
of
a
warning
on
it.
That's
like
this
image
won't
be
cropped
or
I,
don't
know
something
somewhere
where
we
can
tell
people
that,
like
you
can
still
add
an
SVG
because
a
lot
of
times
all
you
need
is
resize,
you
don't
need
it
style
for
that.
B
You
just
find
it
the
size
you
want,
but
if
you
needed
something
like
gray
scale
or
rotate,
like
those
other
things
that
do
need
Gd,
we
would
have
to
be
like
sorry
that
does
not
work
on
SPG's,
so
yeah,
just
something
I
think
we
should
look
at
the
change.
Drupal
8
did
for
removing
the
hard-coded
image
types
and
see
what
else
went
in
with
that
patch
to
a
Drupal,
8
core
and
see
if
there
was
other
similar
things
where
they've
already
solved
this.
B
B
A
We
have
a
thing
and
includes
me
in
one
of
the
includes
in
the
files
and
includes
directory.
We
have
a
list
of
all
the
mime
type
things,
and
this
is
outdated
because
the
standards
just
keep
evolving
and
this
thing's
out
of
date.
So
another
thing
would
be.
Another
task
would
be
to
update
that
taste
at
some
point
or
prove
it
and
there's
nothing.
So
now
that
we're
talking
about
design
issues,
we
introduce
the
file.
Sorry
you've
reached
the
last
the
last
one
right.
A
So
so
we've
introduced
the
the
files
file
entity
things
and
where
you
specify
the
file,
the
mime
types
for
its
file
type
that
you
create.
This
is
huge
lists
hidden
in
a
yes,
oh,
so
I
took
a
look
at
some
libraries
that
could
easily
fix,
like
they
provided
in
a
like
nested
thing,
with
check
boxes
that
we
can
use
and
selecting
the
top
one
like.
If
you
select
the
application
image
or
something
it
selects
all
the
what
you
call
it
sub
categories
of
mime
types.
A
B
A
B
A
A
Gif
thing:
is
there
images
that
show
before
and
after
it's
just
it's
been
so
long
that
I'm
not
sure
if
the
actual
after
that
I
have
working,
there
was
actual
code
or
just
not
something
up
yeah,
so
what
it
does
it's,
instead
of
rendering
all
these
states
hidden
options
that
are,
depending
in
the
in
the
radio
set
right
after
the
radio
set,
it
renders
its
option
under
the
respective
video
set
option.
Okay,.
B
A
B
B
Great
anything
else,
you
want
to
add
I.
A
B
I
mean
anything
generally
with
most
of
the
things
that
we
talk
about
in
our
weekly
meetings.
They
should
be
the
highest
priority
things.
Sometimes
they
also
include
like
the
most
recent
things
right.
If
it's
something
that's
timely
or
something,
people
are
focused
on
again,
that'll
come
up,
but
I
think
in
general
we
do
try
and
the
things
that
we
keep
on.
The
agendas
are
things
that
we
think
are
high
priority.
I
did
notice
that
on
this
particular
agenda,
all
three
or
maybe
just
two
of
them.
B
A
B
B
B
B
A
B
D
B
A
B
So
what
I
usually
do
is
be
like
look
in
all
the
milestone
stones
for
things
text
with
UX.
Those
we
know
are
high
priority
and
if
they're
like
you,
know
high
priority
UX
issues,
they
will
be
tagged
for
the
next
bug
release
and
then,
if
they
aren't
like
mm-hmm,
look
at
the
master
list,
it's
the
same
thing
with
bugs
right
like
if
there
isn't
really
any
priority
assigned.
How
would
you
organize
them?
Look
if
you
want
quick
ones.
B
A
The
same
thing
that
worried
Rockwell
much
with
the
bats
that
look
when
he
goes
to
the
least
he's
so
lucky,
if
not
hundreds
of
issues,
and
he
displays
indicators
for
us
that
you
know
frequent
the
very
shaky
like
you
can
look
at
the
number
of
comments.
For
example,
he
can
see
when
he
was
last
updated,
and
these
are
usually
good
indicators,
but
sometimes
things
do
get
forgotten
and
what
what
I've
noticed
in
this
is
like
I've
started.
A
This
discussion
is
that
they
have
been
seven
issues
that,
because
there
was
no
activity,
because
we
were
focusing
on
something
when
we
did
that
task.
When
we
do
the
releases
that
says
either
bumper
milestones
or
remove
the
milestones,
we
just
remove
the
milestone
altogether
and
then
they
just
get
forgotten.
Yeah.
B
B
Particular
thing:
I,
don't
think
it's
gonna
happen
anymore,
because
we
have
our
new
criteria,
for
things
being
milestones
have
to
have
an
advocate,
but
yeah.
They
also
feel
like
the
reason
that
worked
was
because,
if
we
mark
something
as
high
priority
and
nobody
worked
on
it
for
two
releases,
it
obviously
isn't
high
priority.
So
didn't.
B
If
we
had
time
for
other
things
that
were
higher,
so
it's
like
a
priority.
It
is
an
interesting
thing
right
because
there's
like
real
priority,
which
is
the
stuff
we're
working
on
for
some
reason,
is
a
priority
and
then
there's
like
conceptual
but
just
like.
We
would
love
it
if
these
things
got
done
and
I
think
that
what
what
that
was
an
indicator
of
it's
like
real
priority
like
oh,
if
nobody's
working.
A
It's
not
exactly
that
it's
so
previously
we
had
many
I,
won't
say
many,
but
multiple
issues
that
were
say
its
person's
personal
priority
or
they
were
advocating
for
it.
But
with
that
change
that
you
mentioned
before,
we
throttled
that
to
a
single
thing
per
person
and
instead
of
having
a
way
to
just
keep
the
rest
of
them
in
there
sort
of
like
Raider,
we
just
moved
them
in
the
general
bucket
and
then
they
get
lost,
that's
the
bit
where
they
get
lost.
A
A
B
Also
like,
if
we
get
our
bot
working,
we
could
say
like
if
it's
assigned
to
someone
and
they
haven't,
worked
on
it
in
two
months-
remove
the
assignment.
So
we
could
have
that
automatically
happen,
but
I
feel
like
there
are
github.
Has
tools
for
this
I,
don't
remember
what
they
are.
I
think
it's
like
you
can
follow
issues
or
watch
them
or
something
where
you
get
like
a
personal
list,
rather
than
like
a.
B
B
A
I
have
been
using
that,
but
it's
an
additional
browser
specific
hard
on
it
supports
many
browsers.
But
yes,
so
I
get
I
get
an
extra
button
where,
like
in
each
issue
on
the
sidebar,
where
it
says,
subscribe,
unsubscribe,
which
unsubscribe
to
many
things
so
I
get
slow
for
females.
So
I
don't
do
that.
I
can
I
have
an
additional
button
just
below
it.
That
says,
Mike
hasn't
read.
C
B
A
B
B
Site
I
revisit
the
issue,
so
the
things
that
are
like
highest
priority,
like
I,
have
eight
sites
that
all
have
this
problem.
That
issue
is
gonna,
get
a
lot
of
attention
because
of
every
core
update
and
I
mean
like
again
the
same
problem
on
every
one
of
those
sites.
Every
part
it's
gonna
get
a
tree
because
it's
like
it's
you,
but
then
there's
a
bunch
of
stuff
that,
like
just
bothers
me
like
the
sites,
don't
really
need
the
patch.
It's
easier
experience
improvement.
It's
gonna
make
my
life
better,
but
the
clients
don't
care
right
and.
C
A
Is
annoying
me
because
I
try
to
put
myself
in
the
shoes
of
the
end
user
and
it's
like
everything
is
that
I
mean
yeah
I
often
I
often
get
into
it,
because
I
have
my
OCD
I
get
into
these.
What
I
call
the
rabbit
holes
where
I
try
to
fix
one
thing,
and
then
these
need
sweetie
as
well,
so
yeah
create
another
issue
for
it.
I.
B
B
B
B
A
A
B
A
B
Way
of
somebody
knowing
if
someone
else
is
working
on
an
issue,
so
I
definitely
think
we
shouldn't
change
that
process,
because
otherwise
and
like
everyone's
gonna,
be
working
on
one
issue
like
if
they're
everybody's,
passionate
about
it
won't
be
stepping
on
each
other's
feet
a
lot,
especially
because
the
way
Paul
requests
work,
you
can't
merge
them
together.
Yes,
Mike,
Jim,
Kolbe
right.
You
think
this
is
not
a
platform
for
social
community
code,
whatever,
maybe
like,
it's
really
important
that
we
have
that
tool
that
allows
people
to
know,
don't
work
on
this.
B
A
B
A
B
B
A
B
B
A
So
my
thought
of
working
on
issues
is
this
as
well.
So
if
I
sign
thing
that
the
specific
issue
that
I
that's
the
old
one
that
I'm
assigned
to
myself,
it's
not
necessarily
that
I
will
work
on
a
PR
I'll,
just
revisit
see
what
the
others
are
doing
is
just
try
to
push
it
forward,
but
maybe
what
I
need
to
get
into
the
habit
of?
Is
that
just
once
I've
done
that?
But
it
just
said:
I'm
assigning
myself
and
if
I'm
not
planning
to
actually
actually
work
on
it
anymore,
yeah
all
right,
cool,
okay,.