►
From YouTube: Backdrop Design call 8/27
Description
Backdrop CMS Design!
A
Guess
the
we
usually
start
talking
about
backdrop,
the
product
there's
a
bunch
of
UX
and
design
improvements
in
the
queue
we've
got
a
couple
of
them
that
went
in
in
the
latest
release,
which
I
think
was
a
security
release
which
came
out
last
week.
A
There's
a
whole
bunch
more
queued
up
that
will
probably
get
into
the
next
version
and
then
in
the
one
point
or
in
it
doesn't
welcome
in
want
a
whole
bunch
of
stuff
that'll
come
out
in
one
point
to
which
is
on
we're
going
to
be
including
WYSIWYG
or
rich
text,
editing
in
a
whole
bunch
of
field
modules
and
then
I
think
the
1.3
release,
which
could
be
super
useful
for
people
are
interesting.
A
Design
is
gonna,
make
focused
mostly
on
usability
and
minor
improvements
just
to
make
the
product
better
as
it
is,
rather
than
adding
a
ton
of
new
features.
If
we
want
to
put
some
field
modules
and
administrative
modules
and
stuff
on
that
move
stuff
into
corliss,
that's
fine,
but
I
think
the
primary
fix
is
just
going
to
be.
41.3
is
just
going
to
be
cleaning
up
the
tool
that
we
have
so
other
things.
We're
going
to
be
working
on
is
adding
a
new
front,
end
design.
A
So
if
anyone
has
been
working
on
backdrop
themes
and
they
have
something
that
they
think
is
a
nice
clean
front-
end
theme
that
people
could
launch
a
site
with.
We
can
definitely
talk
about
moving
that
in
decor,
which
will
be
interesting,
but
we
do
want
to
have
that
develop
and
kinship.
So
it's
a
port
or
build
a
contribs
initiating
q,
saying
you're
a
nursing
moving
that
front
end
theme
into
corn.
A
We
can
consider
reevaluate
adjust
as
needed
and
schedule
that
for
the
future
we
also
have
a
style
guide,
which
I
think
is
going
to
become
more
and
more
important
as
things
go
forward
that
will
help
guide
our
user
experience
decisions.
So
when
we're
trying
to
figure
out
which
tools
to
use
wherein
backdrop
we
should
document
and
how
that
decision
was
reached
in
what
that
tool
is
used
for,
so
that
module
developers
know
when
they're
building
user
interfaces
for
their
tools.
A
What
kind
of
patterns
to
follow
we've
got
one
kind
of
loosely
stubbed
out
at
a
backdrop,
ops,
a
style
guide,
but
but
we
know
that's,
not
the
style.
Glad
we're
talking
about
the
little
scattered
I
was
just
talking
about
the
user
interface
guidelines,
which
is
different
from
the
style
guide.
We're
working
on
user
interface
guidelines
to
guidelines
to
the
style
guide
is
what
helps
us
determine
how
things
should
look
and
that
I
think
is
mostly
done
as
we
find
things
that
need
new
styles
or
need
updated.
A
Styles
will
update
them
on
the
stove
at
first
and
that'll,
be
what
we
use
to
figure
out
how
to
make
things
look
consistent
in
different
places,
so
I
think
it
might
even
be
worth
removing
this
style
guide
from
this
agenda
because
we
don't
have
any
to-do
items
left
there.
A
I
think
for
the
most
part
of
stuff
we
wanted
to
get
styled,
is
styled
I,
don't
know
less
if
I'm
wrong
about
that,
but
I
think
we're
in
pretty
good
shape
with
that
right
now,
yea
there's
making
things
mobile
optimized
but
yeah
as
far
as
desktops
concerned,
everything's
good
good
to
go.
Okay,
so
I'm
going
to
take
that
an
agenda,
so
we
don't
keep
talking
about
it
every
week,
but
yeah
in
general
there's
a
bunch
of
stuff.
A
We
need
to
improve
slightly
for
mobile
just
because
we
haven't
ever
been
mobile
before
and
we
do
have
a
handful
of
issues
for
individual
tasks.
They
think
on
that
on
Bob
drop
the
product
as
well
as
on
this
dog,
all
right.
So
big
news.
This
is
the
whole
point
of
today's
meeting
backdrop:
CMS
org.
Our
flagship
website
finally
has
find
modules
things
and
layouts
pages
yay.
A
So
there
Darius
did
a
bunch
of
great
design
work
on
figuring
out
exactly
how
those
should
look
and
work
unless
you
did
a
bunch
of
great
development
on
building
them
out.
They're
now
live
on
the
public
website
and,
as
people
start
writing
more
modules,
names
and
layouts.
Those
will
continue
to
update
automatically
and
we
do
have
some
features
that
are
in
the
designs
that
have
not
been
implemented.
Yet
there
are
development
tasks
there.
A
In
terms
of
we
aggregate
the
data,
we
need
to
display
it
the
way
we
want
and
then
well
of
course,
once
we
have
the
data
figure
out,
you
need
to
figure
out
how
to
make
it
look
correct
on
the
page,
but
I
think
we're
pretty
close.
I
mean
it's
obviously
close
enough
to
launch,
which
is
great
and
that'll
just
get
better
with
time
so
tax
remaining.
A
Work
is
made
to
look
the
way
it's
supposed
to
look,
and
then
we
can
go
ahead
and
close
that
ticket
so
I'm
guessing
those
tests,
you
probably
all
be
filed
in
the
backdrop,
CMS
org
issue
queue
and
anyone
who
wants
to
work
on
that
there
is
a
little
bit
of
integration
needs
to
happen
with
project
modules
and
views.
Integration,
I
think,
will
be
great
because
right
now
our
listing
pages
are
done
through
reviews,
but
also
just
trying
to
figure
out
like
where
the
information
comes
from.
A
If
we
need
to
query
stuff
from
github,
there
will
be
some
integration
with
our
github
project
module
as
well,
so
just
a
little
test
there
to
get
that
done,
but
I
think
it's
looking
fantastic
and
I'm
so
excited
that
we
were
able
to
to
get
those
out
for
the
world
to
see
alright.
So
upcoming.
We
have
a
couple
of
layout
changes.
A
So
we've
got
a
little
follow-up
task
on
those
and
then
we
also
want
to
start
building
out
the
community
aspect
of
the
backdrop
CMS
website,
which
will
mean
we
need
to
let
people
log
in
we
need
to
let
people
edit
their
projects.
We
need
to
just
kind
of
figure
out
how
the
logged
in
user
experience
differs,
make
sure
everything
looks
okay.
What
does
that
note?
A
Edit
form
looked
like
just
kind
of
spending
some
time
on
that,
so
we've
got
a
couple
of
design
review
task,
so
we're
going
to
have
Darius
look
over
the
current
state
of
things
and
see
if
we
need
to
update
anything
to
fit
with
our
branding
or
you
know,
make
it
look
a
little
less
like
default
backdrop.
Also
on
our
list
here,
other
than
the
backdrop
website
itself.
We
have
a
category
for
swag
all
stuff
that
we're
going
to
try
and
buy
and
hand
out
or
give
away,
as
thank
you.
A
Gifts
in
exchange
for
donations.
First
on
the
list
is
a
backdrop
dragon
t-shirt
and
we
have
contracted
the
guy
who
made
drop
our
original
dragon
to
give
us
a
whole
bunch,
more
dragons
and
a
whole
bunch
more
poses
and
then
we'll
be
able
to
pick
out
a
handful
of
those
that
we
want
to
use
for
stuff
in
the
future.
So
if
we
want
a
t-shirt
and
button
and
a
hat
or
a
hoodie
or
whatever
we
can
pick
out
whatever
dragons
we
want
and
use
them.
A
So
I
am
super
excited
to
take
a
look
at
some
of
our
little
dragons
and
see
what
what
the
herd
is
looking
like,
so
that'll
be
great
and
then
once
we
get
the
Dragons,
we
will
try
and
figure
out
which
one
to
use
on
a
t-shirt
and
hand
those
over
to
there
is
to
try
and
get
them
formatted
correctly
for
the
shirt
shirts
printed
and
the
plan
is
to
hand
them
out
at
the
backdrop
summit
at
fat
camp
on
october
22nd.
A
So
if
you
really
want
to
drag
a
t-shirt,
come
to
bad
camp
can't
come
to
fat
camp.
Let
us
know
and
there's
definitely
some
way.
We
could
accept
a
donation
and
mail.
You
a
shirt
so
trying
to
figure
out
how
to
get
that
worked
out
in
order
to
get
people
that
the
Dragons
they
need.
We
also
have
a
reveal
j/s
slide
deck.
It
was
something
that
I
threw
together
really
quickly
and
Wes
made
pretty
and
functional.
A
I,
haven't
actually
got
a
chance
to
use
it
less,
since
you
have
but
I
think
we're
planning
on
doing
a
talk
on
in
two
weeks
at
nerds
summit,
and
I
would
love
to
use
it
then
so
we'll
probably
pull
that
down
and
take
a
look
at
it
and
see
how
to
use
it.
I
wasn't
doing
it
correctly
last
time,
so
I'm
really
looking
forward
to
that.
Thank
you
for
all
the
work
you've
done
on
that
and
today
and
anyone
else
who's
doing
a
talk
on
backdrop.
A
It
is
public,
I,
think
it's
in
the
vector
of
ops
group
and
we
would
love
to
kind
of
make
that
the
canonical
source
of
all
information
anyone
needs,
especially
if
you
have
something
new
that
you
think
other
people
might
want
to
share
something
that
that'll
be
a
great
tool
for
the
vector
of
community.
We
also
have
a
task
here
to
create
branding
assets,
so
these
are
things
like
background
images
for
facebook
and
twitter.
I
know
we
had
a
little
bit
of
activity
on
that
recently.
A
That
happened
in
email
threads,
and
I
wanted
to
move
that
into
a
github
issue
so
that
other
people
could
kind
of
see
the
conversation
and
pick
up
where
that
left
up-
and
I
haven't
done
that
yet
I'll
try
and
get
that
done
today
and
then
yeah
I
guess
I
already
talked
about
the
human
interface
guidelines.
A
We
need
to
get
moving
on
that
too,
especially
as
we
start,
cleaning
up
backdrops
user
interface
and
I
think
that
working
on
the
1.3
release
with
the
UX
clean
up
is
going
to
be
a
great
time
to
start
documenting
the
decisions
we
made
and
why
they
made
them.
And
then,
if
we
find
anything,
that's
inconsistent,
we
can
clean
that
up
at
all
at
the
same
time
document
why
and
I
think
it'll
help
us
make
a
better
product
as
a
whole,
so
I'm
really
looking
forward
to
getting
to
that
all
right.
A
Well,
that
is
all
we
have
for
the
agenda.
Is
there
anything
else
design
really
did
you
want
to
talk
about
Wes
that
we
haven't
been
covering
or
questions
or
anything,
don't
think
so?
No
I'm,
good,
all
right,
well,
I
think
we're
doing
really
well,
in
terms
of
you
know
getting
designs
done
and
getting
them
implemented,
mostly
because
of
you.
So
thank
you
so
much
for
all
of
that.