►
From YouTube: Backdrop design call 4/28 (reached a decision on how to the bootstrap grid system for layouts!)
Description
Today’s design agenda: http://bit.ly/1qsrRu3
A
Going
live
all
right,
we
are
an
artist,
Thursday,
April,
twenty-eighth,
a
happy
backdrop
Thursday
everyone
today
we're
starting
off
with
a
design
meeting
where
we're
going
to
review
tasks
that
need
designer
focus
for
backdrop,
CMS,
starting
with
our
website
backdrop
CMS
org.
We
are
currently
working
on
a
new
showcase
section
of
the
site
where
people
can
post
websites
that
they've
built
with
backdrop
CMS
and
credit
themselves
their
companies.
Anyone
who
has
contributed
to
the
Vectra
project
long
way.
A
We
should
start
thinking
about
a
design
for
the
showcase
section
of
the
site
there,
a
couple
of
links
to
example,
sites
that
do
showcases
like
WordPress
and
Drupal,
and.
A
And
we
can
use
those
as
examples
if
we
want
I
think
the
biggest
challenge
was
trying
to
find
a
way
to
do.
A
showcase
is
to
figure
out
how
to
show
mobile
versions
of
screens,
which
are
like
super
long
and
skinny
versus
desktop
versions,
which
are
super
wide
and
fat
in
some
kind
of
a
carousel
terrace
you've
probably
run
into
this
before,
but
that's
the
thing
that
like
makes
my
brain
hurt
in
terms
of
trying
to
figure
out
how
to
make
it
look
pretty.
Also
that's
next
on
our
list.
A
Ok
were
some
kind
of
care,
so
said
the
VRC
word
all
right
so
other
than
that
we
have
two
other
pages
that
are
needing
design
on
the
layouts,
find
layouts,
page
and
I.
Think
we
currently
have
a
design
for
the
fine
steam
page
we
haven't
implemented.
We
need
to
do
that
and
then
we
can
kind
of
pull
from
the
defined
a
theme
page
and
the
find
a
module
page
and
see
if
they're
elements
that
would
work
for
a
find
layouts
page,
but
that's
kind
of
where
we're
at
right
now
also
layout
project
pages.
A
We
have
designs
for
theme,
project
pages
and
module
project
pages,
the
same
kind
of
thing.
We
just
need
to
kind
of
figure
out
what
we
want
to
put
blair
and
put
it
together.
I
apologize
for
the
design
meeting,
information,
not
being
twitted
I,
don't
know
why
I
didn't
go
out
usually
way,
auto
scheduled
tweets,
but
it
could
have
been
that
was
over
overlooked
on
the
scheduling
or
it
could
have
also
been
tweeted
from
the
wrong
account.
Sometimes
I
get
that
wrong.
A
So
if
you
guys
were
hoping
to
find
it
on
Twitter-
and
you
didn't
it's
probably
my
fault
than
I'm
sake
anyway,
I'm
glad
you
guys
who
are
here
actually
game,
okay,
so
the
designs
we
currently
need
for
backdrop
semester
or
the
showcase
section,
the
final
layout
page
and
the
layout
project
page.
Although
layouts
and
lance
projects
can
be
derived
from
modules,
entities,
design
review-
and
this
is
probably
something
we
could
get
input
from
anyone
on.
A
So
this
we
need
the
news
section,
which
is
it
/
news
and
has
a
blog
listing
in
the
left-hand
column,
has
videos
and
tweets
in
the
right
hand,
column
and
a
list
of
events?
Just
kind
of
making
sure
that
we're
not
doing
anything
on
those
pages
that
go
against
the
aesthetic
of
the
rest
of
the
site
or,
if
there's
anything
else
that
could
be
improved.
We
could
use
your
review
there.
Also
with
the
news
page
itself.
A
It's
just
kind
of
a
list
right
now
that
could
be
dressed
up
a
little
bit
or
add
to
sidebar
whatever.
So,
if
anyone
has
any
inspiration
for
that
page,
that
could
be
great
and
then
surface
provider
listing
which
we
added
last
week
currently
just
lists.
Anyone
who
wants
to
provide
backdrop
services.
We
are
going
to
be
adding
filters
on
there.
A
So
what
I
thought
I
would
do
is
hook
that
up
to
this
filters
for
geographic
location
in
area
of
expertise,
so
that
if
you're
looking
for
a
company-
and
then
there
also
happens
to
be
a
person,
that's
an
expert
and
you
can't
find
a
company
you've
got
kind
of
another
resource
there
to
you
might
consider
a
contractor
instead,
but
I
think
over
time.
We
might
also
need
to
add
a
contractor's
page
that
allows
you
to
search
specifically
for
a
contractor.
A
So
it's
not
just
kind
of
mixed
in
with
the
company
listing,
but
we
can
wait
until
that
need
arrives
before
we
need
to
build
that
page,
so
just
fun
for
thinking
thinking
about
for
the
future.
So
that's
where
we
are
with
backdrop
CMS
to
org
I.
Think
we've
made
a
bunch
of
great
progress
on
it
recently
with
Sun
in
a
news
letter
last
week,
kind
of
telling
people
about
what's
going
on
there
and
after
that
newsletter
we
had
a
bunch
of
new
people
sign
up.
A
So
that's
a
good
sign
and
I
think
we
should
continue
focusing
on
vector
semester
org,
as
well
as
being
a
place
where
our
community
can
kind
of
come
together
and
get
access
to
the
things
that
they
need.
Next,
on
the
design
agenda
is
backdrop
it's
for
backdrop,
marketing
and
there's
only
one
new
thing
on
this
list
since
last
week,
and
that
is
that
me
came
up
with
this
great
idea.
A
We
could
have
some
information
about
backdrop,
maybe
on
the
back
of
the
card
or
maybe
on
the
front,
depending
on
how
the
design
works,
and
so,
if
someone
PMC
talking
to
somebody
else
about
backdrop,
lingo,
here's
our
website
check
this
out
and
if
the
card
says
something
about
what
backdrop
is
then,
when
the
person
who
receives
it
looks
at
it
later,
they'll
be
like
oh
yeah.
This
is
that
nonprofit
CMS
or
whatever
it
is
that
we
put
on
the
card,
and
that
might
be
really
useful
too.
A
So
we
could
definitely
use
help
in
the
design
area
with
a
business
card.
If
somebody
wants
to
take
a
step
that
I
create
an
issue
in
the
backdrop
CMS
or
q,
it's
number
2
28.
It
has
like
I
know
like
information.
We
might
want
on
the
cart
other
things.
We
need
new
stickers,
specifically
for
apple
laptops,
to
do
something
cute
with
the
Dragon
and
Apple.
So
if
somebody
wants
to
work
on
that,
it's
kind
of
a
good
fun
task,
a
low
low
risk
high
reward.
A
Perhaps
then
we
also
still
need
background
images
for
twitter,
facebook,
social
media,
I
kind
of
think.
So
if
somebody
wants
to
help
us,
what
kind
of
branding
is
that
it
could
be
a
fun
task
as
well,
if
you're,
pretty
cool,
again
I
stood
in
branding,
you
can
check
out
the
tag.
In
the
backdrop,
CMS
org
queue
for
marketing,
there's
also
a
tag
in
that
queue
for
design.
They'll
have
stuff
like
the
business
cards
and
the
stickers
come
on
check
that
and
then
next
on
list
most
exciting
is
back
drop.
A
One
point
for
our
new
release,
which
is
scheduled
for
May
fifteenth,
which
is
just
coming
up
here
in
two
weeks,
a
little
more
than
two
weeks
in
a
highest
priority
for
the
next
release,
really
to
design
our
a
new
set
of
four
end
layouts
and
a
new
front.
End
theme,
which
I
think
we
have
updates
on
both
this
week
and
I.
A
We're
putting
in
a
subset
of
the
original
ads
we
wanted
and
we
have
kind
of
a
good
direction
based
on
a
lot
of
the
code
that
Wes
had
worked
worked
on
in
his
new
friend
and
theme,
and
now
maybe
he's
trying
to
put
it
together
into
a
fix
for
layout.
So
I
don't
know
either.
One
of
you
wants
to
update
on
that.
B
B
Well,
I
guess.
Maybe
last
night
today
I
went
ahead
and
updated
the
gin
and
diplomat
PR,
which
contains
like
radix
layouts
from
bootstrap
3,
possibly,
and
then
I
updated
them
to
the
bootstrap
for
grid,
which
now
relies
on
flexbox
forward
the
page
layout,
and
then
I
put
in
a
bunch
of
semantic
stuff
and
accessibility
stuff
in
there.
Just
so
would
be
you
know
good
for
that
market
going
forward.
B
B
A
Okay,
so
for
the
changes
that
you
made
to
the
bootstrap
stuff,
were
you
pulling
those
from
wes's
changes?
Are
those
the
same
or
is
this
something
different
because
I
know
Wes,
you
made
some
changes
to
a
bootstrap
for
as
well,
and
we
should
make
sure
that
they're
the
that
we're
on
the
right
track
there,
and
we
should
also
made
me
figure
out
how
like
how
to
maintain
those
going
forward,
because
good
start
for
is
still
in
alpha.
A
If
we're
going
to
be
making
any
changes
to
that,
it's
I,
don't
even
know,
maybe
it'll
be
better
to
put
it
in
like
a
separate
CSS
file
or
on
some
way
that
we
can
continue
to
merge
in
its
are
far
as
it
develops.
I.
B
Guess
I'll
quickly
go
first
I
just
took
these
sass
from
the
bootstrap
site
and
I
compiled
it
to
become
the
good,
because
it's
currently
an
alpha
in
which
they
don't.
You
know
you
can't
get
the
CSS
source
code
for
the
flexbox,
quid
or
and
I
think
you
know
the
only
CDN
link
is
a
min
ified
alpha,
so
you're
not
really
going
to
get
much
with
the
grid.
There
yeah.
C
C
Jen
gave
me
some
feedback,
I
prefaced
everything
in
bootstrap
with
l
dash,
and
so
my
thinking
on.
That
is
that
if
we
have
classes
that
shouldn't
be
extended-
or
you
know
shouldn't
be
like
touched
other
than
using
them
in
markup,
it'd
be
nice
if
they
were
easy
to
spot
and
if
they
all
had.
You
know
one
or
two
things
that
kind
of
held
them
together
so
L.
It
probably
isn't
a
good
example,
because
I
I
think
it
is
appropriate
to
extend
else
I
bar,
for
example,
but
no
one
should
be
extending
you
know,
call
large.
C
You
know
three,
which
is
like
saying:
I
want
this
to
be
three
columns
on
large.
No
one,
no,
don't
touch
that,
but
leave
it
alone
kind
of
thing
and
then
same
but
same
thing
with
like
clear
fix
or
element
and
visible.
These
kinds
of
things
I
think
it'd,
be
nice
long-term,
not
not
1.4,
necessarily
long-term,
if
they
were
easy
to
spot
so
that
it
would
just
I
think
it
could
reduce
errors
and
and
kind
of
make
it
easier
to
get
started.
C
A
You
can
target
them
if
you
want
or
not
and
and
you'll
know,
when
you
see
that
you
shouldn't
be
defining
layout
styles,
like
you,
shouldn't,
be
like
floating
this
right
because
that's
responsibly
the
live.
But
if
you
wanted
to
add
like
a
background
color
to
your
sidebar,
you
can
definitely
do
that,
but
for
the
bootstrap
classes.
A
They
know
what
they're
called
and
if
we
start
changing
the
name
so
that
you
drop
in
a
you
know,
call
three
wide
and
it
doesn't
work
because
you
forgot
the
l
dash
that's
going
to
be
kind
of
frustrating
for
new
people,
and
we
should
keep
the
classes
that
people
usually
is
with
bootstrap
the
same
if
we're
going
to
be
using
bootstrap
and
backdrop
or
we
kind
of
lose
the
advantage
of
using
the
traffic
backdrop,
we
kind
of
have
our
own
non
grid
system
now
in
core
and
I.
A
D
I
want
to
back
that
up
to
and
that
as
far
as
learnability
goes
like,
whenever
you
tell
somebody
it's
like,
oh,
we
use
something
that
pre-existed
they're
all
like
yeah,
that's
great
you're
like
well,
except
we
changed
it
a
little
bit
and
then
that's
always
like
a
major
like
WTF
for
person
coming
in
because
they're
like
I
that
it's
using
this,
but
it's
like
well,
it
is
except
that
we
changed
it
and
then
then
it's
not
really
the
same
thing
anymore.
Yeah.
C
A
Thinking
about
about
that
I
think
it'll
also
help
us
inform
what
we
need
to
do
in
the
future.
I
totally
agree
that
question
poll
is
dumb
if
you
have
flexbox,
but
it
would
be
weird
if
we
implemented
a
solution
that
then
everyone
in
backdrop
like
learned
how
to
deal
with,
and
then
we
had
to
pull
it
out
and
put
in
bootstrap
for
solution
later
so
I
don't
know
if
that's
something
we
should
put
in
now
or
not
I'm
kind
of
on
the
fence
about
it.
So
and
one
thing
I.
A
I
mean,
I
think,
that
the
main
benefit
of
using
bootstrap
is
invictus.
Bootstrap
is
the
best
grade
system.
It's
because
people
know
it,
but
that
said,
like
the
more
we
diverge
from
what
bootstrap
is
actually
doing.
As
far
as
a
good
system,
the
last
people
are
gonna
know
how
it
works.
You
know
I'm
I,
don't
know,
I
mean
I
feel
like
if
we
is,
if
we
make
it
do
the
same
thing
somehow,
then
that's
fine,
but
it
would
just
be
much
easier
if
it
just
did
what
they
expected
it
to
do.
Okay,.
C
C
My
thought
was
that,
if
I,
if
I,
do
a
feature
detection
and
find
that
the
browser
doesn't
support,
flexbox
I
just
load
up
the
float
grids
system
lower
in
the
Cascade.
So
it
overrides
everything,
so
that
would
be
graceful
degradation
because
that
it's
a
it's
a
very
small
minority
of
people
that
won't
support
flexbox,
but
it's
there.
But
that
means
that
order
wouldn't
work
and
I
feel
ok
with
that.
It
just
means
that
for
some
people
the
sidebar
might
not
be
on
the
right
side.
C
A
I
mean
I
feel
like
if,
if,
if
we
don't
include
the
order
stuff
initially,
then
whoever
it
is,
that
builds
their
website
if
they
want
to
use
order,
they're
gonna
have
to
add
order
and
then
they're
going
to
have
to
decide
what
happens
for
IE
and
and
it
kind
of
says
it
pushes
the
responsibility
off
of
us
for
making
work
for
everyone
and
onto
the
people
who
choose
to
use
order.
Whereas
if
we
limit
order,
then
we
need
to
solve
the
problem
for
everyone.
Yeah.
A
C
C
A
D
Yeah
that
tiny
little
bit
of
what
is
it.
We
took
something
out
of
moderniser
like
the
one-liner
to
do
to
detect.
C
A
C
C
What
if
we
made
another
like
we
on
the
only
did
the
I
think
one
dot
too.
We
had
all
those
like
theming
things
that
are
all
kind
of
codependent.
We
made
like
a
special
dev
branch.
What
if
we
did
that
and
then
I
can
start
putting
basis
in
core
instead
of
having
it
be
this
contribs
in
and
then
any
and
I
can
function
off
of
the
same
stuff.
C
A
It
so
this
Asus
thing
is
kind
of
a
separate
issue,
I
think
than
the
layouts
thing.
We
should
talk
about
that
too,
but
I
think
what
we
need
to
do
is
get
the
bootstrap
grid
system
style
sheet
somewhere
in
two
layouts,
regardless
of
whether
the
theater
or
not,
and
so
the
question
is
I
mean.
Maybe
this
is
a
question
for
a
neat
to
like
how
do
we
handle
that?
A
That
sounds
good.
Any
thoughts
need
on
where,
where
the
spell
should
live,.
D
It
uses
a
relative
path
to
point
the
the
CSS
file
for
radix,
which
is
bootstrap,
of
course,
but
but
if
we
do
that
for
core,
it
doesn't
quite
solve
our
problems
and
that
we
want
to
make
it
so
that
adding
a
bootstrapped
based
layout
in
a
contributed
be
like
the
easiest
thing
possible.
You
shouldn't
need
a
CSS
file.
D
You
just
add
a
template
with
the
right
classes
and
then
there
you
go
right,
but
the
trouble
is
is
that
if
we
just
use
the
stylesheet
ski
as
a
layout,
you
can't
know
where
your
layout
is
installed,
whether
it's
in
a
multi-site
or
whether
it's
in
the
layouts
director.
What
so
using
a
relative
path,
doesn't
work
if
you're
a
contribute,
essentially
idea.
A
I
had
about
that
was
if
we
included
the
radix
grid
system
by
default
for
or
for
all
layouts
and
then
would
give
way
out
some
way
to
opt
out
of
having
that
stylesheet
included.
So
if
all
core
layouts
use
the
same
CSS-
and
we
have
a
lot
of
them,
then
it
kind
of
makes
a
little
more
sense
because
it's
less
code
to
include
it
globally
than
specifically.
But
then
we
do
need
a
way
that
can
trip
layouts,
who
don't
want.
A
The
grid
system
can
say
no,
and
so
there
couple
of
ideas
like
I,
recommended
setting
some
crazy
new
flag
in
the
info
file,
which
Nate
I
know
you
didn't
like.
But
another
thought
is
if
we
added
a
utility
like
drupal
8,
has
this
option
to
exclude
style
sheets
that
works
in
modules,
things
and
layouts?
A
If
we
didn't
that
same
kind
of
utility
for
backdrop,
it
would
be
a
developer
experience
when,
for
anyone,
who's
working
in
the
theme
player-
and
we
could
use
that
same
feature
in
layouts
to
say
it's
like
remove
princess
and
style
sheet
and
then
they
would
be
able
to
remove
it
if
they
didn't
want
it
and
add
whatever
one
they
wanted
using
this
style
sheets
key.
That's
already.
There.
D
A
I
do
think
that
long-term,
like
this
is
kind
of
like
ck
editor,
where,
if
we
put
something
in
core
people
will
use
it,
there
will
be
less
and
less
of
a
use
case
for
removing
the
core
grid
system.
I
mean
we
don't
know
that
now
because
we
haven't
done
it
yet,
but
fury
people
will
just
start
using
bootstrap
and
stop
using
other
good
sis.
Well,.
D
Well,
what
will
happen
eventually,
like
with
one
hundred
percent
certainty,
is
that
a
new
version
of
bootstrap
or
a
new
grid
system
will
become
dominant
or
the
most
popular
more
popular
than
version
4
of
bootstrap,
and
eventually
we're
going
to
do
this
again
and
we're
going
to
need
to
make
another
set
of
layouts
deprecated
or
hide
all
of
the
current
ones
and
then
add
a
whole
new
set
of
layouts.
That
is
like
now.
D
These
are
the
default
core
layouts,
because
trends
change
right,
and
so
it's
nice
that
we're
we're
setting
ourselves
up,
that
we
can
hide
the
current
layouts,
replace
them
with
new
ones
and
then
on
new
sites.
Look
at
the
new
layouts
and
on
old
sites.
They'll
continue
seeing
the
old
ones
and
that's
fine
right
and-
and
that's
that's
great-
that
we're
preparing
ourselves
for
that.
D
C
The
way
the
class
naming
works
I
feel
like
there
would
have
to
be
something
as
game-changing
as
responsive
design
happening
again
where,
because,
like
it's
pretty
general,
it's
just
like
this
is
a
column.
It's
this
wide
and
it
it
becomes
a
slide
at
this
breakpoint
like
it
I,
don't
know,
I
mean
you're
right
it
eventually,
it
will
I
just
feel
like
it
had.
It
won't
be
coming
soon
knock
on
wood,
yeah.
A
If
we
did
add
a
feature
like
manually
added,
remove
style
sheets
that
also
doesn't
have
anything
to
do
with
which
sells
you
were
adding
and
removing,
because
you
can
use
it
on
anything.
So
it's
just
a
matter
of
like
look
at
your
code,
decide
what
you
want.
We
don't
want
turn
on
turn.
It
off
I!
Think
it's
a
good
idea
anyway,
but
it
would
mean
that
anyone
had
a
kinship
theme
is
specifically
disabled
I.
A
You
know
in
in
specifically
able
boots
trick
disabled
bootstrap,
for
if
we
changed
that
they
would
need
to
update
that
line
in
their
contributed,
disabled
foot,
step,
5
or
Omega
or
whatever
we
move
to
in
the
future,
and
that
would
be
an
API
changed.
So
we
would
have
to
do
that
at
a
major
version,
not
a
minor
version,
but
I
also
think
like,
if
we're
going
to
switch
grid
systems,
that
would
have
to
happen
Adam
major
version
and
that
might
be
okay,
I,
don't
know
I
feel
like
either
of
those
solutions.
A
I'd
be
fine
with
like
making
people
remove
a
style
sheet
or
using
a
toggle.
Do
you
have
a
recommendation
for
another
solution
that
would
allow
us
to
add
style
sheet
to
all
the
layouts
rather
than
having
to
remove
it?
Yeah.
D
I
mean
it's
almost
obvious,
but
but
it's
a
lot
of
work
I'm
not
sure
about
it
is
that
you
could
have
base
layouts
like
based
themes,
and
you
could
just
say
this
is
the
base
layout.
You
know,
use
bootstrap
and
then
that
would
load
the
the
defaults
which
I
assume
mostly
it
would.
It
would
use
the
preprocessed
functions
of
the
of
the
base
layout
and
the
CSS
files
of
the
base
layout
and
the
template
of
the
base
layout.
But
of
course
you
would
be
likely
to
override
that
right.
So.
A
Could
we
do
that,
like
you
know,
right
now,
we
already
do
that
with
layout
TPL,
dot
PHP
being
in
in
provided
by
the
layout
module
or
ever
comes
from.
Could
we
do
that
same
thing
like
if
we
made
all
of
core
layouts
dependent
on
a
base
layout,
we
can
move
that
template
and
add
the
style
sheet
all
there
or.
D
A
D
I
mean
well
the
layout
TPL
dot
PHP
file
that
is
in
pores
is
just
because
layouts
don't
have
the
ability
to
get
have
a
hook
theme.
They
don't
have
any
hooks
at
all
right
and
so
the
hook
the
module
owns
the
base
layout,
just
because
it
needs
to
register
it
in
hook
theme,
that's
the
only
real
reason,
yeah
so.
A
A
D
I
guess
in
that
sense
it
wouldn't
really
make
any
it
wouldn't
make
much
sense
for
it
to
inherit
the
layout
or
the
region's.
Unless
you
didn't
do
either
right.
I'm
inherit
the
template
or
the
region's,
but
I
mean,
but
you
could
I
mean
just
not
have
any
I
guess,
but
I'm
not
quite
sure
what
value
you
would
I
mean,
because
you
would
end
up
with
the
exact
same
markup
and
in
this
case,
because
they're
all
bootstrap
based
class
names,
you
just
end
up
with
exactly
the
same
layout.
But
what.
C
D
C
D
A
D
C
A
D
C
D
D
A
Why
don't
I,
ok,
so
I
like
I,
like
this
idea
to
adding
a
lender
info
file
that
says
include
whatever
I
think
we
can't
just
tell
booth
draft,
though,
because
we're
going
to
have
conflicts
with
bootstrap
like
other
stuff
I
wish
you'd
called
something
like
with
Jeff
grid
system
with
Shepherd
for
or
whatever
I
think.
That's
a
good
approach.
I
think
we
should
take.
A
Andy's
work
and
maybe
Andy,
can
I
file
a
pull
request
against
your
project.
Is
that
may
be
how
to
try
to
figure
out?
How
do
we
can
get
all
this
together?
I
think
we
can
do
that
and
then
just
put
like
move
the
style
sheet
that
Andy
had
into
the
CSS
directory
in
the
layout
module
to
find
the
library
update
files.
Add
the
new,
oh
I'll
make
the
list
I'll.
Have
you
take
a
look
at
my
many
things,
I
think's
getting
complicated
so
but
okay.
E
B
F
But
I
think.
A
C
A
That
may
not
be
necessary
for
one
I
don't
know.
Maybe
it
is,
but
I
was
thinking
like
414.
If
we
deprecate
all
those
core
layouts
nobody's
going
to
use
them
anyway,
they
won't
see
them
in
the
UI.
They'd
only
get
the
new
layouts,
oh
I,.
C
C
A
C
A
So
maybe
we
just
work
on
edge,
Andy's
repository,
then
so
Andy.
If
you
want
to
add
Wes
and
I
to
that
project,
that
might
be
a
good
way.
We
can
work
on
it
together.
Yeah.
A
C
C
C
F
C
F
Love
that
it's
awesome
cool
when
he
died
obligated
all
fit
with.
B
B
Nothing
works
together
right
in
radix,
but
now
they
do
like
when
you
change
layouts,
you
keep
all
the
existing
blocks
and
the
placement
myself,
you
know,
even
if
you're
gonna
do
so
a
play
out
to
something
you
would
still
you
know,
I've
seen,
saving
the
blocks
so
that
there
would
be
nice
great.
Oh.
C
Yeah
one
thing
I
was
thinking
about
in
relation
to
standard
class,
naming
it'd
be
nice.
If
well,
maybe
I,
don't
know
if
this
practical
but
I'm
having
utility
classes
around
like
this
is
a
primary
region.
This
is
a
secondary
region,
so
a
theme
can
just
say:
I
want
secondary
regions
like
a
sidebar
to
have
this
background
color
and
not
necessarily
have
to
know
what
it
is
and
like
another
thing,
this
is
a
old
thread
and
we
don't
it's
not
like
a
1.4
thing
for
sure
was
like
having.
C
If
we
have
classes
that
you
can
add
two
regions
allowing
themes
to
specify
classes
that
a
user
can
pick
from.
So
like
the
theme
Cassadine
yeah,
the
theme
could
provide
things
like
make
it
make
this
the
you
know,
sidebar
background
color
or,
like
you
know,
you
name
you
named
things
so
that
yeah,
the
user
who's
doesn't
know.
Any
CSS
can
can
do
that.
C
C
There's
some
changes
that
I'm
I'm
testing
out
in
basis
that
I
think
I'm
just
going
to
move
into
core.
For
example,
making
the
contextual
modules
gear
in
the
top
left
corner
will
avoid
a
lot
of
layout
issues
where
it's
in
a
weird
place
that
you
can't
hover
over
just
because
of
how
things
layout,
if
its
display
block
it
could
be
hiding
behind
another
element
or
something
the
top
left
corner,
I
think,
is
more
reliable
in
the
top
right
corner
is
being
in
a
place
where
you'll
actually
be
able
to
hover
over
the
gear.
C
C
D
C
A
Let's
just
get:
let's
just
get
our
hands
on
andy's
project
and
we
can.
A
In
there
it's
just
kind
of
a
clone,
of
course,
so
we
can
put
what
I
brought
on
off
wherever
we
want
and
we'll
figure
out
how
many
for
us
to
create
against
poor
from
that
I
haven't
feeling
it
will
probably
need
them
to
be
separate,
but
will
want
them
all
to
be
tested
together,
nope,
so
we
gonna
muck
around
in
there
as
much
as
we
want
and
then
figure
out
how
to
take
it
apart
to
put
it
into
law,
request
any
sense.
Okay,.