►
From YouTube: Backdrop CMS Design check-in 2/19
Description
Backdrop CMS has design tasks. Let's review them, and work on anything as necessary.
B
A
So
our
design
tasks
currently
involve
porting
the
backdrop
CM
esta
or
primary
website
to
backdrop.
It
was
on
Drupal
7
before
we
have
that
under
way
nearly
finished
I
would
like
to
say
you
can
currently
view
it.
If
you
want
to
see
it
now,
at
new
backdrop,
CMS
org
we're
probably
going
to
need
a
design
review
over
there.
Just
make
sure
that
we've
gotten
everything
that
was
in
the
original
theme
and
everything
that
was
in
the
latest
designs
actually.
B
A
It
into
the
theme
and
then
there's
probably
a
few
things
over
there
that
haven't
been
designed
stuff,
we've
kind
of
added
on
to
the
site
higgledy-piggledy
that
could
use
a
look
over
as
well
so
I
was
gonna,
try
and
get
Darius
to
do
that,
but
Wes.
If
you
want
to
take
a
look
at
that
and
give
us
your
feedback
there,
that
would
also
be
really
great.
Then
we
have
a
the
new
design
from
Darius
includes
mobile
navigation,
which
is
super
fancy.
It
has
like
a
little
hamburger
menu.
A
So
it
was
kind
of
left
our
to-do
list
right
now
for
for
that
theme,
but
I
think
we're
pretty
close
in
terms
of
our
primary
website.
Maybe
we
should
add
some
new
tasks
for
the
primary
upside
to,
because
what
we're
going
to
need
here
in
the
very
near
future
is
adding
the
ability
to
post
your
own
project.
A
So
we're
going
to
need
design
on
the
node,
add
form
for
projects.
I,
don't
know
if
we're
going
to
have
different
ones
for
modules
or
themes
like
drupal
org,
but
we
could-
and
we
also
are
going
to
need
design
for
ano
a
project
page
and
design
for
a
project
listing
like
five
modules
or
find
themes
or
layouts.
A
A
The
process
of
you
know
getting
all
this
design
stone,
getting
them
up
on
our
site.
Other
things
that
we're
working
on.
We
have
the
API
website,
API,
dot
backdrop
CMS
org.
It's
currently
running
an
amazing-looking
version
of
the
Bartik
theme.
It
has
you
know
the
wrong
branding.
Forests
got
the
wrong
fonts.
It's
got
the
wrong.
You
know
colors,
all
that
stuff,
so
be
good.
To
take
the
theme
that
we
built
for
and
the
backdrop
CMS
torg
primary
website,
throw
it
onto
the
API
site
and
say
how
close
is
it?
A
Do
we
need
to
specifically
design
anything
for
the
API
site,
like
we
have
kind
of
a
different
layout,
going
on
with
the
right
now
with
becca
sidebar
on
the
right,
which
I
think
is
the
way
drupal.org
site
works
as
opposed
to
before
on
our
side.
It
was
on
the
left,
I
don't
know
if
it
was
specifically
put
on
left
on
purpose
or
if
that
was
just
have
what
we've
done
before.
A
What
do
we
need
to
add
more
spacing
it's
like
code
blocks
or
anything
like
that,
so
what
I
was
going
to
do
now
that
that's
on
backdrop,
pay
pay
sites
on
backdrop
is
we
could
maybe
also
set
up
a
new
for
the
API
site,
a
like
new
new
dash
api
doc,
dr
CMS
two,
or
something
like
that
someplace,
where
we
can
throw
up
the
theme
and
what
some
designers
do
a
review
of
that
as
well
and
see
how
much
work
that's
going
to
need
in
order
to
get
it
matching
our
branding
and
then
so?
B
A
I
think
so
getting
the
current
theme
ported
to
backdrop
is
our
highest
priority,
because
we
have
a
bunch
of
other
stuff,
that's
blocked
by
that
and
so
making
sure
we
get
a
design
review
of.
What's
already,
there
is
more
important
than
anything
anything
new
and
exciting,
with
APA
site
the
primary
site.
I.
Think
that's
why
I
said
so.
A
I
would
say
like
adding
a
project
page
like
we
can
leave
that
ugly
if
we
have
to,
but
I
would
say
you
know,
I
would
like
that
experience
to
be
good
for
people
who
are
contributors
to
backdrop.
So
if
we
could
get
that
designed
before
we
build
it,
that
would
be
ideal
if
it
doesn't
get
done
in
that
order
of
time.
A
We
need
to
build
a
project
listing
and
we
do
have
the
ability
to
pull
in
a
lot
of
that
information
from
github,
but
it
would
be
good
if
we
could
kind
of
smooth
that
out
over
for
people
so
yeah
I'd
say
this
is
probably
our
current
order
of
importance
outside
the
API
psychic,
because
it
works
so
well.
Right
now
might
actually
be
lower
priority
than
working
on
backdrop.
A
The
product
which
has
a
release
date,
so
I,
would
say
API
site,
probably
would
come
after
the
product
I
release
date
for
the
next
version
of
the
software
is
May.
Fifteenth
and
I
would
like
to
see
branding
in
the
software
by
then
and
API
site
works
so
well
now,
even
though
it
doesn't
match
our
branding
I.
Think
it's
going
to
postpone
that
we
had
to
okay.
A
So
speaking
of
backdrop
of
product,
we
have
a
new
style
guide.
We
had
Darius
go
through.
He
made
us
a
bunch
of
initial
designs
which
we
then
had
some
help
from
running
or
would
actually
getting
into
our
style
guide
and
then
Darius
looked
at
this
dog
and
said:
oh
yeah,
there's
some
things
that
need
little
tweaks,
that
weren't
into
the
designs
and
he
started
actually
writing
code
directly
into
the
style
guide.
To
get
it
to
look
like
his
vision,
which
I
thought
was
great
and
I.
Think
he's
done
with
that.
A
We
have
a
check-in
schedule
with
him.
I
think
it
was
going
to
be
2
p.m.
today.
I
need
to
email
him
back
and
confirm
that
just
to
go
over
stuff
that
he
either
you
know
was
thinking
about
what
wasn't
sure
about
whether
it
should
go
in
or
what
have
you
you
know,
maybe
stuff
he
couldn't
get
implemented
for
whatever
reason
so
I
I
think
that's
good
to
go
for
now,
and
if
there
are
any
changes
they
started
eating
it
too.
A
I
can
definitely
let
you
know
why
Stan
all
posts
of
the
issue
queue
and
all
that
so
that
everyone's
aware
of
what's
going
on
but
I
would
say
for
now
treat
that
style
guide
is
final.
If
you
see
anything
in
that,
it's
a
little
bit
off
feel
free
to
adjust,
but
in
general,
like
the
impression
is
correct.
Okay,.
C
I
think
this
style
guide,
like
actually
he's
done
a
lot
like
it's
it's
not
kind
of
done
now.
It
looks
like
it
looks
like
at
least
styled
everything,
but
some
things
I
think
might
we
might
want
to
take
a
review
of
some
things
like
the
button.
Styles,
for
example,
like
he's,
got
like
a
primary
button
in
a
secondary
button,
but
it's
crazy
because
the
primary
buttons
blue,
but
the
secondary
button
when
you
hover
over
it,
is
green,
and
so
it
kind
of
it's
like.
C
B
A
B
Goop
around
and
make
a
couple
gift
ideas
that
gif
Forge.
If
for
whatever
you
want
to
say
what
that
could
be
I
personally,
don't
like
that
little
clock
looking
guy,
because
it
feels
it
feels
like
oh
I'm
waiting
and
like
the
time
and
clock
kind
of
metaphor,
I
think,
isn't
kind
of
negative,
but
good
I'll,
big
dork
about
it.
I
got
my
dog
in
real,
quick,
they're
yelling
at
me,
bareback,
okay,.
A
So
one
thing
that
what
might
be
good
is
before
we
have
a
check
in
with
Darius
today,
if
you
could
put
all
these
thoughts
that
once
you
just
had,
for
example,
into
a
document
that
we
can
work
through,
so
that
we
can
address
whatever
feedback
you
have
with
serious
today,
so
that
we
get
unblocked
on
implementing
stuff
yeah.
A
And
then
that
way
we
can
refer
to
it
later
we
won't
be
like.
Where
is
the
google
talk?
It's
a
google
thing.
Google
docs
you're
like
where
things
go
to
die.
Okay,
can't
search
google
docs
with
the
internet
with
the
google
search
and
so.
A
Often,
will
google,
and
as
long
as
the
thing
that
you're
looking
for
us
exactly
the
worst
researching
for
you,
can
usually
find
it?
Okay,
all
right,
I
was
like
github
backdrop
style
guide
and
your
diaper
okay,
so
in
terms
of
the
style
guide,
we
think
it's
done.
It
needs
some
feedback.
We
have
a
meeting
with
Darius
today
to
review
that,
then
we
need
to
figure
out.
Then
this
is
the
hard
part
how
to
get
the
changes
that
are
in
the
style
guide
into
the
product
and
the
hard
part
is
that
backdrop
one
this
ship.
A
So
we
don't
have
complete
flexibility
over
changing
everything,
in
particular
markup
that
comes
out
of
system,
module
and
theme
inc
and
needs
to
change
as
little
as
possible,
because
we
do
have
people
who
might
already
of
be
providing
themes,
/
I,
don't
we
don't
to
break
those
themes?
So
ideally
we
would
be
able
to
do
things
like
take
changes
to
the
status
messages
and
put
them
directly
into
the
status
messages
that
come
out
of
core.
A
However,
if
it
requires
like
adding
a
new
span
tag
or
a
div,
Tigers
fans
might
be
okay,
we'll
have
to
look
at
what
the
changes
are,
but
something
that's
going
to
break
a
theme
that
change
is
going
to
have
to
go
into
seven
instead,
so
that
you
know
when
people
they're
custom
themes
won't
show
that
change,
but
the
administrative
interface
will
still
show
the
correct
branding
for
backdrop.
So
what
might
be
good
is
to
go
through
the
style
guide.
A
B
A
And
figure
out
for
each
item
where
those
changes
need
to
happen
and
that's
going
to
require
a
code
review
and
not
necessarily
code.
That's
in
the
style
guide,
that's
code
that
you
want
in
the
real
thing.
This
delicate
code
is
not
exactly
where's,
not
the
right
starting
point
and
it
might
not
be
the
right
ending.
B
A
Either
so
doing
that
kind
of
a
methodical
review
and
then
what
I
was
thinking
we
could
do
to
in
order
to
divide
work.
A
little
bit
more
easily
is
create
kind
of
two
meta
issues:
14
change
the
go
into
core
or
system
module
and
theme
tank
and.
A
And
one
that
are
changes
directly
to
the
7
theme,
and
that
might
be
a
way
that
we
can.
If
we
created
one
pull
requests
for
each
of
those,
you
could
apply
the
first
pull
request
and
say
you
know:
does
it
break
any
contributes
like?
If
you
justify
the
core
one,
we
could
see
what
kind
of
branding
changes
we're
getting
just
from
changing
that
the
innards
of
core
or
the
other
one
you
can
fly
just
the
pull
request
for
seven,
then
you
can
say
like.
Does
the
seventh
theme
change
in
the
way
that
we
want?
A
Does
it
work
with
the
way
the
core
is
now
and
we
can
kind
of
separate
those
two
things
that
does
make
it
really
hard
if
you
have
like
is
github
working
process,
makes
it
hard
to
collaborate
on
anyone.
Pull
requests
for
requests
very
specifically
belong
to
one
person.
In
order
for
someone
to
work
on
someone
else's
for
WordPress,
you
have
to
like
a
fork,
it's
kind
of
a
pain
and
so
I
thought
that
it
might
be
good
if
we
have
only
two
people
working
on
this.
A
If
it's
you
and
Ronnie,
that
would
be
a
good
work
flow,
because
there
would
be
a
good
way
to
divide
that,
but
if
it
ends
up
being
like
you
know,
other
people
want
to
contribute
and
we
have
more
working
on
it.
We
might
need
to
break
it
up
into
more
than
to
pull
requests
and
have
like.
Okay.
Here
are
the
five
thanks
for
putting
in
27
everybody
grab
one
and
that's
the
way
drew
Boyd
did
it.
They
did
it
one
element
at
a
time
and
the
reason
I
didn't
want
to
do.
A
That
initially,
is
because
it
seems
like
a
lot
of
work,
especially
the
way
I
do
with
the
emerge.
Do
everything
all
at
once,
but
I'll.
Let
you
decide
Wes,
what's
going
to
work
best
for
you,
if
you
would
rather
do
them
one
element
at
a
time
or
if
you
would
rather
do
them
I.
You
know
I
theme
at
a
time
or
a
system
at
a
time
or,
however,
yeah.
B
I'm
thinking
maybe
like
we
usually
identify
components
right
so,
like
you
know,
it
might
be.
One
component
is
all
these
basic
body
kind
of
body,
copy
kind
of
styles
like
strikethrough
small,
so
like
all
that
might
be
one
component
so
that
you
they're
not
overly
small
but
I,
don't
want
to
be
overly
big
and
like
status
message
is
a
pretty
nice
little.
A
Yeah-
and
that
sounds
good,
and
then,
if
you
want
to
start
that
and
the
way
that
I've
been
doing
this
too
in
the
github
issue
queue
you
can
create
and
I
think
I
did
this
in
the
in
the
top
of
the
implementation
issue,
you
can
create
little
like
checkboxes
feel
free
to
group
those.
However,
you
want
I
think
you
should
even
have
permission.
A
Let
us
know
if
you
don't
to
edit
the
top
issue
right
there,
which
is
basically
like
editing,
anyone's
comments
so
careful
with
that,
but
feel
free
to
go
ahead
and
edit
those
lists
and
rearrange
those
checkboxes.
A
However,
you
need,
and
if
you
want
to
start
making
that
listen
if
the
check
boxes
already
have
their
wrong,
that's
fine
just
redo
them,
but
then
that
way
we
can
kind
of
get
an
idea
of
what's
going
on
and
then,
if
Ronnie
comes
and
says,
oh
I
need
you
know,
I've
got
a
couple
of
hours
today
which
they
work
right.
You
can
point
him
at
that
list
and
say
you
know
I'm
working
on
the
top
section,
but
take
anything
else
or
add
a
comment
to
the
bottom
saying
working
on
top
section.
A
A
Yeah,
those
are
the
two
tricky
things
with
that
and
I
think
all
the
other
things
that
we're
working
on
their
design,
related
and
backed
up
the
product
have
issues
that
are
tagged
with
a
design.
So
if
we
have
anyone
who
has
you
know
five
minutes
and
they
want
to
contribute
their,
you
know
design
intellect,
but
maybe
not
code.
If
you
click
that
link,
there's
a
link
in
that
agenda
today
or
you
can
just
search
for
anything,
that's
tagged
with
audience
design.
A
You
can
find
some
issues
that
need
designer
feedback
and
some
issues
actually
need
designs
if
you
wanna
mock
up
designs,
so
anyone
is
just
a
little
bit
of
time
and
they're
watching
this
video
and
wants
to
contribute
in
some
way.
We
are
trying
to
make
it
easy
to
identify
to
ask
specifically
for
designers
in
the
issue
queue
to
other
people
who
have
more
time
more
than
five
minutes
and
I
want
to
contribute
to
design
for
backdrop.
A
What
we
really
need,
I
would
love
for
us
to
be
able
to
do
is
include
a
front
end
theme,
that's
not
Bartok
in
poor
and
our
path
doing
it
is
having
somebody
either
porta
theme
from
Drupal
7
or
creating
new
themes
specifically
for
backdrop
that
supports
all
the
layouts
and
core
that
looks
great,
that
is
fairly
design
agnostic
and
that
it's
versatile,
which
is
hard
I,
know
for
designers,
but
something
that
we
can
put
in
core.
A
That
is
not
Arctic,
and
so,
if
we
can
get
a
contributed
theme
and
then
someone
in
plus
and
a
chic,
you
move
this
theme
in
decor.
We
can
do
a
really
thorough
review
of
the
code
and
that
contributed
theme
or
the
style
or
whatever
it
is
and
say.
Yes,
we
want
this
in
core.
We
love
the
way.
It
works
great
code,
good
job
and
move
it
in.
But
in
order
to
do
that,
we
want
to
have
not
just
one
theme
to
look
at
emcore.
A
We
won't
have
a
couple
to
compare
and
right
now
we
do
have
one
on
our
radar
there's
a
theme
called
radix,
which
is
based
on
a
panoply
theme
in
Drupal,
which
is
fantastic
and
I.
Think
it's
probably
the
first
thing
we
had
for
backdrop,
which
is
also
really
great,
which
means
it's
going
to
have
a
nice
long
lifetime
and
a
lot
of
people
using
it.
But
I
would
love
to
get
more
themes
for
us
to
be
able
to
choose
from
to
put
in
decor.
A
So
designers
coming
into
backdrop
want
to
contribute,
make
a
team
design
a
theme.
If
you
can
pair
up
with
someone
who
writes
code,
that's
even
better.
If
you
write
code
yourself,
that's
fabulous
but
get
us
some
themes
and
contribs
that
we
have
some
options
for
everybody
knows
it
for
ok,
so
I
think
we
talked
about
the
backdrop
API
website
already,
but
I've
rearranged
in
the
agenda
by
order
of
importance.
So
here
it
is
it
kid?
Ok,
other
things
are
working
on
in
the
product.
We
have
just
like
the
backdrop
design
tagged
issues.
A
A
In
the
backdrop,
cue
that
aren't
tagged
like
the
design
issues
are,
but
they
start
with
square
brackets
and
the
letters
UX
inside
inside
of
them
and
so
anytime
you're
using
backdrop
and
you
get
confused
by
something
go
ahead
and
create
an
issue
and
type
you
know
put
in
the
title
square
back
at
you
x
and
then
that'll
indicate
to
us.
This
is
user
experience
problem.
We
can
think
about
how
to
solve
the
problem.
A
That
layout
drag-and-drop
interface
and
those
are
going
to
need
design
tasks
as
well.
So
that's
why
it's
included
in
this
meeting,
especially
people
have
interface
design
experience,
as
opposed
to
like
make
it
look
pretty
design
experience,
that's
something
that
the
Drupal
community
historically
has
been
really
short
on,
and
we
would
love
to
get
more
experts
in
that
area
for
backdrop,
especially
if
we
are
trying
to
move
into
the
WordPress
market
where
user
experience
is
super
important
for
us
being
able
to
compete
and
actually
get
those
people
to
like
using
our
product
as
well.
A
A
We
also
have
this
great
document
on
factor
ups,
human
interface
guidelines
that
was
inspired
by
a
similar
document
that
Apple
has
about
how
all
of
its
software
should
be
to
interact
with
and
hardware
too
I,
suppose
in
Apple's
case
and
I
would
like
to
have
the
same
kind
of
thing.
For
us
where,
if
we
can
have
some
documentation
on
when
people
should
use
drop
buttons,
when
people
should
use
vertical
tabs,
I
think
it'll
be
really
easy
for
module
developers
to
follow
those
instructions.
A
Whereas
right
now
we
have,
you
know
a
bunch
of
different
opinions
about
how
those
should
be
used
and
when,
like
we've,
we
love
drop
buttons.
So
we
put
them
all
over
the
place
and
backed
up
core
and
just
this
week
there's
a
discussion
that
started
about
you
know
what
should
be
in
a
java
and
should
an
external
link
me
in
a
job
button.
There
isn't
any.
You
know,
guidelines
for
us
in
core
about
whether
you
should
open
a
drop
button
and
go
off
site
like
it
seems
like
an
internal
thing.
A
A
To
date,
there
is
a
module
for
Drupal
7
called
module,
module,
filter
module
which
I
personally
hated
because
it
had
a
use
of
vertical
tabs,
which
I
felt
like
was
not
what
vertical
tabs
were
intended
for,
but
there
wasn't
any
documentation
anywhere
about
what
vertical
taps
were
intended
for,
and
so
much
love,
Julie
vertical
tabs
are
gradual,
weird
use
them
anywhere.
Interface
is
cluttered,
and
it's
like
okay
I
understand.
A
Why,
then
you
know
there
was
an
attempt
to
do
that,
but
I
would
love
for
someone
to
tell
me
when
to
use
these
things
that
you
could
point
to
that
and
say.
This
is
a
good
case
for
that,
or
this
is
not
a
good
case
for
that.
So
we
have
that
for
backdrop,
the
same,
an
interface
guidelines
document
it
is
not
done
and
the
guy
who
started,
I
think,
is
really
busy.
A
These
days
he's
not
working
on
it
actively,
and
I
would
love
for
someone
who's
super
interested
in
the
way
that
people
interact
with
computers
to
pick
this
up.
So
if
anyone
has
a
couple
minutes
of
spare
time,
they
want
to
take
a
study
of
backdrop.
They
want
to
take
a
stab
at
working
on
this
document.
It
is
in
github,
you
can
fork
it.
You
can
write,
I,
think
it's
using
chuckle,
so
you
can
write
in
markdown
syntax.
You
don't
need
to
be
a
coder
just
kind
of
stuff
out
pages
and
get
us
some.
A
A
So
we've
got
some
time,
but
it
also,
I
think,
is
going
to
need
some
careful
thought
so
getting
going
on.
That
is
also
gonna,
be
a
part
for
us,
and
then
we
also
have,
along
that
same
line
set
of
backdrop
brand
guidelines,
and
I
think
I
was
tempted
to
remove
this
from
the
agenda
this
week,
because
we
talk
about
it
every
week
and
it's
I
think
been
decided
that
we
are
close
enough
to
done
with
it
that
we
don't
necessarily
need
to
work
on
me
anymore.
A
Like
is
this
information
that
should
be
on
backdrops
website
or
in
a
github
issue,
queue
or
I.
Don't
know
in
a
Dropbox
for
backdrop
like:
where
do
we
put
these
resources
and
is
there
a
good
place
to
share
them
and
I
know
we
talked
about
it
two
weeks
ago
and
I?
Don't
actually
remember
what
we
decided,
those
should
go,
but
I
don't
think
we
need
any
work
on
the
style
guide.
Necessarily
I
think
we
have
we
have.
We
know
what
we're
dealing
with
in
terms
of
you
know,
struggling
for
the
product
is
basically
done.
A
It
just
needs
some
field
back
the
style
guide
for
backdrop.
Cms
toward
the
website
is
basically
done
because
we
have
a
website,
but
I
have
a
feeling
that
going
forward
we're
going
to
have
new
things
designed
and
we're
going
to
need
to
have
a
place
to
point
designers
and
say
this
is
our
style
guide.
You
know,
let's
make
a
modules
page
a
page
to
find
modules
and
refer
to
this.
A
As
your
you
know,
document,
and
maybe
all
we
need
is
another
document
like
the
human
interface
guidelines,
one
like
another
Rico
under
backdrop,
ops-
that
has
you
know
four
pages
in
it,
something
very
basic.
That's
like
here's,
how
volunteers
or
color
palette
that
might
be
sufficient
as.
B
An
outsider
I
just
had
a
couple
thoughts,
a
semi
outsider,
so
I
usually
go
to
I.
Try
to
dig
in
like
about
pages
a
lot
of
times
and
see.
If
there's
something
in
there
about
you
know
it.
Press
kit
sometimes
has
it
or
whatever,
but
looking
at
your
site,
I
was
looking
at
the
hand
gut
handbook
and
if
design
and
user
experience
is
something
that
you're
going
to
want
more
involvement
in
down
the
road.
Have
you
have
developer
guide?
B
A
A
Yeah
and
then
that's
also
good
to
you,
because
you
know
if
we
want
to
set
up
for
the
beginning.
This
is
a
friendly
place
for
designers
having
a
developer
guide
and
not
a
designer
guy
kind
of
sets.
The
wrong
tone
there.
So
I,
like
that
idea
to
the
downside,
to
having
all
the
stuff
on
our
primary
website
is
that
it's
not
as
open
as
like
having
it
in
a
github
repository
like
the
human
interface
guidelines
stock,
so
would
like
to
do
if
possible,
is
to
create
those
pages
on
the
primary
website.
A
That
say
like
the
most
basic
things
when
designing
for
backdrop
refer
to
these
resources
and
then
have
those
resources
being
github
so
that
we
can
have
faster
iteration
and
more
collaboration
and
stuff.
But
I
do
think
that
having
that
right
on
the
primary
website
right,
where
one
can
find
it
is
going
to
be
super
beneficial,
okay,
I
love
it
and
then
things
like
the
color
palette.
A
We
can
throw
that
up
like
on
the
website,
for
people
to
see
with
the
hex
codes
and
everything
and
I
think
that's
also
a
good
place
rather
than
having
like
a
file
session.
Dashpot
of
dropbox,
you
can
actually
see
it
like
on
the
web
page.
I
think
it's
going
to
be
great
too
okay,
so
I'm
going
to
make
it
to
do
here.
Then.
A
Alright
and
then
I
guess
the
next
question
is
we
have
this
meeting
once
every
two
weeks
fortnightly,
and
this
is
kind
of
what
we
talked
about
every
two
weeks.
Is
there
anything
that
we
need
to
add
this
agenda
that
we
should
be
thinking
about
that
we're
not
thinking
about
related
to
design
tasks
we
used
to
have
stuff
on
here.
That
was,
like
you
know,
designing
stickers
and
t-shirts
and
hoodies,
and
all
that
became
a
non-priority
it.
So
I
removed
it
from
the
agenda
I'm,
just
something
we're
talking
about
it
again.
A
Over
and
over
lying
again,
let's
make
us
stickers.
We
have
to
try
again,
oh
I,
think
women
had
a
couple.
People
were
interested
in
that
Chuck
the
jagan
and
ran
and
I.
Don't
know
if
they're
working
on
it
or
not,
but
anyway,
not
as
big
a
priority,
so
I
dig
it
off,
but
if
there's
anything
else
really
to
the
product
or
related
to
the
environment,
we're
trying
to
create
for
designers
I
would
love
feedback
on
that.
So
I
know
if
you
guys
have
any
thoughts.
No.
A
Okay
and
then
we
also
have
a
tender
remaining
kind
of
open
shouldn't
time,
where,
if
there's
anything
that
we,
you
know
anyone
who's
joined
the
meeting
wanted
to
talk
about.
We
could
talk
about
that.
I
know,
Wes
your
prime
area
for
style
guide
stuff,
and
we
talked
about
that
in
the
solid
section
of
the
agenda.
I
don't
have
any
other
questions
about
like
how
we
work
or
anything
like
that.
That
is
better
discussed,
face
to
face.
B
Yeah
I,
mostly
just
I,
can
cut
talk
a
little
bit.
I've
been
trying
to
figure
out
things
so
right
now,
it's
kind
of
like
I
feel
like
I'm.
Looking
at
something
that's
like
has
you
know,
there's
a
lot
going
on,
but
I'm
not
quite
sure
I
don't
want
to
like
be
the
guy
that
pulls
a
Jenga
block
out
that,
like
messes
things
up
like
you
can
I
can
put
up
like
a
pull
request.
You'd
be
like
that's,
not
what
we
want.
Do
it
worse.
B
That
would
happen,
but
it's
big
yeah
just
been
more
like
you
know,
I
haven't
really
contributed
an
open
source
before
and
it's
like,
how
do
I,
how
do
I
at
add
some
some
value?
How
do
I
get
get
in
there
and
like
okay?
This
needs
to
be
done.
This
is
I
can
do
it
so
I
feel
like
now.
I
have
a
better
grasp
on
like
okay
I
can
chunk
out
some
tasks,
we're
just
trying
to
make.
B
A
B
B
B
B
B
C
I
think,
for
starters,
what
we
should
probably
do
is
make
a
meta
issue.
We
usually
have
a
like
general
conceptual
issue
of
what
did
the
big
large
task,
and
then
we
put
yeah
like
check
boxes
like
Jen
was
saying
and
I
was
thinking
indicate
the
project
progress.
It
then
and
then
cross
link
all
of
these
sub
issues.
As
you
start,
making
the
individual
components
and
things
yep.
B
C
A
A
C
So
I
think
that
would
be
good
to
just
say.
You
know
we,
because
this
one
mostly
was
around
discussing
like
how
to
implement
on
the
style
guide.
But
now
the
style
guide
is
kind
of
it's
done.
You
know
thanks
to
Darius,
so
so
yeah,
maybe
maybe
have
a
different
one
for
yep
and
that'll
level
implementation,
that'll.
C
A
Alright,
well,
I
think
that's
it
for
a
meeting
today,
but
we
do
tend
to
me
every
other
thursday
at
twelve
o'clock.
So
if
anyone
who's
watching
right
now
would
like
to
join
in
person,
you're
welcome
to
do
that.
I'm
also,
if
anyone's
watching
later
wants
to
join.
That's
fine.
If
you
can't
make
a
noon
pacific
time,
thursday
meeting
you
can
always
join
us
on
IRC,
you
can
check
us
out
in
the
github.
You
can
tweet
at
backdrop.
Cms
org,
there's
lots
of
people
around
doing
work
all
the
time.
A
A
But
thanks
for
joining
us,
we're
excited
to
have
you
on
board
and
we
will
see
you
in
this
EQ
cool.
Alright,
thanks,
bye,
guys,
you
later
bye.