►
From YouTube: Backdrop Design 4/27
Description
Today’s design agenda: http://bit.ly/2pdVShM
A
All
right
brown
hair,
it's
Thursday,
April
27th.
This
call
is
for
a
quick
check-in
on
design
related
tasks
for
backdrop,
CMS
on
the
agenda.
For
today
we
have
a
bunch
of
issues
specifically
being
fixed
or
included
in
backdrop
1.7.
Since
code
freezes
next
week,
there
are
likely
still
design
related
issues
that
could
get
in
post
code
freeze,
but
we
already
have
some
stuff,
that's
already
gotten
in
which
is
great.
Since
last
design
meeting
we
we
didn't
really
redesign
the
autocomplete
widget,
we
just
kind
of
added
style.
A
It
wasn't
there
before,
but
now
that
autocomplete
will
work
and
look
a
little
bit
more
like
the
rest
of
our
theme
in
lots
of
different
places
where
it
appears
on
the
site.
The
two
examples
that
I
use
most
often
are
when
you're
editing
any
node.
You
can
go
to
the
authoring
information
section
and
type
in
a
username
there
and
not
a
lot
of
complete
on
all
existing
user
names
and
we're
also
about
to
introduce
a
new
feature.
We're
in
a
link
dialog
in
CK
editor.
A
So
we
sorted
all
of
that
out
at
once,
so
that
was
emerged,
which
is
fantastic
how'd
our
two
issues
we
could
probably
use
some
more
feedback
on
we've
got
one,
that's
super
close,
which
is
redesigning
the
status
report
in
the
update
status,
listing
so
modules
that
have
available
updates
and
there's
a
pull
request
for
that
I
think
there's
one
little
bug
left
in
it
I
think
it's
great
starting
point
for
what
we
want.
A
Those
two
pages
to
do
I
think
there's
probably
still
room
for
improvement,
in
particular
in
the
user
experience
area,
but
I
think
if
we
can
get
that
into
one
seven,
that
will
be
a
big
win
and
we
can
continue
to
iterate
going
forward
if
we
want
a
little
more.
A
It's
in
sonim
there's
an
option
in
here.
Oh
my
gooosh
adieu
views.
First,
there's
also
an
open
issue:
issue
number
930
for
bringing
the
CSX
on
the
views
UI
a
little
bit
closer
into
line
with
the
rest
of
the
user
interface
in
the
17.
It
looks
like
they're
greater
you
just
posted
a
new
poll
request
for
that
today
that
updated
a
couple
more
little
things,
but
that
could
use
some
feedback
and
then
I
wanna
do
see.
A
A
I
saw
yours
and
it
was
Gregory's
awesome.
Wait.
I
just
run
a
lot
of
github
issues.
I
could
have
gotten
it
confused.
A
B
A
A
B
What
we
were
going
to
do
is
we're
going
to
let
the
dust
settle
and
see
what
your
boy
saying
over
in
the
normalize
issue
tracker
and
there
hasn't
been
any
activity
in
the
past
couple
of
weeks
in
the
normalized
issue,
record
I
think
that
people
are
accepting
the
removal
of
the
opinionated
styles
and
are
in
general,
supportive
of
the
opinionated
CSS
replacement
file,
I'm
still
not
totally
sure.
If
we
should
dive
in
and
update
to
6-2
normalized
version
6
or
not
like
we
could
very
well.
B
A
Feel
that
way
to
issues
currently
tagged
with
one
seven,
which
is
why
I
wanted
to
bring
it
up
again
today.
But
if
we
want
to
push
it
to
one
eight
and
then
by
then
the
dust
hopefully
will
be
more
permanent.
A
B
C
I,
don't
think,
but
by
the
way,
the
the
maintainer
czar
speaking
all
that
the
I
don't
think
they're
gonna
they're
gonna
back
up
from
that.
It's
a
firm
decision,
it's
more
like
the
rest
of
the
people
using
the
library
just
realizing
that
it's
a
fact
now
and
I
get
with
Lucia
gated
one
H
I
would
have
done
it
myself,
but
I.
Don't
think
we
have
that
friends
yet
so
perfectly
fine
makes
sense.
C
B
Because,
even
if
I'm,
it
seems
like
set
now
that
he's
not
going
to
put
the
opinionated
styles
back
in
normalize,
we
don't
know
what
the
solution,
like
the
final
accepted
solution
for
having
those
opinionated
styles
is
like.
There's.
There
is
an
opinionated
library,
that's
true,
but
we
don't
know
if
that's
going
to
become
the
de-facto
solution
for
people
to
want
this.
You
know
so
I
mean
waiting
is
our
best
course
of
action.
C
I'm
not
sure
if
this
fits
their
design
meeting
thing
that
I
know
it's
a
great
feature.
I
mentioned
that
on
get
er,
sorry
on
the
github,
but
it
feels
funny
how
the
new
title
block
dates:
block
debates,
that'll
block,
sorry
of
thing
that
it's
happening
when
you,
when
you
add
a
block
such
a
block,
then
the
default
title
sudo
block
just
disappears
and
then
reappears.
It
just
feels
a
bit
funny,
but
we
can
discuss
that
them
get.
A
Help
as
well
yeah,
so
the
we're
proposing
adding
a
new
feature
to
one
phone
that
would
give
us
a
block
that
we
can
place
anywhere
on
the
page
that
will
display
the
page
title
and
the
problem
is
that
we
have
configuration
settings
in
the
layout
itself
with
an
element,
visual
element
that
has
I
configure
length
where
you
put
in
a
bunch
of
settings.
When
you
add
the
new
block,
you
now
have
the
same
settings
duplicated
in
the
block,
and
so
it's
a
little
bit
of
a
confusing
experience
where
it's
like.
A
Do
I
configure
the
page
title
where
the
page
title
is
configured
or
do
I
configure
it
in
the
block
and
then
why
can't
I
just
drag
that
pseudo
element
into
a
region
and
I
think
that
four
one
seven
there
might
be
a
easy
fix
for
this
in
terms
of
just
like
hiding
stuff,
that's
going
to
be
confusing.
Like
the
instant
you
place,
the
student
like
the
real
block
on
the
page.
The
pseudo
block
disappears
and.
A
And
then,
if
we
could
copy
the
like
settings
from
the
student
block
into
the
real
block,
when
you
place
it,
then
when
you
go
to
configure
it
you,
it
would
you'd
see
the
stuff
that
was
already
there.
So
I
think
we
can
kind
of
make
that
user
experience
a
little
better
from
a
like
it,
not
seeming
broken
perspective.
I
agree.
A
It
would
be
better
if
we
could
grab
the
title
and
drag
it
and
drop
it
where
you
want,
but
that's
probably
going
to
be
a
bigger
piece
of
functionality
that
we
have
to
develop
so
that
we
can
make
an
element
grab
a
bowl
and
then,
when
you
drop
it
it
would
essentially
do
the
action
of
placing
the
other
block
in
the
page.
I
think
it's
possible,
but
I
think
it
may
be.
A
Maybe
that's
something
that
we
should
not
need
for
a
requirement
for
getting
the
initial
placeable
block
problem
solved,
but
like
how
to
follow
up
like
let's
do
some
greatest
work
on
user
experience
here
and
build
in
a
tool
that
will
let
us
sort
of
drag
and
drop
that
block
in
the
same
way.
We
can
drag
yet
drag
and
drop
the
other
ones,
but
have
a
different
different
engine
on
the
back
end.
Well,.
D
I
think
that
the
question
of
where
we're
actually
going
within
the
long-term
with
this
weather,
we
want
to
keep
the
pseudo
block.
I
mean
this
is
a
great
solution
for
dealing
with
the
fact
that
there's
a
bunch
of
sites
out
there
now
that
have
this
duo
block,
but
would
we
want
to
like
for
new
installations?
Would
we
want
to
continue
using
the
super
block
or
we
want
to
place
a
title
block
in
one
of
the
regions
by
default?
Yeah.
A
That's
another
good
point
to
like
it
might
just
be
easier
to
say,
starting
in
backdrop,
1:8
there's
no
pseudo
Block
in
the
layout.
All
new
layouts
come
with
the
block
placed
and
then
nobody
would
ever
even
see
that
and
then
in
backdrop
2.
We
can
just
remove
it
and
that
would
eliminate
a
lot
of
these
problems.
Yeah.
B
Yeah
we
basically,
we
need
to
come
up
with
another
set
of
layouts,
like
the
same
way
that
we
deprecated
our
original
layouts
and
replace
them
with
new
ones.
We
could,
in
theory,
do
that
you
enduring
one
dot,
X
and
deprecated
the
current
layouts
with
the
whole
new
replacement
set
of
layouts
that
don't
have
the
title
or
tabs
or
action
links
or
anything
hard-coded,
and
instead
it's
all
blocks
well,.
A
I
mean
the
way
those
work
now
it
should
be
fine,
even
if
you
don't
have
any
content
there
right
or
are
there
like
wrapper
elements
that
will
still
appear
like
there
might
be
some
stuff
we
can
do
with
with
like
if
statements
like
it,
if
title
print
title
I,
don't
assume
there's
always
going
to
be
it
I
mean
I
agree.
It
would
be
better
to
have
layouts
that
will
cleaner
for
people
to
start
from
and
copy.
B
No
I
I
mean
the
tone
some.
B
B
Often
you
can
just
move
it
in
the
first
place,
and
that
makes
things
substantially
easier
for
other
things
like
tabs
and
action
links
and
the
method
is
aren't
even
represented
in
the
layouts
UI
right
now,
like
they
don't
show
up
as
blocks
there's
no
way
to
configure
them
or
anything.
Those
are
hard
codes.
I'm
a
little
bit
worried
organize
a
little.
B
E
B
C
D
Yeah
I
mean
basically
my
point
was
that
we
can
do
that
if
we
want-
and
if
you
want
to
go,
do
that
you
could
do
that.
But
I'm.
Just
saying
like
you
know,
if
we
want
to
move
towards
having
the
it
be
a
block
by
default,
going
forwards
instead
of
the
pseudo
element,
then
we
might
not
want
to
waste
the
time
on
dragging
that
pseudo
element.
B
We
already
have
some
funny
business
and
they're,
just
like
Jen
suggested.
As
you
add
the
title
block,
the
title
pseudo
block
disappears
yeah,
so
we
already
have
some
craziness
going
on
and
then
probably
just
be
a
difference
of
craziness
to
accomplish
the
same
thing
and
it
differently.
Yeah
I
tried
different
UX
I
mean.
D
D
A
Buy
her
something
you
can
I
think
it's
just
about
like.
If
we
remove
the
student
like
which
comes
with
the
tabs
in
the
title,
we
would
need
the
place
that
come
like
that.
I,
don't
know
what
it's
called
the
collective
block,
the
one
that
has
all
of
those
things,
because
we
can't
ever
have
an
instance
when
those
things
aren't
printed
to
the
page.
So
I
think
like
leaping
our
existing
like
layout.
Template
solution
in
place
is
good,
we're
like
if
somebody
removes
tabs
we're
going
to
put
them
on
a
page
anyway.
A
Somebody
remove
those
messages
we
have
to
put
those
on
the
page
anyway,
like
having
that
fallback
and
having
it
for
not
and
layout,
is
important,
but
I
don't
know
that
having
a
title
on
in
the
layout
is
important,
and
so,
if
we
wanted
to
remove
that
in
the
layout
I
don't
know,
we
could
probably
do
that
car
mode,
yeah,
the
combo
block,
but
yeah
anyway,
I
think
for
1:7
Gregory.
We
should
identify
the
pieces
that
make
you
the
most
uncomfortable
and
see
what
we
can
do
to
fix.
A
That,
like
I,
think
like
adding
some
JavaScript
to
hide
things,
is
easy,
adding
hot
JavaScript
to
drag
the
pseudo
block
is
going
to
be
hard.
So
that's
why
we're
pushing
back
a
little
bit
on
that,
but
anything
we
can
do
to
make
it
better
easily
like
there
might
be
other
things
we
can
do.
We
should
aim
to
do
that
and
then
we
should
Corrine
another
issue
where
we
can
kind
of
talk
through
this
process
of
like
what
are
we
going
to
do
with
the
layouts?
What
are
we
going
to
do
like?
A
Should
we
just
get
rid
of
this?
You
know
title
permanent
like
installations.
If
we
can
figure
out
like
okay
once
we
know
where
we
want
to
go,
I
think
we're
moving
the
pseudo
title
area
is
probably
a
good
direction
and
we
can
start
figuring
out.
How
are
we
going
to
get
there
and
how
much
of
that
can
we
do
in
one
point
at?
A
C
I
think
it's
four
one:
seven,
it's
too
great
a
feature
to
just
push
it
back
to
one
eight,
just
because
it
feels
upward
the
way
that
it
is
now
it's
very
acceptable
and
then
for
one
eight
or
maybe
because
it's
a
UX
issue,
maybe
iterate
over
the
17.8
cycle.
We
can
improve
it
yeah.
If
you
have
to
stop
us,
because
it's
a
it's
a
really,
it's
a
feature
that
people
can
use
now
and
that
it's
been
requested
a
lot
so
and
especially
since
it's
it's
what
Mike
said
as
well.
A
A
A
Almost
so
I
fixed
think
I
fixed
about
it
yesterday
about
it.
Looking
a
little
funky
on
mobile
devices,
but
I
was
unable
to
reproduce
that
problem
and
he
was
unable
to
reproduce
my
solution.
So
it
would
be
good
to
get
some
more
testing
on
that,
just
to
make
sure
that
the
layout
on
mobile
is
not
broken.
C
C
A
Posted
some
feedback
on
that
too
I
think
we
need
to
be
careful
that
we
don't
copy
a
user
interaction
patterns
from
forms
on
to
reports,
so
like
drop
buttons
in
there
would
make
me
uncomfortable
because
there
aren't
any
operations.
These
aren't
operations.
But
I
did
like
your
point
that,
like
when
these
things
are
like
actionable
items,
they
should
be
buttons
and
not
links
and
I
did
update
on
like
available
updates
available
page.
There
was
the
button
that
was
like
check
more
now.
I
turn
that
into
a
button
style.
A
We
could
use
that
just
like
generic
button
style.
I
think
that
would
be
good.
So
people
know
like
this
is
not
just
a
link.
It's
going
to
perform
an
action.
I,
don't
know
where
to
put
the
button
I
think
you
have
a
really
good
point
about
the
fact
that
on
mobile,
like
the
run
cron
link
disappears
like
is
that,
where
do
we
put
it
so
that
it
doesn't
disappear?
Had
a
couple
of
ideas
like
we
could,
we
could
put
it
in
a
new
column,
just
not
call
it
operations
and
that's
probably
fine.
A
We
could
put
it
outside
of
the
description
field.
Step
so
that
it
would
always
be
visible,
so
we
could
either
do
it
above,
so
it
would
be
like
the
description
of
the
problem.
The
link
that
says
show
more
and
then
like
a
button,
do
something
or
we
could
put
it
like
below
I,
don't
know,
I
have
a
there's
a
lot
of
solutions.
I
would
love
to
see
some
kind
of
mock-up
ahead
of
time,
even
if
it's
just
like
dropping
in
this
before
we
start
writing
code,
because
we
play.
C
But
the
easiest
solution,
if
it
makes
sense
with
that,
would
be
to
make
its
entry
be
sort
of
like
behaving
the
ones
that
have
a
more
link
behaving
as
expandable
field
sets.
I
think
we
have
that
happen
elsewhere,
as
well.
I
think
vertical
tabs
acting,
so
they
should
be
at
a
more
button
there
when
a
mobile
and
if
there's
an
action
which
still
show
the
description,
but
it's
hidden
there,
life
makes
sense.
Okay,
so.
A
Anything
else
you
can
think
up,
no
okay.
So
the
only
other
item
on
the
agenda
today
was
just
to
talk
about
the
new
theme
for
backdrop:
CMS
org
I
know
s
has
made
a
ton
of
progress
on
that,
but
he's
out
this
week
at
Drupal
con.
So
maybe
we
should
chat
with
him
when
he
gets
home.
Oh
and
I
know
he
and
Tom
came
to
me
yesterday
when
they
were
working
on
content
for
the
new
homepage
too.
So
they've
been
been
working
on
it,
while
they're
awake,
which
is
exciting
thanks,
guys
I.
C
E
A
No
type
should
be
called
feature:
I,
don't
know
if
he
created
it
on
the
website
or
if
he
just
created
it
on
his
computer,
wherever
he
happened
to
be
working
with
less
so.
A
A
Nope:
okay:
let's
go
ahead
and
wrap
up
this
meeting
and
we
will
have
our
developer
call
in
half
an
hour
and
yeah
getting
closer
thanks
for
all
the
iterations
and
all
the
design.
Issues
in
the
keel,
I
think
backed
up
something's
gonna.
Look
really
pretty.