►
Description
Today’s design agenda: http://bit.ly/1VbNKJw
A
All
right,
we
are
on
air,
happy,
Thursday,
April,
14th
everybody
we're
going
to
do
a
quick
check
in
on
outstanding
design,
tasks
for
backup
CMS,
starting
with
backdrops
website,
and
we
have
a
blog
news,
section
I,
don't
know,
I
think
we're
still
calling
it
news,
but
we've
changed
the
heading
to
say
it
was
a
blog.
So
man,
whatever
that
section
is
it's
gonna,
need
a
design
review.
It's
up.
It's
working.
It
just
might
not
be
kind
of
in
line
with
this.
A
That
I
could
the
rest
of
the
site,
that's
something
we
had
slated
for
Darius,
but
anybody
who
understands
design
is
welcome
to
take
a
stab
at
that
too,
and
offer
some
pointers
in
terms
of
things
we
might
change
to
make
that
section
of
this,
like
more
consistent
with
the
rest.
That
issue
is
number
110.
In
the
backdrop,
CMS
org
issue
queue
same
thing
is
true
of
the
events
listing.
A
We
have
made
it
so
that
anybody
who
is
hosting
or
an
attending
event
where
they
want
to
hear
more
about
backdrop,
can
post
it
on
the
website.
It's
just
using
the
default
styles.
There's
nothing
fancy
on
the
event
page
or
in
the
sidebar,
so
we
should
just
make
sure
that
that
works,
the
way
it
is
or,
if
not,
we
need
to
add
some
embellishment.
We
could
do
that
as
well,
and
that
is
issue
188.
A
In
the
backdrop,
semester
or
q,
more
exciting
new
things
we're
working
on
and
we're
trying
to
get
a
showcase
section
so
that
anyone
who's
built
a
site
in
backdrop
can
post
it
in
the
backdrop
showcase
on
the
website
and
that
will
give
people
who
are
looking
into
backdrop
as
a
possible
solution
for
them.
Some
examples
of
sites
that
have
been
completed
and
kind
of
success
stories
for
that
it'll
also
give
developers
a
chance
to
kind
of
show
off
some
of
the
stuff
that
they've
been
doing.
A
So
we
want
to
make
sure
that
we
can
get
proper
attribution
associated
with
each
of
those
posts.
We
have
a
spreadsheet
of
content,
buckets
which
I
think
is
probably
close
enough
to
final-
that
we
could
start
building
that
page.
It
just
has
a
list
of
the
kind
of
things
that
we
want
to
include.
We
have
things
like
the
company
companies
that
were
responsible,
maybe
even
things
like
hosting
providers.
I
don't
know
if
that's
super
relevant
but
I
shots,
perhaps
more
than
one
some
way
to
show
off
mobile
ones.
A
A
So
if
we
have
anyone
who
wants
to
work
on
coming
up
with
a
brilliant
design
for
the
showcase
section
of
our
site,
we
definitely
could
use
some
help
in
that
area,
so
definitely
tasks
there
for
the
taking,
and
then
that
is
issue
number
176.
In
the
backdrop
same
esta,
hora
q,
so
if
anyone
has
any
feedback
on
what
content
or
wants
to
give
a
design
a
shot,
that's
a
good
place.
Just
put
a
comment
to
the
issue.
A
Saying
I
want
to
take
a
stab
at
it
and
let
us
know
like
what
your
time
frame
is
and
then
we
can
follow
up
when
you're
ready
and
see
how
it's
going.
Also
we're
happy
to
help
with
anything
as
needed
through
the
process
and
then
another
thing
that
I
think
we'll
be
able
to
get
up,
maybe
without
being
blocked
on
design,
is
a
service
provider
listing.
This
is
something
that
has
worked
really
well
for
drupal.org,
just
allowing
people
to
mention
that
they
provide
services
around
rupal.
A
So
I
want
to
do
the
same
thing
for
Mac
draft
we're
going
to
have
a
service
provider
listing
where
people
who
do
development
can
listen
songs
as
developers
designers
to
listen
selves
as
designers
hosting
companies
can
listen.
Salsas
companies
that
host
backdrop
just
that
we
can
kind
of
start
to
show
the
world
a
little
bit
of
the
community.
That's
built
around
backdrop,
as
well
as
helping
people
who
are
looking
at
back
job
and
find
people
who
work
on
backdrop
to
kind
of
pair
everyone
together.
A
To
find
know
who
did
this
website
I
want
to
hire
them
click
and
then
have
contact
information
for
that
company.
So
we
cain't
we
can
integrate
all
of
that
in
the
future.
Once
we
get
references
in
detector
and
so
beyond
those
kind
of
new
things,
we
have
a
bunch
of
old
things
that
need
to
be
revisited
on
the
find
themes
and
find
layouts
pages
on
backdrop.
Cms
org
need
a
little
love
the
find
themes
page.
We
actually
have
a
design
for,
and
we
could
get
somebody
with
fronted
skills
to
start
working
on
that.
A
If
they
wanted
to
again,
we
need
a
couple
of
things
on
the
developer
side
to
like
trying
to
figure
out
how
to
pull
in
images.
If
we
want
to
pull
images
over
from
github
or
if
we
want
to
try
and
link
to
them
directly
on
github,
we
don't
know,
there's
kind
of
a
little
technical
challenge
and
how
we
want
to
handle
that.
And
then
you
know,
if
there's
anything,
that's
missing
from
the
designs
that
we
can't
actually
build.
A
Yet
there
will
be
some
development
tests
there
and
making
sure
that
we
have
all
the
information
we
need.
The
layout
project
is
a
little
bit
a
little
bit
more
difficult,
trying
to
build
out
that
find
layouts
page
because
they
don't
have
any
designs
yet,
and
that
was
something
that
we
left
originally,
because
we
weren't
really
sure
what
people
were
going
to
do
with
layouts
if
they
were
going
to
build
an
individual
lab
or
a
set
of
layouts.
And
how
are
we
going
to
visually
represent
the
users
what
these
layouts
look
like?
A
Initially,
that
doesn't
have
any
images
or
we
could
do
something
like
the
themes
that
have
one
I'm,
just
try
and
figure
out
some
way
to
better
represent
those
initially
and
then,
when
we
figure
out
our
like
multiple
images
solution
that
we
want
to
get
in
four
themes
anyway,
or
maybe
even
modules
as
well.
We
can
kind
of
do
that
across
the
boards.
A
We
just
need
someone
to
kind
of
take
what
we
have
and
adapt
it
for
what
we
need,
which
is
sometimes
harder
than
okay,
taking
something
from
scratch,
but
we
do
need
some
help
with
that
find
layouts
page
now
that
people
are
starting
to
do
more
with
backdrop,
giving
them
better
tools
to
get
those
things
done,
it's
going
to
be
really
valuable,
so
that's
backed
up
CMS
org.
Also
I
would
like
to
send
a
newsletter
on
april
twentieth.
A
Do
you
think
would
be
great
I,
don't
think
the
Showcase
is
going
to
be
done,
but
we
can
point
that
out
is
coming
soon
and
mention
that
if
you
have
sites
that
are
built
with
backdrop,
you
can
add
them.
Maybe
next
time
around
the
next
time
we
send
a
newsletter
and
that's
available.
We
can
tell
people
that
it's
ready,
but
I
think
it
would
be
great
to
just
get
people
creating
accounts
and
posting
and
testimonials
or
events
or
service
provider
listings
all
that
stuff
that
we
have
already
that
people
don't
know
about.
A
We
can
do
a
little
kind
of
blast
around
next
time,
so
if
anyone
has
any
time
between
now
and
next
week
and
wants
to
do
a
design
review
on
any
of
that
stuff,
that
will
be
great,
too
I.
Think
the
timing
would
be
great
if
we're
going
to
get
a
whole
bunch
of
eyes
on
the
site.
So
I
think
it's
fine,
but
you
know
making
it
prettier,
sell
ways
good
all
right.
A
So
there's
also
speaking
of
marketing
backdrop,
there's
also
a
tag
in
the
backdrop
CM
esta
hora
q
for
marketing
I
know
that
may
be
the
issue.
Queue
is
not
a
place
that
people
we
do.
A
lot
of
marketing
usually
look
for
tasks,
but
that
was
the
tool
we
had
I'm,
so
so
only
started
to
use.
So
if
you're
particularly
interested
in
marketing,
you
can
definitely
check
there.
There
are
some
issues
that
are
related
to
marketing
and
design,
for
example,
we're
looking
for
some
stickers.
A
That
would
look
good
on
a
Mac
for
something
having
to
do
with
the
dragon
in
the
Apple
so
that
the
you
put
dragon
sticker
over
the
Apple
it'll
light
up
and
wait.
It's
really
cute.
So
if
anyone
has
any
inspiration
on
dragons
and
apples,
that's
a
probably
fun
issue
to
work
on
its
number
189
in
the
queue.
A
Then
we
also
have
this
long-standing
issue
of
needing
some
more
consistent
branding
assets
for
facebook,
twitter
google+,
like
a
background
image
that
kind
of
conveys
the
philosophy
of
backdrop
somehow
how
we're
open
to
feedback
on
that
one
and
that's
issue
121
as
well.
So
if
you
want
to
fiddle
around
and
make
us
some
images
will
be
happy
to
look
at
them
and
maybe
abuse
them
for
real,
because
we
have
kind
of
nothing
right
now,
so
anything
is
better
than
nothing
all
right.
Let's
talk
about
the
exciting
stuff.
Dr.
up.
A
1.4
is
the
next
minor
version
of
backdrop.
That's
up
for
release.
It's
currently
scheduled
for
May
fifteenth,
which
is
a
month
from
tomorrow.
So
that's
pretty
soon.
We've
got
a
lot
of
major
things
on
the
horizon
for
1.4,
so
I'm
not
sure
all
of
them
will
get
in,
but
we're
going
to
see
how
far
we
get
on
relating
to
design.
There
are
still
a
handful
of
user
experience,
issues
that
didn't
get
in
after
the
1.3
release,
which
is
our
user
experience
release.
Oh,
we
would
love
to
have
resolved
by
1.4.
A
Then
you
can
just
search
the
issue,
queue
for
issues
there
in
the
milestone
or
is
just
have
like
you
X
in
the
in
the
tag
and
title,
and
then
you
can
find
those
but
more
major
issues
are
we
want
to
put
in
a
new
front,
end
theme.
I
know
Wes
you've
been
doing
a
ton
of
work
on
that
lately.
Do
you
want
to
give
us
an
update
on
where
the
team
is
at
I.
B
B
You
can
use
rims
the
I,
don't
remember
where
they
fall
off,
but
yeah
if
you
use,
if
you're,
most
comfortable
or
if
you're,
not
particularly
comfortable
with
p.m.
inheritance,
Remz
everywhere
would
effectively
do
the
same
thing.
I
like
using
ms
everywhere
for
basically
I,
don't
know
how
much
I
want
to
get
into
this
I'm
writing
a
little
about
article
about
this
right
now.
B
Actually,
basically,
if
you
have
a
component
like,
let's
say
the
menu
and
the
menu
rapper
sets
of
font,
size
and
REM,
so
it
kind
of
resets
any
potential
inherits
everything
outside
of
it
won't
affect
everything
inside
of
it
and
then
everything
inside
of
it
is
set
with
e
m.
That
means,
if
you
wanted
to
scale
just
the
menu,
you
only
have
to
change
one
font
size
on
the
wrapper,
and
so
you
can
scale
each
component
individually
and
you
don't
get
the
weird
contamination
of
like
p.m.
inheritance.
B
C
C
Oh
seven
years
ago,
they
were
talking
about
thanks,
but
I,
but
the
browser's
have
changed
since
then,
and
now
by
default,
all
browsers
when
you
zoom,
they
don't
zoom
text
only
anymore,
they
all
yeah.
Actually,
when
you
zoom
in
a
browser
like
in
Firefox,
Chrome
or
edge
all
of
them,
it
doesn't
actually
zoom
the
text.
What
it
does
is
it
tells
the
browser
that
its
viewport
is
less,
and
so,
if
you
zoom
in
enough,
you
eventually
get
the
mobile
like
media
style,
shigs
everything,
even
even
though
you
might
have
a
browser
like
1200
pixels
wide.
C
The
web
page
treats
it
as
though
it's
like
320
pixels
wide,
because
you've
told
it
that
the
CSS
that
my
browser
is
only
320
pixels
wide
and
then
the
browser
just
inflates
everything
to
fill
the
available
space
sure.
So
so
that
works
with
everything,
because
everything
thinks
that
it's
all
just
320
pixels
wide.
So
it
makes
the
font
freaking
huge,
as
well
as
everything
else,
but.
B
B
It'll
still
have
the
same
break
point,
but
the
text
will
be
significantly
bigger,
so
your
line
length
might
be
like
three
words
per
line.
What
you
looking
terrible
so
having
all
your
breakpoints
in
EMS
gets
around
that
and
then
whether
or
not
yeah
we
do
like
all
rammer
am
at
a
I'm,
not
all,
but
a
mixture
of
Remini
M
is
whatever
but
I
think
it.
The
other
cool
thing
about
doing
the
way.
B
I'm
thinking
is,
if
let's
say,
I,
make
a
sub-theme
and
I
it's
off
of
basis
or
whatever
the
theme
that
we
have.
If
it,
if
basis
defines
everything
like
I
said
where
the
component
is
kind
of
encapsulated
in
sets
of
REM.
So
let's
say
you
know
a
hero.
It
might
say
that
the
font
size
is
1.5
REM,
because
everything's
gonna
be
kind
of
big
in
it.
If
I
wanted
to
shrink
that
down
or
make
it
bigger,
but
that's
the
only
thing
I
want
to
do.
I
liked
everything
else.
I.
B
Only
have
to
change
one
thing
and
everything
scales,
so
it
makes
it
makes
it
a
lot
more
elegant
potentially,
but
like
that's,
if
you're
a
huge
nerd
like
me
or
we
can
document
it
really
well.
So,
like
I'm,
not
I
really
like
this
idea,
but
I'm
not
saying
like
this
is
the
only
way
to
go.
I
think
it
is
kind
of
idealistic,
but
I
think
we
can
make
it
work.
Yeah.
A
I
mean
I
think
my
main
concern
is
that
like
I,
really
like
the
idea
of
working
in
and
serve
ramps,
but
it's
really
hard
for
people
to
follow
like
what
sighs
that
font
actually
is
in
this
particular
location.
When
you
do
that,
and
so
when
I'm
doing
themes
using
SAS
or
you
know,
whatever
I
write
a
mixin
that
lets
me
specify
the
font
and
pixel.
So
they.
A
A
What's
going
on
having
it
in
pixels
is
super
helpful,
but
I
don't
think
that
the
breakpoints
need
to
be
in
pixels,
especially
if
it
affects
accessibility.
I
think
we
could
be
plugging
points
and
m's,
but
we
should
just
put
comments
in
the
code
that
explain
what
that
is.
So
that
way
people
can
say,
oh,
you
know,
add
a
normal
font
size
is.
This
is
whatever
pixels
and
we.
A
B
A
Wanted
to
do
it
we
want
to
do
like
ends
everywhere,
and
we
have
that
if
we
would
just
have
to
do
that
same
kind
of
documentation
where
it's
like-
and
you
know,
this
menu
block
were
adjusting
the
font
size
down
twenty
five
percent,
so
you
know
something
that
was
16.
Pixels
is
now
whatever
and
then
I
don't
know.
I
just
leave
need
to
do
that
kind
of
I
think
not
only
in
some
kind
of
documentation
page,
but
also
in
the
code
itself.
Over.
B
A
Recommend
like
creating
an
issue
to
talk
about
it,
because
we
don't
really
know
what
our
like
average
users
are
up
to
these
days
either
and
I
think
like
if
we
could
get
more
of
a
conversation
around
who
is
using
our
site,
do
you
use
browser
and
Zoar
whatever
we
can
kind
of
figure
figure
it
out
for
backdrop
to
you
and
that
might
be
a
good
time
to
switch.
If
that
is
what
we
want
to
do,
yeah.
A
B
We
could
go
the
other
way
and
people
might
want
to
be
larger
because
they
have
low
vision
on
the
other
thing
about
zoom
that
I
realized
at
least
in
chrome.
I
don't
know
if
it's
the
same
in
other
browsers
and
maybe
you
can
set
it
faulting,
but
my
zoom
setting
is
site-specific
so
like
yeah,
I'm
not
sure.
If
they'd
be
annoying
fruit,
I
don't
know,
maybe
there's
just
way
set
default
like
I
want
all
sites.
This
zoom,
because.
A
B
Would
with
the
browser
implies
that
implementation
I
would
be
the
most
elegant,
but
the
guy
that
did
the
training
said
that
a
lot
of
people.
He
does
a
lot
of
user
testing
with
low
vision,
and
you
know
different
kind
of
issues,
and
he
said
that
a
lot
of
them
use
like
either
a
browser
extension
or
the
default
setting
to
actually
increase
the
font
size
and
not
zoom
I
was
like
oh
no.
C
Yeah
I
wonder
yeah,
that's
it's
a
little
surprising
to
me
because
the
trend
these
days
is
leaning
so
heavily
towards
larger
fonts.
You
know,
yeah
that
that
I
mean
I.
Guess
that's
one
reason
why
you
wouldn't
want
to
use
default
zoom
everywhere,
because
if
you
had
one
hundred
fifty
percent
default
zoom
on
a
site
already
had
eighteen
point,
pics
18.5
know
you'd
end
up
with
these
massive.
You
know
players
on
a
lot
of
sites,
so
just
setting
zoom
across
the
board
isn't
quite
right.
C
You
know
it's
just
it's
really
kind
of
more
the
older
sites
that
are
like
the
tiny
font
size
and
the
newer
ones
are
just
generally
a
lot
better
and
an
extra
with
our
ad.
With
the
the
revised
seven
I
mean
some
people
have
been
complaining.
The
fonts
to
large,
although
I
think
that,
with
the
way
trends
are
going,
we
made
the
right
call
there
just
by
making
it
basically
big
enough
for
everybody
and.
B
B
C
Larger
is
it
in
vogue
and
so
to
solve
the
immediate
problems
like
if
we
just
make
it
make
all
of
our
fonts
just
about
everywhere.
You
know
they
whatever
it
would
be
usability
acceptable.
For
you
know,
I
mean
I
mean
I,
guess
maybe
that
really
varies.
It
depends
on
how
bad
your
vision
is
or
whatever
but
yeah,
and
you
could
get
encompass,
even
a
larger
percentage
of
people.
If
the
font
is
just
big
enough
in
the
first
place,
yeah.
B
I
actually
saw
a
guy
recently
it
was
low
vision.
He
had
his
phone
like
right
up
literally
right
up
to
his
eye
and
he
was
winking
and
then
he'd
go
like
this,
because
he
could
only
see
the
guy
at
the
accessibility
training
said.
Imagine
just
seeing
you
know
through
a
straw
and
a
straw
might
be
smaller
and
larger,
depending
on
how
bad
the
vision
is.
Imagine
that
blew
my
mind
like
I
had
no
idea
that
was
it
and
and
like
he
said,
that's
the
most
common
accessibility
issue
with
that
with
websites.
A
B
B
If
you,
the
very
first
link,
is
what's
on
this
page
and
it's
just
an
unreleased
of
the
headings,
basically
like
a
table
of
contents
and
I,
just
think
it's
good
as
I
a
person
that
is,
can
whatever
I
don't
have
any
real
issues
using
websites
but
like
it's
also
good
for
accessibility
reasons,
I
thought
that
was
really
nifty
I,
don't
maybe
it's
not
appropriate
for
maybe
like
on
our
API
back
to
up
CMS.
That
could
be
really
cool.
I,
don't
know,
I
really
like
just
like
a
jump.
C
C
B
B
C
A
B
C
A
Alright,
so
that's
a
good
ideas
for
the
new
theme:
I
love
them
all
good
job.
The
next
item
on
our
agenda
is
to
talk
about
the
new
layouts.
We
have
not
made
a
lot
of
progress
on
new
layouts
and
with
one
point
for
a
month
away.
That
might
not
happen.
We
have
a
bunch
of
thinking
to
do
about
how
to
integrate
the
layout
CSS
and
the
theme
CSS
in
terms
of
libraries
in
terms
of
placement.
A
In
terms
of
all
of
that
stuff,
we
also
figure
out
how
to
handle
upgrade
paths
from
the
current
layouts
that
are
in
core
two
potential
new
ones,
and
we
need
to
try
and
find
a
way
to
do
all
that
without
breaking
any
one
site.
So
markup
changes
that
sort
of
thing
and
we'll
try
a
you
know
and
get
that
done.
We
do
still
have
a
month
and
this
community
does
have
a
way
of
getting
a
whole
bunch
of
stuff
done
at
close
to
launch
time.
So
it's
good.
A
We
have
launches
three
times
a
year,
but
we'll
see
we'll
leave
that
on
the
list,
because
I
think
it's
going
to
be
a
killer
feature
for
backdrop
to
have
a
ton
of
layouts
that
are
ready
to
use
out
of
the
box.
But
if
we
have
to
push
something
to
1.4,
that's
probably
the
likely
the
likely
feature
that
won't
make
it
just
because
it's
had
the
least
progress.
So
far,
so
we'll
see
keep
an
eye
on
it.
Not
given
up
yet.
Oh.
B
Ok,
I
thought
what
if
oh,
ok,
two
things,
one
if
we
put
REMS
everywhere
for
font
sizes
to
enable
you
know,
people
who
change
the
default
font
size
we'd
have
to
have
a
px
fall
back
anyway
for
ie8,
and
that
would
self
document
what
that
size
is
intended
to
be,
which
could
be
cool.
A
A
It
in
then
anyone
who
has
it'll
be
like
oh
I,
want
to
play
with
this
and
we'll
get
a
whole
bunch
more,
so
that
excellent
excellent
idea,
love
it.
It
was
that
two
things
yes,
cuz,
the
fall
back,
okay,
just
making
sure
than
something
all
right.
So
if
anyone
who
wants
to
know
what
else
working
at
1.4,
there
is
a
milestone
in
the
github
issue
queue,
you
can
look
for
all
issues
typed
with
14
and
there's
also
a
tag
on
the
issue,
queue
for
all
issues
related
to
design.
A
If
we
have
somebody
who
loves
documenting
those
kinds
of
things,
we
need
to
volunteer
for
that.
We
have
a
couple
of
ideas
about
making
it
a
requirement
to
get
the
documentation
done
every
time.
Some
new
element
goes
into
core,
but
I
think
we
need
a
better
starting
point
than
what
we
have
now
before.
We
can
start
adding
stuff
to
that
Wade.
Someone
kind
of
think
through
that
and
at
least
make
us
an
outline.
A
So
that
would
be
a
great
task
for
somebody
new
to
jump
in
and
Duke
just
involves
looking
at
how
things
are
going
and
writing
it
down.
So
not
a
lot
of
work,
not
very
calm.
Well,
it's
kind
of
complicated,
but
it
so
it's
a
good
good
place
to
start
okay.
So
that's
all
we
have
for
today's
agenda.
Is
there
anything
else
you
guys
want
to
talk
about
today.
C
I,
don't
think
so,
I
think
yeah,
I
I,
think
our
design
focus
for
the
next
release
is
definitely
on
the
new
theme.
If
we
can
make
that
happen,
and
that
would
be
huge
yeah
we've
got
the
the
general
developer
meeting
coming
up
in
20
minutes
and
yeah
I
mean
the
things
that
we're
targeting
a
lot
of
stuff
for
this
release,
and
it's
only
a
month
away
and
if
we
can
get
in
the
things
that
we
have
like
most
of
the
way
there,
then
it
will
be
an
awesome
release.
B
C
Yeah,
so
yes,
but
it's
not
as
important
like
right
now.
Well,
we've
done
with
a
project.
Browser
is
like
basically
project.
Browser
kind
of
doesn't
really
have
a
UI.
At
this
point,
light
I'm,
sorry
doesn't
have
a
design
will
say
it
that
way
where
it's
like
your
typical,
like
all
of
the
functionality,
is
there,
but
it's
really
not.
C
C
So
at
this
point,
like
project
browser
is
like
so
close
that
I
think
that
what
we'll
do
is
we'll
probably
merge
it
here,
assuming
doc
home
unfinished.
Is
it
up
in
like
next
week
or
so,
and
then
we
can
iterate
on
it
beyond
that.
So
design
feedback
is
definitely
appreciated,
but
at
this
point
will
polish
the
functionality
get
it
in
and
then
iterate
on
it
got.