►
From YouTube: Backdrop CMS Design check-in 2/5
Description
A check-in on remaining design tasks for Backdrop CMS.
A
Alright,
we
are
on
air,
is
Thursday,
februari,
5th
2015,
we're
here
today
to
talk
about
design
tasks
for
backdrop,
CMS
most
of
you
probably
already
know
backdrop:
CMS
is
a
content
management
system
specifically
geared
towards
small
medium-sized
businesses.
A
So,
thanks
for
working
on
right
now,
the
backdrop
CMS
org
flagship
website
is
being
ported
to
backdrop.
That's
something
I'm
gonna
work
on
today
and
donates
been
itching
to
work
on
that
too.
So
we
might
have
to
fight
over
who's
doing
what,
but,
as
I,
get
supported.
The
backdrop
will
also
need
to
take
the
current
theme.
A
That's
on
that
site,
import
it
to
backdrop
as
well
and
in
that
process
will
be
able
to
implement
the
last
feature
that
I
think
we
have
signs
whether
we
haven't
built
yet,
which
is
the
mobile
navigation,
so
we've
been
holding
off
on
that
until
it
got
moved
to
pack
job
that
is
in
our
near
future
and
other
things
we've
got
going
on.
The
API
site.
Nate
has
already
boarded
a
backdrop
which
is
great,
but
it's
currently
running
Bartik
theme.
A
So
the
question
is:
if
we
take
the
front-facing
site
for
API
for
the
non
apx
ight
and
put
it
on
the
API
site
is
going
to
be
better
than
we
have
now.
I
think
it
will
I
think
we
should
try
it
and
see
because
it
will
need
some
adapt
ding,
because
the
design
that
we
have
worked
for
worked
out
for
the
primary
site
is
going
to
need
a
little.
You
know
fussing,
it's
not
the
same
content,
it's
not
the
same
kind
of
stuff.
A
So
we'll
take
a
look
at
that
once
we
get
that
up,
Darius,
maybe
I'll,
throw
that
on
a
dev
site
and
send
you
a
link
to
it
just
to
have
you,
like
you
know,
look
at
you
like!
Oh
my
god,
it's
not
gonna
work,
then
we'll
know
it's
not
going
to
work,
but
it's
kindergarten.
A
That
would
be
a
good
direction
to
go
for
that
I
think
other
stuff,
we're
working
on
backdrop,
the
product
which
I
think
is
our
primary
focus
right
now
it's
out
our
website
is
good.
We've
got
to
move
that
over
obviously,
but
next
on
the
list
is
backdrop
of
product.
We
have
a
new
style
guide.
I
was
just
taking
a
look
at
it
right
now,
Jerry's
before
this
call
and
I
squeals
with
delight
good.
C
C
A
B
B
A
About
to
link
in
the
Hangout
to
but
yeah
this
is
our
github
style
guide.
I
didn't
look
so
much
better
in
the
form
elements.
Look
free,
oh
yeah,.
C
A
I
mean
so
what
we're
looking
at
for
timeline
here,
too,
is
once
we
get
done
with
this
style
guide.
We've
got
a
couple
of
people
who
are
ready
to
start
implementing
things
in
fact
Jeff,
but
we
have
some
technical
challenges
to
figure
out
how
to
do
that.
So
we've
got
two
current
approaches
and
I'm
not
sure.
We've
made
a
decision
yet
on
how
we're
going
to
do
it.
A
But
if
the
change
involves
markup
changes,
that's
much
harder
because
other
people
might
have
been
depending
on
the
markup-
that's
already
in
core
at
this
point,
so
those
changes
would
need
to
go
into
the
theme
itself.
So
we'll
need
to
be
kind
of
looking
at
each
element,
figuring
out
how
those
changes
should
be
made.
A
The
stuff
that
can
go
into
core
we
can
put
into
core,
but
I,
don't
think
that's
going
to
go
in
is
super
urgently
and
then
the
other
things
we're
trying
to
do
is
figure
out
for
the
stuff
that
can't
go
directly
before
the
stuff
that
has
to
go
or
in
this
system
or
where
it
came
from
originally
the
stuff
that
has
to
go
into
the
seven
theme.
A
We
need
to
make
a
decision
about
whether
we're
going
to
change
seven
or
whether
we're
going
to
introduce
a
new
admin
theme
that
contains
all
of
our
interaction
patterns
and
colors
and
shapes
and
whatever
we've
got
going
on
and
then
for
new
versions.
The
backdrop
we
can
change
the
default
themes,
then,
what
shifts
out
of
the
box
you
get
backdrops
admin
theme
turned
on,
but
for
all
people
that
are
currently
running
back
drop.
A
That
would
just
keep
seven
unless
they
want
to
change
that
theme
themselves
and
for
that
change,
that's
not
going
to
happen
until
May
fifteenth,
so
it
the
bigger
chunk
of
stuff
we're
working
on
either
way
whether
it's
pushed
into
seven
or
into
a
new
theme
that
probably
won't
go
out
till
May
fifteenth.
So
it's
just
a
matter
of
looking
at
deciding
what
needs
to
go
where
some
things
like
system
just
changes
we
might
be
able
to
make
earlier,
but
I,
don't
think
we're
in
a
super
hurry
anymore.
A
B
No
I
don't
have
anything.
I
I
mean
that
I
think
we
do
need
to
decide
exactly.
We
said
whether
or
not
we
want
to
modify
Stefan
and
just
make
it
be
the
theme
in
backdrop
or
if
we
want
to
hope
you
want
to
make
a
new
one.
There
there's
virtues
to
both
approaches:
I'm
kind
of
personal
and
leaning
towards
just
modifying
seven,
because
the
idea
of
maintaining
two
themes
for
all
the
one
x
release
doesn't
seem
very
appealing
to
me.
Yeah.
A
B
A
B
A
A
The
user
interface
problem
is
when
you're
on
the
themes,
page
there's
like
a
drop-down
list
and
if
it
says
something
like
seven
in
it,
you
have
no
idea
like
what
that
has
any
relation
to
like
what
is
this
job
down?
I,
don't
know
we
can.
We
can
also
say,
and
we've
studied
it
in
Drupal
7
and
it's
failed.
We
can
study
it
and
backdrop
with
like
or
in
test
studies
or
whatever
different
names
and
see
if
even
changing
the
name
helps
because
if
it
doesn't,
then
it
doesn't.
A
A
There's
only
one
admin
theme
out
of
the
box:
we
could
even
disable
that
element
until
someone
adds
an
admin
theme
and
then
you
wouldn't
be
confused
by
it.
It
wouldn't
even
be
there
to
distract
you.
What,
if
you're,
not
going
to
add
anything,
you
don't
eat
that
selector
gamer,
so
that
might
call
feasibility
problem
without
having
to
change
any
names
on
anything
yeah.
B
I've
mentioned
that
in
the
past
that
we
can
put
in
the
dot
info
file
whether
or
not
it's
an
admin
themer,
not
so
admin
eagles,
true
in
the
dot
info
file.
And
then,
if
it's
not
an
admin
theme
like
it's
ridiculous,
that
it
lets.
You
put
your
front
end
theme
as
an
admin
theme
when
most
of
the
time
that
doesn't
work
in
the
first.
B
A
A
Already
slightly
better
than
Drupal
7,
but
yeah,
ok,
so
there's
other
solution
to
this
problem.
The
don't
involve
changing
the
name
and
I
think
that's
a
good,
a
good
path
forward.
Then,
should
we
just
go
ahead
and
call
this
decision
and
say
when
we're
ready
to
make
the
changes,
some
of
them
will
go
into
core
and
someone
will
go
to
seven
and
we're
going
to
throw
out
the
idea
of
a
new
admin
theme
I.
B
Think
that
that
sounds
good
for
the
time
being
and
we
can
address
your
naming,
it
consistently
concerned
yeah
into
X
and
we
can
just
rename
the
theme
and
keep
the
same
appearance
if
I
mean,
and
we
can
do
another
update
if
we
want
to
at
that
point
but
but
yeah.
Even
if
we
keep
it,
we
can
just
rename
it
to
X
and
and
then
that'll
be
that
ok.
A
I
think
that
sounds
good
I
make
an
issue
to
go.
Update
that
github
issue
a.
A
A
B
B
A
Okay,
well,
we
will
solve
the
D
D
confused
admin
themes,
page
in
a
different
issue.
Okay,
I'll
make
an
end
up
for
that
too.
Well,
moving
on
so
many
issues:
okay,
alright,
so
other
things
were
working
on
and
a
new
front.
End
theme,
so
drupal
had
both
garland
and
bartok
as
front
end
theme
options
in
Drupal
7,
neither
of
which
were
super
super
useful
in
the
real
war
world,
drupal
8
they
removed
Garland
and
did
not
add
another
front,
end
theme,
and
when
we've
worked,
we
inherited
that
same
situation.
A
So
we
currently
have
one
a
front
end
theme
in
backdrop
which
is
Bartok
and
we
have
no
alternatives
and
though
bartek
is
pretty
useful
in
terms
of
showing
like
integration
with
color
module
and
how
to
override
thanks
a
bunch
of
other
stuff
going
on
I,
don't
feel
like
right
now.
You
could
actually
use
Bartek
on
their
site
when
they
ship
it.
They
look
at
it
and
go
I
need
a
new
FEMEN.
They
put
something
else
on.
I
would
love
if
we
could
have
some
kind
of
front.
A
A
Something
which
is
a
bootstrap
based
front
end
theme.
It
was
I,
think
one
of
our
first
teams
both
boarded
the
maybe
d
first
theme
that
was
boarded
to
backdrop.
It
looks
pretty
good,
it
is
generic,
it
is
something
I
think
anyone
could
use
and
I
would
love
to
see
something
like
that
going
to
pour,
and
we
are
process
for
getting
a
new
friend
and
theme
into
core,
I
think,
is
to
build
it
and
contribute
have
a
little
bunch.
People
test
it
and
then
kind
of
nominate.
One
of
these
kinship
themes
for
inclusion
in
core.
A
I
would
love
if
we
could
get
more
than
one
option
to
decide
on,
so
that
we
could
kind
of
compare
pros
and
cons
of
different
themes.
I
think
we
have
a
rad
new
volunteer
to
do
a
bunch
of
front
and
work
for
backdrop,
and
we've
asked
them
to
create
a
contributing
port
anything
or
create
something
new
or
whatever.
Just
for
comparison.
I
just
want
to
throw
this
out
so
anyone
else
who
is
a
friend
designer
senior
developer
whatever.
A
If
you
want
to
create
a
front
end
theme
for
backdrop,
inking
trip,
we
are
looking
for
new
friend
and
things
to
put
it
to
park,
just
something
that
someone
could
actually
ship
a
site
with.
So
if
you
had
something
like
that
that
you've
been
using
a
Drupal
7
or
you
know
a
base
theme
that
companies
use
or
whatever
it
is,
we
are
on
the
lookout
for
something
like
that.
A
A
Ok,
so
we
also
have
a
special
tag
on
in
the
github
queue
for
all
design
related
issues,
and
this
is
the
kind
of
thing
where
sometimes
someone
will
say
you
know
I
really
wish
that
this
thing
looked
different
and
then
you
know
all
the
people
in
the
queue
are
like
I
agree,
but
none
of
us
have
any
design
skills.
So
we're
not
going
to
be
right
now.
Making
a
mock
ups
were
thinking
about
better
ways
to
solve
that
problem.
A
So
we
have
this
tag
and
audience
design,
and
then
we
can
hopefully
get
some
designer
user
interface
people
to
weigh
in
on
the
issue
saying
whether
we
should
do
something
about
it
or
not,
and
if
we
showed
them,
we
need
a
new
design
piece
for
it,
and
so
we've
kind
of
a
one
will
look
up.
Yes,
he
really
puts
that
in
here.
A
There's
I
think
we
have
issues
right
now,
I,
don't
think
I
went
back
through
the
list
of
all
of
our
existing
issues
and
typed
anything
that
had
a
design
requirement
with
needs
designed,
but
anytime
anything
new
goes
up.
I,
usually
try
and
tag
it,
and
if
anyone's
working
on
the
issue
queue
and
finds
anything
that
looks
like
it
needs
design,
go
ahead
and
add
the
text.
It
certainly
could
be
missing
or
if
you
add
me
wishes,
add
that
too
and
I
think
this
is
something
we
can
kind
of
keep
an
eye
on
as
well.
A
There's
some
doozies
in
here
to
like
we
did
want
to
split
the
edit
form
for
editing
content
into
two
columns,
and
that
was
the
kind
of
thing
that
we're
like.
Oh
that's,
gonna
be
really
hard.
We'll
postpone
that
and
do
that
later,
that's
gonna
need
some
thought,
a
same
thing
for
the
cut
you
I
for
building
layouts
bullion
said
he
was
gonna.
Work
on
I
think
he's
gonna
be
here
this
week.
Is
it
this
tonight
Chelsea
yeah
begin.
A
So
next
week
we're
gonna
get
to
talk
to
him
in
person
and
we'll
see
how
much
work
he's
done
on
interface
for
that,
but
that
might
be
on.
You
know,
he's
busy
and
not
working
on
it.
That
would
be
something
that
I
would
like
to
get
sorted
out
sooner
rather
than
later
we're
doing.
A
lot
of
promotion
on
how
awesome
layouts
is
I
would
like
to
be
more
awesome
before
everyone
reads
the
articles
and
gifts.
It
takes
a
first
bin.
A
So
that's
something
that
we
could
definitely
use
some
help
on
there
too,
and
if
either
of
you
guys
see
anything
here
that
you're,
like
oh
I,
can
fix
that.
Let
let
let
us
know,
let's
see,
lost
my
agenda.
A
Okay,
so
it's
similar
to
the
design
tag
that
we
have
on
the
github
key.
We
also
have
a
way
to
identify
issues,
they're
specifically
related
to
user
experience
and
rather
than
using
attack,
we're
just
prefixing
the
title
with
the
square
brackets
in
the
letters
UX
in
it,
so
that
anyone
who
has
any
problems
with
usability
can
create
an
issue
type
with
you,
ax
and
we'll
try
and
figure
out
the
right
way
to
all
that
that
may
involve
redesigning
something
that
may
not
may
just
be
at
some
help.
A
Texture,
you
know,
make
the
thing
behave
in
a
different
way
at
a
feature
or
whatever
it's
all
the
issue,
but
that's
also
on
our
list
here,
because
it
made
factor
in
and
then
also
we
have
this
great
set
of
human
interface
guidelines,
which
we
started
on
a
while
ago,
which
I
think
is
is
something
that
would
be
good
for
us
to
get
nailed
down.
I
know
we
didn't
get
it
done
before.
A
One
point
o
came
out
and
I'm
not
sure
all
of
the
interfaces
in
core
match
our
guidelines,
but
we
were
trying
to
kind
of
document
the
tools
that
we
have
in
fact
refer
people
interacting
for
software
like.
When
do
you
use
a
vertical
tab?
When
do
you
use
a
you
know,
button
or
when
you
use
a
drop
button
and
I
think
that
it
will
be
good
for
us
to
kind
of
established
what
those
interfaces
are
and
when
they
should
be
used
so
that
contribs,
a
oh,
you
know,
I
need
to
build
an
interface.
A
What
tools
should
I
use
in
one
of
the
rules
that
I
follow
for
that
in
Drupal?
It's
kind
of
completely
arbitrary
when
someone
decides
to
use
a
vertical
tab
even
in
core,
there
are
some
places
that
use
them
in
the
correct
way.
In
some
places
they
use
them
in
a
way
that
was
not
intended
for
them
to
be
used,
and
so
it
makes
you
really
hard
for
contribute
a
killer
figure
out.
What
to
follow.
I
think
we
have
a
great
start
on
these
human
interface
guidelines.
A
A
I'm
gonna
paste
a
link
to
this
too,
but
if
anyone
is
super
interested
in
a
computer
human
interaction
and
wants
to
help
us
go
through
and
fill
this
out
and
figure
it
out
what
what
our
guidelines
should
be,
I
think
that
would
be
really
great
for
for
a
backdrop
before
we
could
get
to
220
and
what
it
really
starts
to
be
super
important
about
usability
and
and
when
we
start
to
target
these
people
who
are
used
to
having
a
super
slick
user
interface.
A
B
A
good
example
of
something
that
we've
never
really
quite
figured
out
is
like
a
user
interface
element
that
we
have
that
gets
abused
and
are
used
and
used
all
the
time.
Its
vertical
tabs.
For
example,
like
we
even
have
an
issue
for
you,
know,
applied
vertical
tabs
to
all
entity
types.
But
it's
it's
rough,
because
we
don't
actually
know
that
vertical
tabs
are
actually
appropriate
for
all
those
locations
and
that's
what
the
human
interface
guidelines
is
intended
to
do
is
to
say
you
know,
use
element
X
in
situation.
Why?
A
I
think
we've
talked
about
this
a
couple
of
times
too.
We
have
a
similar
document
for
raksha
backdrop.
Brand
guidelines
on
drupal.org
has
a
super
extensive
page
that
talks
about
how
logo
needs
to
be
positioned
and
how
much
space
should
be
around
it
and
what
colors
should
be
used
in
our
press.
A
Kit
page
is
kind
of
a
super
lightweight
version
of
that
that
talks
about
how
backdrop
got
its
name,
how
what
its
logo
looks
like
what
its
dragon
looks
like
and
that's
kind
of
it
I,
don't
know
if
we
need
anything
more
extensive
than
that.
A
I
originally
thought
that
we
wanted
a
page
for
electrical
orcs,
but
the
more
I
look
at
our
press
kit
I
feel,
like
that's
probably
fine,
I
think
it
would
be
good
to
have
our
brand
guidelines,
in
particular,
like
our
color
palette,
published
somewhere,
where
people
could
find
it
more
easily
because
I've
had
a
couple
of
people
be
like
hey
I,
remember
that
you
mentioned
the
fact:
I've
had
a
color
palette,
but
I
can't
find
any
email
on
the
document.
I,
don't
think.
A
That's
necessarily
the
right
place
for
that
is
on
the
press,
kit
page,
because
that's
not
something
that
the
press
needs
to
know.
It's
only
a
resource
that
kind
of
our
internal
team
needs
to
use
anyone
who's,
making
stickers
or
t-shirts.
Or
you
know,
web
pages
or
whatever
it
needs
to
have
those
colors,
but
I,
don't
know
what
the
right
place
is
for
them.
So
I
don't
know
if
anyone
has
any
ideas
about
that.
C
I
mean
I
think,
like
you
said
it's
a
full
out
of
the
scope
of
what
the
frets
would
need,
but
there
is
a
significant
amount
of
overlap
between
what
they
want
and
what
you
know
designer
or
a
theme
or
somebody
would
also
need
access
to
and
I
think
I,
really
like
how
simple
the
scrolling
version
of
it
is.
You
know
it's
just
all
right.
There
yeah.
C
A
So
we
could,
we
could
add,
like
another
section,
you
were
thinking
maybe
to
the
bottom
of
the
page.
That's
like
hey
for
mortar
for
building
stuff,
here's,
here's
a
couple
of
other
resources
and
just
throw
it
up
there.
Yeah.
C
A
A
an
official
place
because
maybe
stuff
will
come
like
come
up
like
this
more
often
where
we
need
some
way
to
distribute
things
to
people.
Maybe
we
just
need,
like
an
official
backdrop,
stuff
place
so
like
I
know,
keeping
design
files
and
github
is
not
super
handy
right.
Now.
All
of
our
backdrop,
stuff
seems
to
live
on
github,
but
don't
like
like,
like
these
image
files
and
the
press
kit,
we've
posted
on
this
page
because
it
seems
to
be
a
better
fit
for
it,
but
maybe
we
need
a
different
solution.
A
A
Yeah
right
now,
I
just
every
time,
I
see
this
color
graphic
in
the
agenda.
I'm
like
I
wish.
We
had
a
better
place
to
keep
this
sure
when
everyone's,
like
I,
think
I
saw
the
color
somewhere
where
there
I'm
like
it
was
in
the
agenda.
That's
the
only
voice,
you've
seen
it.
Okay,
well
we'll
figure
out
whether
we
need
a
more
official
brand
guidelines,
automatic
and
I.
Think
we
don't
more
comprehensive.
We
could
add
something
we
wanted
to
or
we
could
just
throw
resources
up
in
some
folder
somewhere
point
at
them.
C
Wide
as
possible
is
good
too,
because
some
of
those
get
really
just
like
accepted
like
we
need
10
pixels
around
the
logo
and
this
and
that,
like
no
one,
ever
really
reads
that
or
follows
it
anyway.
That's
pretty
obvious,
like
don't
make
our
logo.
If
you
do
you
don't
know
what
you're
doing
any
one,
you
probably
wouldn't
have
read
it.
B
A
And
I
think
I've
got
a
link
in
here
for
our
official
font,
but
I.
Don't
think
this
is
our
official
font
anymore.
This
still
says,
source
sans
pro
is
that
right,
Darius
at.
A
A
It's
a
collection
of
layouts,
it's
a
collection
of
panel,
like
other
panels,
modules
like
panel
Iser
and
feel
the
bowl
content
pains
and
a
bunch
of
other
stuff
that
fits
together
into
a
really
great
package
in
backdrop.
We
have
panels
everywhere
panels.
We
don't
have
panel
Iser,
which
creates
a
layout
for
each
piece
of
content
on
your
site.
We
don't
have
feel
double
panel
pains,
but
we
are
planning
on
making
blocks,
feel
the
bowl
which
would
be
equivalent,
but
that
won't
detail
back
up
to
and
then
a
whole
bunch
of
other
stuff.
A
Like
panel
analyzer,
we
don't
have
a
plan
for
are
in
back
Jeff,
so
that's
something
that
could
be
ported
probably,
but
it
would
need
to
be
ported
to
back
shops
version
of
layouts,
obviously
not
to
work
with
the
panels
module
as
it
doesn't
wrinkle
7.
So
philosophically,
there's
a
bigger
issue
here,
if,
like
we've,
moved
the
panels
API
and
it's
now
called
layouts,
but
how
how
all
the
pieces
fit
together
and
backdrop
is
going
to
work
a
little
bit
different
than
it
did
in
Drupal.
So
I
don't
know
Nathan
answering
some
of
these
questions.
B
Yeah
well,
I
think
you
basically
covered
it.
I
mean
the
concept
of
monopoly
is
a
little
bit
more
than
just
then
just
laying
stuff
out
as
Jen
and
I
I've
talked
about
this
past
week.
That
it
includes
monopoly
basically,
is
a
it's
a
distribution
that
is
built
around
all
of
the
functionality
of
panels,
but
panels
is
like
kind
of
the
like
the
the
most
basic
concept
of
panoply.
It's
the
level
of
integration,
that's
put
into
it.
That
makes
monopoly
something
different
than
panels
or
penalize
her
by
itself,
and
so
layouts
itself
replaces
panels.
B
So
you
don't
need
panels,
that's
very
certain,
but
all
the
concepts
that
panoply
integrated
into
panels.
We
basically
don't
have
any
equivalent
of
at
this
point,
but
if
they
all
could
be
written
for
vac
drop,
but
the
Albany
they'll
need
to
be
written
against
layouts
instead
of
panels.
So
the
the
possibility
is
there,
but
it
would
take
a
lot
of
work
still
to
kind
of
make
all
of
those
pieces
work
with
backdrop.
A
And
so
I
think
like
in
terms
of
how
all
the
pieces
fit.
We've
got
a
couple
of
different
options
into
how
to
pursue
these
things
to
like
in
Drupal,
there
were
people
that
made
blocks
into
feel
double
entities.
There's
this
module
called
beam
and
then
there's
also
people
who
made
content
paints
into
feel
double
entities
which
we
feel
double
panels
pains
or
feel
double
content
pains
or
something
like
that.
Those
two
solutions
are
the
same:
one
of
them
just
goes
into
the
blocks
system
and
one
goes
into
the
panel
system
and
a
backdrop.
A
A
So
if
we
can
get
a
beam
for
backdrop,
one
that
might
be
the
thing
that
goes
in
to
backdrop
to
that
would
solve
both
those
problems
in
into
court.
If
we
just
if
we
liked
the
way
that
solution
happened
and
I
for
a
panel
Iser
that
I,
don't
think
I
mean
that
was
kind
of
I
guess
flow
into
some
version
of
context.
I,
don't
I,
don't
know
how
you
would
do
that
without
them
panels.
I
guess
it
would
probably
be
context.
A
The
pee
analyzer
is
something
that
would
also
could
be
ported
directly
to
backdrop.
The
API
under
under
the
hood
for
panels
is
very,
very
similar
to
the
API
under
the
hood
for
layouts.
It
just
needs
to
be
rewritten
in
an
object,
throwing
an
infection.
I
think
it's
only
different
the
same
way
that
we
port
a
layup.
That's
the
same
way.
A
We
poor
plugins
other
plugins,
like
access
rules
and
panel
Iser,
is
a
bunch
of
stuff
like
that,
could
be
ported
in
the
same
way
to
make
it
work
for
for
backdrop,
so
there
is
kind
of
a
very
straightforward
path
to
get
pee
analyzer
into
back
job.
If
you
wanted
to
to
go
that
route
and-
and
I
think
that
would
solve
half
half
the
problems
and
then
the
other
things
that
panoply
provides,
I
think
the
thing
that's
most
valuable
thing
is
most
attractive
to
me.
A
Aren't
that
great
set
of
responsive
layouts
that
it
comes
with
out
of
blocks
and
hopefully
porting
those
will
be
super
quick
and
easy,
but
again
layouts
in
panels
for
plugins
for
panels.
Layouts
and
back
jeff
are
a
top-level
concept
like
a
modular
theme.
So
probably
what
we
would
like
to
do
is
take
all
the
layouts
from
panel
Iser
pork
them
into
like
a
an
individual
whole
bunch
of
individual
layout.
So
you
can
pick
choose
what
you
want,
or
maybe
even
a
module
that
provides
a
suite
of
these
layouts.
A
A
Think
that's
the
kind
of
thing
where
you
know
the
more
layouts
we
have
in
core
the
more
useful
backdrop
with
comes
out
box,
but
it's
a
different
kind
of
a
porch
so
rather
than
porting
it
from
a
plugin
for
layouts
report
it
to
a
completely
top-level
concept,
so
I
think
everything
that
exists
in
finale
and
we've
only
covered
a
couple
of
those
things.
But
everything
that
exists
now
can
be
moved
into
backdrop.
A
If
you
wanted
to
create
a
very
similar
thing,
like
kenapa
lee
in
backdrop,
they
would
just
all
need
to
be
thought
about
a
little
differently
in
how
you
get
them
moved
over.
So
hope
that
answers
that
question
and
that's
actually
a
good
thing
to
bring
up
too,
because
we've
been
talking
about
it.
A
lot
is
something
I,
think
a
lot
of
people
who
are
using
phenomenally
now
or
wondering
like
what
are
their
options
for
the
future,
because
Drupal
8
doesn't
have
a
panels
yet
I'm,
not
sure
how
much
progress
is
happening
in
that
direction.
A
So
they're
like
well
there's
kind
of
almost
a
panels
and
backdrops.
So
what
is
the
path
there?
Look
like
so
yeah?
That's
kind
of
I
think
we're
ready
all
right.
Are
there
anything
any
other
items
we
should
discuss?
Are
there
any
missa?
I
gets
a
bigger
question.
Are
there
any
other
design
tasks
that
we
should
talk
about
in
this
meeting?
It
feels
like
we're
getting
a
lot
of
stuff
done,
which
is
good,
but
also
that
our
list
is
getting
short,
so
no
no
need.
If
there's
anything,
that's
bothering
you
we
need
designed
no.
B
C
C
A
Alright,
well
thanks
guys
for
coming
today
meeting
we
will
be
back
online
in
half
an
hour
to
talk
about
development
tasks
funny
one
sooner
than
that.
Otherwise,
I
will
see
you
and
I
are
see
wat.