►
From YouTube: Backdrop Design - June 20th
Description
Today’s design agenda: http://bit.ly/2QizQbz
A
All
right
we're
on
air
today
is
Thursday
June
20th,
and
this
meeting
is
to
check
in
on
design
and
usability
tasks
for
backdrop
CMS
on
the
agenda.
We
have
a
couple
of
things
on
vector
up
CMS
to
org
that
need
attention.
The
first
one
number
422
is
our
sandbox
demo,
which
is
up,
which
is
great,
but
the
follow
up
tasks
from
that
were
around
cleaning
up
the
try
backdrop
page,
which
is
now
linked
from
the
home
page.
A
We
want
to
make
it
look
a
little
cleaner,
just
so
things
like
logos,
being
consistently
transparent
and
consistently
vertically
centered,
and
with
some
text
in
the
right
places,
I
tried
to
find
transparent
versions
of
the
deed
of
and
whatever
the
other
logo.
Wasn't
they
couldn't
just
by
doing
an
image
search.
So
that's
probably
gonna
require
somebody
reaching
out
to
those
organizations
or
maybe
looking
at
their
websites
to
see
if
they
have
a.
A
And
so
we'll
just
need
to
figure
out
where
to
source
those
logos
from
I
agreed.
It
would
be
better
if
they
were
all
transparent
and
vertically
centering
things
in
CSS
is
hard.
I
also
noticed
that
when
I
launch
the
page
but
I
was
like
that
close
enough
for
now
we'll
fix
it
later
and
so
now
it's
later
and
we
need
to
fix
that.
But
yeah
we
can
do
that
with
a
pseudo
element,
I
think
and
then
I
don't
actually
have
a
link
I.
C
A
Really
yeah
well,
oh
also
so
I've
noticed
this
being
a
recurring
trend
is
that
when,
whenever
I
want
to
use
a
logo
and
I
have
a
lot
of
websites
that
have
like
a
logo
filled,
everybody
is
using
SVG's
now
for
logos,
but
backdrop
doesn't
allow
image.
Svg
handling,
so
I
tried
to
create
a
like
a
file
field
in
car,
or
we
could
upload
images,
just
pretending
their
files
and
then
a
special
wrapper
that
wrap
them
in
like
an
image
tag,
but
I
think
and
I
might
make
that
into
a
good
trip
module.
A
C
Is
this
is
coming
up
more
often
in
the
Q
that
we
have
four
cups
EMS,
so
it's
general
Drupal
lack
of
supporting
it
VG's
and
that's
both
v7
and
v8.
There
is
a
contribute
that
has
a
field
there's
a
problem,
so
you
can
there's
a
few
problems.
One
of
them
is
that
the
dot
SVG
extension
needs
to
be
added
to
they
allowed
expansions
for
images.
That's
one
but
then
uploading
an
SVG
field
does
not
generate
thumbnail
for
is
VG's,
which
is
the
second
bit.
A
It
sounds
like
that:
module
extends
the
image
field.
I
was
thinking
of
extending
the
file
field
so
that
you
would
get
away
there's
also
issues
of
like
validation
like
if
you
put
in
minimum
maximum
dimensions,
it
tries
to
validate
the
size
on
an
SVG
which
it
doesn't
need
to
do,
and
so
like
there's
a
bunch
of
stuff
that
fails
using
the
normal
image
thing.
Yeah
I'll
take
a
look
at
that
module
and
see
yeah.
C
A
Okay,
improving
these
are
experience,
four
modules
themes
and
layouts
pages,
so
I
have
a
branch,
I
think
I
pushed
it
up
where
I've
been
doing
all
the
work
on
the
redoing
of
the
modules
themes
and
layouts
pages.
The
initial
work
just
replaces
the
field
of
view
with
a
view
that
uses
a
View
mode
with
a
display
that
uses
a
View
mode
for
projects
instead
of
a
field,
and
the
project
then
will
reference.
A
It's
like
most
recent
releases,
not
through
a
fused
relationship
but
as
part
of
rendering
the
View
mode,
and
so
it
made
the
view
a
little
simpler,
so
that
I
could
do
things
like
add
different,
like
sort
order
criteria
which
was
a
little
tricky
before
if
we
wanted
to
get
like
featured
stuff
in
there.
I
also
wanted
to
do
something
really
clever
where
those
pages
are
layouts
and
on
the
left
side.
I
wanted
to
have
like
the
results
of
our
normal
search
and
on
the
right
side.
A
I
wanted
to
have
results
of
other
things
that
you'll
need
to
know
about,
while
you're
searching
for
modules
like
if
you're
searching
for
token
module
you'll
find
an
old,
maybe
even
you
won't
get
the
token
one,
but
what
I
want
to
have
come
up
on
the
sidebar
is
like
upgrading
from
Drupal
here's.
What
you
need
to
know
about
a
token
module
and
backtrack.
That's
been
moved
into
core
whatever,
so
people
can
get
a
list
and
then
at
the
bottom
of
that
I
wanted
to
have
like
a
more
info
thing
and
in
a
perfect
world.
A
We're
gonna
get
here.
I
want
someone
to
be
able
to
say
like
these.
Are
the
18
modules
I'm
running
on
my
site,
put
them
in
somehow
and
then
get
a
list
of
instructions
on
like
how
to
handle
all
of
the
stuff?
That's
either
like
printable
or
downloadable
or
referenceable,
via
an
external
link
or
something
because
right
now
you
have
to
look
them
all
up
one
at
a
time,
but
I
don't
know
how
to
do
that.
A
C
D
A
The
way
that
CK
editor
handled
setup
in
Drupal
7
was
that
they
made
you
create
like
a
profile
and
then
the
profile
had
all
the
stuff
you
wanted
configure
for
CK
editor,
and
then
you
would
just
attach
that
profile
to
a
text.
Format
and
back
up.
All
of
those
settings
are
part
of
the
text
format
and
we
don't
have
as
many
settings
as
were
included
in
the
profile,
and
so
we
need
to
do
sort
of
a
careful
like
look
at
the
I'll
pull
out
the
things
we
want
add
them
to
the
text
format.
A
The
profile
was
attached
you,
but
then
I
think
would
also
be
good
to
like
notify
people.
These
are
the
settings
that
we
don't
have
in
backdrop
and
from
their
configuration,
so
we
can
tell
like
okay,
these
are
the
things
that
you
wanted,
that
we
don't
have
and
that
way,
if
there
is
a
kinship
module
which
I
think
people
are
working
on
now,
that
would
add
back
some
of
the
features
from
Drupal
7.
A
C
Thing
is
that
we
have
the
users
statistics
net
for
modules
and
there
was
a
thing
up
to
get
to
see
how
we
have
the
two
downloads
whatever
and
then
active
installs.
But
there
should
be
a
link
that
says
a
few
uses
this
or
something
like
that,
the
equivalent
that
we
have,
indeed,
a
port
that
shows
maybe
a
grant
as
well
like.
D
A
That
would
be
really
great
I
think
there
is
a
spark
lines
module
that
would
let
us
display
those
numbers
as
spark
lines,
so
we
should
check
that
out.
I
also
love
the
idea
of
showing
like
usage
over
time,
like
increasing
I,
think
will
be
really
meaningful
for
people
and
this
you
have
like
a
module
that
like
see,
Canada
or
stop
getting
used
to
1.2.
A
That's
really
old
1.2
websites
that
are
out
there
I
know
yeah
I,
think
that
would
be
great.
The
only
problem
is
we
okay,
I,
don't
think
so.
I
think
there
is
a
kinship
module
for
spark
lines
and
then
there
might
have
been
some
custom
integration
John
on
drupal.org
but
I'm
pretty
sure,
there's
a
module.
Oh
I
hope
it
wasn't
for
Drupal
sake,.
C
A
Comes
from
the
right,
I,
don't
know:
they're
they're,
all
fields
on
the
project,
but
they're
populated
from
different
places.
So
one
of
them
comes
from
the
project
usage
module
and
one
of
them
comes
from
the
project.
Github
modules
like
download
counts,
come
from.
Github
and
usage
comes
from
project
module
likes.
D
A
C
C
A
I,
don't
think
there
is
yeah.
Okay,
so
are
also
on
the
website.
We
have
an
issue
here
for
upgrade
paths
for
modules
in
core
that
it.
The
issue
that
I
have
linked
here
is
a
documentation
issue,
but
the
reason
it's
on
the
design
and
usability
meeting
agenda
is
because
I
want
to
figure
out
how
we
can
expose
this
information
to
people
in
a
way
that's
meaningful.
So
right
now
we
have
one
page
that
is
like
these
62
modules
have
been
included
in
vector
core.
A
C
So
I'm
thinking
that
some
of
the
module
modes
that
are
created,
we
need
a
field
like
in
core
sins
or
something
like
that
and
there's
that
it's
twofold,
so
we
have
outdated,
readme
files
on
github,
sorry,
github
modules,
for
example,
I
was
looking
at
the
ckeditor
and
it
was
saying
something
along
the
lines
that
this
will
not
be
required
when
see
here
it
gets
medicine
which
which
has
happened
now,
so
we
need.
Maybe
people
like
from
the
bug
squad
to
update
the
witness
of
those
things,
because
some
people
might
end
up
directly
on
it
yeah.
C
So
this
needs
to
be
updated
and
then
on
the
work
side,
we
need
to
make
sure
that
a
the
perspective
nodes
for
those
modules
mentioned
that
they've
been
merged
and
be
whatever
is
being
pulled
for.
The
browser
like
the
project
browser
is
that,
okay,
that
mojo
is
not
required
unless
you
have
an
older
version
of
backdrop.
This
is
where
I
say
so.
A
There
is
a
field
on
the
upgrade
instructions,
node
that
but
I
couldn't
I
I
tried
to
make
it
like
a
drop-down
and
I
realize
that's
set
like
sometimes
it
wasn't
entirely
included.
So
I
want
a
different
language
and
there's
no,
it's
just
a
text
field,
but
the
way
that
it
works
with
nodes
on
back
trips.
A
You
musta
org
I,
agree
that
we
need
to
update
it
for
people
who
only
go
to
get
home,
but
I'm
backed
up
CMS
to
work
instead
of
getting
the
project
node
that
has
the
download
link
you
get
the
placeholder
node,
which
has
the
upgrade
instructions.
So
all
of
the
projects
that
were
on
backdrop
CMS
are
that
have
been
moved
into
core,
have
been
unpublished
so
that
hopefully
people
won't
find
them
on
the
site.
They'll
get
the
other
ones.
Instead
does.
A
D
A
C
So,
for
example,
like
people
that
are
using
a
safe
draft,
if
you
think
that
ends
up
in
court,
there
might
be
quite
a
few
sites
using
the
country
mode.
So
we
still
want
to
show
another
version
of
it.
That
sort
of
like
see
how
we
said
that
that
there
should
be
versions
that
have
a
dependency
on
system
module,
smaller
or
equals
to
so
for
people
that
have
not
upgraded
here,
they
might
still
make
the
contributor
in
I,
don't
know
if
we
want
to
support
that
or
if
it
becomes
complicated,
yeah.
D
A
In
one
three
I,
don't
think
we
should
support
that
via
the
I
I.
Don't
think
that
should
like
I
think
if
those
kinds
of
people
need
to
upgrade
because
there's
gonna
be
bugs
and
security
issues
and
stuff.
But
if
you
have
a
use
case
that
demands
that
you
need
to
be
running
one
two,
you
can
definitely
grab
that
project
from
github.
You
can
search
it
and
contribute
oh
and
get
it
that
way.
So.
A
But
we
can
have
you
know,
information
about
both
of
them
appears
like
here's,
your
module
and
then
on
the
side.
It
could
be
like
included,
in
course,
since
and
then
have
all
the
center
of
information
there
too.
So
as
long
as
we
get
both
of
that
both
pieces
of
information
to
people
I
think
that's
fine
heard
two
releases.
A
Yeah
upgrading
next
we
are
gonna
talk
about
backdrop,
the
product
itself
in
user
experience,
improvement
issues
for
that.
The
first
issue
here
is
number
three
thousand
seven
hundred
and
fifty
five,
which
is
a
planned
new
feature
for
backdrop,
114,
which
is
the
addition
of
a
layout
that
you
can
configure
to
be
as
many
rows
and
as
many
columns
in
each
row
as
you
want.
Chocolate
has
been
working
on
this
for
a
while.
It
is
coming
along,
really
well
I
think
we
need
more
reviewers.
We
need
to
get
back
on
the
design.
A
We
need
feedback
on
the
user,
experience
and
I
think
it
can
probably
go
in
pretty
soon,
even
without
all
of
the
reviews
on
stuff,
because
it's
pretty
close,
it
doesn't
see
him
broken.
It
does
I
think
it's
gonna
do
job,
but
it
would
be
good
to
get
more
feedback
on
it.
If
there's
anything
that
people
find
confusing
about
it,
we
want
to
try
and
address
that,
and
then
we
have
a
set
of
follow-up
issues
that
will
make
it
even
better
that
we
are
currently
working
on
yeah.
C
A
A
draggable
the
box
is
checked,
but
I
could
tell
I
could
have
just
been
a
aux-in
I,
don't
think
I
think
we
should
look
at
like
divvy
and
some
of
these
other
tools
that
exist
I
think
Drupal.
8
is
working
on
a
flexible
template
as
well
and
see
how
they
handle
moving
rows
and
see
what
design
elements
they
use
for
that
because.
D
A
C
A
A
C
Doc
will
materially
on
I,
mean
a
couple
of
weeks
earlier,
incubated
that
yellow
cover
and
yellow
color
background,
color
and
hover,
which
at
least
sort
of
like
signifies
that
you're
over
a
row,
and
it
includes
the
respective
drop
button
II.
Yes,
so
you
have
some
sort
of
indication,
at
least
that's
what
okay.
A
C
A
A
Another
thing
I
was
thinking
is
that
if
we
we
could
set
up
two
feeds,
one
for
promoted
modules
and
Whitford
on,
and
then
we
could
have
the
normal
search
results
below
and
just
always
show
like
one
promoted
module
for
each
search,
and
so
that
way
it
wouldn't
push
the
regular
original.
It's
too
far
down,
but
it'd
be
kind
of
like
Google
Ads,
for
you
like
you,
do
a
search,
but
you
never
click
the
top
one,
and
then
for
people
who
do
need
the
one
that's
promoted.
It's
there,
I,
don't
we
aren't
gonna
have
that
many.
C
I
think
we
have
one
or
two
currently
yes
and
thing:
we
decided
that
that
will
be
the
number
like
I
don't
want
to
get
people
there.
It's
basically
telling
the
same
thing
as
d8
experimental
modules,
but
without
having
there
any
drawback
of
adding
them,
adding
them
to
core
and
then
removing
them
from
Corinne,
causing
the
hello
clip.
Yeah
yeah.
C
A
E
A
Will
help
get
sort
of
steer
more
people
towards
the
easiest
path
in
the
future,
rather
than
choosing
something
that's
sort
of
filled,
which.
C
Was
the
same
goal
that
d8
had
but
d8
included
those
in
core,
and
now
there
are
actual
like
we're
facing
problems
were
when
things
get
removed
and
it's
like
the
developers
didn't
communicate
to
the
site
owners
that
you
know
yeah.
That's
that's
a
cool
feature
we're
using
now,
but
there
is
the
risk
of
you
know
it
being
removed
from
core
and
it
did
happen
and
it
did
break
things.
So
we
have
the
benefit
of
having
the
project
browser
there.
C
A
That's
a
little
bit
of
a
tricky
issue
because
we
have
to
update
the
feed
that
your
site
and
just
when
it's
pulling
in
which
modules
are
available,
as
well
as
the
core
in
order
to
style
them
differently.
So
I
think
right
now
we're
locked
on
the
feed
update
part
of
it.
We've
got
backed
up
CMS
to
org
has
promoted
modules.
C
A
A
Moving
on
to
design
stuff,
it
looks
like
we
only
have
one
issue
specifically
related
to
design
and
at
some
point
the
basis
theme
ended
up
getting
a
hover
color
over
the
account
links
that
needs
to
be
removed.
I
think
it
was
added
because
the
account
links
didn't
have
any
hover
State
at
all,
and
that
might
have
also
been
a
mistake.
I
think
they
were
supposed
to
have
a
like
text
underline
or
something
but
right
now,
it's
really
confusing.
A
If
you
have
only
a
few
items
in
your
main
menu,
both
of
them
act
the
same
way
like
the
main
menu.
So
we
need
to
get
that
hover
color
off
of
there,
so
that
we
can
tell
the
difference
between
the
links
that
are
in
the
menu
in
the
links
up
there.
The
account
links,
so
we
have
an
issue
for
that:
3748
I'm,
not
sure
I,
don't
think
that's
going
to
be
too
terribly
complicated.
I
think
we
just
you,
know,
find
where
the
hover
State
is
and
that
and
remove
it
in
the
CSS.
A
But
we
do
want
to
make
sure
we
do
some
testing
with
color
module
to
make
sure
that,
because
previously
color
module
would
have
changed
that
color.
If
you'd
colorize
to
your
theme,
the
generated
CSS
files
will
still
have
that
hover
and
so
I'm
not
entirely
sure
how
that'll
work
after
we
remove
that
from
the
CSS.
A
C
So
one
thing
that
is
related
to
the
header
in
the
z-index
of
the
menus,
the
menu
items
I
started
using
this
new
main,
relatively
new
maintainer,
for
a
trip
that
has
created
the
nav
bar
and
put
it
over
the
number
menu.
And
there
was
a
point
where
he
was
stuck
because
the
z-index
of
menus,
the
main
nav
import,
is
preventing
so
he's
hit
a
roadblock
where
he
cannot
fix
a
thing.
I'm,
not
sure,
but
I
didn't
take
a
deeper
look
at
it.
C
But
I
think
that
we
might
need
to
fix
that
in
core.
So
he
tried
to
fix
it,
but
it
couldn't.
Unless
we
come
up
with
a
solution,
we
might
paint
to
decrease
yes,
so
what
happens?
Is
nav
bar
now
has
drop-down
menus
serve
like
expandable
menu,
the
same
that
way
that
the
admin
bar
has?
But
when
you
hover
over
the
point
where
there's
many
navigation
links?
Yes,
it
disappears.
So
you
can't
go
sorry,
it's
a
usability
and
he
said
that
he
tried
everything,
but
he
couldn't
walk
around
so.
A
D
A
We
want
to
make
sure
it
goes
on
top
of
that.
So
it's
got
to
be
really
high
to
account
for
all
the
other
content
on
the
page
and
because
navbar
is
an
alternative
to
a
solution
that
most
people
are
going
to
be
using
I.
Think
it's
not
going
to
be
a
majority
concerned.
I,
don't
think
it's
something!
That's
worth
changing
core
in
order
to
support,
but
I
do
think.
We
should
figure
out
how
it
can
be
supported
because
we
don't
want
the
stuff.
C
A
C
A
A
Right
anything
else,
we
need
to
talk
about
design-related,
we're
kind
of
out
of
time
today,
cuz
our
late
start
and
so
I
would
prefer
to
go
jump
into
the
Deaf
meeting.
It's
no
kidding,
okay,
alright!
So
let's
go
ahead
and
wrap
this
and
we
will
see
you
guys
in
a
moment.