►
From YouTube: Backdrop Design Meeting May 21 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
B
A
D
A
Not
sure
about
that,
he
moves
back
and
forth.
I
am
Jen,
Lambton
I
am
joining
us
from
sunny
California
and
we
should
move
on
to
the
agenda.
Okay,
so
design
theme
is
your
experience
initiative.
So
for
those
of
you
who
aren't
calling
on
weekly
meetings
also,
we
did
submit
a
handful
of
initiative.
Proposals
to
the
PMC
I
believe
two
weeks
ago
and
I'm
not
sure
I'll
check
that
issue
and
see
how
that's
going,
but
we
don't
have
a
go
button.
A
And
so
there
are
a
handful
of
new
issues
and
that's
no
link
from
the
agenda
here
for
the
style
guide
for
any
common
elements
that
we
think.
If
all
themes
made
themselves,
look
good
on
this
style
guide.
It
would
get
us
closer
to
making
those
themes,
look
good
across
all
sites
and
people
weren't
trying
them
at
the
beginning.
And
so
that
includes
things
like
having
all
10
core
layouts
in
there
with
sample,
perhaps
sample
content
in
every
region.
A
A
handful
of
standard
views,
examples
and
just
making
sure
that
the
styling
first
standard
elements
looks
good,
would
also
mean
that
we
could
set
up
development
site
or
test
sites
that
included
all
of
these
elements.
That
would
allow
people
to
look
at
themes,
not
necessarily
on
their
own
site,
put
on
example
sites.
A
We
have
some
infrastructure
work
to
do,
I
think
in
order
to
get
that
up
and
running,
but
we
have
some
good
opportunities
now
using
things
like
tugboat,
which
is
what
gives
us
our
demo
sandbox
is
on
vector
V
and
a
stat
org,
there's
also
a
tool
called
Zen
CI
that
lets
us
do
the
testing
of
issues.
In
the
backdrop
core
q.
They
could
also
be
leveraged
to
spin
up
sites
on
demand
so
and
there's
also
some
options
for
I.
Think
Luke.
A
You
mentioned
like
one
having
one
site
with
a
handful
of
themes
on
it
that
you
could
switch
between
rather
than
having
one
site
with
one
theme
for
every
theme.
One
side
for
you
and
so
I
think
that
we've
got
some
great
options
for
how
to
move
forward
on
that.
We
just
need
to
would
figure
out
to
figure
out
how
to
do
it.
Look
do
you
have
any
other
thoughts
on
the
design
theme
initiative
that
aren't
related
to
the
things
that
I'm
most
excited
about?
So
it's
just
talking
about
that.
C
Maybe
I
there's
two
things:
they
they
come
to
mind.
I
mean
similar
to
the
idea
of
having,
while
themes
for
use
cases
having
a
list
of
yeast
cases,
something
I've
been
noticing,
as
I've
been
going
into
two
things
like
wicks
and
Squarespace,
that
there's
be
defined
by
a
couple
of
like
standard
things
that
people
do
with
websites
and-
and
maybe
we
should
you
know,
make
or
have
work
comes
great,
some
sort
of
list
that
has
those
kinds
of
things.
C
The
other
thing
that
I'm
not
sure
has
been
kind
of
talked
about.
Yet
specific
I
mean
it's
always
on
our
mind,
but
but
I've
been
thinking
having
about
responsive
things
recently
and
and
I
wonder
if,
besides
testing
different
themes-
and
you
know
having
display
elements
for
different
themes,
if
we
want
to
specifically
guide
users
or
how
to
test
on
on
different,
you
know
device
widths,
for
example,
or
like
how
much
of
that
we
should
be
responsible
for
versus,
assuming
that
the
builders
will
know
to
do
that.
A
C
A
That
and
so
I
think
we've
got
two
problems
here.
One
of
them
is
like
making
sure
these
tools
exists,
that
people
can
do
the
thing
and
then
the
second
one
is
making
sure
that
information
gets
to
the
people
who
are
building
themes
and
that
could
be
like
a
custom
theme
on
your
own
site
or
a
theme
you're
contributing
like
you
want
to
make
sure
you
test
it
on
mobile
regardless.
But
if
we
had
a
style
guide
that
included
all
these
common
elements,
we
might
be
able
to
say
hey
theme
developers.
A
If
you
want
to
contribute
a
theme
to
backdrop,
we
recommend
you
install
the
style,
guide,
module
and
then
check
your
site
on
the
following
device:
lids
or
something
like
horizontal
and
vertical
phone
tablet,
desktop
whatever
and
see.
If
I
don't
think
that
should
necessarily
be
a
barrier
to
getting
a
theme
in,
but
we
have
some
pretty
clear
instructions
on
what
to
do
for
like
module
development,
and
we
do
code,
reviews
and
stuff.
A
We
treat
theme
developers
as
though
their
mantra
blockers,
which
in
most
cases
is
good
because
everyone's
a
developer
but
I
think
the
way
that
people
evaluate
themes
is
very
different
from
the
way
to
people
evaluate
modules.
Most
people,
not
opening
module,
will
install
it
and
use
it.
But
people
who
are
choosing
a
theme
don't
want
to
use
it.
They
want
to
see
it
first
yeah.
So
I
think
that
we
might
have
that
just
be.
A
C
C
A
C
C
But
we've
already
like
surpassed
what
any
kind
of
tool
is
going
to
handle,
but
clearly
it's
a
dock
of
some
sort.
It's
recommendations
and
I
think
I,
which
are
having
like
one
thing
like
make
sure
it
works
one
desktop
and
like
don't
forget
to
test
it
on
a
farm
yeah
and
then
I
write
my
paragraph
in
some
kind
of
thrones
weird.
You
know
like
help.
C
A
Yeah
and
I
think
you
know,
with
with
the
core
layout
system
being
responsive
out
of
the
box.
The
amount
of
work
any
given
theme
has
to
do
to
keep
that
should
be
minimal.
So
I
don't
think
it's
asking
a
lot
of
people
to
make
sure
there
are
themes,
look
good
on
phones.
A
The
only
way
I
could
see
that
being
a
problem
is
if
you're
moving
from
something
like
Drupal
7
theme
that
maybe
already
had
a
bunch
of
code
in
it
that
handled
layouts
and
regions,
and
they
were
trying
to
apply
that
to
backdrop
layouts
and
throw
out
backdrops
layout
responsiveness
and
redo
it.
That
might
be
problem.
If
that
theme,
hadn't
also
been
adjusted
for
responsiveness
on
Drupal
7.
A
C
A
That's
interesting,
it
almost
seems
like
yeah
like
we
as
a
like.
Everyone
in
the
world
should
assume
that
everything
works
on
a
phone,
and
that
should
be
a
safe
assumption,
but
in
reality
it's
not
as
but
yeah
so
part
of
me
is
like,
oh
maybe
we
should
put
like
a
checkbox
somewhere.
We
can
be
like
this
theme
works
on
or
whatever,
but
no
it
should
be
the
other
way.
It
should
be
like,
of
course,
it
works,
and
if
it
doesn't,
there
should
be
some
way.
C
A
Yeah
yep
Xing
that
yeah,
it's
tough
I
mean
as
a
developer,
like
I,
don't
develop
on
a
phone
develop
on
a
desktops.
That's
what
my
instinct,
just
like
I
developed
the
desktop
first
and
then
I
add
the
phone.
So
I
can
see
how,
like
that's,
how
you
might
think
it
need
to
render
to
like.
Oh
I'll,
just
write
all
the
code
in
the
Majestic
and
when
you
have
to
do
mobile.
Firstly,
you
have
to
go
back
or
it
seems
to
be
like
okay.
This
is
what
I
see
now.
D
C
C
A
A
That's
crazy!
That's
like
how
we
did
it.
You
remember
back
when
we
used
to
have
like
it
your
site,
the
mobile
version.
What
was
that
28,
10
or
something
yeah.
B
C
You
know
still
sucks
I
mean
the
rest,
no
one
in
the
world
back,
he
does
it
well
and-
and
you
know,
we've
got
lots
of
stuff
to
do,
but
you
know
we
wanted
to
grab
a
competitive
advantage.
We
could
be
the
first
to
do
it
right.
You
know
more
than
half
of
pageviews
happen
on
a
phone,
so
we
fired
up.
The
preview
shoot
you
see
should
get
the
first
thing
designed
and
then
I'm
like
I
should
go
or
at
the
end
is
when,
like.
A
Think
we
have
like
I,
don't
know,
wait
so
we're
trying
to
make
it
so
that
in
the
theme,
preview
or
steam
I
guess
we
call
it
a
preview
image.
There's
like
a
way
you
can
upload
like
one
image
that
represents
to
your
theme
and
we're
trying
to
change
that
set
instead
of
being
a
single
screenshot.
It's
like
a
whole
bunch
of
screenshots,
and
my
hope
for
that
is
that
it
would
be
desktop.
Mobile
tablet,
like
you,
could
have
different
sizes
in
there
I
hadn't
considered
the
preview.
A
Experience
also
need
to
happen
in
mobile,
but
I
could
totally
see
that
I
mean
because
our
sites
are
responsive
and
you
can
and
like
resize
your
browser
and
see
what
they
look
like.
We
could
just
put
in
like
a
little
iframe
and
totally
deliver
that
experience
without
too
much
work.
We
just
need
to
do
it
yeah
interesting.
Can
we
I'd.
A
A
So
I'm
not
sure
which
little
bit,
but
we
already
have
the
ability
to
preview
like
content
in
an
iframe
and
the
color
module
stuff,
doesn't
an
iframe.
So
I
was
thinking.
If
we
took
that
iframe
and
made
it
like
mobile
size,
the
site
would
automatically
show
you
the
mobile
like
what
it
would
look
like
on
mobile.
Actually.
A
C
A
So
this
is
also
leaning
back
towards
your
original
recommendation
in
lieu
of
having
like
one
site
that
allows
you
to
use
something
like
game
switcher
to
change
themes
in
preview,
because
you
could
have
like
a
page
that'd,
be
like
preview,
desktop
preview,
mobile
and
you
switch
to
mobile
and
it
delivers
that
iframe
experience
and
the
theme
switcher
could
be
on
that
page.
It
would
just
like
switch
out
like
here's,
your
mobile
X
page
on
whatever,
and
you
can
navigate
the
whole
site
in
the
iframe
yeah,
so
that
could
even
I.
A
Don't
know
that
if
that
needs
to
be
a
feature
of
theme
switcher,
maybe
so
that
if
you
throw
that
module
and
the
site,
you
automatically
get
that
experience.
But
that
would
be
something
that
would
be
fairly
easy
to
implement
there.
And
then,
if
we
had
a
site
with
game
switch
on
it,
you
can
even
allow
a
lot
of
people
to
be
like
go
to
the
themes.
Page
install
things.
You
want
a
preview,
click
click,
click,
ok,
looks
like
yeah
I,.
A
Yeah,
that
does
also
assume
the
people
previewing
the
teams
or
the
developers
or
I
think
in
some
cases
here,
the
decision
maker
and
which
team
it
is
isn't
the
person
who
does
the
building
I
mean
I,
don't
know,
look
it's
another
thing
where
it's
like
I,
don't
want
to
preview
themes
and
I'd
like
to
see
them
that
way,
but
am
I
the
person
who's
gonna,
use
that
page
the
most
or
am
I
gonna.
Send
my
client
there
and
be
like.
D
A
C
C
A
And
I
think
if
that
experience
was
one
where
like
it
could
be
I
don't
know,
the
easiest
thing
to
do
would
be
heavily
won
my
frame
and
a
little
select
list.
It's
like
what
size
do
you
want
it
and
you
can
change
it
to
whatever
size
you
want
having
all
four
of
them
on
the
page.
Also,
if
you
had
four
options,
whatever
seems
reasonable,
if
you
had
a
large
enough
page,
you
can
also
stack
them
vertically.
If
you
didn't
make
that
page,
responsive,
yeah,
okay,
this
is,
it
seems
not
too
hard.
A
Will
you
make
an
issue
for
the
theme
switcher
module
that
just
says
something
like
investigate:
mobile
previews
and
I'll.
Try
and
take
a
look
at
that
after
today's
meetings.
Okay,
that
sounds
sounds
so
reasonable.
Okay,.
A
We
only
have
a
couple
minutes
left.
So,
let's
move
on
to
product
design,
there
was
one
issue
that
Peter
wanted
us
to
talk
about:
issue
number
44,
Oh
8
in
the
core
queue.
The
title
is
show
enabled
text
filters
above
disabled
text
filters.
So
for
those
of
you
who
are
not
familiar
with
the
text
filter
interface,
this
is
the
thing
that
just
got
an
overhaul
and
back
table
116
where,
when
you're
setting
up
a
text
format
there's
a
whole
bunch
of
different
filters
that
can
run
on
that
format.
A
They
do
things
like
wrap
paragraph
tags
everywhere.
You
have
like
a
line
break,
they
convert
links
or
URLs
into
links
and
they
can
strip
out
HTML
tags
and
the
order
in
which
those
operations
are
performed
is
important
because
you
don't
want
to
like
strip
out
the
anchor
tag
after
you've.
Just
added
an
anchor
tag
for
a
link.
Have
you
had
those
things
in
the
wrong
order?
A
There
wait
like
put
them
below
and
I'm
gonna
turn
them
on.
They
put
them
back
in
order.
That
would
be
fine
or
if
there
was
some
way
where
we
didn't
actually
change
the
weight
in
configuration
when
they
got
moved,
and
it
was
just
some
trick
visually
that
moved
them
to
the
end
of
the
table.
That
might
be
a
good
way
to
do
it,
but
I
wouldn't
want
to
like
change
or
pull
them
into
a
different
table
or
something
that's
something
that
just
wouldn't
prevent
that
order
from
getting
lost.
A
If
we
move
them
around
so
I,
don't
know
Peter
I
haven't
read
the
whole
issue,
I,
don't
know
if
there's
anything
in
there
in
particular,
that
was
discussed
about
how
to
retain
that
value.
A
Okay,
that
sounds
reasonable.
I've
lost
the
link
already,
but
yeah
I
think
if
we
moving
around
with
JavaScript.
That
makes
sense,
and
is
that
tables
not
sortable?
Is
it
like?
There's
no
table
sort
on
there?
There's?
Oh,
no,
it's
just
the
check
boxes,
I'm
thinking
you
remember
there
being
something
funny
about
that.
So
that
should
be
fine.
I'll.
A
Take
a
look
at
that
issue
later
and
add
a
comment
but
yeah
it
definitely
most
of
the
interfaces
we
have
in
backup
core,
where
we
have
items
that
are
unable
to
invite
um's
that
are
disabled
to
disabled
ones,
fall
below
so
that
when
you're
reading
the
table
top
to
bottom,
you
get
the
stuff
you
want.
First,
so
I
think
that
makes
sense
just
that
particular
thing.
A
That
is
a
little
funny
because
it
is
a
table
of
information,
but
it
also
has
order
in
it,
which
is
unlike
most
of
the
other
tables,
that
we
have
information
with
disabled
items.
So
just
have
to
be
done
carefully,
but
if
we
can't
figure
it
out,
that's
also
something
we
could
apply
to
any
future
tables
we
might
have
that
have
disabled
items
wait
also.
A
C
C
A
Back
type
uses
the
bootstrap
chord
grid
system,
which
does
all
of
its
breakpoint
management
stuff
with
classes
and
CSS,
and
so,
if
your
theme
wanted
to
do
it
differently,
it
could
remove
the
CSS
file,
that's
added
by
core
and
add
its
own
or
CSS
library,
in
our
case,
or
it
could
change
the
classes
on
different
elements
if
it
just
wanted
them
to
be.
You
know
two
columns
wide
instead
of
three
columns
or
one
column
or
what
have
you
the
way
the
themes
interact
with
the
layout
system.
A
So
if
you
wanted
to
change
the
grid
system
entirely,
not
use
bootstrap,
you
can
do
that
in
the
theme.
If
you
wanted
to
change
the
braid
points
in
the
bootstrap
grid
system,
I,
do
this
a
lot!
You
can
do
that
in
your
theme
by
overriding
a
single
style
sheet,
so
it's
possible
to
do
what
you're
asking
from
a
theme
perspective,
but
there
isn't
like
a
user
interface
for
breakpoints
like
there
is
using
something
like
the
break
point:
module
and
Drupal.
C
A
So
if
you
have
a
well-documented
theme
or
you
already
understand
how
bootstrap
works,
you
can
use
all
of
the
interfaces
all
over
backdrop
to
add
classes
and
again
those
things
have
to
work
together
and
you
have
to
know
what
classes
to
use
where
Wes
wrote
a
module
that
reads:
classes
out
of
your
themes,
info
file
and
puts
them
into
the
user
interface
for
you,
which
is
I,
think
a
little
better
because
it
doesn't.
You
don't
have
to
know
how
your
theme
is
built
before
you
add
the
class.
It
helps.
A
C
D
A
Yeah,
it's
also
like
there's
a
whole
bunch
of
issues
that
are
related
still
like
importing
can
take
having
dependencies
there's
a
whole
bunch
of
stuff
that
has
use
cases
in
the
real
world,
but
gets
really
complicated.
What
used
to
hurt?
You
can
also
imagine
these
cases
where
people
who
can
get
into
a
lot
of
problems
like
you,
wouldn't
think
that
installing
a
theme
might
like
overwrite
some
setting
you
had
somewhere
else
and
if
you'll
add
config
import,
we
wouldn't
have
any
way
to
control
like
what
config
is
important
people
good
looking
forward.
A
Anything
and
same
thing
with
dependency
is
like
you
could
get
yourself
where
you're
like
theme
depends
on
a
module
which
depends
on
a
theme
which
I
don't
know,
there's
like
a
like
a
whole
bunch
of
really
tricky
stuff,
but
yeah
I.
Think
all
of
them
are
valid
and
deserve
careful
consideration,
but
I
don't
have
no
answers
to
whether
they're,
actually
good
ideas
or
not.
C
Cut
their
heart,
I
was
just
picturing
from
the
content
admitted
it's
very
easy
to
imagine
to
just
you
know
whether,
whether
they're
on
the
phone
or
computer-
it's
like
you
know
if
they're
coming
to
get
this
information
from
my
thing,
if
they're
you
know
no
matter
what
we
have
to
tell
them
like
the
thing
that
they're
looking
for
you
know,
they're
the
comfort
of
my
restaurant
they've
asked
to
know
the
location
all
that
I
gotta
give
them
the
location.
I
gotta
give
that
address
now.
C
C
A
A
Yep,
alright,
let's
let's
go
ahead
and
wrap
this
meeting,
because
we
have
a
developer
meaning
to
jump
into
with
a
bunch
of
exciting
news,
so
I'm
go
ahead
and
the
or
actually
Luke
is
gonna
go
ahead
and
end.
The
recording.