►
From YouTube: Backdrop CMS weekly 7/24
Description
Backdrop CMS
A
A
So
this
is
going
to
be
a
system,
that's
very
similar
to
Drupal
7,
but
hopefully
a
little
easier
to
understand.
We're
also
going
to
be
adding
some
new
features
to
Drupal
7.
So
there's
a
lot
of
new
features.
Interpolate,
we
want
to
add
new
features
to
backdrop
as
well,
but
same
rules
apply.
We're
only
gonna
be
adding
these
new
features,
and
we
don't
have
to
change
APA's
very
much
to
do
so,
and
our
new
features
need
to
be
applicable
to
the
eighty
percent.
A
So
we
aren't
going
to
be
adding
any
new
edge
cases,
just
the
only
to
be
adding
kind
of
lowest
common
denominator
features.
Our
timeline
for
backdrop
has
recently
changed.
O
year.
We've
been
talking
about
shipping
this
product
this
summer.
Part
of
the
reason
that
we
set
that
deadline
is
because
we
wanted
to
be
sure
we
were
out
before
tripoli,
but
it
looks
like
drupal.
A
8
is
not
as
near
as
we
perhaps
might
have
thought
it
would
they're
still
kind
of
struggling
to
get
a
bunch
of
their
stuff
done,
and
so
I
think
that
we
should
use
the
time
that
we
have
to
spend
working
on
making
backdrop
better
finishing
the
tasks
that
we
have
in
front
of
us
and
making
sure
that
we
have
a
really
good,
solid
system
to
compare
to
Drupal
8
when
both
of
them
are
out.
So
we're
going
to
be
pushing
the
release
date
from
backdraft
from
summer
2014
to
fall.
A
2014
and
that'll
give
us
time
to
finish
up
the
blocks
and
layout
system
figure
out
how
the
new
theme
system
is
going
to
fit
with
layouts.
Do
some
general
cleanup
on
user
interface,
user
experience
and
release
a
really
good,
solid,
polished
product,
which
I
think
will
be
great?
Let's
see
before
we
get
into
our
project
progress
report
I
want
to
kind
of
do
a
recap
of
Drupal
corn
or
drupal
corn
camp
as
its
referred
to
in
Iowa,
which
is
where
nate
and
I
were
last
week.
We
had
a
really
great
time
there.
A
So
it
was
a
good
first
introduction
to
them
and
I
think
it
got
some
good
conversations
going
and
we
had
our
first
public
sprint
on
Sunday,
which
we
were
a
little
bit
worried
about,
but
ended
up,
working
out
really.
Well,
we
had
a
backdrop
sponsored
Drupal
8
sprint
today,
as
well
as
backdrop
which
was
great
and
then
at
our
table.
A
A
The
people
had
filed
have
already
been
merged
since
then,
so
I
thought
that
was
really
great
and
generally
at
the
feedback,
was
really
good
about
about
back
up
there
a
whole
bunch
of
people
saying
that
was
what
they
wanted,
and
that
was
encouraging
to
hear
that,
and
it's
been
kind
of
a
while,
since
we've
had
something
to
show
people
and
and
to
have
them
get
their
hands
on
it
be
like.
Oh,
this
makes
sense
that
was
good
to
hear
too
so.
A
B
A
A
New
interface
for
setting
up,
layouts
and
layouts
are
going
to
be
completely
separate
from
the
theme
so
that
your
team
will
really
become
more
of
a
skin
and
it
will
be
able
to
skin
any
number
of
provided
layouts,
either
layouts
that
come
for
layouts
that
come
from
other
and
kinship
projects,
but
I
think
it'll
finally
start
to.
We
can
separate
those
two
things
that
people
will
kind
of
start,
you
being
just
being
able
to
see
a
theme.
A
B
So
there's
a
there,
isn't
any
new
progress
since
I
posted
the
video
last
week,
but
if
you'd
like
to
check
out
blocks
and
layouts
and
where
we
currently
are
with
that,
you
can
check
out
a
youtube
channel,
youtube.com,
slash
backdrop
CMS
and
you
can
see
a
screen
or
a
screencast
of
where
blocks
and
layouts
currently
aren't
or
we're
all.
Looking
really
pretty
good.
We've
got
the
base
system
in
place.
We've
got
conditionals,
we've
got
it
all.
Saving
the
cmi
we've
got
dragon
drop
layouts.
B
The
biggest
parts
that
it's
currently
missing
is
that
it
sound
great
and
fully
into
the
theme
system.
So
it's
not
replacing
regions
at
this
point
so
that
just
is
probably
the
biggest
sticking
point
that
is
left.
But
after
that
we
still
have
a
lot
more
work
to
do
like
building
out
all
the
necessary
blocks
that
we
need
and
oh
and
integrating,
and
so
that
so
you
get
contexts
into
the
blocks
and
things
like
that.
B
We've
got
a
bunch
of
work
yet
to
be,
but
but
it's
functional
and
you
can
use
it
and
it's
pretty
exciting
to
to
look
at
the
overall
architecture.
So
progress
on
that
is
it
issue
86.
There
are
currently
two
branches
of
work,
one
that
is
like
the
latest
work
that
I'm
doing
and
then
there's
also
a
branch
that
is
just
like
a
stable
branch
that
you
can
check
out.
That
is
like
a
layout
demo
branch
or
something
like
that.
But
all
that
information
is
an
issue
86
and-
and
you
get
more
information
about
there.
A
That's
great
alright.
So
the
next
issue
on
our
agenda
here
is
using
core
views,
as
you
all
probably
know,
is
the
number
one
download
contributed
module
for
Drupal
hi,
it's
in
corporate
Jubilee
and
I
think
that
it's
gonna
be
a
huge
advantage
for
backdrop.
It's
kind
of
something
that
sets
for
drupal
apart
from
wordpress,
so
having
an
impact.
Job
will
be
huge
for
us
as
well.
I
know
that
at
the
sprint
this
weekend
we
got
a
bunch
of
people
tasked
on
views.
A
If
you
don't
want
these
on
your
site,
you
can
find
some
way
to
turn
it
off,
but
it's
the
kind
of
thing
where,
if
we're
going
to
be
replacing
like
the
node
page
and
turn
listing
pages
and
all
the
administrative
pages
with
views,
it
really
should
be
required
in
it,
and
you
shouldn't
get
this
right
off,
so
we've
removed
that
from
the
interface
place
for
the
eighty
percent.
Think
that's
what
we're
going
to
want
so
I
think
that's
good.
A
In
views,
UI
is
also
turned
on
by
default,
so
people
won't
have
kind
of
this
magical
experience
of
how
did
this
thing
it
on
my
page,
they'll
be
able
to
just
go
and
edit
it
right
away,
and
then
we
can
write
some
documentation
somewhere
about
like.
If
you
want
in
performance
improvements,
you
can
turn
it
off
on
live.
That
is
a
good
practice,
but
it
is
hard
to
enforce
as
we
found
in
the
real
world,
so
we're
not
going
to
leave
it
off
by
default
so
and
we've.
B
A
All
right
so
then
ice
major
system,
we're
working
on
is
a
config
management.
This
is
the
separation
of
configuration
from
content
in
in
Drupal
7.
Both
of
these
things
were
stored
in
database,
sometimes
in
the
same
place
and
ives
in
different
places,
and
it
made
it
really
hard
to
deploy
new
features
and
even
new
sites
from
one
environment
to
another.
Pulling
the
configuration
out
of
database
and
storing
it
in
files
is
going
to
make
that
much
easier.
A
Backdrop
is
rewritten
from
the
ground
up
to
use
CM
I,
just
liked
your
blades
and
our
systems
a
little
different
than
your
blades,
but
we
think
it's
that
more
in
line
with
our
projects,
goals
and
we've
been
making
a
bunch
of
progress
since
the
beginning
of
the
summer
on
getting
all
of
the
cmi
converted
over
we've
got
almost
all
of
the
variables
converted
and
a
bunch
of
subsystems
are
now
underway
as
well.
So
I
don't
know
if
me
or
probably
wanna
give
us
an
update
on
De
my
stuff.
C
B
B
Yeah,
I'm
not
sure
if
John
is
actually
gonna
get
to
that.
I
think
that
we
started
him
on
the
views,
conversions
for
comparing
the
user
and
content
listings,
because
those
were
related
to
actions.
Ok,
tom,
but
I'm,
not
really
sure.
If
he's
gonna
get
around
to
doing
actions
themselves,
we
might
need
to
touch
base
with
him.
Ok
I
thought
he
was
doing
the
other.
A
Way
around
actions,
first,
an
envious
but
I,
don't
know,
ok
well,
either
way,
there's
a
whole
bunch
of
progress
going
on,
which
I
think
is
great
and
we
got
a
whole
bunch
of
new
people
to
look
at
the
cmi
system
as
well.
So
getting
some
feedback
on
the
way
that
backdrop
did.
That
I
think
will
be
good
for
us
too.
So
that's
good
all
right.
A
So
there
are
three
major
kind
of
release,
block
or
areas
that
we're
working
on
and
they
also
be
moving
along
just
great
and
we've
got
a
whole
bunch
of
other
stuff
that
we're
trying
to
do
at
the
same
time
as
well,
including
keeping
up
with
Drupal
two
major
ways:
we've
got
craft
sports
from
Drupal
7,
so
these
are
commits
that
have
been
made
to
Drupal
7.
Since
we
forked
backdrop,
we
want
to
make
sure
that
any
bug
fixes
that
have
gone
into
Drupal
7
are
also
in
backdrop.
A
A
Don't
know
that
we
have
a
meta
issue
for
729,
but
there's
I
know
a
couple
of
serious
regressions
with
729
that
we
need
to
figure
out
how
to
fix
either
the
same
way
the
triples
going
to
fix
them
or
a
different
way
for
back
job.
So
we
should
set
up
a
meta
issue
for
all
the
stuff
that
we
can
merge
in
right
away,
which
would
be
great
I
can
do
that
today,
but
I
think
all
the
other
one
so
John
looks
like
we've
got
security,
one
security
issue,
that's
open
and
then
all.
A
All
of
the
issues
from
7,
24,
27,
27
I,
think
are
in
birthday.
I
think
this
agenda
might
not
be
up
to
date
and
then
728
should
also
I've
got
the
last
five
of
those
in
a
polar
crest
right
now
getting
tested.
So
I
think
we
should
be
close
on
that
as
well.
So
all
that
stuff
should
be
729,
I,
think
most
of
the
commits
from
729
and
I'll-
probably
just
go
straight
and
no
problem,
except
for
them.
We've
got
to
figure
out
what's
up
with
the
regression
issue,
so
that'll
require
a
little
examination.
A
B
A
A
We
shouldn't
get
make
sure
that
we've
got
our
stuff
being
consistent,
but
if
it's
not
not
super
important,
those
might
get
to
wait
and
then
the
JavaScript
we're
almost
done
where
74
out
of
109,
so
I'll
look
over
those
two
and
I
think
what's
left
of
those
may
also
be
less
important
or
can
be
handled
later.
So
it's
good
for
minor
things
that
we're
working
on
is
you're,
not
release
blocking
the
things
that
are
important
for
us
and
we're
working
on
rebranding
me.
A
Installer
page
I
put
this
issue
back
on
the
agenda
just
because
we
also
had
a
bunch
of
progress
made
this
weekend
at
the
sprint
we
got
Anton
to
make
us
some
pretty
designs
for
what
the
backdraft
and
seller
should
look
like.
That
includes
elements
of
our
new
branding,
our
new
logo
and
kind
of
some,
some
of
the
same
general
cleanup
that
happened
on
the
Drupal,
8,
installer
and
I'm
working
on
today,
trying
to
code
that
up.
A
A
Don't
think,
there's
been
any
movement
on
that
lately,
so
it
might
be
good
to
reach
back
touch
base
with
the
a
designer
there
and
make
sure
that
that's
going
forward
to
and
then
we've
got
some
user
experience,
improvements
that
are
going
on
also
husband,
any
movement
yet
on
the
rich
text
editor.
But
now
with
a
launch
scheduled
for
fall,
I
think
we
might
be
able
to
get
that
in
it'll,
be
awesome
and
then
terminology
updates
that
we've
been
making
a
lot
of
progress
on
this
too.
A
We've
got
a
bunch
of
stuff,
that's
already
moved
around.
We
took
the
permissions
page
in
the
roles
page
and
move
them
underneath
configuration
and
a
little
clean
up
around
the
page
titles
on
those
and
then
we're
also
working
on
changing
the
navigation
links
to
the
modules
page
and
reorganizing
top-level
items.
Just
so
that
people
can
find
things
a
little
bit
more
easily.
A
We've
got
content
user
accounts
groups
together,
followed
by
modules
and
themes
that
are
grouped
together,
followed
by
a
structure
and
config
which
are
grouped
together,
not
group
together,
single
links,
but
next
to
each
other
in
in
the
menu
I.
Think
we'll
make
a
little
bit
more
sense
and
we're
going
to
rebrand
that
the
way
it
works
in
the
admin
menu
now
the
top
level
items
aren't,
wants
people
click
on
so
they're
more
like
category
headings,
and
when
you
drop
down
you
get
to
the
slash
list.
A
Page,
that's
for
clickonce
that
I'll
have
a
different
name
on
it.
So,
for
example,
in
the
themes
list,
the
top
level,
winces
appearance
and
the
second
level
winces
themes
and
the
modules
page,
the
top
one
will
say
functionality
in
the
second
one
will
say
modules,
so
I
think
that'll
kind
of
help
teach
people
that
themes
control
your
site's
appearance
modules,
control
your
site's
functionality.
People
are
looking
for,
the
keyword,
module
will
still
be
able
to
find
it
and
I
think
just
makes
it
a
little
bit
more
sense.
A
C
B
There's
a
big
much
bigger
discussion
ended
up
opening
up
there,
but
I.
Don't
think
that
that
will
happen
right
away.
I
think
that'll
happen
like
there
was
a
suggestion
to
reorganize
pretty
much
everything,
but
at
this
point
like
we're
just
titling
things,
so
they
make
more
sense
of
a
hierarchical
structure,
bone
on
actually
changing
any
pads
or
changing
where
they
go
or
the
nesting
or
anything
like
that.
B
So
at
this
point
we're
just
setting
it
up
so
that
it
works
better
in
a
hierarchical
structure
like
previously,
it
was
like
content
content
and
that
wasn't
wasn't
helpful
and
people
people
you
know
so
we're
making
it.
So
the
top
level
item
is
different
than
the
sublevel
item
and
I
think
that
is
in
a
really
good
spot.
If
I
get
any
additional
feedback
that
we
can
get
quite
love
to,
have
it
in
you
to
a
nine.
A
A
All
right,
lastly,
what
we're
working
on
it
in
minor
improvements
is
themed
system
clean
up.
This
is
generally
just
consolidation
of
stuff
that
is
duplicated
and
a
little
cleanup
up
the
syntax
and
the
template
files,
and
this
will
also
tie
in
nicely
with
our
blocks
and
layout
system
when
we
figure
out
how
layout
templates
we're
going
to
be
working,
so
I
think
there's
a
bunch
more
work
to
it
to
come
there
as
well.
So.
A
The
next
section
of
our
meeting
is
for
updates
from
the
PMC
and
I.
Don't
think
there
are
any
this
week
other
than
the
fact
that
we
have
pushed
their
release
date
from
summer
to
fall
under
peripheral
things
that
we're
working
on
we've
got
an
API
site.
Who
has
that
underway,
creating
a
place
for
us
to
put
our
change
requests
and
they'll
also
have
fed
up
to
actually
with
the
backdrop,
codebase
I'm
an
update
server,
which
we
need
someone
to
work
on.
If
anyone
wants
to
volunteer
for
that,
that
would
be
really
great.
A
You
can
have
a
service
that
will
let
anyone
register
github
project
as
a
backdrop
related
project,
which
I
think
will
be
useful
for
backdrop,
CMS
org
to
aggravate
module,
some
things
that
are
specifically
for
backdrop
and
then
we
also
have
more
work
coming
for
our
primary
I've
site.
Obviously
getting
our
new
logo
on
there
a
little
reprint
right
before
the
launch
would
be
great
too
and
then
prints.
A
We
had
our
Drupal
point
sprint,
which
went
really
well
we're
going
to
be
doing
a
similar
rent
at
triple
cute
twin
cities,
which
is
in
two
weeks
and
then
and
then,
of
course,
every
thursday
after
this
meeting.
So
this
morning,
we've
already
been
sprinting
about
a
passover
will
continue
and
then
I
want
to
see
if
there
were
any
other
questions
or
anything
else
that
we
should
add
to
this
weekly
agenda
comments.
I.
A
Well,
in
that
case,
I
guess
we'll
wrap
this
meeting
and
continue
in
IRC.
So
if
anyone
who's
watching
the
video
right
now
wants
to
ask
us
anything,
you
could
happen.
Irc
our
channel
is
found
backdrop
or,
of
course
you
can
tweet
at
us
or
add
a
comment
on
our
Facebook
page
or
you
can
try
and
add
something
on
google+,
but
I
don't
know
how
it
works.
So
I
would
recommend
avoiding,
haven't
you
have
it
all
possible,
but
yeah.