►
From YouTube: Backdrop weekly 9/1 (Backdrop 1.5 rundown!)
Description
Today’s development agenda: http://bit.ly/2bJMAWQ
A
Hey
everybody
happy
September,
welcome
to
the
first
September
hangouts
for
backdrop.
Cms
we
get
together
every
week
and
talk
about
backdrop
at
this
time
and
see
it's
Thursday,
1
p.m.
pacific
time.
Anybody
can
join
this
meeting
if,
if
you've
been
a
long
time
watcher
but
I've
never
called.
It
then
feel
free
to
join
these
meetings
any
week
and
you
can
participate
in
help
collaborate
and
provide
some
inputs
on
backdrop,
CMS
general
announcements.
For
this
week,
Calla
box,
RC
1,
was
released.
They
just
sent
out
a
mailer
this
morning.
A
A
You
can
donate
to
back
up
CMS
at
backdrop,
CMS
org,
slash,
contribute
you
can
get
a
thank
you
dragging
t-shirt
and
or
hoodie
for
your
donations.
We
also
accept
any
sort
of
contribution,
issue,
partition,
participation,
pull
requests,
etc.
And
then
you
can
just
send
a
request
to
info
I,
backup,
CMS
Oregon.
We
will
send
you
a
free
t-shirt
for
your
contributions.
A
Let's
see
and
free
phpstorm
licenses,
if
you
have
joined
the
backdrop,
contribute
which
you
can
do
by
porting
a
module
to
backdrop
and
then
going
through
the
backdrop,
contribute
a
shin
process.
We
will
send
you
a
upon
request.
A
free
phpstorm
license
that
you
can
use
for
your
open-source
development
of
backdrop.
A
We
have
lots
of
those
licenses
if
you
would
like
one
contact
info
at
backdrop,
CMS
borg
updates
from
the
project
management
committee
this
week
and
there
are
no
updates
scheduled
in
here.
We
have
several
pmc
memories
here,
any
announcements
or
anything
from
the
PMC,
okay,
excellent
all
right.
So
let's
go
right
into
our
usual
weekly
routine,
in
which
we
first
talked
about
infrastructure
infrastructure
things
around
the
backdrop
project
that
likes
the
software
itself.
Primarily
this
means
integration
with
github
and
our
primary
website.
Fact:
web
CMS
Borg
the
project
packager.
A
We
had
lots
of
on
and
off
issues
with
packager
kind
of
having
various
problems
due
to
some
changes
at
github
and
then
some
changes
on
our
end
and
then
things
not
working
out
well
together,
but
we
fixed
all
of
those
integration
issues.
Currently
that
may
it
made
it
so
that
releases
on
fact
I've
CMS
or
we're
not
properly
pointing
at
the
right,
zip
files.
That
issue
has
now
been
resolved.
A
Sorry
I'm
in
your
individual
backdrop,
websites,
so
that
when
you
installed
a
module
web
module
through
the
UI
or
through
drush
for
that
matter,
it
could
confirm
the
checksum
to
make
sure
that
it
was
the
right
archive
and
it
was
not
somehow
maliciously
swamped
in
transit,
which
seems
unlikely,
but
is
entirely
possible
under
weird
circumstances,
so
that
age
issue
is
issued.
1992
security
and
handsome
the
width
lips
get
integrated
a
testing
infrastructure.
We
have
a
long-standing
issue
to
add
script
based
testing
to
backdrop.
The
issue
is
issued.
A
2097
Drupal
8
recently
added
a
javascript-based
testing
into
simple
test
which
we
feel
like
it
would
be
entirely
feasible
for
us
to
backport
into
backdrop
itself
and
that
would
enable
better
testing
evolve.
Our
JavaScript
driven
interfaces,
which
is
increasingly
important
special
things
like
our
rich
text,
editor
and
dialogues,
and
a
lot
of
interfaces
that
are
currently
JavaScript
only.
A
Automatic
updates-
this
is
definitely
a
wishlist
item
and
not
something
that's
slated
for
the
next
release.
Extra
sound
slated
for
any
release
currently,
but
we
would
love
for
it
to
be
possible
as
part
of
our
commitment
towards
lowering
the
cost
of
ownership
of
websites,
we
would
like
to
enable
an
option
for
automatic
updates,
starting
with
security
updates
most
likely,
and
we
have
some
ideas
around
how
to
handle
this,
but
there's
been
no
implementation
started.
It's
all
just
brainstorm.
At
this
point.
A
A
B
Just
we
need
testing
on
it,
I
put
out
a
blog
post
and
backdrops
en
esta
org,
and
that
should
serve
as
the
guy
four
steps
to
reproduction
to
verify
that
this
works
and
if
we
feel
that
it
works,
we
can
merge
that
into
the
upstream
reloaded.
We
have
and
I
think
Jen's
volunteering
to
esta
yep
great
some,
the
other
rush
things
are
known
and
they
just
as
last
week.
He
said
they
just
need
investigation.
Nobody
has
had
the
bandwidth
yet
to
do
that,
but
they
will
come
onto
our
radar.
A
Okay,
great
yeah
I
could
all
have
very
further
than
that,
but
yeah,
it's
all
in
the
issue.
Queue.
A
C
So
I
mean
I,
went
to
triple
camp
LA
last
weekend
and
the
biggest
takeaway
we
had
from
that
event
is
that
backdrop
needs
to
do
a
better
job
of
marketing.
Surprise
for
us,
and
in
particular,
I'm
trying
to
refocus
a
lot
of
our
efforts
are
have
been
so
far
to
try
and
explain
to
people
what
the
difference
is
between
backdrop
and
Drupal,
but
we
are
missing
all
of
the
points
that
make
people
want
Drupal,
so
I
think
it
would
be
good
to
kind
of
look
at
the
like.
C
Why
would
you
choose
triple
list
and
add
some
of
those
bullets
to
the?
Why
would
you
choose
back
chocolate
as
well?
I
put
two
new
items
on
the
home
page.
One
of
them
was
just
about
the
fact
that
you
can
expand
backdrop
with
add-ons
and
the
other
one
is
that
you
can
write
code
easily,
which
are
two
big
selling
points
for
Drupal
I
think
there's
a
whole
bunch
of
other
ones.
C
Those
are
just
once
that
I
was
thinking
of
off
the
top
of
my
head,
but
we
should
take
a
look
at
Triple
S
to
make
sure
that
we've
got
all
that
stuff
on
our
list
as
well,
and
I
also
got
at
every
follow-up
question
I
got
with
like
what
are
you
doing
about
marketing
marketing
marketing
I
was:
do
you
have
a
showcase
and
so
I
think
we
need
to
kind
of
make
that
the
next
hitless
on
our
site,
and
we
need
to
make
sure
that
it's
not
just
like
a
slideshow
of
screenshots
of
websites
that
are
running
back
Jeff,
but
a
compelling
story
in
each
case
of
how
backdrop
enabled
a
company
to
achieve
its
goals,
how
enabled
it
to
stay
within
its
budget
or
whatever
story
it
is
that
that
company
has
to
sell,
needs
to
actually
be
conveyed
in
that
showcase
node,
so
that
it's
it's
not
just
about
fiction.
C
Pretty
pictures
are
important,
but
making
sure
that
there's
a
compelling
story.
There
would
be
really
good
too,
because
the
people
who
are
trying
to
decide
whether
they
should
use
vector
right
now
are
looking
for
those.
You
know
compelling
reasons.
Like
things
that
are
real
human
beings,
getting
success
from
using
backdrop,
so
I
kind
of
have
a
little
renewed
focus
on
trying
to
figure
out
what
it
is.
C
We
should
be
doing
with
the
website
making
sure
that
each
we
have
kind
of
personas
in
mind
who
it
is
that's
coming
to
the
backup
site
and
what
they
need
to
know,
and
it's
not
just
the
triple
developer,
which
is
the
one
we're
all
familiar
with,
but
also
the
site
owner.
The
agency
lead,
whoever
it
is
that
needs
to
see
success
stories
and
what
those
success
stories
need
to
tell
them.
C
When
you
take
them
into
consideration
too
so
kind
of
a
renewed
focus,
I'm
thinking
about
like
what
do
we
actually
want
them
to
do
when
they
get
to
our
website
like?
Do
they
need
to
read
the
handbook
or
should
we
like?
What
is
what
is
the
intended
goal
or
like?
We
have
a
website
that,
like
what
what's
the
point,
I
think
sometimes
we
haven't
thought
not
all
the
way
through.
So
anyone
wants
to
help
with
that.
We
want
them
to
sign
up
for
an
Euler.
We
should
pick
it
up.
C
Okay,
that's
a
good
point
too.
He
said
that
we
should
try
and
figure
out
people
who
are
leaving
Drupal
or
chose
not
to
use
it
for
some
reason,
figuring
out
what
what
the
reason
is
and
see
if
we've
solved
those
problems
and
if
so
state
that
somehow
like
get
get
that
yeah
I'm,
not
sure
if
we
talked
about
it
last
week
or
not,
but
Jeff
did
off
this
fantastic
integration
with
getting
down
load
count
from
github
and
after
he
did,
that
I
was
totally
motivated
to
actually
make
it
show
up
on
the
website.
C
So
if
you
go
to
any
project
page
except
for
actually
I
think
it
is
even
on,
but
the
backdrop
project
itself
see
in
the
sidebar
there's
a
number
of
downloads
from
github
as
well
as
active
usage
statistics,
and
let
me
tell
you
it
looks
a
lot
better
with
number
of
downloads
that
it
did
just
with
active
usage,
which
makes
me
think
that
maybe
people
aren't
using
the
update
status,
module
or
I
don't
know,
but
yeah.
It
looks
great.
C
So,
thanks
for
getting
that
information
to
Jeff
I
think
it
looks
fantastic,
so
much
better
on
the
site,
and
then
they
did
have
one
follow-up
that
maybe
we
should
take
that
feature
and
merge
it
back
into
project
github
module.
So
anyone
that's
using
the
project.
Github
module
could
benefit
from
that
as
well.
We
don't
have
to
maintain
custom
field.
There
are
some
advantages
to
having
a
custom
field.
C
We
are
currently
using
the
built-in
views,
support
and
the
built-in
one
clock
/
field
thing
that
you
get
for
free
with
backdrop
that
we
would
need
to
write
ourselves
if
it
was
just
part
of
project
github.
But
since
the
other
numbers,
like
the
usage
numbers
already
are
facing
that
issue,
we
need
to
do
a
little
cleanup
on
project
module
anyway.
So
these
integration
block
stuff,
like
that,
I
added
I
added
blocks
for
everything
while
I
was
in
there.
But
getting
these
integration
would
be
great,
but
yeah
looks
good.
C
So
thank
you,
everyone
for
all
your
help
on
that
other
stuff,
piano
so
much
other
stuff.
We
want
to
work
on.
We
talked
about
support
a
documentation,
in
particular
in
the
last
meeting.
We
have
all
of
this
fantastic,
in-depth
documentation
and
we
just
need
to
figure
out
how
to
organize
it
in
a
way
that
makes
sense
to
users,
and
then
we
can
expose
it
on
the
site.
The
link
to
the
top
level
book
page
for
documentation
is
user
dash
guide.
C
If
anyone
wants
to
take
a
look
at
it,
I
think
we
just
need
to
find
a
way
to
make
it
more
easily
digestible
for
the
QuickStart
people
like
right
now,
there's
one
page
called
quick
start
guide
and
I.
Don't
know
how
we
can
call
more
attention
to
that,
like
I,
would
love
to
have
maybe
that,
like
some
kind
of
promo
on
that
thing,
on
the
landing
page
or
something
just
kind
of
get
new
people
to
that
page,
faster,
the
other
stuff
we're
working
on
forms,
we
want
forums
with.
C
Moving
very
quickly,
but
we
know
we
want
them.
We
also
know
single
sign-on,
that's
been
a
little
pain
for
me
to
test
so
I've
been
doing
other
stuff.
Instead,
if
anyone
else
wants
to
figure
out
how
to
test
single
sign-on,
I
was
thinking
putting
on
the
API
site
might
be
a
great
place
to
start.
That
is
where
I
live,
develop.
Our
all
our
developers
are
most
of
the
time
and
our
developers
are,
the
people
are
most
likely
to
have
github
account,
so
it's
also
slightly
less
trafficked
so
be
a
safe
place
in
case
it
exploded.
C
We
can
unexploded
really
quickly
without
causing
too
much
damage,
but
yeah
anyone
wants
to
take
a
stab
at
that.
I
could
definitely
use
some
help.
Getting
that
tested.
C
A
Coolio
yeah
I'm
excited
about
the
other
guy
said
today
was
the
first
day,
I
actually
wouldn't
looked
at
it,
and
there
is
a
lot
of
really
great
stuff
in
there.
We
talked
about
that
in
the
design
meeting
how
it
needs
to.
It
has
a
lot
of
presentation,
things
that
need
to
be
worked
out,
but
the
content
is
it's
really
just
great,
which
you
can
see.
Actually
bankruptcy,
mustard
or
exhaust
use
your
dash
guide,
because
I
guess
people
watching
they
don't
always
open
up
the
agenda.
A
A
Yeah
Jen
does
headed
to
the
agenda
here
that
if
we
don't
make
another
release
before
September
15th,
what
will
happen
is
145
will
be
the
last
one
dot
for
release
that
coincides
with
the
release
of
150.
Traditionally,
that's
what
we
do.
We
push
out
the
very
last
bug-fix
release
on
the
same
day
as
as
the
next
minor
version
kind
of
has
been
the
last
hurrah
of
that
previous
minor
version.
So
you
can
see
all
the
issues
that
have
been
fixed
or
slated
to
be
fixed
as
soon
as
possible
by
using
the
145
milestone
in
github.
A
Let's
see
important
bug
fixes.
We
have
a
section
here
for
like
catastrophic
bugs
in
our
software
that
need
to
be
fixed
as
soon
as
possible.
We've
gotten
most
of
them
nailed
down,
but
we
still
have
this
big
problem
where
images
are
deleted
after
six
hours,
if
you've
uploaded
them
into
a
block
through
the
rich
text.
Editor,
let's
issue
1373
and
it
meets
the
patch
needs
some
review
and
need
some
work.
A
I
spent
a
lot
of
time
reviewing
everything
that
needed
reviewing,
but
I
didn't
get
to
this
again,
so
yeah,
more
ideas,
more
testing
and
more
implementation.
All
and
you
did
if
you
want
to
visit
issue
1373
as
soon
as
we
fix
that
book,
that
in
as
soon
as
possible,
if
it
gets
fixed
in
the
near
future
like
in
the
next
week,
we
will
immediately
make
the
next
bug-fix
release
to
get
that
problem
solved
for
people
as
quickly
as
possible.
A
We
have
only
two
weeks
until
the
release
of
backdrop
150,
which
we
have
been
calling.
The
editorial
experience
released
I'm
a
little
bit
worried
that
we
might
not
live
up
to
that
slogan,
but
it
will
be
an
exciting
release.
Nonetheless,
all
right
items
that
we've
got
slated
for
150,
first
of
all,
triple
750,
was
released
about
a
month
ago
and
included
several
minor
feature
improvements
as
well.
We
want
to
get.
A
We
want
to
make
sure
that
we
get
feature
parity
with
all
of
the
new
items
that
were
added
into
Drupal
7
dot
50
before
that
will
be
States.
One
item
of
note
is
an
issue
that
we've
been
working
on
for
a
while
is
adding
full
utf-8
supports
for
four
byte
characters,
which
means
which
means
emoji
support,
basically,
for
the
light
lay
person
so
that'll
be
great.
We
have
a
pull
request.
That's
fully
working
its
marked
needs
review.
A
It
could
use
some
additional
eyeballs,
but
if
no
additional
I've
always
show
up,
it
will
be
merged
probably
next
week.
So
that's
great.
The
reference
module
is
when
I
have
been
saying
for
months.
Probably
the
most
important
item
in
this
next
release
and
it's
in
not
a
good
place
right
now.
It's
issued
1301,
it's
also
in
a
contributory
under
a
backdrop,
contribs
reference
and
yeah
discuss.
A
That
doesn't
necessarily
mean
that
those
things
off
the
table
because
reference
module
could
continue
to
be
developed
as
a
contributed.
An
arbitrary
reference
module
could
simply
depend
on
it,
but
it
being
in
court
would
be
ideal,
but
we
don't
have
basically
the
time
to
finish
it
at
this
point.
So
there's
or
border
right
and
upgrade
path,
which
is
probably
just
as
important
no
expression
about
that
yeah.
B
A
Yes,
sorry
yeah.
There
was
a
little
bit
of
kerfuffle
in
the
issue
of
you
about
making
a
single
field
reference,
multiple
types
of
entities
and
we've
I.
Think
almost
everybody
has
agreed
that
we're
tabling
that
functionality
for
later
release
pretty
much,
no
matter
what,
but
in
arbitrary
entity
reference
field.
Just
that
would
allow
pointing
it
users
or
no
it's
four
terms.
One
per
reference
I
mean
11
type,
referencia,
any
other
ideas
or
thoughts
on
reference
module.
It's
solutions
for
coming
up
with
something
in
two
weeks
or
table
in
it
for
16,
I.
Think.
C
That
it
sounded
like
the
best
solution
that
we
derive
dot
was
the
solution
that
we
were
originally
taking
and
nobody
was
super
excited
about
settling
for
a
less
good
solution.
So
I
think
we
should
take
the
good
solution
and
just
push
it
to
the
next
release.
I.
A
A
A
That
sausage,
but
you're
right,
then
we
also
have
a
lot
long,
precedence
of
kicking
things
down
a
couple
of
releases.
If
they're
not
finished,
sick
editor
got
kicked
twice,
it
was
supposed
to
be
in
one
point
0
and
didn't
make
it
and
didn't
make
it
into
one
point:
one
either
and
then
did
got
into
1.2
I
think
that
was
right.
So
it
was
eight
months
delayed,
but
it's
better
to
delay
feature
that
it
did
delay
the
entire
release.
So
that's
that's
better
policy,
so
I'm
also
yeah
in
that
book.
Okay,
thanks
Luke.
A
C
A
Why
not
okay,
I
think
I
think
that's
a
good
idea.
I
mean
it's
not
actually
necessary
from
a
procedural
standpoint,
because
we
use
it
for
conflict
resolution,
but
I
think
just
to
put
authority
behind
it.
You
know
that
there's
yeah
that
it's
a
good
idea
that
it
would
basically
doesn't
feel.
C
A
little
worried
because
might
hasn't
been
hearing
the
last
few
weeks,
I
want
to
make
sure
that
he
has
to
say
in
the
conversation
and
I
think
if
we
make
it
a
PMC
issue,
it'll
at
least
get
his
attention.
Okay,
that.
A
A
We
actually
just
spend
a
good
chunk
of
time
talking
about
this
one,
because
the
design
call
was
right
before
this
and
it
yeah.
We
really
wanted
on
down
a
rabbit
hole
there
during
that
meeting.
So
lots
of
great
conversation
know
about
solutions
for
solutions
for
getting
basis,
wrapped
up,
sweetie
speaking
of
jetting
basis,
wrapped
up
a
recap.
We
have
been
doing
a
whole
lot
of
work.
A
Getting
court
ready
to
accept
basis,
including
moving
things
out
of
seven
and
into
generic
location,
so
the
faces
can
reuse
things
like
open
sans
and
the
responsive
tabs
and
the
font
detection
loading
and
all
of
these
things
that
were
pioneered
in
seven.
But
now
we
need
for
basis
as
well,
so
there'll
be
moved
into
miss
core
system
module
or
wherever
to
be
shared
between
themes,
which
is
great.
A
E
Know
if
we
sit
on
this
call,
but
it's
going
to
be
a
good,
a
good
I
want
to
say
it
back
in
front
end,
but
that's
kind
of
a
site
site
editor
way
to
looking
at
it,
but
you
can
use
you
can
use
basis
to
edit
your
content
types
and
you
can
use
it
to
actually
you
know
if
you
user
facing
site
so
yeah,
it's
looking
like
it's
it's
doing
quite
well
there
and
yeah
lots
of
it's
nice
that
we're
kind
of
thinking
about
there's
a
lot
of
issues
around
a
theme
related
things
that
aren't
necessarily
basis,
but
we're
kind
of
thinking
about
all
this.
E
A
Okay,
yeah
speaking
of
responsive
menus
and
other
front
and
eggs
you're
right
that
it
seems
like
because
basis
is
that
feature
that
is
likely
to
be
that
the
big
impact,
like
the
banner
feature
for
4
15
at
this
point,
we're
also
looking
at
a
whole
bunch
of
other
front-end
related
things
to
really
kind
of
amp
up
the
out
of
box
experience,
because
people
will
install
the
new
version
of
backdrop
and
they'll
see
the
new
theme,
but
there's
a
lot
of
things
in
the
theme
or
in
the
in
that
issue
that
are
in
a
mock-up
that
we
would
like
to
also
implement.
C
A
Talk
about
that
I
had
flooded
that
idea
and
we
could
shove
it
into
14
and
not
make
it
the
default
and
then
hitta
radon
and
14,
but
I
wit.
If
this
continues
to
get
polished,
then
I
had
been
under
the
impression
that
it
would
be
the
default
again,
but
maybe
we
should
put
it
in
and
then
Bob
it's
going
to
be
down
to
the
wire
for
sure
like
this.
A
E
A
to
back
it
up
is
that
you
can
override
one
file,
skin
dot,
CSS
and
change
every
single
color
they're
all
laid
out
very
simply
in
one
easy
to
override
file.
If
you
remove
it,
the
colors
will
revert
to
default.
But
if
you
ever
read
the
one
file,
it'll
it'll
they'll,
do
everything
so
I
think
even
though
doesn't
have
color
module
support,
it's
it's!
It
is
kind
of
set
up
to
be
easy
to
easy
to
make
your
own
okay.
C
Well,
that
might
also
be
good
like
so
I
I
I'm
not
against
this
idea
at
all.
It
was
just
as
surprised
because
I.
C
Pushed
out
all
of
our
processes,
one
release,
including
the
putting
it
in
without
making
it
default,
but
if
you
guys
want
to
make
it
fall,
I'm
totally
fine
with
that
I
think
it
also
helps
the
color
module
thing
where,
like
I,
don't
like
color
module
and
personally
would
like
to
just
remove
it
from
core,
and
so,
if
our
default
theme
doesn't
support
it
out
of
the
box,
I
think
that
gives
us
a
little
more
freedom
to
do
what
we
want
with
it.
C
E
And
I
actually
I
want
to
make
not
I
want
to
make
a
module.
That's
more
like
it's
a
superset
of
color,
so
it's
like
the
CSS
module.
So
like
kind
of
like
square
space,
where
you
have
you
know
a
control
that
you
can
you
have
a
bunch
of
like
you.
Might
you
might
want
to
change
padding
or
you
might
want
to
change.
You
know
all
these
different
things
and
colors
of
things
would
be
one
of
them,
so
yeah
I,
that's
what
I
would
rather
have
and
whether
it's
theme
settings
or
module
or
whatever.
C
If,
if
that
module
does
get
done
in
the
12
X
cycle
and
people
like
it,
that
might
be
a
much
better
candidate,
rather
than
like
figure
out
what
to
do
with
color.
It's
just
like
replace
color
with
this
instead
and
make
that
part
of
backed
up
to
so
I,
wouldn't
kind
of
rather
have
your
focus
fee
in
that
direction
anyway,
and
if
that,
if
that
module
works
in
one
with
basis,
then
like
win,
you
know
so
yep.
E
C
C
Yeah,
so
we
just
talked
about
that
in
the
design
meeting
and
I
think
I
have
a
past
a
path
forward.
The
original
nails
like,
oh,
my
god,
this
is
such
a
slippery
slope
on
all
the
other
stuff,
that's
tied
to
the
/
node
thing
and
I
think
our
consensus
has
been
let's
put
in
something
new
without
taking
out
something
holds,
because
it's
going
to
be
easy
to
put
in
something
new,
there's
already
an
issue
in
the
queue
for
allowing
people
to
turn
off.
C
/
note,
I
think
if
we
can
get
that
teacher
in
now
with
this
change,
that
would
be
fantastic
and
then
in
factor
of
two,
if
we
want
to
remove
/
node
entirely
because
nothing
excusing
anymore,
we
can
there's
a
bunch
of
other
stuff
like
RSS
settings
which
are
used
on
/
node
and
on
the
taxonomy
term
page.
Those
pages
should
be
views
anyway.
I
think
when
we
get
in
the
change
for
those
pages
for
counting
views,
we
can
also
remove
the
setting
for
our
SF
settings.
That
now
only
affects
those
pages.
C
C
We
can
do
all
the
clean
up
later
in
conjunction
with
all
the
other
issues
that
related
to,
and
then
we
also
had
a
chat
in
this
is
I,
meaning
about
how
to
do
our
hero
block
and
basically
we're
just
going
taking
on
the
block,
we're
going
to
add
one
extra
feel
to
it
for
a
background
image
and
if
no
background
images
provided,
then
any
theme
could
use
CSS
to
provide
its
own
background
image
and
if
one
is
write
it
in
the
UI
it'll
just
be
inlined
and
pumped
in
there.
C
So
it's
just
a
normal
bucket
has
a
title
you
can
put
whatever
links
you
want
into
it.
You
can
format
it.
However,
you
want,
but
for
the
most
part,
the
only
significant
differences
it'll
have
a
user
interface
for
adding
an
image
that
image
Nate
was
also
suggesting
we
record
the
file
path
and
not
the
file
id
and
that
way
if
the
path
exists
on
the
live
server.
Even
if
the
ID
is
not
identical,
you
can
I'll
deploy
your
changes.
C
It'll
be
a
little
less
strange
from
eastern
chickens,
be
referencing
content
in
your
config,
so
good
for
thought.
I
think
we
have
a
path
forward
on
all
that
stuff
and
I.
Think
it'll
make
basis,
look
much
better,
so
maybe
all
maybe
I'll
throw
a
basis
in
money
in
my
local
and
start
testing
the
homepage
on
that
yes,
well,
we.
A
D
Maybe
can
you
say
something
now
that
you
mentioned
a
field?
Can
we
make
a
start
by
making
this
field
allowing
this
field
to
have
multiple
values?
So
for
now
the
first
value
gets
picked
up
and
used
as
an
image,
but
in
the
future
we
can
use
the
multiple
values
for
the
slideshow
thing
that
we
said
that
what
your
place
like.
C
I
was
thinking
about
that
too,
but
the
way
that
we're
printing,
the
image
is
a
background
image
on
the
tag
is
not
going
to
work
with
multiple
values
and.
C
E
C
This
is
like
this
slippery
slope.
I
started
going
down
where
it's
like
I'm
on
an
image.
I
want
to
enter
title
I
want
to
link
around
the
image.
I
want
to
link
on
the
image.
I
want,
I,
went
and
then
I
realized
that
what
I
wanted
was
a
blocked
entity
where
you
can
add
your
own
fields
to
it,
and
then
I
wanted
a
few.
And
so
what
I
think
this
is
just
going
to
be.
C
Like
super
simple,
put
a
background
in
a
John
a
block
and
then
the
other
things
we
want
will
be
a
motivating
factor
to
actually
get
a
content
type
block
into
core,
with
an
example
of
being
a
slide
and
a
view
that
is
the
homepage,
slider
and
so
I
think,
like
kind
of
forcing
us
to
be
limited,
is
going
to
force
us
to
make
that
go
into
core,
so
I'm
thinking
that
that's
the
best
best
of
best
possible
architecture,
and
we
shouldn't
kind
of
like
shoehorn
it
in
here.
C
C
C
I
have
a
really
created
the
idea.
I,
don't
think
I
should
mention
till
after
1.5
comes
out.
It
related
to
the
URL
list
notes,
as
opposed
to
a
new
entity
type
4
blocks.
I
was
also
thinking.
If
we
do
get
this
references
thing
in,
we
could
get
rid
of
taxonomy
as
a
separate
entity
type,
and
it
would
just
be
a
node
that
happens
to
have
a
view
on
it.
There
could
be
like
a
checkbox
for
like
show
listing
or
whatever
and
then
any
content,
that's
referencing
that
node
would
appear
in
the
list.
C
Exactly
like
two
economy
does
now
so,
rather
than
going
the
drupal
route,
where
everything
became
an
entity
from
Drupal
6
to
triple
seven
we're
kind
of
going
back
to
Drupal
6,
where
everything
becomes
a
node,
so
we
have
a
node
term.
We
have
a
node
block
like
back
to
when
things
were
simpler,
but
maybe
not
better.
Oh
so
anyway
play
the
scene.
Don't
think
about
that
for
at
least
two
weeks,
but
it
would
fit
with
our
URL
list
notes
pattern.
It's
all
saying:
okay,.
A
Okay,
yeah
me:
okay,
yeah
I
want
to
also
on
akkalla
issue
2001
that
allows
/
node
to
be
disabled,
I,
know
Jeff
and
Gregory.
You
guys
have
been
kicking
back
and
forth
on
that.
One
I
love
the
solution
to
that.
A
To
that
issue:
I
love
it
just
if
/
node
isn't
the
front
page
then
get
this
disabled
brilliant
like
that
is
just
so
fantastic
because
either
/
node
is
your
front
page
or
you
never
ever
ever
want
it
like,
so
that
I
think
that's
just
fantastic,
because
that
will
finally
turn
off
/
note
on
everybody's
websites.
That
is
like
what
the
hell
is.
This
page.
You
know
they
run
across
it
like
two
years
after
their
site
is
launched
and
they're
like
it's
this
page,
there's
all
those
random
crap
on
it
that
isn't
styled.
A
A
C
So
originally
I
opened
this
issue
and
was
like
we
need
to
make
it
easier
for
people
to
make
their
menus
and
responsive
and
at
the
same
time
there
was
an
issue
that
was
like.
We
can't
have
drop-down
menus
out
of
the
box
and
there's
this
usability
problem.
Where
people
go
to
the
menu
system
and
the
indent
things,
and
then
they
wonder
why
there
are
no
leaks
and
so
I
kind
of
marched
them
together.
It
was
like
we
need
responsive,
drop-down
menus
in
core
and
then
Nate
came
along.
C
It
was
like
I
would
love
to
see
a
new
API
for
menu
styles,
and
so
then
we
got
this
great
for
requests
from
chocolate
to
actually
implemented
an
API
for
many
styles,
but
I
was
looking
at
the
other
day
and
I
was
just
like
whoa.
This
is
way
more
than
like
solving
art,
but
Miss
and
user
experience
problems
with
the
current
system.
I
think
it
actually
looks
really
good
I,
really
like
a
lot
of
the
directions.
It's
going
in
I,
don't
think
it'll
be
ready
in
two
weeks
and
so
in
the
design
meeting.
C
An
hour
ago
we
were
talking
about
seeing
if
there's
a
really
simple
way,
that
we
can
solve
the
two
problems
with
like
a
checkbox
that
says,
make
this
venue
responsive
or
a
checkbox
and
says
because
when
you
a
drop-down,
put
it
in
right
now
and
then,
when
we
put
in
the
menu
cells,
API
that'll,
be
when
we're
adding
on
more
options
to
that
forum.
That'll
allow
you
to
control,
exactly
how
you
mean
you
should
respond.
You
can
maybe
change
the
JavaScript
menu.
That's
governing
all
that
stuff
too,
so
that
I
split
out.
C
I
renamed
the
main
issue
to
add
to
my
new
styles
API
and
then
I
created
a
new
issue
that
was
like.
Let's
just
solve
this
weird
bug,
that
we
don't
have
any
responses
than
using
four,
and
maybe
we
can
make
them
drop
down
while
we're
at
it
by
using
write,
JavaScript
library,
so
I
think
we're
doing
a
little
scope
controlling
now
that
we
only
have
two
weeks
left
and
saying:
let's
just
fix
this
little
problem
now
and
then
we'll
revisit
the
menu
style
API
for
16.
A
Yeah
I
think
that
I
think
it's
great
yeah,
the
whole
API
think
actually
wasn't
intended
to
make
things
more
complicated.
It
was
the
fact
that,
or
that
the
thoughts
that
we
might
need
an
option,
it's
like
turn
it
on
our
offense
like
well
on
or
off
really
might
just
be
no
style,
plus
the
first
style
and
then
extra
styles
would
just
be
added.
So
I'm,
fine
punting
on
that
it
was
an
idea
of
maybe
we
could
get
more
by
doing
the
same
amount
of
work
kind
of
thing.
It
cited
the.
C
A
Good
good,
okay,
cool,
okay,
next
item,
improving
the
rich
text.
Editor
is
a
meta
issue,
issue
1087,
and
this
is
really
ties
into
the
editorial
experience
parts
of
this
release,
but
there
hasn't
been
a
whole
lot
of
love
to
it.
I've
been
mentioning
that
I
think
the
key
to
a
successful
release
is
really
going
to
be
driving
hard
on
basis,
because
it's
the
feature
that
is
closest
to
ready
and
making
that
making
a
big
splash
for
their
front
end
theme
and
then,
if
possible,
add
a
couple.
A
great
bullet
features
for
the
rich
text.
A
Editor,
if
possible.
My
thought
is
still,
let's
put
all
of
our
focus
on
the
front
end
and
not
a
box
for
this
release,
because
that's
what
is
most
likely
to
be
completed
and
keep
hammering
on
that,
but
still
it
would
be
nice
if
the
editorial
experience
released
actually
had
some
editorial
enhancements.
So
anybody
that
has
some
bandwidth,
you
can
check
out
issue
1087
or
ping
me
actually
personally,
in
dinner
or
elsewhere,
and
I
would
love
to
help
collaborate
on
that
as
well.
A
Okay,
there's
a
bunch
of
other
things
that
they're
slated
for
150.
Actually,
some
of
them
have
been
trickling
in.
We
went
through
an
extensive
needs,
review,
pass
and
merged
all
kinds
of
things
in
the
past
couple
of
days
are
past
week
or
so
so,
there's
a
bunch
of
other
things
to
also
be
in
15.
Oh,
that
are
nice
to
have,
but
not
the
focus
of
the
release.
A
You
can
see
bankruptcy,
Minister,
Doron
roadmap
for
future
plans.
Probably
what's
going
to
happen
is
after
we
make
the
decision
on
references
will
have
an
item
of
a
feature
to
do
for
16,
because
right
now
16
is
as
of
yet
largely
unplanned.
So
we
also
make
continuous
improvements
to
user
experience
and
developer
experience.
You
can
find
those
issues
square
brackets.
You
x,
+
DX,
on
github.
A
Speaking
of
those
issues,
man
shout
out
to
Gregory,
who
is
now
our
leading
coder
as
far
as
pull
request
counts,
go
oops,
yeah,
oops,
sorry,
Gregory,
the
I,
don't
code,
hahahaha,
ginger
beer,
we've
made
a
dangerous
man.
Here
is
now
he
is
filing
pull
requests
that
fast
and
furious
rate,
which
is
fantastic
and
and
they're
mostly
just
trivial
changes
that
all's
being
moved
far
did,
which
is
fantastic.
We.
D
We
had
we
had
a
talk
with
Miguel.
Is
that
but
the
web?
Sorry,
the
WordPress
guy
about
this
thing.
He
had
a
few
thoughts
and
I
told
him
that
that
one
of
the
exciting
things
in
back
to
appease
that
have
been
a
being
in
Drupal
land
for
like
seven
more
years
and
I
have
never
liked
even
attempted
to
code
and
I
think
it
was.
A
D
D
345
releases
on
backdrop:
CMS,
that's
blast.
Seven,
we
have
55.
Total
country.
Brothers
does
not
change
since
last
week
it,
but
we
have
14
pending
applications,
26
organization
profiles,
which
is
no
update
since
last
meeting
and
351
total
uses
that
plastic
thing
since
last
meeting
and
the
new
stat
that
there
is
the
backdrop
seen
as
the
core
download
is
6140,
which
is
plus
100,
sees
last
meeting
and
that's.
C
Acts
like
I
didn't
look
at
that
since
then,
but
Jeff
read
this
great
blog
post
on
pantheon
and
Russian
termina
stephanie
was
interested
in
giving
that
a
read.
I
was
actually
taking
notes
frantically
when
it
was
in
drafts
a
room
like
opens
and
removed.
This
I
need
this
information,
but
it's
good
stuff.
So
if
you
are
hosting
rockchip
on
Pantheon
and
want
to
know
how
to
do
cool
things
like
fire
up
a
new
backdrop
install
from
the
command
line,
cuz
Gregor
you're
gonna
need
that
soon,
Nostalgia
defended
right
there,
which.
C
Good
I
was
thinking
about
also
doing
a
follow-up
blog
post
about
drupalcamp
LA
and
specifically
talked
about
marketing
things.
Let's
see
if
we
could
get
a
little
more
energy
from
the
marketing
e
folks
to
help
us
with
our
website,
but
I'm
now
thinking
that,
maybe
that
might
not
happen,
because
I
would
much
rather
write
code
for
a
factor
of
15,
so
yeah
we'll
see.
If
that
happens,
if
anyone
else
has
anything
they
think
might
be
good.
On
blog
between
now
and
they're
really
sit
back
up
on
five.
C
We
definitely
would
love
more
content,
so
I
know
jack
is
working
on.
This
would
be
serum
right
up.
I'm
gonna
follow
up,
see
how
that's
coming
along,
but
always
open
to
new
ideas.
A
newsletter
schedule
we're
now
two
weeks
away
from
the
release
of
backdrop.
15,
usually
we
don't
send
a
newsletter
about
a
new
release
until
a
bug-fix
release
comes
out,
so
that
would
give
us
at
least
three
weeks
but
question
I
haven't
sent
there
really
the
newsletter
about
up
14.
Is
it?
Do
you
guys
think
I
should
do
it
now?
D
C
The
time
out
soon
yeah,
we
should
do
what
it's
like:
hey
we're
about
to
do
something
cool,
but
we
did
something
cool
recently
and
we
can
kind
of
like
get
people
excited
about
the
new
release
like
new
for
theme,
I,
don't
know
what
we
can.
Promise
I
feel
like
I
want
to
tell
people
things,
but
maybe
it's
not
smart
for
us
things,
I,
don't
know
what
could
happen.
Oh,
but
yeah,
we
could
just
say,
like
you
know,
keep
your
ears
field
for
new,
exciting
things
happening.
What
do
you
think
Jason
newsletter?
Yes,.
A
C
I
will
do
that
today,
then,
instead
of
worrying
about
a
blog
post,
I
think
that's
more
important,
all
right,
maybe
not
more
important
than
15,
but
I'll
make
myself
to
it
anyway,
on
earnings,
we
have
a
new
video
in
spanish
for
backdrop,
which
is
great
if
anyone
else
is
interested
in
creating
videos.
C
I
know
last
week
an
outreach
meeting
brian
volunteered
to
do
so
for
us,
which
is
fantastic,
he's
the
owner
of
food
fighters,
calm
new
well-loved
backdrop
site,
and
he
wants
to
do
some
videos
on
user
interface,
stuff
reps,
which
I
thought
would
be
really
good.
He
else's
a
lot
of
experience
with
videos,
because
that's
what
he
does
for
flute
reviews
so
kind
of
right
up
his
alley,
which
seems
good.
So
we
need
some
videos.
C
If
anyone
has
any
Oh
they've
already
made,
let
us
know
we
can
kind
of
curate
them
into
the
backdrop
channel
on
YouTube
and
post
them
on
our
website.
All
that
good
stuff,
anything
else.
Anyone
has
ideas
about
stuff.
We
can
do
for
marketing.
Definitely
let
us
know
we
do
have
the
showcase
node
type
on
backdrop:
CMS
org.
If
you
want
to
start
adding
sex
that
you've
built,
we
need
compelling
stories
as
to
why
dr.
F
is
parking
for
those
people
in
our
organizations.
C
Definitely
if
you
have
ideas
of
how
to
tell
that
story,
but
the
neca
I,
we
will
start
curating
our
favorites
when
that
showcase
thing
goes
live
which
will
be
pretty
soon
ish
the
death
different
marketing
sprints
every
Thursday.
After
these
weekly
meetings,
we
get
together
in
github
and
solve
hard
problems
for
backdrop.
So
if
you
have
free
time
today,
you
can
join
us
if
you
have
free
time
any
other
day.
You
can
also
usually
find
us
in
the
get
er
chat
room
as.
D
C
As
the
github
issue
queue-
and
we
are
often
also
still
in
the
IRC
channel
comp
backdrop,
you
can
also
always
tweet
a
dust
at
patrick
GMS
on
twitter,
oh
and
we
have
a
Facebook
page
where
I
think
all
of
our
twitter
stuff
shows
up
automatically
so
it
or
not
on
Twitter
and
you
are
on
Facebook,
you
can
still
see
what's
going
on.
In
upcoming
events,
we
have
an
event
calendar
on
backdrop,
semester,
org
go
ahead
and
take
a
look
there
for
exciting
new
things.
C
If
any
of
you
are
planning
on
coming
to
bad
camp
in
October,
I
was
thinking
about
getting
a
bunch
of
business
cards,
the
ones
that
West
made
us
designs
for
printed
for
bad
camp
and
if
you're
going
to
be
here,
we
can
hand
them
all
out
so
probably
be
cheaper
to
order
them
in
a
big
batch
and
get
them
all
shipped
at
once.
So
that
could
be
an
option.
The
files
are
online.
If
you
want
to
get
the
print
of
yourself,
obviously
having
them
printed
in
Australia's,.
C
Easier
than
that
one
goes
ship
them
there
if
I
or
the
design
files
will
be
much
it
there
now,
but
osarians
I
just.
C
E
C
And
we
will
take
that
also,
we
are
delivering
a
backdrop
summit.
A
bad
camp
I
was
trying
to
figure
out
if
we
had
enough
content
to
kind
of
rework
our
solid
structure.
Last
year,
the
summit
was
a
half
a
day
of
training
in
this
year.
We
might
also
be
doing
a
bad
job
training,
so
I'm
trying
to
put
a
new
content
there.
Every
chat
to
a
couple
people,
the
kallah
box
books-
want
to
do
a
demo.
I'm
gonna
try
and
get
someone
from
Pantheon
to
do
a
demo.
C
I've
got
two
people
lined
up
to
do
case
studies,
but
if
anyone
else
has
anything
they
want
to
share
in
the
back
summit,
that's
not
also
selected
as
a
session.
We
could
definitely
do
that
and
then
we
will
do
kind
of
a
higher
level
session
a
camp
as
well
for
people
who
are
not
able
to
attend
this
on
it.
So
any
ideas
for
content.
We
should
talk
about
also
open
for
summit
day
which
I
working
group.
Sir.
What
have
you
alright?
If
you
guys,
are
interested
in
reading
more
about
back
up?
C
D
Just
real
quick
when
it
comes
to
news,
drupal
south,
is
coming
up
by
Dean
file
a
session
that
it's
actually
one
of
the
late
sessions
like
the
most
of
the
spots
are
filled.
I
hope
that
we
get
approved
so
we
can
be
there,
but
it's
sort
of
like
there's
a
lot
of
late
sessions
and
they're
gonna
vote
and
only
one
gets
to
go
all
right.
Let's,
let's
see
how
that
goes.
C
D
B
For
1.6
I
know
there's
debate
about
what
the
right
solution
is,
but
I
think
the
right
solution.
This
field
will
block
sand.
That
will
give
us
a
framework
for
making
views
slideshows,
and
I
think
it
could
probably
solve
the
garbage
collection
image
is
going
away
and
blocks
to
because
we
could
give
ckeditor
to
those
few
little
entity
blocks
and
not
to
the
text
box
and
those
with
your
content.
Blocks
and
xbox
would
give
your
configuration
blocks.
C
A
Ok,
I
think
I
think
that
might
be
it
we're
at
the
top
of
the
hour
to
though
yay.
Thank
you
everybody
for
participating.
Thank
you.
Everybody
for
watching.
We've
got
a
busy
couple
of
weeks
ahead
of
us,
but
it's
exciting.
So
ok!
Well,
thank
you.
Everybody
happy
back
to
update
will
see
you
guys
in
the
issue.
Queue.