►
Description
Today’s design agenda: http://bit.ly/1TYkljK
A
If
we
can
talk
about
those
issues
in
the
developer
meeting
a
little
bit
later
today
and
then,
if
we
have
any
designers
who
are
there,
we
can
get
their
feedback
on
that
as
well.
If
not,
we
can
take
it
to
the
issue,
queue
so
design
tasks,
starting
with
backdrop
CMS
the
product
itself,
first
of
all,
I
just
want
to
take
a
minute
to
say
thank
you
to
everybody
who
worked
on
all
the
design
and
user
interface
tasks
that
went
into
backdrop
1.3.
This
is
our
first
meeting
I.
A
Think
since
1.3
was
out,
it
was
a
big
success.
Iram
really
excited
to
be
working
with
it
and
giving
it
to
my
clients
I
think
it's
a
huge
improvement
over
the
previous
versions,
and
it
only
got
there
by
making
a
whole
bunch
of
little
teeny
tiny
changes.
So
sometimes
those
little
changes
can
really
make
a
big
difference.
So
I
gots
to
everybody
who
worked
on
that
in.
Thank
you
for
all
the
help.
A
So
next
release
1.4
is
scheduled
for
May
fifteenth
and
that
release
contains
a
couple
of
things
that
are
particularly
of
interest
to
the
design
community
and,
first
of
all,
there's
a
couple
of
user
experience,
issues
that
rolled
over
from
1.3
that
we
didn't
get
done
in
time.
We
would
love
to
see
done
for
1.4.
Some
of
those
are
really
hard
things
like
a
rewritten
field.
Do
I,
but
we
definitely
need
designer
in
an
easier
experience,
expert
feedback
on
those,
and
you
can
see
a
list
of
all
the
issues
for
1.4
on
github.
A
There's
a
link
in
the
india
agenda
for
today's
meeting,
where
you
can
just
search
by
milestone
for
1.4
and
get
up,
but
two
of
the
big
most
important
things
we
need
for
backup.
1.4
are
we're
trying
to
put
in
a
new
front
end
layout
or
a
new
front
end
theme,
so
that
anyone
who
installs
the
backdrops
that
can
launch
with
a
theme
that's
something
I
of
envirotech
vortex.
A
What's
in
there
now
it's
beautiful,
but
it's
a
little
bit
too
stylized
we're
looking
for
something
a
little
bit
more
general
generic
kind
of
white
label
website
feel,
and
so
we've
got
an
issue
on
the
issue
queue.
It's
issue
number
13
61,
which
is
talking
about
what
our
requirements
might
be
for
a
front
end
theme
and
suggestions
or
recommendations
on
what
it
should
look
like
pointing
examples
of
other
themes
that
we
think
might
make
a
good
candidate
that
sort
of
thing.
So
we
have
any
designers
either
listening
to
this
now
or
watching
it
later.
A
If
you'd
like
to
weigh
in
on
what
you
want
to
see
on
a
new
front,
end
theme
for
backup,
Zuma's,
please
add
a
comment
there
and
let
us
know
what
you
think.
Another
thing
that
we
are
itching
to
get
into
1.4
is
a
new
set
of
layouts
right
now,
core
comes
with
four
layouts
and
that's
not
quite
enough
to
build
the
average
website.
A
You
usually
need
either
more
than
that
or
different
options
than
what
is
there
today,
and
so
we've
been
looking
at
looking
at
taking
some
of
these
projects
that
are
sets
of
layouts
and
including
those
in
court,
and
we
need
to
kind
of
do
some
thinking
about
how
that
will
affect
the
existing
layouts
like.
Are
we
going
to
try
and
provide
upgrade
paths,
or
are
we
going
to
leave
the
old
ones,
they're
called
legacy?
How?
How
can
we
do
this
gently
without
breaking
anybody
sites
and
what
those
new
front-end
layouts
should
be
like?
A
How
many
should
we
include
how
complicated
should
they
be
work
sort
of
grid
system?
Should
we
use
all
that
has
issue
as
well
on
github,
it's
issue
number
698.
So
if
you
are
an
expert
in
layouts
or
have
an
opinion
on
what
we
should
be
doing
with
layouts
in
backdrop,
we'd
love
to
have
your
feedback
there
as
well.
A
If
you
are
just
interested
in
issues
that
may
need
designer
or
user
experience
input
for
backdrop,
where
there's
also
a
tag
in
the
issue,
queue
audience,
Cohen,
design,
I,
think
and
you
can
search
all
issues
that
are
related
to
sign.
And
that
way,
if
you
have
some
amazing
photoshop
skills,
I
mirren
interested
in
writing
any
code.
You
can
kind
of
look
at
some
of
the
issues
ago.
A
That
should
look
like
this
posted
a
picture,
sometimes
pictures
the
people
who
can
make
pictures
in
open
source
or
being
a
lot
more
powerful
than
people
who
can
write
code
because
they
could
steer
things.
So
we
definitely
appreciate
people
who
can
make
pictures.
So
if
you
want
to
help
us
out
some
of
those
issues
check
out
that
tag,
Kobe
a
great
place
to
jump
in,
in
addition
to
backdrop
the
product,
we
also
have
backdrop
CMS
org
as
an
area
that
could
use
some
design
attention.
A
We
have
a
couple
of
to
do's
here
that
are
on
list
that
have
been
kind
of
ignored
for
the
last
few
weeks
as
we've
been
working
on
backdrop,
the
product
and
so
the
issues
that
we're
working
on
as
a
new
profile
page
that
we
have
up
right
now.
The
to
do
there
is
to
clean
up
the
edit
form
on
that
profile
page.
A
So
we
can
use
our
front
end
theme
on
editing
profile,
we've
added
a
new
blog
or
news
and
announcements
section,
and
that
would
just
kind
of
pack
together
with
some
styles
that
were
chosen
from
various
other
websites,
but
it
could
use
a
little
design
review
and
that's
currently
on
Darius's
flight.
He
knows,
but
he's
pretty
busy,
so
he'll
get
to
only
has
time
and
then
we're
also
starting
to
think
about
building
a
showcase
section
for
backdrop,
CMS
org.
A
This
will
enable
anyone
who's
built
a
website
to
be
able
to
post
about
it
talk
about
the
cool
things
they
did
with
backdrop
and
show
an
example
of
the
site,
maybe
with
a
link
back
to
it
and
give
them
a
little
SEO
love
there
too,
and
I've
got
it
to
do
there
to
gather
the
types
of
content
we
want
to
include
in
that
showcase
site.
So
look
at
other
showcase
sites
find
out
what
works
for
them.
A
A
Until
we
can
see
the
content
than
it
might
that's
kind
of
where
we
are
with
the
primary
website
and
and
then
we
have
a
couple
of
other
things
long-term-
that
we're
going
to
be
working
on
like
building
an
event
listing
letting
people
list
their
companies
or
into
themselves
as
service
providers
and
I.
We
have
a
couple
of
follow-up
issues
for
the
find
a
module
will
find
the
layout
find
a
theme
sections
of
the
site
as
well
and,
as
you
all
probably
know,
there
are
backdrop
t-shirts
in
hoodies
available.
A
If
you
make
a
donation
to
backdrop,
we
can
send
you
one
and
thank
you
gift.
If
you
are
already
a
contributor
to
the
backdrop
project,
you
have
earned
a
t-shirt,
so
you
can
send
an
email
to
info
backdrop.
Cms
org.
We
consider
contributor
rather
loosely
so
obviously
we're
not
looking
for
code
samples
or
for
us.
But
if
you
have
participated
in
in
conversations
or
provided
designs
for
anything
that
also
counts
as
being
a
contributor
and
you
have
art,
a
t-shirt
would
be
happy
to
set
one
up.
Also
just
really
quick.
A
We
should
mention
that
there
are
slides
available.
In
the
backdrop,
ops
group
on
github,
these
are
available
for
anyone
who
wants
to
give
a
talk
on
backdrop.
We
would
also
love
it
if
anyone
who
gives
a
talk
in
changes
or
adds
to
that
slide,
deck
would
contribute
them
back
so
for
crests
welcome
there.
A
We
have
a
couple
of
issues
in
the
backdrop
Sam,
esta
or
cute,
that
are
related
particularly
to
branding
or
marketing,
and
we
can
definitely
use
some
help
in
that
area.
If
anyone's
marketing
expert,
you
can
search
the
chic
you
for
the
tag
audience
marketing
and
see
what
we've
got
going
on
there
and
the
one
we're
working
on
most
recently
or
most
relevant
to
this
call
is
creating
some
online
branding
imagery.
That
can
go
with
backdrop
and
on
the
facebook
page
on
the
twitter
page
anywhere.
A
We
need
kind
of
a
banner
image
and
I
know:
we've
gotten
a
couple
of
great
posts
as
a
start
that
are
kind
of
the
right
on
the
right
fetal
for
backdrop,
but
we
haven't
gotten
anything
definitive
yet
I
know,
there's
a
couple
working
on
that.
So
thank
you
advance
for
all
the
effort
you're
putting
into
that
and
we're
looking
forward
to
seeing
where
that
can
go.
A
If
anyone
wants
to
follow
that
issue,
it's
number
121
in
the
factor
of
ceylon
start
work
queue
and
then
Mike,
just
because
I
think
you
might
want
to
weigh
in
on
this
and
I
noticed
that
you
just
joined
one
of
the
things
that
we
talked
about
earlier.
We
talked
about
meeting
it
as
a
different
ending
Andy
came
today
to
see
was
hoping
to
talk
about
that
I.
A
Don't
know
if
I
mean
I
wanted
to
take
some
time
in
this
meeting
to
talk
about
it,
but
we
were
thinking
that
maybe
what
we
should
do
is
wait
for
the
developer
meeting
and
then
get
kind
of
more
eyes
on
the
problem
would
be
able
to
talk
about
that
since
we
don't
have
any
of
our.
I
just
I'm
booked
here,
usually.
B
Yeah
well,
I
mean
most
of
us
will
say:
we
probably
want
a
list
of
requirements
to
start
house
yeah
and
just
you
know,
coming
up
with
relief.
You
know
a
and
like
they'll,
be
a
probably
argument
like
you
know
what
grid
system
use
or
you
know
what
frameworks
to
include
and
stuff
like
that,
but
it
seems
like
sort
of
like
the
basic,
the
basic
things
that
we're
looking
for
is
kind
of
a
good
start
for
any
project.
B
A
I'll
go
through
the
issue
queue
and
see
if
I
can
pull
out.
Some
things
that
people
have
mentioned
is
there's
a
whole
bunch
of
stuff
in
the
comments
about
possible
requirements,
and
if
we
can,
maybe
liquid
doesn't
list
at
the
top,
we
can
talk
through
those
and
see
if
there's
anything
else,
we're
missing,
and
even
if
we
don't
have
a
consistent
consensus
on
what
to
do
yet.
If
we
can
kind
of
narrow
down
like.
Is
it
really
important
that
it
works
with
color
module?
B
A
That's
great
and
that's
a
great
thing
to
announce
in
this
meeting
to
so.
Anyone
who
watches
this
video
later,
if
you
have
a
really
good
idea
of
a
kind
of
a
blank
slate
but
usable
watchable,
today
kind
of
site
that
you
see
out
there
that
you
think
should
be
inspiration
for
backdrop,
take
a
screenshot
and
post
it
in
the
issue.
Queue
that
issue
again
for
a
new
friend
and
theme
for
back
job
is
number
thirteen
sixty
one.
A
In
the
backdrop,
it's
you
and
there's
link
to
that
in
the
agenda
and
there's
also
it's
in
the
1.4
milestone.
If
you
just
go
to
the
issue,
queue
and
search
for
that
way,
okay,
well,
a
few
other
things
I
guess
to
touch
based
on.
We
are
hoping
to
get
human
interface
guidelines
going
for
backdrop,
and
we
can
kind
of
build
these
as
we
need
to,
but
trying
to
figure
out
when
certain
interface
elements
should
be
used
and
when
they
shouldn't,
we
need
to
document
what
we're
doing
in
court.
A
We
need
to
figure
out
if
that's
actually
want
to
do
or
not.
No
I
need
to
try
and
go
through
and
update
core
to
match
the
things
we
do
want
to
do
and
stop
doing
the
things
you
don't
want
to
do
and
then
hopefully
can
trim
when
they're
building
user
interfaces.
If
anyone
is
really
interested
in
documenting
user
interfaces,
there's
a
publix,
github
repo
you
can
contribute
to.
We
haven't
had
a
lot
of
progress
on
that
lately.
A
B
A
B
C
B
It
sort
of
like
when
people
ask
like,
like
we
just
did
the
config
block
at
the
Boston
config
and
then,
like
some
other
to
get
someone
was
like.
Why
didn't
we
do
that?
And
it's
like
resin
like
just
explaining
all
over
again
or
pointing
them
to
the
original
ticket,
where
they
can
like
sort
of
bailed
through
the
entire
back
and
forth
discussion?
It
would
be
great
if
we
actually
had
like
even
more
than
just
the
design
guidelines,
a
place
to
document
like
why
we
did
things
right.
A
Where
do
you
think
this
should
live
like
we
have
this
place
for
change
records
that
are
very
specifically
for
like?
Oh,
if
you're
changing
code,
here's
the
code
before
and
after,
but
should
we
have
another
type?
That's
lame
like
similar
to
a
change
record,
but
more
like
an
explanation
record
or
something
that
we
can
just
talk
about
like
how
we
made
these
decisions
or
well
I
mean
yeah.
B
Yeah,
I
mean
that's
a
good
question.
I
thought
that
nate,
when
you
did
the
announcement
of
all
the
cool
improvements
in
the
latest
release,
that
was
sort
of
a
good
rundown,
of
least
like
a
lot
of
the
visual
changes
and
stuff
like
that,
and
if
we
somehow
it
sort
of
a
demise
that
and
indexed
it
and
had
one
of
those
for
every
release.
That
might
be
good.
D
Okay
yeah
and
we
should
we
should
have
one
of
those
februari
release
at
this
point.
I
know
our
last
our
last
one
wasn't
quite
so
elaborate.
But
honestly
we
had
a
lot
of
stuff
to
show
off
this
really
so
I
felt
like
it
actually
needed
it.
This
release
required
a
lot
more
explanation
than
the
previous
one
did
where
it's
just
like
I
thought.
D
A
D
A
One
related,
but
I
found
the
release
for
one
point:
one
knee
is
on
your
blog.
Maybe
we
should
move
back.
Sweden
have
the
blog
like
that.
Maybe
we
should
move
that
over
and
just
create
an
older
post
on
backdrop,
so
that
people
are
looking
for
like
what
was
in
1.1
could
find
that
on
our
site,
yeah.
D
A
A
That's
not
going
to
scale
having.
I
was
looking
at
that
when
I
set
up
the
1.4
on
the
road
map.
I
was
like
this
doesn't
make
any
sense
to
have
these
in
order
some.
What
you
want
is
a
plat
them,
but
as
if
one
maybe
I'll
reverse
the
order,
and
then
I
was
like
no,
that
isn't
nice.
I
just
left
it,
but
at
some
what
we
are
going
to
need
to
figure
out
how
to
put
the
old
stuff
on
another
page
so
that
the
road
map
adjust
the
future
yeah
I.
Think
that's
fine
yeah.
B
A
Okay
and
well
I,
don't
think
we
have
anything
else
to
talk
about
today.
I
think
we
should
wait
and
talk
about
front
end
theme
and
layouts
in
developer
meeting
today
too
and
see
if
we
can
kind
of
nail
some
stuff
down
I'll
take
some
time
between
now
and
then
to
try
and
figure
out
what
happened
in
that
issue
queue
since
the
last
time,
I
was
in
there
and
maybe
make
a
list
of
things
people
are
debating,
and
then
we
can
talk
about
them
in
the
meeting
and
see
if
that
helps.