►
From YouTube: Backdrop Design - Nov 8th
Description
Today’s design agenda: http://bit.ly/2PurM6r
A
A
One
of
them
is
the
modules
themes,
layouts
search
pages,
which
is
something
we've
known,
has
been
an
issue
for
a
while.
We
have
a
sort
of
meta
issue,
number
422,
I'm,
sorry,
442
and
the
back
drugs
I
missed
at
work.
You
four
people
have
been
discussing
all
of
the
different
things
we
can
do
to
make
it
better.
We
have
designs,
we
need
to
fix
the
search
ordering
and
we
want
the
results
to
include
more
than
just
marketing
some
layouts,
but
also
information
about
models,
things
and
Lance
that
maybe
aren't
needed
anymore.
A
So
last
week,
I
had
a
plane,
flight
or
and
nothing
else
to
work
on
and
I
thought
that
was
a
perfect
use
of
time.
I
have
another
one
tonight,
so
I'm
company
makes
more
markets
on
today
that
I
have
started
reworking
the
view
it
used
to
be
like
based
on
feels
implement
a
bunch
of
different
fields
from
related
objects
and
I've
switched
it
to
use
a
special
you
mode,
that'll
load,
the
module
summary
in
a
way
that
matches
the
design
and
also
include
like
a
field
formatter
for
all
of
the
module
info
at
the
bottom.
A
The
node
IDs
of
items
that
might
match
search
and
I'm
writing
a
custom
module
to
alter
the
way
the
search
works
so
that,
when
you
search
for
a
module
name,
it'll
search
the
module
title
field,
more
heavily
weighted
than
the
module
body
field,
for
example,
and
I
think
this
might
get
us
a
better
result
than
what
we
have
right
now.
It
just
starts
reading
all
feel
it's
equally
and
I'm,
hoping
that
we
can
continue
to
tweak
that
as
needed
and
then
and
if
other
people
need
to
adjust
their
search
results.
A
Emily
will
come
up
with
sort
of
a
more
standard
way
for
people
to
do
that.
You
know,
there's
a
couple
of
kinship
modules
for
Drupal
that
allow
that
and
I
think
we
should
be
working
on
solutions
that,
depending
on
can
use
on
their
site
or
similar
results.
So
that's
what
I'm
kind
of
hoping
to
do
with
that.
A
Another
issue
that
came
in
particular
at
the
bag
camp
community
conversation
in
the
summit
was
the
try.
A
demo
button
on
the
home
page
can
be
a
little
confusing
for
people
because
it
goes
to
Pantheon.
If
you
don't
know
what
Pantheon
is
you're
not
encouraged
to
continue
and
going
through
the
signup
process
in
order
to
get
an
account
in
order
to
see
a
site,
and
so
the
first
thing
we
did
right
away
was
changed
the
label
on
the
button
to
say
spit
up
on
Pantheon.
A
Some
people
at
least
wouldn't
be
expecting
a
demo
when
they
click
the
button.
It'd
be
expecting
spent
upon
Pantheon,
and
we
do
want
that
to
be
a
try.
A
demo
button
long
term,
so
Nate
has
been
working
on
using
a
tool
called
tugboat
which
Lola
bot
has
created
for
automatic
builds.
So
it's
something
that's
intended
where
you
can
like
file
a
pull
request
against
a
repository.
It
will
automatically
spin
up
a
sandbox,
much
like
we
have
with
Travis
CI.
A
A
They
just
want
to
try
the
software,
but
even
with
it,
going
straight
to
an
install
screen,
it's
better
than
one
we
have
now,
which
is
taking
a
Pantheon
first
before
you
get
to
install
screen,
so
we're
going
to
try
and
work
to
hook
that
up
as
soon
as
we
can
and
the
way
those
works
is
every
person
who
clicks
on
the
button
gets
their
own
sandbox.
So,
rather
than
something
like
demo
module
or
everyone
who
have
clicked.
A
The
button
would
see
the
same
demo
site
and
once
the
people
could
be
making
changes
to
the
same
site.
Here
we
will
get
their
same
demo
site
and
we
can
determine
how
long
that
site
will
be
around
for
so
you
could
say
like
kill
it
every
24
hours
or
kill
it
after
a
week,
and
that
way
we
could
even
use
something
like
this
for
a
training
like
everybody
go
to
this,
you
know,
homepage
click.
A
The
button
visit
the
site
you
go
to
use
for
today
and
the
tomorrow
will
disappear,
and
that
might
be
something
that
could
be
useful,
for
you
know
more
purposes
than
just
someone
trying
back
drive
so
Nate's
really
excited
about
it.
He's
got
it
most
of
the
way
there.
The
only
piece
left
is
that
we
need
to
set
up
a
page
on
back
job.
A
That
would
be
that,
like
you,
click
the
button
and
then
it'll
be
like
that
you're
about
to
go
to
tugboat
kind
of
interface,
where
we
can
put
in
all
the
information
we
need
in
order
to
send
the
data
we
want
to
tugboat
to
fire
a
society
and
originally
he'd.
Imagine
if
we
put
some
kind
of
like
an
intro
video
on
this
page
to
keep
people
active
until
we
could
load
the
site,
but
it
only
takes
like
eight
seconds
to
build
the
site.
It's
much
faster
than
campeón
sitting
I.
A
A
A
We
can
design
it.
How
we
want
I
was
thinking
having
a
progress
bar.
There
would
be
good,
but
I'm
not
sure
that
there's
like
an
API,
we
can
hit
to
determine
the
progress.
I.
Think
it's
just
like.
Is
it
ready?
Is
it
ready?
Is
it
ready
go
so
we
might
have
to
do
like
a
spinner?
Instead,
it
would
be
like
spinner
and
then,
when
the
answer
we
get
back
is
go,
it
would
just
load
the
whole
thing
so
yeah.
A
Okay,
so
that
is
I
think
everything
that
we're
making
I'm
card
Partizan
or
backdrop
see
I
must
at
work
right
now
for
the
forum
we
have.
One
issue
would
like
to
resolve
it's
issue
number
59
and
that's
that
our
code
block
drop-down
menu
was
quite
enough
to
see
the
code
block
styles
within
we've
had
West
doing
some
work
on
this,
but
we
I
haven't
gotten
something
that
applied
to
the
forum
site
that
actually
worked
so
I,
don't
wonder
if,
like
this
selector
doesn't
match
or
something.
A
Or,
can
you
try
that
recently
and
it's
doing
something
really
weird
so
I,
don't
know,
I
know
you
linked
to
a
comment
on
the
for
requests
that
I
didn't
get
a
chance
to
read
exactly
what
that
is
that
there
could
be
something
in
there.
That
is
causing
modules
to
not
be
installed
or
backed
up
to
think
that
module
something
installed
or
something
I'll.
Take
a
look
at
that
later
today
and
see
if
I
can
figure
out
what
it
is.
Yeah.
B
Use
my
locals
use
beatbox
for
my
locals.
Most
of
them
and
I
have
issues
with
installing
from
the
project
installer,
so
I
haven't
tested
that
what
I'm
gonna
do
is
I'm
gonna,
spin
up
the
dev
installation
and
try
because
I
don't
think
the
same
thing
happens
with
the
project
install
it.
It
only
happens
if
you
manually
put
the
extract
module
in
the
modules
directory
trying.
A
A
We
also
have
the
sticky
submit
question
buttons
issues.
That's
issue
number
566,
that's
one
where
we
have
a
working
full
request
that
we
need
feedback
for
more
people.
Whether
we
think
is
an
overall
user
experience,
improvement
or
not
I
think
it's
something
where
it's
been
using
on.
A
bunch
of
his
sites
already
makes
its
improvement.
A
It's
a
request,
I've
gotten
from
a
couple
of
my
clients,
but
it
is
kind
of
a
very
opinionated
and
so
I
would
love
to
see
more
feedback
from
more
people
in
agreement
that
this
is
an
improvement
before
wood
right
then,
and
what
that
does,
if
you're
not
going
to
finish
it
takes
the
submit
buttons
on
their
content
creatures.
Woman
puts
them
all
these.
If
they're
like
the
bottom
of
your
browser,
so
we're
gonna
list
of
how
much
scrolling
is
involved,
you
always
have
a
submit
button.
B
I
was
demoing
the
v8
recent
visions
of
d8
my
thing
it
was
some
sort
of
either
the
layout
preview
or
the
preview
and
see
how
we've
introduced
the
ribbon
at
the
bottom
of
the
page.
They
have
a
shorter
ribbon
that
runs
across
the
screen
at
the
top
right
below
the
admin
toolbar.
Who
does
the
same
thing
and
I
think
that
they
trying
to
standardize
having
sticky
things
up
there?
Maybe
it
would
be
like
a
I,
think
I,
remember
that
this
idea
was
brought
up
in
the
past.
Maybe
four
different
tickets,
but
yeah.
A
B
A
B
Don't
they
miss
that
and
the
other
thing
is:
if
the
form
is
too
long,
and
they
happen
to
see
that
the
message
says:
click
Save
to
save
your
changes,
but
they
don't
see
the
Save
button
and,
at
some
point
a
finger
filed.
I
think
it
may
be
a
couple
of
years
ago
about
making
the
block
embedding
the
save
button
within
the
message
or
something
that
has
the
less
scrolling
for
the
user.
Oh
yeah,
yeah.
A
B
A
A
Next
issue
31:22
separates
to
help
tack
text
for
status
options,
so
I
think
right
now
there
are
three
status
options.
There's
two
sets
of
help
text
and
it's
live
together
in
one
paragraph
after
the
last
option,
and
so
the
attempt
was
to
separate
the
text
so
that
it
goes
with
each
option.
So
each
option
has
an
explanation.
A
A
Cuz
it
looked
like
a
nice
piece
of
oil
painting
for
to
just
like
tell
it
started
that
one,
it
might
even
to
me
to
just
tell
people
what
the
problem
was
when
they're
running
updates,
rather
than
just
saying
there
is
a
problem
you
could
say
this
particular
model
couldn't
be
this
particular
thing:
we've
had
that
information
already
we
just
had
to
print
it
to
the
page,
so
I
think
that's
it's
ready.
We
just
need
someone
to
do
some
testing
on
it
modak
modules
in
the
Installer.
This
is
also.
A
This
is
something
that
requires
changes
in
a
handful
of
places.
One
of
them
is
the
feed
that
comes
out
of
project
module
and
I.
Think
that's
the
hardest,
one
because
I
think
that's
just
a
custom
query
that
determines
that
and
then
once
we
get
the
promoted
modules
at
the
top
of
that
list,
we
need
to
also
get
them
to
here
in
your
application
when
you're
using
the
installer.
A
B
B
We
mentioned
that
in
the
previous
meeting
and
I
think
Nate
had
an
objection
because
it
said
that
the
promoted
thing
might
be
used.
For
other
reasons.
That's
why
I
said
we
need
to
come
to
a
common
ground.
What
we're
gonna
use
if
it's
gonna,
be
that
which
I
don't
have
an
objection
or
if
it's
gonna
be
a
separate
like
an
additional
checkbox
yeah.
A
A
But
I
don't
know
if
he
art,
like
I,
think
the
reason
we
might
be
thinking
is
cuz.
He
might
have
something
else
in
mind
for
that
checkbox
and
I.
Don't
know
what
that
is,
but
yeah
for
me.
I
just
thought
promoted,
because
if
we're
going
to
put
it
in
project
module
and
other
sites
might
use
project
module
using
something
in
court
would
be
good,
but
I
don't
know
if
he
has
other
plans
for
that
today.
Yeah.
A
A
And
then
any
other
user
experience
issues
we
have
for
vector
are
attacked
with
square
bracket
UX
and
we
have
even
a
subset
of
those
for
one
point,
one
two:
if
anyone
is
interested
in
working
in
these
experience
issues,
all
of
them
can
probably
go
in
the
for
1.12
unless
they
are
significant
enough
that
they
need
to
be
pushed
to
one
point,
one
two,
but
either
way
search
grants.
Issues
are
prioritized
and
I'll
try
and
get
them
in
as
soon
as
they're
ready.
A
Alright.
So
in
the
handful
of
design
related
issues
too,
first
one
is
number
30
209,
which
is
add
three
to
find
color
schemes
the
basis
theme.
So
we
have
a
pull
request
on
that.
Actually,
that
adds
a
handful
of
predefined
colors
things
I
think
they
were
taken
from
Bartok,
but
I
want
to
make
sure
that
before
we
commit
them,
we
run
all
those
color
combinations
through
an
accessibility
checker
to
make
sure
the
contrast
is
hiding,
and
if
we
find
that
the
contrast,
any
of
them
isn't
high
enough.
A
I
would
like
to
get
that
fixed
in
Bartok
as
well.
So,
just
making
sure
it'll
text
on
background
comes
out
in
a
way
that
everyone
can
read
it
and
I
think
other
than
that.
It's
ready
like
it
looks
like
all
of
the
color
schemes
are
there
and
they
changed
correctly
and
they
look
good.
We
just
need
to
make
sure
the
colors
are
correct
or
not
your
colors,
the
median
very
easy
here
for
her
interview,
all
right.
Here's
an
issue
that
needs
opinions
its
number
3309.
A
This
is
something
I
do
on
a
lot
of
my
themes.
Swear
I
will
manually,
go
and
remove
the
tabs
from
the
user
login
page.
The
fact
that
it
says,
like
plugin,
I,
certainly
set
registered
or
plugin
range
or
possibly
site,
is
something
that's
a
total
giveaway
that
it's
at
your
for
backup,
site
and
so
I
often
like
to
remove
those
and
instead
replace
it
with
links
on
the
form
and
the
form
that
goes
into
this
sidebar
use.
A
Your
login
form
already
contains
these
links
where
it's
like
here's
a
little
foramen
and
there's
a
link
to
either
login
it
register.
So
I
often
just
take
that
text
and
drop
it
into
the
mean
form
with
a
port
for
mater
and
then
remove
the
tags
from
that
page
too,
so
to
make
it
look,
Lester,
bully
or
less
back
jockey
and
so
I
thought,
because
I
do
that
on
every
site.
A
Is
this
something
we
should
only
do
in
basis,
because
we
think
anyone
who
extends
basis
wants
this
feature,
but
not
everybody
who
has
a
custom
theme
or
is
it
something
that
would
benefit
every
site
if
we
removed
its
site
wide
so
I
think
we
just
need
more
feedback
on
that
I'm
personally,
like
remember
everywhere,
everyone
will
love.
It.
A
B
Actually
with
you,
then,
then,
because
I
see
it
as
a
part
in
most
modern
sites.
I
think
this
is
a
thing
of
the
past
like
that
stayed
with
Drupal
the
backdrop,
but
if
it
is
to
break
people's
sites
like
if
they
have
already
styled
this
page,
then
the
only
compromise
that
I
can
think
of
is
if,
at
least
in
basis,
we
made
it
an
option
in
the
theme.
B
B
A
Would
be
a
problem,
though,
for
anything
that
is
not
basis
right,
they
wouldn't
get
that
advantage.
So,
like
most
of
my
sites,
I've
got
a
couple
that
are
bases
them
some
things,
but
most
of
them
are
not,
and
so,
if
we
put
that
change
in
for
it
wouldn't
affect
any
of
those.
But
if
we
made
some
kind
of
like
user
settings
checkbox
like
a
higher
higher
up
in
the
theme
where
you
could
decide
whether
you
wanted
those
types
to
be
displayed
or
not
or
and
then
we
could
do
like
a.
A
Template
reprocess,
alter
or
a
or
whatever
way,
I
don't
know
where
what
level
on
the
page
that's
on
probably
layout
something,
and
then
we
could
also
do
a
form,
alter
to
stick
those
and
things
in
higher.
So
we
could
have
it
either
be
a
checkbox
words.
I
put
it
back
the
way
it
was
before,
or
we
could
have
the
checkbox.
That
would
be
like
make
it
the
way.
A
I
want
it
now
and
then
people
could
opt
in
so
we
can
have
it
default
to
being
off
for
new
sites,
and
people
have
old
sites
could
still
have
it
on
something
like
that,
but
we
wouldn't
break
old
sites
that
all
new
site
sitting
on
it.
We
just
need
to
figure
out
like
how
much
extra
code,
it's
adding
to
add
that
backwards,
compatibility,
innovates,
so
I
was.
B
Taking
a
skew
I
was
taking
to
see
if
we
have
a
generic
settings,
global
settings
thing
under
appearance
and
we
don't
have
a
specific
tab,
but
we
have
the
section
that
says
that
has
the
setting
about
the
administrative
team
and
it
already
has
a
checkbox
that
says,
use
the
administrative
thing
when
editing
or
creating
codn't.
Maybe
such
an
option
fit
somewhere
there.
Well.
A
Also
might
fit
with
the
user
account
settings,
since
this
is
just
about
logging
in
we
have
a
section
about
login
information
right.
We
can
have
something
there.
It's
like
I,
don't
know
it,
don't
that's
turning
or
logging
with
an
email
address
or
not.
You
can
put
it
there
and
be
like
do
you
want
tabs
on
the
login
one.
B
B
A
Okay,
let's
see
install
our
design
mobile
update,
we
have
designs.
I,
don't
think
that
for
quest.
Yet
this
is
number
28
73,
so
he
needs
I'm
going
to
work
on
that,
and
then
we
also
have
an
issue
to
make
the
basis
maintenance
page
look
nicer
that
that's
25
28
and
that
also
needs
someone
to
work
on
it.
So
we
have
both
examples
of
article
7
of
what
the
maintenance
stage
can
look
like
when
it's
designed-
and
it
just
looks
like
it's
been
overlooked
and
basis.
B
The
one
that
West
started
31
71
about
the
redesign
of
the
views
UI,
which
is
quite
interesting
like
regrouping
things
in
the
UI,
so
that
it
makes
sense
and
it's
less
intimidating
so
I
know
that
whis
doesn't
have
a
lot
of
time
recently.
But
maybe
someone
else
can
pick
it
up
if
we
decide
what
we
want
to
do
with
it.
Okay,
which
is
also
suggesting
that
we
should
add
something
similar
to
the
theme
preview
that
we've
introduced
in
the
color
preview,
like
previewing
the
views
in
an
actual
parent
theme
or
anything
yeah
yeah,
okay,.
A
So
my
major
concern
about
changing
views
is
that
Muse
is
so
complicated
that
if
we
change
it
significantly
we're
going
to
be
breaking
everybody's
current
understanding
of
how
to
use
it.
But
if
we
change
it
slowly,
a
little
bit
at
a
time,
I
think
that
might
be
our
best
option.
So
I
love
the
idea
of
putting
in
a
better
preview,
so
regrouping
things
I
think
it's
going
to
be
really
hard
because
it's
gonna
take
anyone
who
knows
how
to
use
a
view,
and
it's
gonna
make
them
neat
to
learn
something
new
for
that
job.
A
B
There's
two
things
to
consider
there:
the
people
that
are
abusing
and
configuring
views
are
advanced
users,
but
if
someone
an
on
advanced
user
decides
to
actually
start
using
it
or
learning
about
it,
they'll
probably
find
video
tutorials
online
that
refer
to
the
old
UI,
so
it
might
be
confusing,
but
at
the
same
time
it
seems
like
from
the
mock-up
that
Wes
has
provided.
It
seems
everything
is
more
tidy
and
organized
in
a
in
a
way
that
it
makes
sense.
I,
guess
we'll
have
to
and
I'm
not
sure
if
he
had
a
suite
somewhere.
A
A
A
A
That
would
just
give
people
sort
of
an
indication
that
back
up
this
is
the
place
for
backdrop,
whether
it's
a
cemetery,
a
ball
or
registration
desk
or
whatever.
It
is
we're,
definitely
interested
in
how
many
printed
materials
created,
which
means
need
amount
of
designs
and
so
well.
Anyone
is
interested
in
designing
a
booth
or
just
a
pop-up
in
or
we
can
put
next
to
a
booth.
We
are
thinking
about
it,
so
there's
the
volunteers
and
that's
all
I
have
for
today's
meeting.