►
Description
Today’s design agenda: http://bit.ly/2cFnbd8
A
Alright,
we
are
on
air,
it
is
Thursday
I,
November
10th.
Sadly,
we
are
talking
about
design
pests
for
back
job
in
West
had
mentioned
that
he
was
interested
taking
a
stab
at
the
new
homepage
design,
which
is
issue
number
301.
In
the
backdrop,
sea
monster
or
q
Mike
McCaffrey
I,
recommended
example
site.
Was
it
the
Django
site?
What's
yeah.
B
A
That
will
also
fix
our
mobile
problems
with
the
menu
that
we're
having
today.
But
I
was
blocked
on
that,
because
I
thought
it
might
significantly
impact
the
design
of
how
the
page
works
with
the
drawer
and
all
that
as
well.
So
there's
probably
some
way
we
could
keep
it
kind
of
similar
like
if
we
added
the
drawers
like
a
sidebar
on
the
handbook
pages,
and
we
could
even
recycle
that
design
for
documentation
pages.
If
we
thought
it
was
good,
but
I
just
got
stuck
with
not
as
a
developer.
A
Non-Designer
I'm,
like
I,
don't
know
what
it'll
look
like
I,
don't
know
how
to
build
it.
So
what
said
he
would
be
willing
to
take
a.
B
A
B
A
A
D
A
So
other
issues
were
having
with
design.
We
need
to
figure
out
some
way
to
incorporate,
incorporate
imagery
for
both
the
the
theme
in
layout
pages
and
I.
Think
we
even
have
some
designs
for
how
to
do
that
already.
There
are
some
trick,
your
tasks
on
how
we
get
a
project
to
identify
it
simmer,
imagery
and
I
think
there's
an
open
issue
about
adding
more
things
into
the
info
file,
so
that
the
theme
could
specify
more
than
one
image
same
with
layouts,
and
then
we
could
find
some
way
to
pull
those
in
from
github.
A
Did
backdrop
CM
esta
or
display
them
on
back
to
be
honest,
or
maybe
even
also
render
them
in
backdrop
itself,
when
you're
in
the
project
install
our
pages,
but
I
would
love
to
see
some
movement
on
that
and
I.
Don't
know
whether
that
needs
to
come
design
first
or
implementation
first,
because
both
things
are
kind
of
stuck
but
I.
Think
that
would
help
us
out
a
lot.
B
A
C
A
A
The
so
when
you're,
looking
at
installing,
like
modules
teens
early
outside
in
your
site,
you
don't
get
any
imagery
and
I
think
that's
fine
for
modules
cuz.
Most
of
the
time
you
don't
necessarily
need
a
screenshot,
but
for
themes,
it's
really
useful
to
see
what
they're
gonna
look
like
and
for
layouts
to
have
some
kind
of
visual
cue
of
like
what
the
layouts
doing
or
what
layouts
you
get
might
also
be
valuable.
I'm.
Just.
A
Might
have
a
screenshot,
but
they
were
not
currently
included
in
the
info
file
and
so
there's
an
open
issue.
That's
trying
to
talk
about
what
other
information
we
might
want
to
collect
in
the
info
file
to
be
able
to
activate
in
display
and
multiple
images
are
not
currently
supported
in
themes
and
we're
going
to
need
probably
multiple
images
in
layouts
anyway.
A
So
we
might
solve
that
problem
for
both
teams
and
Lance
at
the
same
time,
by
adding
some
kind
of
screenshots
in
information
into
the
info
file,
and
then
that
way
it
would
give
themes
the
ability
to
put
screenshots
or
if
they
wanted
same
thing
with
layouts,
and
we
can
pull
them
in
to
display
them
either
on
backdrop
CMS
to
Oregon
the
modules
and
themes
and
layouts
pages
or
on
backdrop
itself,
when
you're
on
the
Installer
it'll,
give
you
a
screenshot
of
the
thing
you're
about
to
install
so
I
think
so
I
go
ahead.
A
Oh
just
cuz,
I
think
there's
several
things.
We
need
to
figure
out.
We
need
to
figure
out
how
to
get
the
information
we
want.
We
need
to
figure
out
how
to
integrate
it
into
the
systems.
We
already
have,
and
then
we
need
to
figure
out
a
design
for
what
it's
going
to
look
like
once
we
get
it
there
and
Walter.
So.
C
A
C
A
It's
just
a
matter
of:
do
we
want
to
write
the
code
twice
or
not,
and
so
it's
the
reason
it's
not
written
now
is
because
it
was
assumed
it
would
change
and
it
hasn't
changed
well.
D
With
layouts
we
can
show
that
scream
like
the
icon,
yeah,
the
icon.
Then
you
have
the
issue
of
some
layouts
having
sub
layouts.
Their
packages
of
the
the
project
layout
would
be
would
include
more
layouts.
Does
that
make
sense?
So
it's
multiple,
not
just
one
and
I,
know
I
know
it
makes
sense
for
feelings,
as
you
said
more,
but
also
modules.
D
A
So
I
think
I
think
I
mean
you're
right
Mike.
We
could
build
support
for
the
thing
we
have
now,
but
it
won't
it
I
mean
we've
got
to
build
it
differently
for
module
seams
and
layouts,
or
we
could
solve
the
problem
and
build
it
the
same
way
in
the
future.
I
don't
know
what's
more
important,
like
maybe
it's
just
important
that
we
get
screenshots
and
for
themes,
yeah.
C
A
Yeah
trying
to
figure
out
how
to
handle
that
on
backdrop,
CMS
org
in
terms
of
the
find
pages
do
we
want
to
pull
in
that
information
into
fields?
So
it's
visit
visible
to
views
or
do
we
want
to
just
add
a
new
view,
hook,
that'll
point
to
the
remotely
hosted
images
that
are
on
github.
So,
just
like
some
decision-making
problems,
you
need
to
figure
out
how
to
actually
reference
those
files
and
display
them
and
probably
whatever
decision
we
make.
Their
would
also
need
to
be
true
for
how
we
ended
it.
A
On
a
backdrop,
the
Installer
page,
two
yeah,
alright
other
things
we
need
to
work
on
documentation
section,
is
really
close.
E
A
That
launched,
I
think,
is
blocked
on
figuring
out
how
to
put
a
link
in
the
menu
at
the
moment,
which
is
where
I
got
stuck
last
week.
I
think
we
can
add
a
link
into
the
menu
now,
but
we
don't
have
a
drawer
so
that,
even
if
you
clicked
on
it,
there
isn't
any
kind
of
drop
down
and
draw
a
rough
open
way
to
see
the
links
that
are
in
that
section,
so
I
don't
know
we
can
put
into
top
level.
A
If
we
need
to
it'll
be
great
if
we
could
figure
that
out
and
then
forum
section
is
next
on
the
list,
once
we
get
documentation
linked,
oh
I
didn't
mention
the
showcase
section
in
here
either
I
suppose
we
don't
need
to
design
for
anymore.
We
have
two
signs
for
the
showcase
landing.
What
does
need
to
still
be
implemented.
D
A
Design,
meaning
was
that
outreach
meeting.
I
met
with
jordan
from
fafsa
interactive
and
he
did
give
me
some
great
homework
to
do
about
figuring
now
how
we
want
backdrop
to
be
represented
in
different
places
and
if
I
can
finish
that
they
are
willing
to
take
over
the
setting
where
newsletters,
which
I
think
will
be
really
handy,
but
they
needed
to
have
some
information
to
figure
out
like
what
kind
of
voice
we
wanted
to
use
and
make
sure
that
it's
consistent
with
the
rest
of
our
branding.
A
But
I
think
they
also
had
other
advice
on
how
we
can
help
get
the
word
out
about
backdrop,
but
it
wasn't
design
related.
It
was
about
content
and
one
of
the
things
that
was
really
high
on
that
list
was
getting
the
case.
Studies
thing
going
and
so
I
think
we
should
continue
getting
that
done.
The
problem,
of
course,
is
that
we
don't
actually
have
content.
We
have
designs,
but
we
don't
have
any
case
studies
and
we
don't
know
like
I
put
a
couple
of
them.
A
I
didn't
write
the
words
well
and
so
I
think
getting
their
help
on.
That
will
also
be
good,
and
so
hopefully
we
can
get
some
kind
of
starter
content
up
and
then,
if
I
can
turn
that
over
to
Jordan
and
say
hey,
we
have
these
case
studies,
but
they're
not
compelling.
How
do
we
fix
that
he'll
be
able
to
say
like
well,
because
these?
A
This
is
the
kind
of
thing
you
need
to
say
in
a
case
study
and
that
will
hopefully
help
us
kind
of
three
architects
that
content
type
in
order
to
ask
the
right
questions
of
the
people
are
filling
it
out.
So
that's
kind
of
what
I'm
hoping
to
get
out
of
that
short
term.
D
Think
that
the
respective
them
thinking
drupal.org
asks
as
well,
where
people
I
don't
know
if
it's
a
specific
field,
but
people
list
the
modules
they
use
and
in
what
way,
it
would
be
a
good
idea
to
sort
of
like
list
for
four
sites
that
were
converted
from
v7
to
bunch
of
lists
the
modules
that
they
were
using
in
what
they
don't
need.
Now,
because
it's
in
court,
that's
a
nice
idea.
We
got
rid
of
these
days
in
this
because
now
it's
a
core
feature
entertaining.
A
So
we
had
a
bunch
of
of
fields
that
we
left
off
that
were
on
the
the
drupal
showcase
that
we
didn't
put
on
backdrop,
because
we
were
waiting
for
references,
but
I
feel
like
something
like
what
you
just
described,
probably
isn't
a
good
fit
for
references
anyway,
because
you
need
people
to
have
room
to
explain
why
they
did
things.
They
did
so.
Maybe
I'll
just
make
that
like
a
text
area-
and
we
can
ask
a
question
and
how
people
answer
it
and
how
whatever
way
is
relevant
for
their
project
and.
D
It's
good
to
be
truthful,
rather
than
saying
you
know,
excited
about.
You
know
we
don't
use.
We
might
also
tell
them
like
where
there
are
any
modules
that
you
were
using
and
functionality
that
you
lost
I,
don't
know,
because,
because
it's
good
to
convey
the
message
that
we
don't
want
to
trap
people
in
getting
in
the
backdrop
and
then
finding
a
surprise
that
our
module,
X
or
feature
X
doesn't
exist.
Yes,
something
like
that.
Okay,.
D
C
Theoretically,
theoretically,
anything
that
they
don't
have
like
you
know
they
can
pour
it
over
or
someone
else
can
help
them
port
it.
Over
so
I
mean
the
Showcase
is
supposed
to
be
sort
of
like
a
longer
term
thing.
It's
not
supposed
to
hopefully
be
constantly
changing
for
these
things,
so
it
seems
yeah.
A
A
Of
the
reason
why
it
was
because
modules
z
existed
for
backdrop
and
module,
X
existed
for
Drupal
and
that
might
have
part
of
their
decision
making
process
which
could
be
interesting,
but
I
do
think
it's
important
that
we
not
paint
the
picture.
That
backdrop
is
limited
because
Mike's
right,
like
there's,
no
reason
for
that
limit,
we
can
fix
it
eventually
it
just
maybe
wasn't
there
yet
when
that
person
needed
it.
A
Alright,
so
figuring
out
how
to
ask
that
question.
I'll,
look
at
how
it
was
asked
how
questions
are
asked
on
drupal.org
and
also
on
the
blue
drop,
which
is
a
site
that
was
created
in
order
to
generate
showcases
for
drupal
org
and
see.
If
there's
they've
got
a
different
way
of
asking
questions
that
might
generate
more
compelling
answers
from
people.
A
C
A
Hopefully,
you
and
Wes
can
make
some
progress
on
that
I'm
open
to
any
suggestions.
So,
okay.
C
A
Don't
have
like
a
auto-generated
one
but
I
we
can
sequel
sanitize
it
using
Drash
and
that's
what
I've
been
doing.
So
if
you
want
a
copy
of
database
to
work
with,
I
can
send
a
new
one.
Yeah.