►
From YouTube: Backdrop Design call
Description
Design task check-in
A
November
fifth
and
we're
gonna
have
a
quick
design
task
check
in
meeting
for
backdrop,
starting
really
quick
talking
about
the
product
itself.
I,
we
have
our
next
minor
release.
1.3,
it's
a
design
or
user
experience
focused
release,
so
we're
trying
to
make
some
significant
changes
to
the
interface
to
make
the
product
better
and
of
those
we
have
a
couple
of
a
few
major
ones
that
we
want
to
improve.
First
is
layouts
layouts
as
a
new
system,
we
added
in
backdrop
one.
A
We
know
that
the
current
interface
is
not
perfect,
but
it's
definitely
workable
as
it
is.
We
want
to
spend
some
time
improving
that
experience.
We
have
a
list
of
follow-up
issues,
they've
been
created
based
on
getting
the
first
version
in
it.
We
just
need
to
crank
through
and
I
think
most
of
them
can
be
added
in
1.3.
That
issue
on
github
is
number
345
and
I
think
we're
on
the
way
to
making
good
progress
with
that
one.
Another
thing
we'd
like
to
prove
is
the
views
you
I.
A
We
don't
want
to
change
it
too
much,
because
we
know
that
the
views
you
I
has
been
really
successful
in
Drupal
7
and
that
the
people
who
know
it
already
know
it
and
trying
to
change
it
up
from
under
them
sometimes
makes
people
grumpy.
But
we
do
have
a
couple
of
tests
with
views
that
include
things
like
making
the
font
consistent,
making
it
the
right
size,
making
the
interface
mobile-friendly
there's
a
bunch
of
just
little
improvements.
A
A
bigger,
much
harder
problem
to
solve
is
the
field
you
I,
and
this
is
something
that
was
not
super
great
when
it
was
first
invented
and
we've
been
carrying
a
lot
of
baggage
throughout
Drupal
with
the
field
you
I,
it
got
worse
from
Drupal
6
to
Drupal,
7
1
fields,
lion
core
and
it
stayed
worse
through
all
of
the
Drupal
7
early
cycle
and
that's
what
we
inherited
for
backdrop.
There
are
a
handful
of
law
issues
for
field.
You
I
in
Drupal.
Handful
of
issues
reveal
do
I.
A
What
is
the
right
user
interface
for
solving
that
problem,
building
something
new,
so
that
issue
is
number
seven
seventy-nine
on
github
and
it
looks
like
I'm
not
sure
if
this
is
new
since
this
week
or
nuisance
last
week,
but
it
looks
like
Wes
has
been
doing
a
bunch
of
work
on
trying
to
change
the
order
in
which
we
build
the
form
which
I
again
don't
agree,
is
the
right
way
to
build
a
field
system.
But
that's
the
only
way
we
have
oh
I,
think
making.
A
What
we
have
better
is
definitely
an
improvement
and
we
should
start
there.
So
if
anyone
wants
to
see
at
work
on
that,
it
looks
like
I,
don't
know
which,
like
comment,
numbers
are
not
super
clear
here,
but
it's
issue
779
see
I.
Think
he's
been
posting
screenshots
along
the
way
too.
So
you
can
check
that
out.
Okay,
we
also
have
a
whole
bunch
of
other
issues
scheduled
for
the
1.3
user
experience
release.
A
Some
of
them
are
really
tiny,
just
changing
words
and
changing
classes
on
things,
and
some
of
them
are
a
little
harder,
or
at
least
will
require
more
thought
like
moving
things
around
in
the
user
interface,
adding
features
that
make
things
more
intuitive.
But
if
you
check
out
the
milestone
on
github
for
1.3
point,
oh,
you
can
see
a
whole
bunch
of
user
experience,
tagged
issues
there
and
we'll
see
how
many
of
these
we
can
get
through
on.
Not
all
of
them
need
to
wait
until
the
1.3
release.
A
A
So
this
is
something
I
think
is
super
important
for
backdrop
as
we're
trying
to
start
competing
more
and
more
with
WordPress
is
trying
to
make
the
user
experience
much
better.
Drupal
is
notorious
for
being
hard
to
use.
I'm,
confusing,
inconsistent
and
I
think
it
will
be
great
if
we
can
kind
of
solve
some
of
those
problems
in
backdrop,
and
especially
if
we
could
help
that'd
be
a
roadmap
for
what
Drupal
is
doing
in
the
future.
A
You
know:
there's
a
bunch
of
work
going
on
in
Drupal,
8,
make
it
a
little
more
user
friendly,
but
I
think
we
can
kind
of
both
solve
different
problems
and
share
answers
and
both
products
get
better.
So
that's
that's
my
goal
here
and
having
an
entire
release.
The
1.3
cycle
devoted
to
user
experience
I
also
think,
is
going
to
be
huge
risk
because
it'll
show
like
okay.
Yes,
we
got
the
product
out
on
time.
A
So
I'm
very
excited
about
1.3.
We've
got
a
bunch
of
other
stuff
we're
working
on
two.
That's
not
actually
backdrop
the
product,
but
I
wanted
to
spend
a
couple
minutes
talking
about
the
website,
I
guess
which
is
next
on
our
agenda
here.
So
we
added
find
modules,
themes
and
layouts
pages,
which
is
really
great.
We
know
we
have
some
development
tasks
left
before
we
can
finish
implementing
those
designs.
We
need
to
get
these
integration
for
some
things.
A
We
need
to
get
data
reporting
working
correctly,
but
we
have
kind
of
a
really
great
path
forward
for
forgetting
those
completed.
But
in
addition
to
those
things
we
want
to
allow
people
to
be
able
to
log
in
to
the
backdrop
website-
and
this
is
going
to
come
with
a
handful
of
its
own
design
and
user
experience
related
tasks.
As
well
so
we
want
to
be
able
to
put
on.
A
Things
on
the
website
for
people
to
do-
and
this
is
something
I
think
we
talked
about
in
our
other
meeting-
that
maybe
isn't
in
this
agenda,
but
the
things
we
want
to
be
able
people
do
being
able
to
join.
Something
feels
good
like
when
you're
like,
oh
I'm,
gonna,
join
backdrop
community.
If
you're
not
a
developer,
and
you
don't
work
on
github,
we
don't
have
a
really
great,
welcoming
workflow
for
getting
you
to
be
part
of
the
community.
A
So
I
think
just
having
somebody
be
able
to
sign
up
or
login
to
our
website
will
create
that
initial
part
of
joint
feeling,
like
you're
joining
something
for
people
who
are
developers.
We
don't
want
to
have
to
make
them
create
a
new
account
for
something
Neal,
so
giving
a
single
sign-on
with
github
will
kind
of
decrease
the
amount
of
pain,
that's
associated
with
signing
up
for
something
so
it'll
lower
the
barrier
to
entry,
but
it
still
will
be
optional
right.
A
So,
if
you're
not
up,
when
you
don't
have
a
github,
you
don't
have
to
do
it.
But
if
you
have
a
button
to
click
that
will
sign
you,
man
I
think
that
would
be
super
helpful.
We
could
also,
then
automatically
associate
the
committers
for
projects
with
nodes
you
have
access
to
edit
and
similar.
So
that's
something
to
think
about,
but
once
you
log
into
the
website,
if
you're
not
a
developer,
you
can't
edit
your
projects.
A
What
do
you
do
right,
like
it's
kind
of
weird,
to
give
somebody
access
to
join
something
and
again
and
poke
around
there's
nothing
to
do
here.
So
what
I
thought
it
would
be
really
great
is
focusing
on
the
things
that
we
want
to
add
to
that
website,
so
allowing
people
to
add
a
Drupal
friendly
event
right.
So,
if
you're
an
event,
organizer,
Teufel,
friendly
fact,
you're,
friendly
Drupal
event
or
backdrop
event
or
open
source
software
event.
Where
you
want
to
see
backdrop,
you
want
to
learn
about
backdrop
or
you
want
to
talk
about
Bactra.
A
Those
would
be
really
good
to
get
an
official
event
calendar
up.
That's
not
like
a
Google
feed
that
somebody
has
to
email
us
to
post
something
on
to
so
I
think
that
would
be
something
that
could
be
an
easy
win
just
like.
Let
you
create
an
event
node
or
you
can
put
in
whatever
description
you
want
about
it
and
maybe
link
to
the
event.
That
would
be
good.
A
Here's
a
list,
a
whole
bunch
of
service
providers
and
contractors
who
are
interested
in
doing
backdrop,
work
and
I
think
we
for
the
initial
things
we
have.
We
have
a
list
of
supporters
and
I
website
already.
We
could
leave
that
as
as
the
you
know,
the
bottom
half
of
that
page.
So
if
people
haven't
logged
into
the
website
and
haven't
created
and
a
listing
things
is
my
company
contact
me
for
backdrop,
work
for
this
is
my
personal
or
whatever
it
is.
A
So,
like
add
something
to
the
showcase,
so
I
think
building
a
showcase
is
going
to
be
much
a
bigger
task,
because
it's
gonna
require
like
a
lot
more
design
than
like
here,
fill
out
this
form
and
we'll
put
you
in
this
list,
but
I
do
think
that
that
would
be
nice
to
get
kind
of
us.
Like
item
number
three,
so
letting
people
log
in
letting
people
a
defense.
It's
going
to
be
easy,
such
as
appears
in
the
list,
letting
people
list
themselves.
A
The
service
providers
just
going
to
be
easy
sellers
appear
in
a
list,
but
getting
a
showcase
that
actually
does
a
good
job
of
like
selling
the
site
that
has
been
built.
I
think
is
going
to
require
a
lot
more
design
and
thought
and
workflow.
So
I
would
love
to
get
that
on
our
radar
in
terms
of
what
that
experience
is
like
and
visiting
backdrop
site
and
trying
to
see.
That's
another
thing.
A
That's
really
important
in
the
sales
call
right
where
someone's
like
show
me
sites
that
are
built
on
backdrop
and
you're
like
I
need
to
show
you
like
three
of
my
own,
but
I
think
it
would
be
really
great
to
get
a
more
polished
official-looking.
You
know
showcase
going
so
I
think
that's
kind
of
what's
next
on
our
agenda
for
that
so
I'm
going
to
update
this
in
terms
of
agenda
items
here
so
I.
What
did
I
talk
about?
Building
the
showcase
and
a
service
rider
listing
I.
A
A
That's
a
good
idea
to
trying
to
figure
out
like
maybe
before
we
let
me
login
what
kind
of
information
we
want
to
collect
about
people.
It's
always
something
we
can
revisit
later,
where
it's
like.
Oh
I,
want
to
know
what
country
you're
in,
but
I
think
like
getting
some
initial
metrics
when
people
login
would
be
good
like
as
people
are
creating
accounts
will
get
a
more
accurate
data
sample
than
if
we
have
to
add
something
later,
because
that
we're
going
to
go
back
and
edit
there
I
can't
quality
like.
A
I
think
maybe
what
we
should
do
is
look
at.
What's
on
drupal.org
and
see
what
I
know
they're
collecting
about
people
and
they
just
kind
of
say
we
don't
need
this.
We
aren't
going
to
get.
You
know
this,
that's
too
early
to
have
like
which
drupalcon,
if
you
attended
for
backdrop,
but
it
would
be
good
to
have
like
a
you
know.
If
you
want
to
have
a
personal
bio,
you
can,
if
you
want
to
upload
a.
B
C
A
A
Profile
page
and
then
maybe
we
can
build
the
event
listing
and
service
provider
listing
and
do
a
review
of
those
the
same
time
we're
doing
the
show
caso
showcase
we
could
put
off
till
maybe
january
or
something,
but
if
we
could
do
the
profile
page
before
the
end
of
the
year.
I
think
that
would
be
fantastic,
so
I
think
that
the
only
urgency
or
is
that
Drupal
EE
is
coming
out,
which
is
fantastic.
It's
supposed
to
be
released
on
november
nineteenth,
which
is
two
weeks
from
today,
but
I
think
what
that's
gonna
do.
A
Is
it's
going
to
start
a
whole
bunch
of
people
to
get
really
excited
about
your
plate
and
they're
going
to
go
when
they're
going
to
look
at
it
and
then
they're
going
to
want
to
compare
it
to
backdrop,
and
so
that
kind
of
surg?
What
they've
heard
of
benchmark
apparent
director
so
I
think
that
surge
of
activity
is
gonna
work
in
our
favor
as
well,
and
so
it
would
be
nice
if
we
can
have
you
know
people
be
like
oh
only
sign
up
for
backdrop
to
and
then
I
can
go
see.
A
What's
there
having
some
kind
of
welcoming
environment
for
them,
so
I
would
say
the
sooner
we
can
get
done,
the
better.
I'm
not
sure
we
can
get
anything
designed
and
implemented
in
two
weeks
or
garden
bullet
is
no,
but
I
would
say
like
if
we
could
get
that
done
before
the
end
of
the
year.
That
will
be
fantastic,
oh
and
Thanksgivings,
in
here
too,
if
you're
american
thanksgiving
is
on
is
that
on
19th,
it's
2026.
Anybody
know
when
these
silly
malik
american
holidays
are.
A
A
C
A
I'm
Thanksgivings
always
on
Thursday,
it's
not
always
on
the
same
day
date
anyway,
so
yeah
with
Thanksgiving
everybody's,
probably
not
going
to
do
any
week.
It
work
the
week
of
the
26.
So
maybe
we
should
shoot
for
like
early
December,
getting
the
designs
done
and
then
getting
it
built
by
January.
First
does
that
seem.
A
A
Alright
other
things
so
that's
kind
of
where
we're
at
with
our
primary
website.
Other
exciting
news
for
those
of
you
who
are
at
their
regular
developer
call
Lassie
I
showed
up
our
adorable
dragon
swag.
So
we
have
this
cute
t-shirt
that
has
our
dragon
friends
when
it
does
get
a
little
weird
fact
up
on
it.
So
if
you
love
dragons
and
you
want
a
t-shirt,
we
can
give
you
this.
Thank
you
gift.
A
Oh
so
you
like
dragons,
then
you
want
more
driving
poses.
We
have
adorable
dragon
hoodies
that
are
warm
and
comfortable,
and
everyone
has
liked
them
so
far.
So
those
are
thank
you
gift
for
a
fifty
dollar
donation.
To
the
backdrop
foundation,
you
can
also
do
on
our
website.
So
again,
shipping
included,
we
have
boxes
of
various
sizes,
so
choose
your
size
from
the
website
in
I'll.
Let
us
know
when
you
make
donation
applause
annual.
Thank
you
well.
Thank
you
dragon.
So
far,
we've
sent
out
of
four
boxes,
I
think
which
is
great.
A
We
had
one
person
who
ordered
a
t-shirt
long
before
we
even
had
a
t-shirt,
just
fantastic,
so
demands
has
been
high.
We
also
gave
out
a
ton
at
that
camp,
which
is
great.
If
you
are
a
backdrop
contributor,
you
have
earned
your
t-shirt
already.
So
I
send
an
email
to
info
of
actors
en
esta
org
and
we
will
send
you
a
shirt
so
Thank,
You
contributors,
let's
see
what
else
inside
here
we
have
a
backdrop
slide
deck.
So
just
just
mention
is
a
backdrop.
Ops
dash,
/
slides
and
it's
basically
a
reveal
j/s
template.
A
Be
a
nice
great
place
to
be
like
a
canonical
source
or
anyone
who's,
paying
a
talk
on
backdrop.
If
you
want
to
contribute,
we've
done
back,
you
can
throw
it
in
that
slides,
folder
and
it'll
come
with
a
little
backdrop
template
and
then
anyone
else
wants
to
give
a
top
round
backdrop.
If
they
don't
want
to
do
the
work
themselves,
what
they
want
to
steal
a
slide
they've
seen
in
someone
else's
talk,
I'll
have
a
place
to
grab
it.
A
Let's
see,
we
also
are
working
on
branding
assets
for
Bactra.
So
this
is
something
that's
been
kind
of
like
a
lot
of
long-running
task,
obviously
very
low
priority,
but
we
need
to
figure
out
like
what
our
online
branding
is
going
to
be.
We
currently
have
a
dragon
mascot.
We
have
a
square
logo
and
we
have
random,
like
fractal
repeating
patterns,
recursion
images
on
social
media
networks.
A
It
would
be
great
if
we
could
get
some
consisting
consistent
branding
to
kind
of
use
everywhere
we
exist,
and
so,
if
anyone
that's,
this
is
kind
of
a
good
design
related
intro
task.
If
you're
interesting
working
on
design
for
back
job
and
start,
you
know
let
us
know
you
want
to
work
on
it
and
start
moving
some
stuff
over
I
have
an
issue
here
or
have
a
task
OSIS
to
do
make
an
issue.
I
think
I
made
an
issue
I'll
try
and
go
find
it.
I
think
I
did
it
in
the
backdrop.
A
Ops
issue
queue.
Maybe
it
didn't
make
an
issue.
No,
I
can't
remember
where
it
is,
but
I'll
go,
try
and
do
that
today
and
put
one
up
somewhere
where
I
know,
we've
had
a
little
bit
actually
already
in
conversation
around
some
assets
that
that
were
beautiful,
but
maybe
not
in
line
with
the
rest
of
my
stuff,
so
we'll
try
and
get
those
up,
and
then
people
can
continue
to
iterate
or
start
over
try
something
different
or
whatever
you
want
on
those
other
things
in
design
and
ux.
A
The
last
item
on
the
agenda
here
is
this
human
interface
guidelines
stock,
which
we
started
probably
a
year
ago
now,
which
I
thought
was
a
fantastic
idea.
This
is
a
document
that,
like
Apple,
has
one
of
these
that
helps
design
how
people
are
supposed
to
interact
with
software.
I
think
will
be
really
great
to
have
one
for
back
up.
There
just
explains
like
the
design
patterns
and
user
experience.
A
That
is
that
we
have
when
they
should
be
used
when
they
should
not
be
used
to
help
us
not
only
in
core
make
things
more
consistent
throughout,
but
also
to
help
get
trip,
developers
try
and
figure
out
when
they
should
build,
which
interface
patterns.
So
we
have
that
kind
of
stubbed
out
on
github.
It's
a.
A
It's
in
backdrop,
ops.
We
should
put
a
link
to
on
here,
but
it
hasn't
actually
been
completed.
So
if
we
have
somebody
new
who
is
really
interesting
news
experience
who
wants
to
kind
of
adopt
that
whole
project
and
say
I'm
gonna
go
through
core
and
I'm
going
to
figure
out
where
we
have,
which
any
interface
pattern
somewhere
they're
used.
If
we
could
just
even
get
that
much
down,
we
could
take
a
good
hard
look
at
it
and
say
this
is
what
we
want.
Is
this
make
sense?
A
A
I
mean
it
would
take
somebody
who
is
super
passionate
about
user
experience
to
kind
of
like
go
through
out.
Cuz
core
is
pretty
big
now,
especially
what
we've
brought
like
Willie
outs
with
his
giant
different
drag-and-drop
interface
and
anything
else
just
kind
of
go
through
and
be
like.
This
is
what
we
have
and
then
look
at
like
is.
Is
that
really
the
only
one
morning.
A
I
mean
I
think
it's
fine,
like
some
of
this
stuff
is
lower
priority
like
getting
brain
asset,
so
be
nice,
but
I,
don't
know,
I
feel
like
one
day
we're
going
to
get
some
amazing
like
WordPress
people
or
like
I,
only
have
five
minutes,
but
I
do
twitter
headers
all
day
long,
and
here
you
go
right,
you
never
know
so,
whoever
it
is.
It's
like.
Oh
I
I
want
to
do
that.
It's
it's
a
nice
self-contained
task.
So.
B
C
I'd
say
in
terms
of
things:
I
mean
design-wise,
we're
looking
pretty
good
on
some
of
the
things
that
Wes
it
had
put
together.
I'd
like
to
see
it
like
a.
We
might
give
that
a
shot
trying
to
implement
the
like
redesigns,
how
to
add
a
field
I
feel
like
that
would
be
a
nice
iteration
that
can
be
done
reasonably
soon.
C
The
views
you
I
one.
We
really
need
comps
for
Mike
McCaffrey
made
an
issue
that
was
improved.
The
UX
beauty
line,
which
is
suggestion,
was
to
use
vertical
tabs
to
separate
out
the
different
concepts
within
views.
Yeah,
it's
it's
funny
because
that
actually
was
kind
of
similar
to
what
we
used
to
have
Interpol
five,
six
or
five
yeah
ages
ago.
We
had
Vertical
tabs,
but
if
we
didn't
use
vertical
tabs
to
separate
concepts
whose
work
attempts
to
separate
the
displaced,
if
you
well.
C
A
A
C
C
A
I
mean
so
the
reason
that
I
mean
that's
a
user
experience
failed,
like
the
reason
that's
hidden
is
because
the
views
UI
is
already
overwhelming,
and
if
you
put
too
much
stuff
on
it,
then
people
won't
click.
Anything
at
all,
so
I
think
like
leaving
leaving
things
that
most
people,
especially
at
first
visit,
are
not
going
to
use
hidden,
is
good
and
having
an
option
to
like
on
expand.
It
is
good
for
the
pro
developer,
like
I.
A
Leave
it
open
on
all
of
my
lipsticks,
because
I'm,
not
afraid
of
use
and
I
will
click
anything
whether
it's
a
smart
idea
or
not
so
I
just
go
and
turn
that
off
and
I.
Think
like
having
that,
like
first
time,
experience
being
positive
is
way
more
important
than
like
making
it
easier
on
the
pros,
because
the
to
know
how
to
fix
it,
but
anyway,
yes,
turn
the
lights
yeah
in.
C
A
Our
first
time
users,
it
does
because
it's
it's
the
visual
impact
that
matters
anyway.
The
point
was,
we
should
take
the
right
hand,
column
and
put
it
below,
because
that
would
give
us
horizontal
space,
but
also
important
is
that
we
probably
shouldn't
change
the
views.
You
I
very
much
in
backdrop,
one
just
because
our
primary
target
audience
for
backdrop,
one
or
people
coming
from
Drupal
and
if
we
take
views
and
make
it
to
significantly
different
there,
we're
going
to
be
alienating
our
target
user
go.
A
B
B
A
A
Was
it
was
cool?
I
mean
there's,
definitely
a
lot
of
things
where
you're
like
they.
They
give
you
a
whole
bunch
of
tools
to
achieve
the
same
goals
but
I
think
they're.
Trying
to
like
me
every
use
case
where
it's
like
the
person
who
wants
to
change
the
layout
and
the
person
who
wants
to
change
the
content
both
have
a
way
that
they
edit
content,
that's
different,
but
from
either
screen.
You
can
change
both
the
layout
on
the
content,
but
it's
different.
B
C
B
B
A
It's
the
same
kind
of
same
kind
of
thing
as
square
space,
where
it's
like
a
really
easy
to
like
site
building
tool,
but
you
can
only
build
you
know
a
fairly
basic
blog
type
site
run,
but
I
was
trying
to
Weebly
I
think
in
particular,
because
they
are
using
something
that
looks
a
lot
like
Aloha,
which
was
the
WYSIWYG
editor
that
almost
went
into
Drupal,
8
and
I
wanted
to
see
what
they
were
able
to
do
with
it.
Oh
they
they
have
a
bunch
of
crazy,
like
inline,
editing
stuff.
Oh
my.