►
From YouTube: Backdrop Design - May 20th
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
Hey
looks
like
we're
live
on
youtube
today
is
may
20th,
and
this
is
our
design
and
user
experience
meeting
before
we
get
into
anything
on
the
agenda.
We
should
go
around
and
do
some
quick
introductions.
B
My
name
is
jen
lampton,
I'm
joining
from
oakland
california.
I
haven't
been
doing
a
lot
in
designer
user
experience
recently
for
backdrop,
but
I
have
a
bunch
of
user
experience
issues.
I'd
love
to
work
on.
If
there
was
more
hours
of
day.
C
Hi,
I'm
greg.
Sorry,
I'm
just
gonna
need
that
I'm
joining
from
chris,
usually
in
australia,
hopefully
soon
there
as
well.
I've
been
fiddling
with
a
few
ux
issues
that
I
will
mention
in
this
meeting
and
I'm
looking
for
some
feedback
and
guidance
and
yeah
passing
on
to
global.
B
All
right
we,
since
our
last
theme
and
user
experience
related
meeting.
I
think
we
have
a
theme
initiative
update
from
luke,
so
we
had
an
initiative
for
backdrop
called
ready
to
wear,
which
was
trying
to
make
more
themes
ready
directly
when
you
put
them
onto
your
site,
you
could
use
in
production
and
luke
has
written
up
a
summary
of
that
initiative
in
the
forum.
So
if
you
go
to
the
forum,
there's
a
category.
B
There's
a
link
in
the
agenda.
I
think
the
category
is
initiatives
how
to
navigate
here.
Yeah,
there's
a
there's,
a
category
called
initiatives
and
then
the
first
one.
That's
the
most
recent
comment:
official
initiative
ready
to
wear
it's
the
last
comment
on
there,
where
he
wrote
all
the
stuff
that
has
happened
in
the
last
year,
including
the
bottom
there's
a
bunch
of
screenshots
of
themes
that
are
ready
to
wear,
which
is
pretty
exciting.
B
So
thanks
luke
for
taking
the
time
to
write
that
up.
I'm
sure
we'll
discuss
it
again
in
our
weekly
meetings.
B
And
then
for
backdrop,
the
product
itself,
we
have
a
handful
of
issues
that
are
tagged
as
design
related
issues
and
a
handful
of
issues
that
are
detected
as
user
experience
related
issues.
I
don't
think
we've
been
making
any
for
very
much
progress
on
any
of
the
design
issues.
B
I
haven't
been
paying
attention
if
we
have,
but
there
is
one
issue
that
I
don't
remember
where
this
stands,
I
think
is
going
to
help
unblock
us
for
all
changes
in
the
future,
and
that's
this
long-standing
issue
about
how
to
make
css
changes
safely
between
core
versions
so
backed
up
core
had
a
1.x
release
in
2015..
B
It's
now
2021,
that's
been
six
years
and
we've
been
really
hesitant
to
make
css
changes
because
we're
likely
to
break
live
sites
by
doing
that,
and
so
for
the
last
two
or
so
years
we've
been
talking
about
how
we
can
introduce
a
system
into
core
that
would
make
it
possible
for
us
to
make
css
improvements
to
new
installs
without
affecting
existing
installs,
and
I
think
we've
landed
on
a
solution
that
everybody
hasn't
had
any
very
strong
objections
to.
B
I'm
not
trying
to
say
everyone
agrees
to
it,
but
it
is
something
that
I
would
like
to
get
some
more
feedback
on.
I'm
gonna
drop
a
link
into
the
backdrop
zulu
channel
for
weekly
meetings,
but
this
is
issue
number
3146
in
the
github
queue.
If
anyone
wants
to
well,
that's
not
the
right
one
too
many
issues
open.
It's
issue.
B
If
anyone
wants
to
look
at
that
and
the
the
big
takeaway
is
that
we're
going
to
try
and
add
a
bunch
of
body
classes
so
anytime,
we
add
a
css
change,
we'll
include
a
new
body
class
and
then
the
css
will
include
that
body
class
as
a
part
of
its
selector.
And
then,
when
backdrop,
two
comes
out,
we'll
just
go
and
remove
all
of
those
special
selectors.
B
So
all
of
it
would
end
up
in
the
base
version
of
two
and
then,
as
we
add
new
stuff,
we'd
start
to
add
selectors
again
for
invector
two.
B
B
The
I
think
the
big
issue
is
that
the
core
layouts
plus
basis
theme
creates
an
example
that
is
not
super
common.
It
isn't
what
most
people
want
and
so
he's
trying
to
find
ways
to
get
something.
That's
closer
to
what
most
people
want.
It's
a
little
too
stylized
and
opinionated,
and
I
had
some
alternative
recommendations
on
how
we
might
be
able
to
do
that
with
templates.
B
But
all
of
my
recommendations
would
affect
existing
sites
and
because
we
don't
want
to
do
that,
included
changes
that
were
only
configuration
and
could
only
be
applied
new
sites.
It
does
create
sort
of
a
messy
user
interface
on
the
back
end,
which
is
what
my
resistance
was
to
it,
but
that
also,
I
think,
could
use
some
more
feedback
from
opinions
for
people,
whether
you
think
admin
interface
is
worth
having
things
closer
to
where
you
want
them.
When
you
start
so.
This
issue
is
number
4113.
B
All
of
the
other
issues
we
have
on
the
agenda
are
not
designed
specifically,
but
they're,
related
more
to
user
experience
and
greg.
I
don't
know
if
you
want
to
go
through
some
of
these.
C
Yeah,
so
I
went
I'm
not
going
to
add
any
more
there's
so
many
interesting
things
to
work
on.
I
just
added
a
few
ones
where
either
we've
done
some
work
and
then
a
couple
of
those
are
yours
as
well,
and
then
they
just
had
some
period
of
inactivity
now
because
lack
of
time
or
reviews.
C
So
I
would
like
to
keep
them
here
for
a
few
weeks
or
fortnights
just
to
draw
attention
to
people
that
what
we
sort
of
like
what
they
think
should
be
prioritized,
which
one
of
those
and
and
maybe
we
can
get
some
feedback
by
just
mentioning
them.
So
these
are
things
that
I,
these
are
the
ones
that
I
selflessly
sort
of
like
remember
from
the
ux
wrist
list
that
I
have
in
my
mind.
C
So
the
first
one
is
issue
44
10,
and
this
is
something
that
then
you've
put
a
request
for
and
it's
to
get
a
to
use
the
admin
theme
for
the
login
form
and
to
sort
of
like
have
it
so
that
that
our
login
page
differentiates
from
the
rest
of
the
site
sort
of
like
what
wordpress
does
I
haven't.
C
I
haven't
looked
at
that
issue
for
a
long
time,
but
this
is
related
to
something
that
we
were
discussing
privately
before
we
started
recording
it's
related
to
a
few
fiends
in
drupal
land
that
are
starting
to
pick
up
sort
of
some
traction,
and
I
think
that
they're
doing
some
good
work.
So
back
in
november,
I
posted
a
few
screenshots
of
how
some
of
those
login
screens
look
like,
and
you
know
you
can
theme
them.
You
can
add
images
whatever
and
there's
a
dark
mode
as
well,
so
it
could
be.
C
It
would
be
nice
to
get
some
feedback
and
I
can't
remember
what
the
decision
was,
but
I
also
at
some
point
recommended
or
suggested
that
we
should
explore
the
idea
of
using
a
separate
layout
which
would
allow
people
to
put
blocks
there
and
customize
it.
But
I
can't
remember
what
the
decision
was
on
that
we
need
to
revisit
that.
C
B
Are
a
couple
of
recommendations
that
made
this
a
little
bit
more
possible
in
order
to
have
a
layout
for
these
two
pages.
Specifically,
we
could
add
a
context
specifically
for
user
login,
register
and
password
pages
and
provide
a
default
layout
of
the
box,
or
we
don't
have
to
provide
one
if
we
don't
want
to.
B
But
at
least
that
way
people
will
be
able
to
select,
like
is
login
pages
or
something
as
an
option,
and
it
would
target
all
three
and
that
would
make
it
more
sensible
to
put
specific
blocks
on
only
these
pages
rather
than
having
to
like
target
by
url
and
say
only
put
this
block
on
this
page
or
only
put
this
box
page
so
either
way.
That's
a
good
idea,
I
think,
and
then
there
are
a
couple
of
other
issues
that
were
problematic
right
now.
B
We
have
a
permission
called
view
administration
theme
which
would
need
to
be
granted
to
anonymous
users
in
order
for
them
to
view
this
page
in
the
back
end
theme,
but
that
permission
isn't
actually
being
used
in
core
right
now.
So
you
can
grant
that
to
people,
but
it
doesn't
actually
control
whether
they
can
see
the
admin
theme
or
not.
B
So
I
have
a
separate
issue
that
removes
that
permission
from
backdrop
core
and
that
created
a
problem
because
there
could
be
people
in
drupal,
7
or
in
backdrop
that
are
using
that
theme
themselves
for
something
else
like,
for
example,
if
you
built
a
view
and
you
granted
access
to
that
view
based
on
the
permission,
views
use,
admin
theme
view
admin
theme
that
could
be
a
problem,
so
we
also
created
a
contrib
module
called
view,
admin
theme
that
provides
the
permission,
and
so
when
we
make
the
update
to
backdrop,
that
removes
the
permission.
B
We
would
also
need
to
include
a
note
that
says
if
you
were
using
this
permission
on
your
site,
here's
a
contrib
module
you
can
install
instead,
so
it's
a
little
messy
and
I'm
not
sure
that
can
or
should
be
done
in
1.x.
B
B
B
C
So
the
the
next
issue-
I'm
not
let's
speed
through
these,
just
just
to
sort
of
like
say
which
ones
they
are
and
what
we
need
feedback
on
then.
The
next
issue
that
was
on
my
this
list
is
5085
and
it's
a
follow-up
to
the
merging
of
the
the
update
pages.
C
This,
like
won't
affect
a
lot
of
people
out
of
the
box
because
it
happens
in
a
specific
situation.
So
if
you
disable
the
manual
save
self
updates,
for
you
will
see
that
the
the
the
system
updates
page
this-
the
unified
updates,
page
sort
of
like
splits
into
two
tables-
and
I
don't
see
any
point
in
that
being
that
way.
So
I
provided
a
few
screenshots
that
explain
it
better
than
my
words
now
and
I
would
like
some
feedback.
C
I
used
the
same
ui
pattern
that
we
have
in
the
modules
listing
page
and
the
status
report,
page
where
we
have
a
more
or
less
link,
which
is
a
toggle
basically,
and
it
reveals
more
information
so
that
that
would
make
it
the
third
place
that
I
can
think
of
in
the
admin
ui
where
we
use
that
pattern,
and
so
I
created
issue
50
90
so
5090,
which
I
I
sort
of
like
suggest
that
we
should
consider
replacing
those
more
or
less
toggles
and
the
the
custom
javascript
that
we
have,
which
is
separate
for
its
module.
C
That
provides
that
and
it's
basically
code
duplication
into
a
details.
Html
element,
so
I
did
file.
C
I
did
file
a
proquest
for
that,
so
you
can
test
and
play
and
see
how
it
feels
the
only
thing
that
we
need
to
do
there
as
a
subtask
is,
if
we
decide
to
go
with
that,
we
need
to
add
polyfill
for
the
details
element
for
all
the
browsers.
C
So
we
need
some
testing
there
before
I
start
doing
more
work.
I
would
like
some
feedback,
but
the
the
exciting
thing
about
it
is
that,
as
part
of
that
issue,
I
started
working
on
issue
324,
which
is
a
really
old
issue,
which
is
to
add
the
details
element
in
the
form
api
and
provide
a
theme
function
for
it,
so
that
contrib
and
core
can
start
using
it.
So
certainly
we
cannot
do
what
drupal
has
done
and
replace
all
field
sets
with
details
in
the
wonder
text
cycle.
C
B
C
So
that
that
issue
is
about
those
pages
specifically
and
if
the
previous
issue
that
I
mentioned
does
get
merged,
I'm
also
going
to
convert
that
more
or
less
bubble
into
music
details
as
part
of
it.
Now
the
pull
request
includes
changes.
That
would
add
details
in
the
form
api
which
should
be
outside
that
issue,
which
is,
as
I
said,
it's
just
a
proof
of
concept.
C
C
Then
I
would
like
to
mention
issue
3157,
which
is
the
save
draft
module
into
poor
peterbilt
was
advocating
for
that,
but
I
dragged
him
into
other
work
related
stuff,
so
he
removed
himself
from
an
advocate.
If
I
finish
with
working
with
the
other
issues.
Clearly,
I
would
like
to
advocate
for
that.
If
here
doesn't
change
his
mind
and
comments
backwards
and
then
related
to
that
is
issue
31.2,
which
is
pretty
close.
So
this
is
about
separating
the
help
text
for
the
publish
options.
It's
pretty
close.
C
C
But
I
think
we're
pretty
close
and
andy
gozella
has
done
a
review.
The
only
thing
that
he
pointed
they
pointed
out
was
because
it's
changing
the
structure
of
the
form
elements.
Maybe
the
nesting
is
not
as
before,
and
should
that
be
a
concern
for
people.
You
know
overriding
that
form,
I
think
not
as
well,
but
I
would
like
some
feedback
from
others.
B
Yeah,
the
form
api
structure
is
not
technically
part
of
the
api,
but
it
is
possible
that
somebody
wrote,
like
a
form,
alter
module
that
would
not
work
anymore
targeting
these
elements
in
their
previous
position.
B
What
we
could
do
is
do
a
quick
scan
of
contrib
and
see
if
we
we
can
find
any
form
options,
sticky
or
form
options
promote
in
their
current
locations,
and
that
will
give
us
a
good
idea
of
what
can
trip
is
currently
doing
to
the
node
form.
It
won't
tell
us
about
custom
stuff,
but
I
think
that
if
we
determine
that,
like
there's
nothing
in
contrib,
that's
doing
it
that
might
be
safe
enough
for
us
to
be
like
okay.
C
Yeah,
it
would
be
an
indicator
so
by
the
way
the
the
status
of
this
issue
is
rtbc,
so
we
basically
need
a
quarter
meter
just
have
a
look
and
see
if
it's
acceptable
the
way
that
it
is
now.
B
On
a
drupal
7
site-
and
it
made
me
really
mad-
and
I
was
like
why
why
do
people
do
this?
What
do
they
want
and
I
think
that
there
are
still
some
features
that
module
filter
offers
that
are
not
in
backdrop
core,
and
I
would
love
to
make
backdrop
core
good
enough
that
people
won't
want
backdrop
module
filter
for
it
and
in
order
to
do
that,
we
need
to
add
back
some
of
the
missing
functionality
so
check
boxes.
So
you
can
see
the
difference
between
portal.
B
Only
modules
can
dribble
only
modules
or
even
custom
modules,
and
then
there
was
another
issue,
a
parallel
issue
that
gave
you
a
search
by
project.
So
right
now
we
group
them
by
project.
It
would
be
good
if
we
could.
You
could
search
by
project
too,
and
that
would
give
us
the
option
to
remove
that
grouping
by
project
if
we
wanted
to
in
the
future.
So
I
think
they
and
there's.
I
think
the
other
issue
also
recommends
sorting
them
alphabetically.
B
B
C
B
Yeah,
if
because,
if
we
allow
people
to
use
more
tags,
because
right
now,
this
there's
a
screenshot
in
this
issue
just
the
same
one
yeah
and
then
so
in
the
top
issue.
There's
a
screenshot
of
like
all
of
the
filters
right
now.
We
have
only
a
search
by
keyword
but
tag
right
now
only
populates
with
the
project
line
in
the
info
file.
But
if
we
added
a
tagline
to
the
info
file,
people
could
make
it
so
that
web
form
could
come
up
under
web
form,
but
it
could
also
come
up
under
survey.
B
So
we
could
get
more
things
that
people
might
look
for
in
there.
So,
like
views
might
come
up-
and
you
know
if
you
had
a
views.
Extension
module
might
come
up
in
views,
but
it
might
also
want
to
come
up
under
user
interface.
So
it
just
gives
you
the
ability
to
provide
more
ways
for
people
to
find
to
your
module.
C
All
right:
well,
this
is
a
handful
of
issues
in
the
agenda
with
links
there.
If
anyone
can
sort
of
like
spare
some
time
to
just
provide
feedback
for
those
to
get
these
moving
again,
we
also
meant
to
have
a
meeting
to
sort
of
like
prioritize
things.
A
B
Our
it
is
time
it
is
201.
So
before
I
stop
this
line
screen,
I
just
want
to
see
if
anyone
else
has
anything
particular
to
add
robert.
I
know
you've
been
very
quiet
all
meeting
I
know
greg
and
I
are
both
famous
for
doing
all
the
talking.
So
I
wanted
to
make
sure
you
had
an
opportunity
to
say
something.
If
you
wanted.
A
Oh
nothing
in
particular,
I
I
would
echo
favorableness
towards
the
the
last
couple
of
ui
changes,
the
module,
filtering
change
and
actually
on
the
details.
There
was
another
topic
that
came
up
some
weeks
back,
which
was
how
to
give
additional
information,
for
example,
on
the
text.
Filters,
I
think,
was
the
context
it
came
up
in
there's.
C
I
think
that
I've
found
that
again
what
you
call
request
for
that
using
a
field
set
at
the
top
of
the
page,
but
I
can't
remember
I
haven't
revisited
that
issue
in
a
long
time,
so
it
was
adding
a
huge
piece
of
help
text,
but
it
was
keeping
it
collapsed
so
that
it's
not
annoying
for
people.
But
if
people
didn't
understand
how
that
page
works,
they
could
expand,
it
read
it
and
then
hide
it.
B
A
Yeah
there
was
a
comment
that
was
brought
up,
that
we
could
do
that
now
using
a
title
attribute,
but
that
requires
a
hover
to
access
and
touch
this
interfaces.
A
B
Yeah,
I
just
dropped
a
link
into
zulip
too.
I
think
this
it's
been
a
long
time
since
we've
talked
about
it,
but
it
was
specifically
adding
a
tooltip
which
very
closely
matches
that
thought
of
like
if
we
could
just
put
something
there
that
had
more
information
in
it.
That
was
not
obtrusive
to
everyone,
but
was
there
if
you
needed
it,
and
so
I
think
this
was
recommending
another
form,
api
element
or
form
api
attribute
that
you
could
add
to
anything
and
it
would
provide
that
kind
of
information.
It
could
be
really
useful.
C
Yeah
all
good
ideas,
by
the
way
that
that
field
said
expanding
collapse
in
fields
with
help
text
is
a
patent
that
is
being
used
in
wordpress.
So
yeah.
B
All
right:
well,
let's,
let's
go
ahead
and
wrap
up
this
meeting
and
we'll
start
our
weekly
developer
check-in,
I'm
going
to
turn
off
the
live
stream
thanks
everybody
for
coming.