►
From YouTube: Backdrop CMS Weekly
Description
Backdrop CMS, the comprehesive content management system for small - med business & non-profits.
A
A
So
will
work
towards
creating
the
same
kind
of
product
with
a
very
different
code
style
in
and
architecture
in
the
back
end.
While
we're
doing
these
things,
we're
hoping
to
fix
bugs
bugs
that
are
existing
in
triple
seven
in
tripoli,
as
well
as
any
other
beds.
So
we
find
along
the
way
and
hopefully
we'll
be
able
to
simplify
some
of
the
existing
systems.
A
We
already
understand
that
drupal
7
is
too
complicated
too
hard
for
new
people
to
learn
too
slow
to
develop
for
Emily
want
to
improve
those
things
by
simplifying
all
the
systems
that
are
already
there.
We
can
only
do
that
without
breaking
api's,
because
one
of
the
things
that
we're
trying
to
focus
on
is
making
backed
up
as
similar
to
Drupal
7
as
possible.
So
we're
going
to
simplify
things
as
long
as
we
don't
have
to
change.
A
Ap
is
very
much,
and
the
same
is
true
for
new
features
will
add
those
new
features
for
things
that
we
think
are
super
important,
but
as
long
as
it
doesn't
require
too
much
change,
so
Drupal
7
and
backdrop
should
be
very
similar
backdrop.
On
a
backdrop
to
should
be
very
similar
to
the
API
change
is
going
to
be
kept
to
a
minimum
the
whole
time.
Our
timeline
we're
hoping
to
have
backdrop
1
point
0
point
0
out
this
fall.
It
is
now
fall,
so
it
is
the
season
which
means.
A
We've
got
to
start
wrapping
up
all
the
stuff
that
we're
working
on
giving
the
the
product
its
last
bit
of
polish
and
trying
to
make
something
that
is
I'm
going
to
be
a
really
convincing
tool
for
people
to
use
here
in
the
next
few
months,
which
will
be
great,
and
then
we
get
to
start
working
on
creating
sites
with
it
and
creating
a
contributor
in
seeing
how
all
that
goes
to.
After
one
point,
0
point
0
is
released.
A
We
will
continue
to
release
updates
on
a
regular
basis,
so
things
that
don't
get
into
one
point,
0
point
0
will
get
into
1.1
or
1.2
bug,
fixes
Lyon
to
those
minor
releases
and
hopefully
will
continue
to
move
the
project
forward
on
a
rapid
pace.
It'll
be
exciting,
so
things
that
we're
working
on
we've
got
three
major
new
projects
that
went
into
backdrop.
1
point
0
point.
B
A
B
So
since
last
week
after
the
meeting
I
published
a
new
preview
video
of
layouts
and
where
they
are
currently,
which
has
been
gathering
a
lot
of
interest
from
from
people
out
there,
Boyan
came
back
and
did
a
UX
review
of
it
and
made
some
great
suggestions
that
that
will
need
to
implement,
as
far
as
merging
into
backdrop
core
currently
working
on
resolving
all
of
the
test
failures
which
really
are
not
so
much
test
failures.
They're,
really
just
adjustments
that
need
to
be
made
to
our
tests
since
block
module
is
no
longer
responsible
for
positioning
blocks.
B
There's
just
like
there's
dozens
of
tests
that
all
assume
that
block
module
is
the
tool
for
doing
layouts,
so
I
have
to
update
and
with
the
tests
to
make
them
work
with
the
new
code
base.
But
that's
going
swimmingly
I
keep
pushing
pretty
regularly
almost
daily
basis
continuing
to
get
the
tests
going
about
three-quarters
of
the
way
through
fixing
all
of
the
tests
and
then,
after
that,
the
big
holdup
is
that
we
need
to
write
replacement
tests
that
check
the
basic
layout
functionality
and
just
make
sure
the
layout
system
is
fully
functioning
for
anyone.
B
That's
out
there
that
wants
to
help
with
that
endeavor
issue.
86.
In
the
backdrop
issue
queue
there's
a
link
to
the
sandbox.
Well,
oh
that
we're
all
of
this
work
is
going
on.
It's
not
quite
pull
request
ready
because
the
tests
are
still
failing,
but
it
is.
It
is
ready
for
end
user
testing
to
see
if
we
can
figure
out
any
problems
within
the
codebase
just
from
users
clicking
around
and
trying
out
different
things.
So
it's
looking
really
good.
B
A
A
A
It
is
gonna
solve
a
lot
of
our
problems
with
the
theme
layer
and
a
bunch
of
other
stuff,
as
well
so
yeah
blocks
and
layouts
and
other
things
that
we're
working
on
things
that
you
can't
live
without
cmi
config
management-
and
this
is
an
it-
doesn't
exist
in
Drupal
7.
We
currently
are
using
this
features
module
to
manage
how
we
deploy
changes
from
local
to
live
or
from
one
site
to
another.
It's
a
it's
the
best
tool.
A
We
have
it's
the
only
tool
we
really
have
to
nor
to
manage
this,
and
it's
not
ideal
people
work
features
for
a
while
start
to
see
it's
its
shortcomings
and
and
that's
why
we've
decided
as
a
community
that
we
need
a
better
solution.
Add
your
blade
is
implemented.
Cmi
backdrop
has
also
implemented
it.
So
if
you
want
to
keep
using
all
of
your
Drupal
7
like,
but
you
need
CM
I
want
to
use
it
right
now
is
gonna,
be
huge
killer
feature
for
backdrop.
A
We've
got
drupal
7
like
thing
with
CM
I
in
it,
so
it's
basically
Drupal
7
plus
am
I,
which
is
great
and
and
we've
got
the
subsystem
and
core
already.
We've
got
some
conversions
underway,
which
is
great.
We
do
need
to
finish
our
conversions
before
we
can
release
backdrop.
1
point
0
point
0.
This
is
a
really
splock
or
for
us
if
we
have
same
iron
core,
but
we
aren't
using
it
for
things
like
content
types
of
fields.
We
don't
really
have
cmi
yeah
the
system's
there.
A
People
can
write
code
against
it,
but
if
we
can't
get
our
primary
building
blocks
of
what
makes
a
backdrop
site
exporting
to
code,
then
it's
not
really
going
to
be
as
go
to
selling
points
velocity.
So
we
need
some
help
with
that.
Since
I
last
week,
we've
started
converting
some
other
stuff,
so
theme
setting.
So
it's
an
issue
that
I've
been
working
on
for
a
while
and
ran
into
some
problems
with
it
and
make
him
in
to
fix
them.
A
It
was
great,
so
we've
got
theme
settings
converted,
we've
also
moved
locations
of
things
to
make
them
make
a
little
bit
more
sense.
A
color
module.
Also
settings
are
now
using
SI
mi.
Sorry
we're
getting
things
one
piece
of
time
converted.
It
would
be
great
to
have
kind
of
more
hands
on
deck
and
help
us
with
some
of
the
bigger
conversions
so
that
we
can
move
that
forward
to,
and
that
will
of
course,
hold
up
I
really.
So
that
is
our
next
highest
priority
item.
A
Other
things
that
we're
working
on
major
things
that
have
happened
in
backdrop.
Core
is
moving
views
into
Corso
visas.
The
number
one
downloaded
contributed
module.
It
helps
you
build
listings
of
things.
It's
in
porringer
blade
it's
in
foreign
backdrop,
and
what
we
need
to
do
is
convert
some
of
the
listings
that
come
from
core
into
a
view.
So,
like
your
front
page
by
default,
that
was
a
list
of
nodes
right
in
in
Drupal
7.
A
We
need
that
to
be
a
view
of
notes
in
backtrack,
so
having
someone
build
that
view
for
us
and
get
that
config
file,
because
views
will
save
to
config
I'm
ready
for
us
to
include
would
be
great
same
thing
for
other
listings
that
are
in
core
and
we've
got
an
issue
there
and
that
will
help
guide
people
to
which
things
need
to
be
converted
in
what
state
they're
in.
So
if
anyone
has
site
building
skills
and
want
to
help
us
set
up
the
views,
that
would
be
a
great
first
step
for
that
also.
A
So
some
of
those
conversions
are
really
straightforward.
Some
of
the
ones
like
admin
listings
are
a
little
bit
more
involved,
but
I
think
getting
the
front
end
once
converted
is
highest
priority
and
that's
probably
our
may
be
our
only
release.
Blocker
related
to
views
having
it
in
core
was
the
biggest
thing.
We've
got
that
I
think.
If
we
had
to
ship
without
admin
listings
converted,
we
would
be
fine.
We
could
can
change
that
at
some
point
later.
A
A
C
B
A
So
other
things
we're
working
on
we're
trying
to
keep
up
with
what
your
pool
is
doing
and
and
we're
doing
that
in
two
different
ways:
number
one.
We
want
to
make
sure
that
everything
that
has
been
committed
to
latest
versions
of
Drupal
7,
all
those
bugs
have
been
fixed
and
those
improvements
have
been
made
to
backdrop
as
well
so
trying
to
make
sure
that
we
go
through
the
commit
log
for
lease
person
triple
seven
and
get
those
commits
poured
it
over.
A
It
looks
like
we've
got
one
issue
left
with
a
couple
of
commits
there
that
need
to
be
added
or
merged
in,
and
we
also
need
to
make
sure
that
any
security
fixes
that
have
been
applied
to
Drupal
7
also
happen
to
backdrop,
and
we've
got
three
of
those
remaining
and
then
we're
also
taking
a
look
at
what
Drupal
8
is
doing.
There's.
A
A
If
you
only
got
a
couple
minutes
and
you
want
to
tackle
those
they're
low-hanging
so
to
speak,
and
then
there's
a
couple
of
minor
things
that
we're
working
on
to
these
are
not
release
blockers,
but
they
are
things
that
we
would
like
to
improve
in
backdrop.
The
first
one
is
making
sure
that
backdrop
looks
and
feels
different
from
Drupal.
So
if
you
install
it-
and
you
start
using
it,
it
shouldn't
feel
like
you're,
using
Drupal,
8
or
Drupal
7.
It
should
stand
on
its
own
and
we're
doing
that
in
a
couple
of
different
ways.
A
We've
got
a
new
administration
theme,
look
and
feel
under
way.
We
reconnected
with
our
designer
Julia
last
week
and
made
sure
that
she,
you
know,
was
able
to
do
what
she
needed
to
do
to
our
style
guide,
which
is
also
on
github,
so
she's
going
to
go
ahead
and
make
some
updates
there
and
then
we'll
have
kind
of
a
good
starting
point
for
what
we
want.
Our
administration
experience
to
feel
like
and
we'll
go
ahead
and
create
some
issues
that
involve
incorporating
her
code
into
the
admin
theme
for
backdrop.
A
Another
thing
that
we're
looking
at
doing
is
cleaning
up
the
entire
theme
system.
We
want
to
make
backdrop
more
appealing
to
front-end
developers.
It's
been
problematic
for
Drupal
for
a
while,
and
we
want
to
kind
of
solve
some
of
those
problems.
We've
done
a
bunch
of
work
in
Drupal
8
in
consolidating
things
and
making
things
make
a
little
bit
more
sense.
A
lot
of
the
work
that's
happened
to
Jubilee
can
also
happen
to
bad
rap.
A
It
was
an
all
conversion
of
template
files
to
twig,
there's
much
of
other
stuff,
and
we've
got
an
issue
for
backdrop
that
involves
making
those
same
things.
The
same
kind
of
changes
for
us
they're
going
to
be
a
little
bit
different
for
backdrop,
because
of
the
way
that
we're
handling
blocks
and
layouts
our
theme
region
problems
are
solved
in
different
ways
in
each
system.
A
So
our
theme
system
cleanup,
has
been
kind
of
on
hold
or
working
around
how
the
blocks
and
layout
system
is
coming
together,
but
it
looks
like
all
that's
fitting
together
really
nicely
now.
I've
got
kind
of
a
good
plan
and
a
good
campinas
for
how
everything
is
going
to
work.
So
that's
starting
to
get
a
little
bit
more
focused
now
too,
which
is
great
and
then
some
other
things
that
we'd
like
to
improve
is
just
general
user
experience.
A
Drupal
has
a
reputation
of
being
kind
of
clunky
and
doesn't
feel
great
when
you're
an
editor
and
you're
trying
to
create
content.
So
we've
got
some
ideas
for
how
to
make
that
process
a
little
bit
better.
We've
already
done
a
couple
of
terminology
updates
and
moved
things
around
and
then
in
the
administrative
back-end
kind
of
make
it
make
a
little
more
sense.
There
we're
going
to
do
a
little
bit
more
of
that,
maybe
not
too
much
more.
A
So
we
want
to
still
seem
familiar
people,
and
then
we
also
want
to
add
rich
text
editor
in
core.
This
is
something
that
is
really
near
and
dear
to
our
hearts,
but,
of
course,
and
not
maybe
is
urging
to
some
of
these
other
things.
So
if
we
don't
get
it
in
in
backdrop,
1
point
0
point
0.
We
can
add
it
shortly
thereafter,
because
we
think
we
can
probably
add
that
editor
without
breaking
too
many
existing
API.
A
So
if
we
can
do
it
by
adding
some
new
AP
is
then
that
doesn't
need
to
happen
before
the
initial
release.
So,
thanks
for
working
on
their
minor
projects
that
aren't
major
release,
blockers
are
improving
the
identity,
cleaning
up
the
theme
system
and
improving
the
user
experience
and
I'm
I.
We've
also
started
a
new
section,
a
list
of
things
that
need
a
kind
of
a
final
sign
off
before
we
release,
and
this
list
is
going
to
get
longer
as
we
get
closer
to
release
here.
A
So
we
did
a
bunch
of
clean-up
on
all
of
our
CSS
files.
It
would
be
good
to
kind
of
have
someone
do
a
review
of
all
of
them.
Kind
of
a
very
high
level
make
sure
all
the
CSS
files
are
in
a
folder,
labeled
CSS
and
that
they
are
all
using
the
correct
formatting
matching
our
style,
our
coding
style
and
just
making
sure
that
everything
is
kind
of
in
order
ready
for
release.
It
should
be
great
and,
as
we
wrap
up,
some
of
these
other
issues
will
do
the
same
kind
of
like.
A
A
We
need
a
review
of
and
right
before,
we
release
we'll
just
kind
of
going
on
that
list
and
go
check,
check,
check,
check.
Okay,
it
all
looks
good,
let's
go,
and
you
know
if
we
we
can
get
them
all
signed
off
on
that's
great.
If
we
can't
we'll
just
know
that
we
we
haven't
reviewed
that
yet,
and
we
can
maybe
take
a
look
at
that
down
the
road
as
well,
so
we're
getting
close,
pretty
exciting,
so
yeah,
that's
project,
other
things.
We
should
talk
about
this
weekly
meeting.
A
We
have
a
point
here
where
we
can
announce
any
updates
from
the
project
management
committee.
So
if
anything
has
been
isolated
in
the
issue,
queue
and
needs
a
decision
made
about
it
like
something
that
the
wooded
affects
the
direction
of
the
entire
project.
That'll
get
escalated,
the
project
management
committee,
a
discussion-
will
be
had
and
then
a
decision
we
made
and
we
passed
back
down
to
either
court
committers
or
people
ask
the
question
and
announced
in
this
meeting.
We
don't
have
any
updates
right
now,
but
in
the
future,
if
those
things
continue
to
come
up.
A
This
is
the
time
we'll
be
doing
that
so
no
updates
today,
but
we're
preserving
this
spot
for
future
announcements
and
then
there's
a
bunch
of
other
stuff
that
we're
working
on
as
well
that
aren't
related
to
backdrop
the
project,
but
that
I
related
to
backdrop,
the
community.
Oh,
we
have
a
primary
website
backdrop
CMS
org.
A
So
we
have
an
API
site
now,
just
really
have
a
theme
on
it,
but
it
does
pull
from
our
code
base,
which
is
great.
So
if
you
want
to
check
backdrops
api's,
you
can
go
to
API
backdrop,
CMS
org
and
check
us
out
there,
which
is
great
we're
working
on
adding
change
records
there,
which
is
something
that
Luke
set
up
for
us.
We've
got
a
content
type.
We
have
a
list
of
things
that,
in
our
github
issue,
queue
that
need
change
records
and
there's
also
a
bunch
of
stuff
that
happened
in
early
Drupal,
8
development.
A
That's
happened
to
backdrop,
but
we
also
need
to
include
there
as
well
so
making
sure
that
our
change
records
that
happen
before
we
work
the
project
get
included.
So
people
can
see
the
entire
set
of
differences,
not
just
what
we've
done
since
we've
been
working
on
it
and
we
have
run
who's
volunteered
to
help
us
right.
Some
of
that
documentation.
He
can
take
a
look
at
the
existing
change
records
and
forth
them
over.
Make
sure
that
you
know
a
change
record
as
it
exists
on
drupal.
A
Org,
probably
is
not
going
to
be
the
same
as
a
change
record
on
dr.
applicants
triples
changed
a
lot
more
since
when
we
took
over
the
change,
so
we're
gonna
need
a
little
clean
up
on
some
of
those
as
well
make
sure
they're
still
accurate
and
then
other
things
where
we
can
include
a
update
server.
So
when
you're
running
a
back
drop
site
and
it
checks
to
see
if
it
self
and
its
modules
are
up
to
date,
it'll
need
somewhere
to
check
and
order
to
figure
that
out.
A
So
we've
got
to
build
one
of
those
and
we
need
to
get
hub
service.
This
is
a
1200.
Anyone
who
is
creating
a
controller
theme
on
github
to
register
that
project
as
a
backdrop
project
and
then
backdrop
CMS
org.
The
primary
website
will
aggregate
a
list
of
all
of
the
project
on
github
and
give
you
an
easy
interface
to
search
and
find,
for
example,
I
need
a
module.
That
Elise
is
my
paths
right.
You
can
type
that
into
the
backdrop
website.
A
Then
it'll
point
you
would
a
github
project
which
I
think
will
be
super
important,
so
we
obviously
have
a
lot
of
work
to
do.
It
is
fall,
so
we
don't
agree
much
time
to
do
it
in
so
we're
going
to
be
doing
a
sprint
every
Thursday
afternoon.
After
this
meeting,
we
work
online
together
on
IRC.
Our
IRC
channel
is
pound.
Backdrop
will
also
be
in
the
issue
queue
today.
So
if
you
can't
join
an
IRC,
but
you
want
to
participate
anyway.
A
If
you
check
the
github
issue
queue,
you
can
help
weigh
in
on
feedback.
We've
had
about
things
that
we
need
to
do
or
test
things
for
us
right,
pull
requests.
If
you're
feeling
brave,
we
could
use
help
with
lots
of
stuff
and
we'll
be
doing
that
all
afternoon,
and
then
we've
also
finalized
our
next
in
real
life,
sprint,
which
will
be
at
bad
camp,
which
is
in
November.
A
We
have
blocked
off
a
table
in
the
coder
area
on
Sunday
November
night,
where
we
can
get
some
work
done
on
I'm
back
drop
the
project,
so
we'll
probably
do
a
session
about
it
on
saturday
we'll
see,
there's
nothing
since
scheduled.
Yeah
so
we're
hoping
it'll
be
saturday,
but
hopefully
we'll
do
the
session
first
and
then
the
sprint
after,
but
we'll
see
it
might
have
to
go
the
other
way
around
so
in
real
life
sprint
on
Sunday,
November
9th.
A
If
you
want
to
come
to
the
area
drupalcamp,
it's
a
good
place
to
meet
everyone,
and
it's
just
a
great
camp
anyway,
might
be
personally
biased
and
then
there's
a
bunch
of
other
stuff
we're
doing
too.
We
have
been
requested
to
give
a
talk
at
the
Pacific
Northwest
Drupal
summit,
so
I
submitted
one
on
backdrop,
I'm
not
sure.
If
it's
been
accepted,
I
haven't
heard
anything
from
them,
yet
it
might
still
be
early
and
they
don't
know
what
they're
doing
yet.
But
I'll
follow
up
on
that
we've
also
been.
A
They
also
asked
us
to
speak
at
so
I
submitted
a
session
to
the
South
America
camp
about
backdrop
and
asked
the
person
who
requested
that
I
submitted
to
run
that
by
the
people
in
charge
of
the
Commerce
just
to
make
sure
that
it
was
okay
and
even
though
he
really
wanted
me
to
submit
the
session.
Apparently,
the
drupal
association
has
decided
that
backdrop.
Talks
shouldn't
be
sessions
at
drupal
events
that
they
can
be
bought
because,
apparently
all
sessions
at
drupal
conferences
need
to
be
about
web
designer
development.
A
That's
okay.
I
think
it's
fine!
I'm
excited
that.
We
have
been
requested
by
the
organizers
of
these
conferences
to
give
talks
at
these
events
and
if
we
aren't
actually
allowed
to
give
the
top.
I
think
that
that
its
fine
there's
still
a
demand
in
the
community
for
people
hear
about
it
and
as
long
as
we
continue
to
give
talks
on
places
and
post
videos,
then
I'll
here
so
I
think
it'll
be
okay,
and
would
you
go
to
the
event
anyway?
A
We'll
do
talks
on
web
former
panels
or
bad
camper
I,
don't
know
something
else
more
durability
to
keep
everyone
happy,
so
yeah,
we'll
probably
not
be
presenting
on
backdrop
at
these
places
that
I'm
super
excited
that
we've
been
asked
anyway.
Okay,
well,
there's
no
one
else
here
other
than
me
and
Nate
today,
but
I
can
see
that
there
are
some
people
watching
which
is
nice.
A
B
I,
don't
think
so.
I'm
just
rolling
along
with
thanks
face
there's
a
number
of
poll
requests
that
are
out
there
I'm
getting
to
review
them
as
as
soon
as
I
can.
So,
if
you
were
one
of
those
people
who
is
submitted
a
pull
request,
thank
you
very
much
and
we'll
get
to
it
soon.
Oh
and
other
people
that
have
submitted
for
requests.
It's
not
a
bad
idea
to
review
other
people's
for
requests
that
would
make
I
were
doing
my
job
a
lot
easier
and
speed
up
and
speed
up
the
whole
process.