►
From YouTube: Backdrop CMS Design / UX 1/8
Description
Design and User Experience fourtnightly meeting for Backdrop CMS
A
Eight
we
are
on
air
live,
it
is
Thursday
January.
Eighth,
we
are
having
our
first
design
meeting
of
2015,
which
is
super
exciting
backdrop.
The
release
is
right
around
the
corner,
so
the
kinds
of
stuff
we're
doing
for
design
are
going
to
be
shifting
here
in
a
little
bit,
because
there
isn't
much
more,
we
can
do
to
backdrop
the
product
so
really
quickly.
A
It
aren't
interested
in
moving
to
Drupal
8,
so
this
is
kind
of
an
alternative
to
to
that
world
long-term
we're
going
to
try
and
take
back
to
the
project
in
shift
it
down
market
even
further,
not
necessarily
in
terms
of
its
features,
but
in
terms
of
its
user
experience
in
terms
of
its
design.
We
want
to
appeal
to
people
who
are
currently
using
WordPress
insights
more
like
that
I
might
be
limited
by
what
they
offer
in
order
to
do
that.
A
We've
got
to
do
a
much
better
job
with
the
experience
of
using
the
product
dribbles
out
a
long
history
of
kind
of
falling
short
in
terms
of
being
friendly
to
designers
and
having
bad
experience.
So
the
purpose
of
this
meeting
is
to
kind
of
focus
on
those
two
areas:
try
and
get
feedback
from
designers
hear
from
people
in
the
community
about
what
it
is
that
they
want
what
things
are
they're
struggling
with
and
try
and
turn
those
into
tangible,
workable
things
that
we
can
do
for
backdrop.
A
So
in
terms
of
what
we're
working
on
right
now,
we've
got
a
list
of
tasks
related
to
design
that
have
been
making
progress.
The
first
one
is
backdrop
CMS
org
our
primary
website.
Since
our
last
meeting,
we've
added
our
logo,
our
logo
mark,
as
well
as
the
local
word.
We've
made
some
slight
changes
to
the
way
the
theme
works,
to
make
it
feel
a
little
bit
better
and
that
was
just
kind
of
in
preparation
for
our
product
launch
we're
going
to
be
sending
people
to
this
website.
A
We
wanted
to
have
a
little
bit
more
impression
and
a
little
more
branding,
so
when
people
get
there,
they
kind
of
get
a
feel
for
what
backdrop
actually
is:
we've
updated
our
fonts
to
match
our
brand
guidelines
and
that
sort
of
thing
so
I
think
for
the
most
part,
the
backdrops
TMS
primary
website
is
done.
The
designs
we
got
from
our
designer
have
a
mobile
and
at
navigation
in
it
that
we
that
has
not
been
implemented.
I,
don't
think
we
had
any
plans
to
do
mobile
navigation,
but
we
have
designs
for
it.
A
So
if
we
ever
get
time
to
navigation
now
we
can
put
that
in
and
it'll
look
much
better
than
it
does
currently
wits
functional
wave
is
now
it's
just
not
super
fancy,
so
we
we
have
the
ability
to
change
that
in
the
future.
Should
we
want
to
so
I
think
so
so
for
further
our
backdrop,
primary
website
right
now
I
think
we're
kind
of
calling
it
good
we're
obviously
going
to
have
to
return
to
that
in
the
futures.
A
We
add
new
sections,
we're
going
to
be
adding
a
section
to
browse
modules
and
a
section,
the
Browse
themes.
Those
pages
are
going
to
need
some
design
user
experience
thought
when
they
get
built,
but
since
we
don't
have
modules
for
teens
yet
to
browse
the
the
design
process
there
is
on
hold.
This
is
the
how
some
actual
content
will
be
able
to
study
that
a
little
bit
better
and
come
up
with
some
decent
ways
to
get
through
it.
So
next
on
our
list
here
is
the
API
website.
A
We
have
a
design
on
backdrop,
CMS
that
work
the
primary
website
and
what
I
was
planning
on
doing
is
taking
the
design
from
the
primary
website
and
just
putting
it
on
the
aki
website
and
then
tweaking
it
as
necessary
and
I
did
that
locally,
and
there
was
a
bunch
of
stuff
that
didn't
quite
work
that
we
just
haven't
themed
because
it
didn't
exist
on
the
primary
website
and
the
lily
out.
A
We
have
currently
with
the
two
sides:
we've
got
one
side
bar
and
then
there's
a
drawer
that
doesn't
work
on
API
site
because
we
don't
have
any
sub
now.
So
we
don't
have
anything
that
would
pop
open
in
the
drawer.
So
I
was
thinking
about
just
removing
the
drawer,
leaving
the
sidebar,
putting
our
navigation.
They
have
on
the
API
side,
there's
a
lot
more
links,
putting
those
into
the
sidebar
that
this
style
to
the
way
it
is
on.
The
main
website
takes
up
a
little
bit
too
much
space.
A
So
what
might
be
good
is
to
the
theme.
That's
on
the
API
site.
Right
now
is
something
that
Luke
found
on
drupal.org
and
it
it's
functional.
But
it's
just
not
very
pretty
and
I
have
an
open
task
for
people
who
are
now
creating
documentation
for
us
on
the
API
site,
who
want
it
to
look
a
little
bit
better
with
code
blocks
and
that
sort
of
and
so
I
don't
put
any
work
on.
This
contributed
theme
that
we
got
from
Drupal.
A
It's
currently
owning
a
Drupal
sites
about
to
be
a
backdrop
site
I,
don't
have
to
do
a
whole
bunch
of
other
changing
around
too,
but
we
should
find
a
way
to
make
that
documentation
more
legible
in
the
short
term.
So
I
think
what
we
should
plan
on
doing
and
I'll
probably
need
some
divine
designer
advice
here
is
just
turning
on
the
the
backdrop
primary
website
theme
and
thinking
about
how
to
handle
that
navigation
away.
A
That's
a
little
smoother,
so
I
don't
know
if
we
want
to
open
that
up
to
feedback
or
what
but
I
think
that's
probably
the
easiest
path
forward
and
will
give
us
less
work
to
do
in
terms
of
when
we
port
both
backdrop,
primary
of
sight
and
backdrops
API
site
to
backdrop
will
only
have
one
theme
to
port.
We
just
need
to
think
about
how
they
work
in
the
two
different
contexts
or
how
the
one
thing
would
work
on
the
API
site.
A
Other
things
we're
working
on.
We
have
backdrop
the
product,
obviously
the
most
important
thing
right
now
we
have
had
an
open
issue
for
I,
don't
know
a
year,
maybe
to
try
and
update
this
style
guide
for
backdrop.
So
this
is
just
for
our
administration
theme.
All
the
basic
elements
like
what
is
a
drought
button,
look
like
what
does
a
form
element.
Look
like
we've
had
several
different
people
offer
to
work
on
it.
A
We
have
a
couple
people
thinking
about
it
right
now,
Darius
our
designer
who
did
the
design
for
the
backdrop,
CMS
main
website
has
done
a
lot
of
thought
about
how
to
improve
the
current
administration
interface.
We
have
a
new
design
for
JA
buttons.
We
have
a
new
design
for
submit
buttons.
We
have
new
designs
for
tabs.
We
have
new
designs
for
the
heading
area,
but
there's
a
bunch
of
stuff
in
the
style
guide
that
hasn't
yet
been
thought
about.
A
So
we
I
asked
him
last
night
if
he
would
take
a
look
specifically
at
status
messages
and
breadcrumbs
and
I
think,
depending
on
what
we
get
back,
some
of
these
changes
we
might
be
able
to
implement
I
know
we
also
have
Ronnie
Norwin.
He
offered
to
work
on
something
yesterday,
he's
looking
at
it
I
think
we
should
check
in
with
him
and
see
what
he's
come
up
with,
but
we've
at
less
than
a
week
now
backdrop
should
be
released
a
week
from
today.
A
Sorry
week
from
yesterday,
wait
from
today
so
I
think
the
amount
of
changes
we're
actually
going
to
people
to
be
able
to
get
in
or
very
minimal
I
didn't
give
us
something
like
changing
the
style
on
a
job
button
that
would
be
possible
if
it's
something
like
I,
don't
know
coming
up
with
new
layouts
for,
like
the
modules
page,
that's
definitely
not
going
to
happen
in
the
next
week,
so
getting
something
I
think
for
me,
the
biggest
thing
is
the
messages.
A
A
Six
days,
but
trying
to
figure
out
how
to
keep
the
whole
thing
kind
of
cohesive
is
also
kind
of
important
in
changing
things.
One
piece
at
a
time
sometimes
doesn't
achieve
that
goal.
B
No
I
think
you're
you're
spot-on,
like
we
don't
have
time
to
make
a
whole
lot
of
changes
at
this
point,
so
I
mean
well.
We
don't
need
to
restrict
ourselves
too
much.
I
mean
we.
We
don't
have
a
lot
of
time
for
the
one
point,
0
point
0
release,
which
is
of
course
in
a
week,
so
I
think
our
best
strategy
is
to
move
forward
with,
with
like
modest
improvements
to
the
style
guide
and
look
to
implement
them
in
a
minor
point:
release.
Okay,
that.
A
Sounds
good
too,
if
we
can
get
the
designs
done
sooner,
that's
good,
and
then
we
can
spend
some
time
implementing
them.
They
might
not
be
in
one
point,
0
point
0,
but
hopefully
we
can
get
it
in
pretty
soon
afterwards,
so
I'm,
not
imagining
a
ton
of
people
will
run
out
and
install
backdrop
and
start
running
it
right.
When
we
release
I
have
a
feeling
we're
gonna
have
a
period
of
time
a
whole
bunch
of
what
trying
it
and
the
number
of
people
are
trying
will
probably
increase
over
time.
A
Also,
we
hope
so
in
terms
of
making
that
first
impression
we'll
be
making
the
wrong
first
impression
to
a
very
small
amount
of
people,
but
the
sooner
we
get
stuck
I
changes
in
will
be
making
the
right
first
impression
to
a
larger
amount
of
people.
So
I
think
it's
fine
and
we
don't
get
it
in
right
away,
but
slightly
sad
and
that's
okay.
As
long
as
we
get
the
designs
and
we
get
a
really
good
product
in
the
end,
that's
really
what's
most
important.
So
anyway,
yes,
designs
are
underway.
A
We've
got
a
whole
bunch
of
people
working
on
it.
Right
now,
which
is
great,
we
just
need
to
be
careful
about
what
we
actually
try
and
change
before.
One
point
no
point
out,
so
we
don't
break
anything
other
things
on
our
agenda
a
little
bit
more
exciting
and
farther
off
into
the
future.
A
One
thing
I
would
really
love
is
if
we
could
get
a
new
front
end
theme
into
core
right
now
we
have
Bartok
Drupal
sandbar
tech
for
the
last
like
five
years,
it's
great,
but
nobody
uses
it
when
they
actually
launch
a
site.
It
would
be
good
if
we
could
get
a
friend
and
team
in
there.
That's
actually
usable,
maybe
something
minimal
like
bootstrap,
ask
that
people
would
feel
like
they
could
actually
have
a
professional
website.
That
looks
like
that.
A
Even
if
there's
no
style
associated
with
it,
I
think
that
would
be
a
really
great
starting
point
so
that
some
look
at
the
launch
a
website
without
needing
to
write
a
custom
theme.
So
we
have
anyone
who
is
particularly
interested
in
creating
a
theme
for
backdrop
that
would
be
of
caliber
to
go
into
core
the
precipice,
for
that
would
be
created
as
a
contribute
it
and
look
at
it
will
do
code
reviews
and
at
some
point
will
decide
if
it's
good
enough,
we
can
go
into
core.
A
So
obviously,
if
you're
working
on
themes
for
backdrop
anyway,
keep
that
in
the
back
of
your
mind
like
is
this
something
you
think
should
be
submitted.
Let
us
know
create
an
issue
if
you
have
something
you're
interested
in
and
we
can
talk
about
it
right
now,
there
aren't
any
contenders,
I'm
hoping
we'll
have
a
couple,
but
but
we
don't
want
a
whole
bunch
of
people
do
a
whole
bunch
of
work.
Vince,
I'm
not
going
to
use
it,
and
let
us
know
if
you're
thinking
about
working
on
that,
so
other
things
we're
working
on.
A
There
are
there's
a
tag
in
orkut
hub
issue,
queue
for
issues
that
need
designer
feedback
or
design.
Some
of
them
are
just
like
hey
look
at
this
thing:
we've
done
make
sure
it's
not
ugly,
and
some
of
them
are
I
have
no
idea
how
to
deal
with
this
problem
and
we
need
actual
designs
and
right
now.
That
list
is
fairly
short,
but
as
things
progress
forward
and
back
BB
trying
to
add
those
labels
to
any
issue
that
comes
up
that
needs
to
sign
feedback.
A
So
if
we
have
people
who
want
to
get
involved
on
necessarily
coders,
we
need
your
experience
as
well
as
your
you
know,
design
files
oh
and
we're
going
to
try
and
make
it
easy
for
you
to
get
involved
using
that
tag,
so
keep
an
eye
on
that
in
the
future.
A
We
also
have
a
similar
tag,
locusts,
actually
tag.
We
have
a
similar
set
of
issues
on
github
for
user
experience,
and
these
aren't
necessarily
things
that
need
designer
feedback,
although
that
will
be
a
part
of
most
of
these
issues,
but
just
things
that
if
you
are
new
to
using
backdrop-
and
you
can't
figure
out
how
to
do
something
or
you
find
something
particularly
frustrating
or
your
instincts
are
telling
you
do
one
thing:
when
you
do
it,
you
find
that
that's
not
the
right
answering.
A
It
was
something
else
we're
trying
to
create
the
general
experience
of
using
backdrop
to
make
it
a
little
bit
better
than
Drupal's,
and
we
need
feedback
for
that.
We
need
people
to
identify
the
issues
that
need
work
and
also
come
up
with
solutions
for
them.
Then
we
also
need
designers
to
design
things
that
sometimes
encoders
to
coatings
in
Drupal
user
experiences,
I,
always
kind
of
been
an
afterthought.
In
fact,
rip
we'd
like
to
kind
of
make
it
a
for
thought.
We
know
we're
starting
with
drupal's.
A
We've
got
a
lot
of
work
to
do,
but
we
are
kind
of
going
through
the
process
of
looking
at
certain
things.
In
fact,
open
saying
is
this
is
your
experience
problem.
This
is
something
that
could
be
a
user
experience,
improvement
and
typing
them
as
such,
in
the
queue
we're
using
github
tag
for
that,
instead,
we're
using
in
the
actual
issue,
title
we're
using
square
brackets
and
then
the
letters,
U
and
X.
A
So
there's
link
in
the
agenda
for
today
to
do
that,
but
you
can
also
just
search
the
issue:
queue
for
anything
with
you
x
in
square
brackets
and
you'll
find
a
set
of
user
experience.
Issues
right
now,
I
think
there's
a
also
a
fairly
small
subset
of
those
there's,
some
big
duties
about
like
changing
names
of
things,
which
always
creates
bike
shed
on
Drupal.
We've
changed
the
names
of
some
things
and
backdrop.
A
We've
talked
about
changing
themes
of
other
things,
I
think
getting
those
sorted
out
would
be
good,
there's
also
some
bigger
problems
that
aren't
just
labels.
Things
like
how
do
you
design
a
user
interface
for
dragging
and
dropping
blocks
right?
We
have
a
kind
of
a
creddie
interface,
and
now
that
is
perfect
in
terms
of
how
it
works,
but
I,
don't
think
anyone's
going
to
be
able
to
figure
out
how
to
use
it
just
by
poking
at
it,
and
we
have
boyoung
working
on
new
designs
for
that
which
will
be
implemented
sometime
in
the
near
future.
A
But
it
would
be
good
to
have
that
same
kind
of
process
involved
for
everything
we
built
where
the
first
thing
is
just
to
get
it
done.
I
get
done
good
in
get
it
working,
but
then
the
second
thing
is
to
think
about,
like
how
do
people
actually
interact
with
this
tool
and
in
order
to
achieve
those
goals
on
a
bigger
scale.
A
We've
also
come
up
with
this
idea
of
setting
up
human
interface
guidelines
and
there's
a
little
bit
about
this
in
our
agenda
under
the
overview
section
down
the
bottom,
where
it
would
be
great
if
we
could
come
up
in
backdrop
land
with
patterns
that
humans
have
on
the
interact
with
the
software
and
then
tools
that
we
give
them
in
order
to
handle
those
interactions.
So
things
like,
when
do
you
use
a
drop
button?
When
do
you
use
auto
complete
field
so
that
as
people
are
using
the
software
they
get
trained
in
a
way?
A
It's
everyone
who
creates
a
module,
creates
their
own
interface
patterns
and
there
isn't
a
lot
of
cohesiveness
across
even
all
of
core,
especially
not
all
of
Kim
trip,
and
it
would
be
great
if
we
get
that
sorted
out
so
good
since
been
working
on
coming
up
with
this
human
interface
guidelines
document,
it's
based
on
I
think
some
work,
the
Apple
stone
about
how
they
wanted
people
to
interact
with
their
hardware,
as
well
as
software
we're
going
to
try
and
do
something
really
similar
here
for
back
job.
We've
got
a
github
repo.
A
It
could
use
some
work
if
anyone
wants
to
take
a
look
at
what
he's
done
already,
we
can
definitely
get
you
involved
in
reviewing
stuff
creating
new
pages,
just
to
kind
of
help.
Get
that
document
going,
which
I
think
is
a
really
great
idea.
So
in
terms
of
our
timeline,
we
don't
really
have
anything.
That's
super
urgent.
The
most
urgent
thing
we
had
was
to
get
our
logo
on
our
website.
Last
time
we
met
and
that's
are.
A
A
We're
Darius
is
going
to
have
a
second
round
of
feedback
for
us
tonight,
we'll
check
in
with
Ronnie
tonight
we'll
see
if
we
can
get
those
two
sets
of
feedback
ready
for
some
way
to
put
something
into
core,
depending
on
how
minor
that
is,
we'll
see
what
sometimes
we
end
up
with
and
then
beyond
that
we'll
need
to
take
those
designs
and
actually
put
them
on
backdrop
longer-term,
like
if
we
aren't
get
in
from
one
point:
X
will
get
it
and
shortly
after
and
then
beyond
that
we
don't
really
have
any
other
deadlines.
A
It
would
just
be
a
matter
of
working
through
everything
else
that
we've
got
in
the
pipeline's
like
do
we
have
anyone
working
on
a
new
front,
end
theme:
do
we
have
improvements
to
make
to
the
admin
theme?
Do
we
have
issues
that
need
attention
and
those
will
go
in
as
they
get
done
so
if
we
get
them
done
for
a
certain
release,
efecto
fill
in
that
be
it
not
release
it
back
drop,
but
we
won't
I.
Don't
know
that
we
have
anything
right
now
that
needs
to
be
scheduled.
A
If
we
have
some
huge
glaring
problem,
we
might
schedule
something
just
so
it
can
get
some
more
focus,
but
it's
not
be
a
plan.
That's
enough.
A
Only
other
thing
on
the
agenda,
which
I'm
not
sure
we
need
to
talk
about
this
every
week
was
setting
up
briand
guidelines
for
backdrop.
I
did
notice
that
the
font
we
have
listed
here-
and
this
is
for
backdrop
CMS
the
primary
website,
not
necessarily
backdrop
the
product.
This
is
not
the
correct
font,
the
open
sans
font.
We
are
going
to
be
using
on
the
product,
but
our
actual
brand
font.
To
remember
what
it's
called.
I
think
ilysm
and
florida
fans.
A
And
I
also
think
it
would
be
useful
if
we
could
create
a
page
for
a
brand
guidelines.
I
know
Drupal
that
work
has
a
nice
one.
I've
had
a
couple
of
texture:
I've
wanted
to
send
someone
who's
working
on
something
to
our
color
palette
and
the
only
place
that
we
have
it
was
in
these
agendas
or
I'd
have
to
email
them
that
image
that
I
put
into
these
agendas.
A
I,
don't
know
where
that
fits
in
the
scope
of
all
of
the
other
pages
that
we
have
on
our
sites,
because
we
don't
have
a
lot
and
I
think
I
looked
at
it
and
looked
up
hang
on
the
primary
website
and
then
it
of
feeling
like
it
wasn't
a
great
fit
for
their
right
now,
rom,
but
maybe
long-term.
We
can
figure
out
how
we
can
post
this
information.
So
it's
a
little
easier
for
people
to
find.
A
Okay-
well,
that's
all
I
have
for
this
meeting
it's
our
first
meeting
of
2015,
which
is
pretty
exciting,
but
it
was
a
short
one
if
we
have
anyone
who
has
any
particular
design
experience
or
wants
to
get
involved
in
design
stuff.
This
is
an
area
where
your
plus
a
history
of
not
being
particularly
good
at
it.
We
want
to
try
and
change
that,
so
we're
open
to
feedback
on
how
we
can
make
things
more
accessible
to
designers
and
how
we
can
make
things
better.
A
We
ready
to
start
with
a
couple
of
issue:
tags
I
think
we
need
some.
Maybe
a
little
more
documentation
might
be
useful
as
to
how
to
get
involved
and
where
to
go.
What
to
do
but
yeah
definitely
give
us
more
feedback
and
we're
interested
in
hearing
from
you.