►
From YouTube: Backdrop CMS design meeting 6/11
Description
Design task check-in for Backdrop CMS
A
All
right
we
are
on
air,
it
is
Thursday
jun
11
and
we're
going
to
do
a
quick
check
in
on
design
tasks
for
backdrop
CMS,
starting
with
backdrop
CMS
org
our
website
last.
We
left
our
heroes,
we
had
a
design
or
the
find
a
module
page
which
I
still
haven't
built
yet
and
we
are
waiting
on
a
design
for
the
module
page
itself,
which
I
think
area
see
we're
working
on.
I
haven't
I,
don't
know
if
you
have
anything
new
to
show
us
it's
last
time.
A
Possibly
not
but
I
think
that's
probably
what
we
need
most
urgently,
because
we
finally
have
modules
on
dr.
Thomas
at
work,
and
it
would
be
great
to
let
people
will
find.
B
A
So
I'm
happy
to
build
the
page
on
a
local
site
that
lets
people
find
them
until
we
have
that
actual
design.
For
the
page
itself,
we
probably
shouldn't
watch
that
we
must.
It
always
launch
it
default
and
then
change
it
later,
but
it
depends
how
bad
this
default.
What's
knucks
other
things
we're
working
on
already
find
themes
page
and
the
theme
Frederick
page
to
find
layouts
page
in
the
layout
project
page.
A
Those
should
all
shortly
follow
the
modules
section
and
should
closely
resemble
them
in
design
as
well,
and
then,
once
we
get
all
of
these
pages
publicly
visible
we're
probably
going
to
get
people
who
want
to
edit
the
pages
like
I'm,
not
only
hearing
one
side
note
serve
photos
or
something
to
their
module
page,
and
in
that
case
we
should
clean
up
the
display
of
the
edit
form
as
well,
so
we'll
eventually
get
there
other
things
we
get
to
work
on.
A
We
have
a
style
guide
that
was
kind
of
hacked
together
from
a
really
really
early
version
of
backdrop
and
then
model
we
modified
the
snot
out
of
it,
and
now
we
have
taken
all
of
our
like
style,
guide,
design,
changes
and
push
them
back.
In
the
backdrop,
so
it'd
be
great
if
we
could
take
backdrop
greatest
HTML
version
of
it
and
push
that
up
as
our
new
style
guy,
then,
when
we
get
sick
working
JavaScript,
we
could
get
our
drop-down
menus.
A
C
A
Are
supposed
to
work
so
I
put
just
a
little
to
do
down
there
for
rebuilding
the
style
guide,
but
isn't
a
sign.
Anyone
I
think
maybe
to
make
an
issue
for
that
too,
so
that
if
somebody
wants
to
jump
in
and
work
on
that,
we
can
use
the
style
guide
can
trim
project
which
should
be
able
to
help
us
create
at
least
a
page,
that
we
want
to
work
on
and
then
voice
just
claimed
it
oh
and
then
we
can.
A
We
can
convert
that
the
static
HTML
so
putting
your
name
on
this
wes,
I'm
in
my
agenda,
okay
and
then
that
I
think
well
how
about
Smoove
forward.
We
don't
have
a
lot
of
things
that
are
totally
you
know.
We
need
a
lot
of
work
from
now
on,
but
I
think
will
be
great
to
have
a
nice
clean
starting
point
for
Windows.
You
change
all
right.
Next
step
is
backdrop
the
product.
We
have
a
fancy
new
admin
theme
that
went
into
1.1.
A
There
are
a
couple
of
minor
issues
that
are
follow-ups
to
the
big
it
admin
theme
changes.
I
noticed
that
Wes
you've
done
a
ton
of
work
on
all
these
little
follow-up
issues,
Sue
and
I.
Think
they're
all
currently
sitting
in
the
pull
request
review
q,
exciting
news
on
that.
We
did
get
our
backdrop
in
turn
back
this
year
and
one
of
his
first
tasks
was
to
do
a
first
review
of
all
of
the
four
requests
that
are
in
the
keel,
so
he's
working
on
that
for
the
last
few
days,
and
that
should
help
us.
A
You
know
if
there's
anything,
obviously
wrong.
We
can
reject
them
really
fast
and
if
they're
actually
ready
to
be
committed,
they
can
be
pushed
over
to
nate's
queue
and
he
can
kind
of
deal
with
them
a
little
bit
more
efficiently.
That
way,
so
hopefully
that
will
help
us
move
through
some
of
our
full
request.
Review
bottleneck
now,
all
right,
so
there
are
a
whole
bunch
of
other
things
that
could
always
use
some
design
or
user
experience
clean
up
in
core.
A
So
hopefully,
that'll
get
worked
out
soon
filled
UI
is
another
part
of
core
that
has
been
problematic
ever
since
the
beginning
of
fields
in
Drupal
and
it's
the
kind
of
thing
where
we
have
the
super
powerful
tool
and
it's
really
hard
to
design
a
really
slick,
efficient
UI
for
something
that's
super
powerful.
So
it
was
bad
when
it
was
first
created.
It
got
worse
in
Drupal
7
because
of
the
way
that
fields
were
separated
into
smaller
parts
and
now
we've
just
kind
of
put
what
we
had
in
Drupal
7
into
backed
up.
A
So
we've
inherited
all
of
this
legacy,
confusing
you
I
SEF.
We
have
a
meta
meta
issue
on
how
to
clean
it
up
we've
linked
to
all
of
the
issues
in
drupal.org
for
ideas
on
how
to
clean
it
up.
That
is
going
to
be
a
really
hard
user
experience
problems
to
solve
so
I'm,
not
counting
on
that
getting
done
overnight,
but
that's
definitely
something
I
want
to
have
on
this
agenda
for
working
on
in
the
future.
A
In
case
they
get
anyone
who's
super
interested
in
trying
to
solve
these
problems,
and
another
thing
that
has
always
been
kind
of
a
nightmare
in
Drupal
is
the
Jews
you
I.
It
actually
got
a
significant
improvement
in
triple
seven
and
we've
inherited
Drupal
subsidies.
You
I,
but
there
are
things
in
herrin
tlie
about
the
view
I
that
are
confusing.
They
could
probably
use
some
cleanup.
A
So
we've
got
an
issue
in
there
for
that,
although
I'm
not
sure
we
have
a
meta
issue
and
backdrop
for
cleaning
up
the
views,
you
I
it's
just
something
that
it's
hard
and
I
think
that
if
we
could
think
of
what,
if
someone
wanted
to
think
about
trying
to
make
it
more
intuitive,
that
would
be
fabulous.
Another
thing
we
have
on
the
list
here
for
backdrop
is
coming
up
with
a
new
front,
end
design.
We
have
some
work
going
on
for
improving
our
kick,
which
is
the
front
end
theme
we
have
right
now.
A
As
that
goes
into
core
right
now,
we've
got
one
great
contender.
It
would
be
great
if
we
had
more
again.
These
things
don't
need
to
go
in
any
particular
version
of
backdrop
like
whenever
they're
ready
we
can
put
them
in,
but
because
this
is
our
design
at
ux.
Mtg.
I'd
like
to
talk
about
them
here,
so
anyone
who's
watching
us
wants
to
work
on
design.
Stuff
wants
to
start
a
front,
end
theme,
it's
nice
and
blanks,
lady,
but
beautiful,
and
can
launch.
We
need
one
of
those,
so
I
started
in
contribs
and
we'll
review.
A
It
will
create
a
core
issue
for
move
at
the
core
and
discuss
possibilities
about
there.
We
also
have
tagged
in
our
github
issue,
queue
which
is
audience
design.
So,
as
we
come
up
with
issues
for
backdrop
that
require
either
design
feedback
or
user
experience,
review
will
be
tagging
them
with
audience
design.
A
So,
if
you're
a
designer-
and
you
want
to
just
take
a
quick
look
over
all
the
open
issues
against
backdrop
that
needs
design
expertise,
there's
a
tag
there
specifically
for
that
all
right,
more
fun
stuff
in
the
swag
department,
we
have
a
couple
of
things
that
we
need.
Our
next
scheduled
backdrop
event
is
a
bad
camp
dates
actually
still
pending
that
Oh.
So
I'm
just
going
to
say,
need
by
October
and
hopefully
we'll
be
able
to
hand
out
t-shirts
and
stickers
in
office
of
a
fat
camp.
A
Of
course,
there
will
be
a
bunch
of
people
who
are
attending
other,
maybe
not
backdrop
sanctioned
events,
the
vector
friendly
events
all
through
the
rest
of
the
summer
and
fall.
If
anyone
is
doing
a
talk
on
back
up
and
wants
to
hand
out
swag,
let
us
know
and
we'll
try
and
get
stickers
either
ships
to
you
or
if
we
have
them
in
a
way
that
you
get
you
can
handle
at
your
talks,
q,
so
I
think
that
would
be
pretty
cool.
We
need
to
order
some
more
stickers.
A
I've
got
some
to-do
items
here
for
me,
order
some
more
dragon
stickers
and
order.
Some
more
word
mark
stickers
and
I.
Think
we
use
sticker
robot
for
favorite
word
mark
stickers
in
those
took
a
while
to
get
out
and
the
sticker
robot
stickers
came
from
or
the
dragon
stickers
and
those
were
I
think
maybe
desert
stick
a
robot
figure,
he'll
I,
don't
remember!
There
are
huge
success
where
those
who
aren't
them
from
where
or
order
mark
and
we
can
get
the
stick.
B
A
A
We
should
order
sticker
robot
stickers
for
the
word
mark
stickers,
because
we
still
have
some
of
those
left
but
we're
out
of
dragon
stickers.
So
I
can
we
should
orders
the
crew
meal
stickers
for
dragons,
so
we
can
get
those
soon
and
then
I
also
think
we
should
send
dragon
stickers
to
anyone
who
is
doing
a
backdrop
talk
so
they
can
hand
them
out
wherever
they
go.
A
A
Okay,
other
things
we
need
I
really
want
to
make
a
dragon
t-shirt,
but
we
need
to
figure
out
how
to
handle
two
colors
and
how
we
want
the
dragon
to
appear
on
a
t-shirt
and
that
might
require
hiring
our
dragon
illustrator
to
draw
us
another
dragon
in
another
position.
Maybe
the
flying
dragon
or
a
fire-breathing
dragon
I,
don't
know,
I
think
it
will
be
good.
One.
B
A
A
All
of
our
previous
teachers
have
been
one
color
to
save
on
costs
so
that
we
could
I,
don't
know,
get
them
done
quickly,
also
and
I
think
if
we
could
do
two
colors,
we
could
get
the
Dragons
like
underbelly,
stripes
and
stuff,
which
I
think
add
a
lot
of
fun
and
yeah.
So
we
need
to
figure
out
how
to
position
that
on
teacher
Trina
makes
any
sense
so
serious.
I
have
that
assigned
to
you
?,
oh.
A
B
A
A
Okay,
so
that's
all
I
have
in
terms
of
swag
I,
don't
know
if
it's
worth
us
doing
more
than
the
tickers
and
t-shirts
right
now
that
both
of
those
have
been
so
successful,
lately
lightening
the
mood
to
just
stick
with,
what's
working
so
okay
flags
to
/
branding
assets.
So
this
is
also
something
I
threw
in
this
meeting,
because
every
now
and
then
I
look
at
our
twitter
page
and
I
realized
I've
got
this
random
image
based
off
from
the
internet.
With
this
background,
that's
like
a
fractal
ish,
repeating
pattern.
A
If
anyone's
watching
this
video
and
they're
looking
for
some
nice
low
hanging
fruit,
design
tests
that
need
to
be
done,
we
could
definitely
use
background
imagery
for
Twitter
or
Facebook
or
any
of
our
social
media
presences.
They
like
meet
images
of
all
sorts
of
random
sizes.
I
think
it
would
be
great
if
we
could
get
that
sorted
out
too,
and
that
could
be
the
kind
of
thing.
If
someone
has
an
hour
here
or
there
want
to
just
throw
something
together,
we
eat
it.
You
can
do
it.
A
It
would
help
with
a
lot
that
might
be
a
great
place
to
jump
in
and
get
started.
A
So
that's
that,
let's
see,
and
then
we
also
have
an
item
on
here
for
our
human
interface
guidelines,
so
this
is
kind
of
stepping
back
from
the
project
a
little
bit
and
saying
you
know,
one
of
the
things
that
makes
like
Apple
products,
so
slick
in
terms
of
their
design
is
that
they
have
really
good
guidelines
around
how
things
should
be,
and
one
of
the
things
that
makes
Drupal
so
poor
in
some
of
its
design
choices
is
that
there
are
no
guidelines
for
anything
and
so
every
developer,
who's
implementing
an
interface
chooses
to
do
it
in
a
particular
way
that
maybe
doesn't
match
any
other
interface
anywhere
else
in
Drupal,
and
so
it
will
be
really
great
for
backdrop.
A
A
You
should
use
a
vertical
tab,
then
people
who
are
building
it
interfaces
would
have
some
rules
to
follow
and
not
necessarily
that
they
need
rules,
but
they
need
guidance
as
to
how
to
create
a
cohesive
whole
like
how
to
create
a
bunch
of
interfaces
for
a
bunch
of
different
things
that
all
our
intuitive
to
people
who
use
it.
So
you
don't
have
to
learn
how
to
use
a
different
interface
for
each
module.
A
So
a
couple
months
ago
we
had
someone
who
was
super
excited
about
coming
in
here
and
writing
these
guidelines
and
we
got
started
on
it.
We
created
a
project,
github
and
I,
know
it's
using
Jekyll
or
something
I,
don't
know
built
out
an
outline
for
what
the
guidelines
should
contain,
but
we
haven't
had
anybody
who
has
the
time
to
go
through
and
add
all
of
the
designs
and
user
interface
patterns
that
we
have
today
as
well.
As
you
know,
some
suggestions
for
things
that
movie
we
want
to
include
for
the
future.
A
So
it's
just
kind
of
an
empty
document
for
now.
I
think
if
we
had
someone
who
maybe
didn't
want
to
contribute
code
or
was
super
in
races
in
humor
human
machine
interface
patterns
and
wanted
to
like
spend
some
time
studying
something
like
this,
it's
another
place
where
I
think
it
would
really
benefit
our
project
to
have
this
document
completed.
But
you
know
it
is
maybe
less
important
than
some
of
the
other
stuff
that
some
of
our
currently
active
contributors
are
working
on.
A
So
we
have
anyone
new
who's,
looking
for
a
place
to
jump
in
that's
another
place
where
someone
could
totally
owned
that
if
they
wanted
to
show
up
and
start
paying
with
hammer
nine
so
another
place,
that's
super
easy
to
get
get
started
on.
So
that
was
all
I
had
in
the
agenda
for
today.
But
I
didn't
want
to
open
this
meeting
up
and
see
if
there
was
anything
else
we
should
be
talking
about
in
the
world
of
design
anything
we
should
add
to
the
agenda
and
talk
about
weekly
or
anything.
D
C
D
A
B
Love
to
get
that
in
and
we
still
have
that
meadow
met,
that
meta
issue
open
for
the
for
the
new
style
guide
that
has,
like
you
know,
two
or
three
items
remaining
in
including
field
sets
I'm,
not
sure.
If
we
want
to
leave
that
open,
it
might
be
a
good
idea
just
to
kind
of
shut
it
down
because
it
or
maybe
make
a
new.
We.
A
A
D
So
what's
it?
What
is?
It
looks
the
same
to
me
when
I
go
to
the
issue
or
a
370,
so
345?
Is
it
all
of
the
different
various
issues
right?
Is
that,
like
the
meta
issue,
okay,
like
a
373,
no
I
just
had
it
sorry
are
once
again
wrong
issue
Fieldy,
why
I
mean
don't
feel
do
I?
This
is
part
of
it.
Isn't
it
and.
A
Well,
I
mean
field
sets
are
on
like
every
interface
everywhere
and
not
only
am
I
going
to
do
with
fields
which
is
a
little
confusing
I
feel
too.
That
is
just
a
HTML
elements
and
we're
just
trying
to
make
sales
for
fields
thats
everywhere.
Field
UI
is
like
okay,
I'm
going
to
create
a
content
type
in
this
content
that
needs
an
image
field
and
node
reference
field
on
or
whatever,
and
just
the
act
of
like.
A
How
do
you
add
an
image
field
to
a
basic
page
like
there's
this
weird
grid
of
all
of
these
fields
across
the
page
with
like
to
add
buttons
at
the
bottom
and
one
of
them's
like
add
new
and
other
ones
that
existing?
And
then,
when
you
add
them,
you
go
to
another
screen
and
you
don't
realize
like
sometimes
it's
another
screen
followed
by
another
screen,
followed
by
another
screen,
and
sometimes
it's
just
one
screen,
and
then
you
like
dealing
second
screen
as
the
same
fields
as
the
first.
It's
just
really
confusing
interface
boom.
C
A
Figure
out
how
to
like
construct
a
thing-
and
it
mean
that's
just
kind
of
arrived
at
that
interface
because
of
what
we're
doing
to
the
database
underneath
it.
So
this
is
a
developer
driven
design,
which
is
a
not
always
the
best
way
to
do
things,
whereas
I
think
if
we
started
from
user
experience
perspective
and
say
what
is
it
we're
trying
to
build?
How
do
you
put
these
things
together?
D
D
A
Any
of
those
content
types
that'll
show
you
what
it
looks
like
now,
and
we
just
have
a
lot
of
like
a
lot
of
the
same
concepts
in
fields
you
at
field,
you
I
in
layouts,
you
I
of
like
the
concept,
is
where
do
I
put
this
thing
on
the
page
right,
but
we've
got
different.
You
eyes,
for
it
like
one
of
the
UI's
is
like
we're
going
to
give
you
a
table
and
you're
just
going
to
drag
and
drop
things
vertically
and
the
other.
A
On
one
of
those
content
types
there's
a
managed
fields:
okay,
I'm
headed
managed
and
there's
both
managed
fields
which
is
like.
How
do
you
add
fields
to
the
thing
and
then
there's
manage
display,
which
is
like
how
you
control
what
they
look
like
when
the
thing
is
finished,
so
one
of
them
is
like
the
input
form
and
one
of
them
is
the
output
of
the
data
and
so
that's
kind
of
a
weird,
like
distinction
of
concepts
to
and
then
in
field
you
I,
we
handle
the.
A
How
do
you
render
the
output
of
the
data
but
in
a
very
different
or
sorry
and
layout,
you
I
in
a
very
different
way
than
infield
you
I,
so
we've
got
the
same
concept
with
completely
different
interfaces
and
I
think
that
we
could
learn
a
lot
from
layout.
You
I
to
field
you
I.
If
there
was
a
way
that
we
could
have
like
the
layout
for
a
content
type
appear
on
the
manage
display
page
like
we
could
I,
don't
know,
there's
some
magic
that
we
could
work
in
there.
But
I
don't.
D
D
D
A
Yeah
I
think
I
think
it
would
be
a
really
fun
problem
to
solve.
It
might
require
some
API
changes,
so
it
might
be
something
we
can't
do
until
backdrop
to
anyway,
but
I
think
like
thinking
about
the
problem
now
and
trying
to
see
like
what
improvements
we
can
make
the
existing
you
I
versus,
what's
going
to
require
it
like
a
rewrite,
is
a
good
way
to.
You
know
start
with
the
perfect
and
goal
and
then
say:
oh
well,
you
know
these
two
things
we
can
do
now
and
everything
else
has
to
wait.
A
B
Just
wanted
to
mention
doc:
wellmont
has
been
going
through
and
porting
things.
It
looks
like
it's
issue,
9
82.
The
issue
is
just
really
simply
titled.
B
That
is
just
lost
with
all
of
the
potential
tasks
that
could
be
done,
find
it
a
really
nice
looking
theme
imported
to
back
drop
and
that's
a
you
know,
a
standalone
task
that
anybody
can
tackle.
That
would
get
you
familiar
with
the
new
layout
system
in
the
theme
system
and
it
would
be
super
helpful
dust
of
the
project.
D
B
D
A
A
The
modules
page
done
soon
like
maybe
by
next
week,
I,
don't
know
what
your
schedules,
like
all.
D
A
A
A
Jun,
18,
ok
and
then
I'll
put
some
dates
on
some
of
these
other
things
too,
but
I
think
like
we
should
focus
on
getting
that
done
before
we
started
the
next
thing
and.