►
From YouTube: Backdrop CMS Design task check-in 5/28
Description
Quick check in on design tasks for Backdrop CMS.
B
So
it
looks
great.
Let's
see,
let's
go
through
the
agenda
that
we
have
sent
out
for
this
week.
The
first
thing
we
actually
talked
about
is
not
actually
a
backdrop,
but
is
backdrop
CMS
dot
org,
which
is
a
flagship
website
in
which
we're
trying
to
do
we're
expanding
out
new
sections
of
the
site
in
it.
As
we
extend
out
new
sections.
Of
course,
we
need
new
new
designs
for
those
sections,
so
the
number
one
thing
that
we're
working
on
or
heading
very
quickly
towards
is
project
listings.
B
B
Now
we've
got
almost
40
projects
that
have
official
releases
that
are
on
backdrop,
CMS
org
right
now,
however,
there's
no
way
to
actually
find
them
on
backdrop,
CMS
dot,
org,
because
we
don't
have
the
project
listing
pages
actually
built
out
yet,
and
so
Darius
have
done
some
designs
for
the
project
listings,
which
looked
great
but
the
next
mockup
or
design
that
we're
lacking
is
the
actual
project
pages
themselves.
So
when
you
actually
look
at
a
project,
you
know,
where
does
the
version
information
go
the
download
button?
B
C
Yeah
I've
got
a
comment
about
that,
actually,
so
for
the
remaining
design
test
that
I
have
that
need
to
be
done.
I
think
that
would
help
me
a
lot
if
we
just
came
up
with
some
arbitrary
deadline,
because
it's
becoming
way
too
easy
to
me
just
to
say
tomorrow,
just
when
I
think,
maybe
after
the
meeting
or
offline
or
whatever
we
could
sort
of
boundaries
around
these
things
like
I.
Finally,
do
it.
B
Bit
hard
to
tell
where
the
priorities
are
with
this
particular
area,
we've
just
finished
up
a
bunch
of
other
things
related
to
project
module
that
and
we
have
enough
projects
on
backdrop,
CMS
org
that
that's
probably
I
mean
it's
our
number
one
priority
as
far
as
backdrop
CMS
org
is
concerned,
is
build
up
the
listings
and
then
start
building
out
the
project
pages,
but
yeah.
Let's
let
slip
some
deadlines
after
after
the
meeting
great.
B
A
So
that
was
just
like
you
know:
forms
in
Drupal
are
always
a
little
bit
yucky
and
if
we're
gonna
allow
people
to
add
their
own
projects
or
modify
projects
that
are
imported
from
github,
we
should
just
kind
of
do
a
review
of
the
form
that
we
get
and
see.
If
there's
anything,
we
do
to
improve
it,
so
I
think
in
terms
of
designing
it,
we
don't
need
to
design
it
first.
We
should
take
a
look
at
it
and
go.
This
is
the
epi?
A
How
do
we
make
it
less
yucky
and
if
we
need
to
split
it
into
a
two
column
layout,
we
could
do
that
or
whatever
it
is
based
on
what
we
have
and
how
many
fields
we
have
on
there
and
how
they
need
to
be
organized
and
that
sort
of
thing
so
I
don't
think
it's
a
design
first
task
as
much
as
a
design
review,
/,
improved
task,
I'm
good
to
me.
Yes,.
B
There's
a
no
dad
forms
in
there
to
edit
forms.
Initially,
people
would
just
be
modifying
their
projects
via
github.
You
know,
as
they
make
an
eerie,
create
the
release
on
backdrop,
CMS
org
and
likewise,
if
they
update
the
readme
within
their
project,
I'll
update
the
readme
on
dr.
up
CMS
torg
so
initially
like
we
don't
even
have
user
logins
yet
so.
D
A
A
A
B
I've
got
serious
cat
action
happening
over
here;
okay,
all
right!
So
that's
it
for
backdrop:
CMS
org
for
the
most
part,
things
are
just
swimmingly
awesome
over
it
by
joseph
e.m
asteroid,
which
is
great
and
then
backdrop
the
product.
So
as
I
mentioned,
1.1
is
out
and
we
included
a
new
administration
theme,
but
there's
some
cleanup
that
needs
to
be
done
that
we're
going
to
just
work
on
iterating
on
the
the
admin
theme
a
little
bit
further
and
probably
improve
that
in
the
bug
fixing
releases
as
we
go
forward.
B
So
a
couple
of
minor
issues
that
Wes
has
been
working
on:
we're
missing
the
border
from
text
fields
and
text
areas
in
mobile
safari.
It's
issue,
9,
42
Jen.
You
had
some
input
on
that
as
to
why
we
were
using
so
apparently
the
problem
there
is
that
we're
using
box-shadow
instead
of
a
border
to
add
the
borders
to
those
input
elements
Jen
of
the
explanation
for
that
I
think.
A
A
D
A
C
C
B
B
D
B
Ok
cool,
so,
let's
see
what's
offer
did
nice
work
messages
and
the
status
report
I.
Think
that
looks
great
and
I
think
that,
while
we're
in
there,
we
should
work
on
fixing
kind
of
long-stay
issued,
there's
no
icon
for
any
any
notices
or
what
is
it
for
information
all
right?
So
there's
like
half
icon.
B
Or
are
there
like
all
things
just
a
little
bit
weird,
but
I
think
appearance-wise
we're
looking
great
there
we're
just
going
to
fix
that
issue.
At
the
same
time,
there
was
one
other
minor
issue:
Oh
field
sets,
that's
what
it
was
I
hadn't
added
that
one
to
the
city
agenda
yet,
but
Darius
WestEd,
an
initial
stab
at
field,
sets
to
try
to
style
them
in
a
way
that
would
work
within
our
current
situation
that
we
have
going
on
with
nested
yield
sets
and
collapsible
fieldset
small
little
stuff
awesome.
A
B
D
D
C
A
It's
like
this
weird
hodgepodge
of
like
early
devil
backdrop
plus
a
bunch
of
code
we
throw
in,
but
at
this
point,
like
most
of
the
code
in
the
style
guide,
has
been
implemented
in
backdrop
1.1,
and
it
might
be
a
good
time
to
like
wipe
the
slate
clean,
pull
in
a
new
style
guide
from
backdrop
11.1
and
if
Wes,
if
you
and
Darius,
want
to
work
directly
in
the
style
guide
to
put
in
these
fields,
edit
styles,
that
might
be
a
good
place
where
you
can
collaborate
on
that
cool.
So
that's
a
thought.
B
A
D
A
A
I
think
in
core
would
be
super
handy
for
people
who
just
wanted
to
like
proto
prototype,
build
and
deploy,
and
right
now,
when
you
launch
a
site
with
Bartok,
it
looks
like
all
other
drupal
and
backdrop
sites,
so
yeah
getting
getting
something
in
core
that
is
blank,
yet
still
modern,
I
think
would
be
fantastic,
but
yeah
we
don't.
We
don't
have
any
urgency
on
that
like
if
we
get
it
in
for
one.
We
can
add
something
new,
that's
fantastic
if
we
don't
get
in
until
two.
A
That's
also
fine,
but
I
wanted
to
talk
about
it
in
this
meeting
every
week,
so
that
we
have
people
who
are
have
design
skills
if
they
want
to
say
that
I
want
to
do
that.
I
want
to
build
a
new
front.
End
theme
that
goes
into
backdrop
core
that
every
backdrops
I
can
use
I
want
you
to
hear
about
it.
I
want
you
to,
you
know,
fall
in
love
with
the
idea
and
run
with
it.
So
it
is
on
our
list
of
to
do's
hello
done
fairly
low
priority,
but
no
no
timeline.
B
D
B
Distributed
like
300
stickers,
stickers
and
like
70
t-shirts,
but
none
of
our
t-shirts
that
there
were
just
the
backdrop
CMS
logo
across
chest.
They
were
a
huge
hit.
We
got
rid
of
all
of
them
by
like
the
third
day,
but
what
we'd
like
to
do
is
have
t-shirts
with
our
mascot
drop
on
them
before
at
least
before
bad
camp,
which
is
November.
A
It's
totally
fine
to
do
whatever
I
would
love
to
have
dropped
in
more
positions
available
as
an
asset
like
I
would
love
to
see,
drop,
flying
or
maybe
trying
to
fly
since
he's
still
baby
dragon
a
job
breathing
fire
might
be
fun,
I,
don't
know,
there's
so
many
things
you
could
do
with
a
dragon,
and
we
right
now
only
have
two
positions,
so
I
would
throw
this
out
to
anyone
watching
this
video.
If
you
want
to
play
with
a
dragon,
we
have
one.
We
want
more
pictures
of
it.
A
We
can
also
go
back
to
our
original
dragon
designer
and
ask
him
for
more
I.
Don't
know
dragon
illustration
illustrations,
but
yeah
I
would
love
to
get
something
on
a
t-shirt.
I
also
think,
because
Darius
is
doing
a
bunch
of
the
design
for
bad
camp.
The
sooner
we
can
get
the
t-shirt
done,
the
less
stress
on
Darius,
which
would
be
good.
So
if
we
want
to
just
say
like
we'll,
give
ourselves
a
month
to
get
a
new
dragon
and
if
we
don't
get
a
new
Dragon,
we
put
the
same
dragon.
A
We
had
on
the
sticker
on
the
t-shirt.
I
think
that's
fine.
Everybody
loved
the
stickers
I
think
they'll
love
the
t-shirts.
We
can
also
do
like
a
new
Dragon
position
every
year
if
we
wanted
to
and
like
flip
it
up.
So
it's
like.
Oh
you
have
the
t-shirt
from
2015.
I
only
have
the
t-shirt
from
2017
and
like
how
do
I
I
don't
know
to
be
kind
of
him.
A
So
with
that
options
it
there
are
some
complications
like
we
have
to
figure
out
whether
we're
going
to
do
two
colors
or
one
color,
and
what
the
dragon
would
look
like
in
one
color
I
think
we
should
just
go
for
it,
go
big
or
go
home
and
do
a
two
color
dragon
in
some
crazy
new
position,
but
that
does
require
more
organizing
on
our
part.
B
B
B
B
C
A
The
last
item
is
just
something
I
just
threw
on
to
this
agenda.
Every
time
I
go
tweet
from
our
twitter
account.
It
bothers
me
that
I
just
randomly
pulled
these
images
off
of
the
internet
and
I'm
using
them
for
backgrounds.
For,
like
our
banner
images
on
Twitter
and
Facebook,
I
grabbed
some
random
fractal
recursion
thing.
A
A
A
B
Cool
all
right,
so
bigger
picture
we've
got
a
couple
of
sort
of
like
whenever
we
could
get
to
them
like
nice
to
have
that.
It
would
be
great
that
we
could
flush
them
out
a
little
bit
more.
We
had
a
start
on
human
interface
guide,
I
answer
back
up
cmf.
That
was
basically
the
concept
of
like
when
you
should
be
using
vertical
tabs
versus
collapse.
The
collapsed
field
sets
the
idea
of
which
patterns
you
should
use
in
which
places
like
when
check
boxes
or
radio
buttons
are
appropriate.
B
That
sort
of
thing
and
gutom
had
a
start
on
that,
but
it
kind
of
fizzled
out
we'd
still
really
like
to
have
that
built
out
in
a
more
comprehensive
human
interface
guidelines,
actually
all
documented
just
so
that
we
can
reference
it,
but
for
now
that
that's
kind
of
stalled
we'd
really
like
to
see
that
push
forward,
though
so,
if
anybody's
interested
in
it,
it's
issue
390.
In
the
backdrop
issue
queue
be
great
to
remove
that
one
forward.
B
Let's
see,
there's
also
an
item
in
here
for
brand
guidelines
and
we
have
the
start
of
a
brand
guidelines
which
is
pretty
good
at
backdrop.
Cms
org
flash
press
kit,
but
I
think
it
would
be
good
if
we
actually
assembled
an
actual
like
right
now.
Our
press
kit
is
really
nothing
but
a
collection
of
a
collection
of
assets.
B
Like
you
know,
it's
got
like
the
svgs
for
the
logo
and
drop
and
and
stuff
like
that
in
it,
but
it
would
be
great
if
we
had
it
actually
documented,
like
the
full
like
canonical
reference
of
like
this
is
how
the
logo
should
be
displayed
and
that
sort
of
thing.
So
we
don't
have
an
official
Brent
brand
guidelines
yet,
but
but
we're
working
on
flushing
them
out
a
little
bit
so
another
nice
to
have
just
like
an
actual
documentation
of
how
the
logo
should
be
used
in
things
like
that.
A
Think
we
should
maybe
think
about
what
our
remaining
design
tasks
are
for
backdrop.
Now
that
we
have
our
admin
theme
in
like
backed
up
a
product
and
see
if
we
should
at
maybe
prioritize
the
issues
in
the
q
and
say
you
know,
would
really
make
a
big
difference
if
this
thing
was
done
and
talk
about
those
in
the
meeting,
because
I
feel
like
what
this
meeting
is
right
now
is
stuff
going
on
and
backed
up
and
stuff
going
on.
A
B
Yeah
I
kind
of
get
the
feeling
that
we'll
always
have
some
design
task,
both
inside
and
outside
of
the
product,
even
though,
like
we
might
not
have
a
like
a
super
large
thing.
Like
the
admin
theme
like
there's,
always
things
to
improve
upon,
like
we
could
start
going
through
and
doing
things
like
trying
to
redesign
the
views
you
I,
you
know
the
cleanup.
A
A
Then,
let's
maybe
for
the
next
meeting,
we
can
pull
out
like
three
issues
or
something
that
we
want
to
work
on
and
talk
about
those
instead
I
would
love
to
get
like
field.
You
I
fixed,
oh
yeah,.
A
They're
so
complicated
it's
hard
to
do
that.
Well,
okay,
is
there
anything
else
it
either,
if
you
guys
want
to
add
or
anyone
else
wanted
to
add,
either
to
the
weekly
agenda
just
this
week.
A
We
can't
hear
you
Nate
up
up
all
right
well,
why
don't
we
just
go
ahead
and
say:
thank
you
guys
for
coming.
We
will
see
you
on
IRC
Darius.
Maybe
we'll
send
some
emails
about
timelines
for
what
comes
next
I
think
Nate.
Can
we
give
Darius
a
login
to
the
backdrop
sites
if
he
can
see
the
module
pages
right
now?
That
might
also
help
move
the
module
page
design
forward
to
or
it's
like.
We
have
all
this
data.