►
From YouTube: Backdrop CMS Weekly meeting 12/18
Description
Today is the day the backdrop preview release comes out... but first, and update on our status.
A
Today
is
the
day
that
we
are
going
to
release
a
preview
version
of
our
software,
for
everybody
to
download
play
with
and
will
give
us
about
a
month
before
we
have
the
first
one
point:
no
point
o
release.
So
if
anything
critical
comes
up
between
now
and
then
we
have
some
time
to
fix
it,
but
we
at
least
we'll
get
it
out.
So
people
can
start
playing
with
it,
hopefully
over
the
holiday
break
when
they
have
some
free
time
and
aren't
doing
work
and
they'll
like
it
all
excited
about
it.
A
Drupal
8
has
a
ton
of
really
amazing
features
that
we
would
like
to
also
include
in
backdrop
we're
going
to
do
them
differently,
because
we
have
different
audience
in
mind,
we're
going
to
try
and
do
them
in
a
way
that
requires
as
little
changes
possible,
which
means
the
architecture
will
be
similar
to
that
of
Drupal
7.
So
hopefully,
anyone
on
a
triple
7
site
will
be
able
to
move
to
backdrop
eat
more
easily
than
they
would
to
Drupal
8
along
the
way
we're
going
to
be
fixing
bugs.
A
So
anything,
that's
a
bug
and
triple
seven
or
a
bug
in
triple
eight
or
above
only
in
fact,
drop
will
fix
and
hopefully,
we'll
also
be
able
to
simplify
existing
systems.
So
Drupal
7
is
already
a
little
bit
on
the
too
complicated
side.
So,
where
possible,
we're
going
to
be
ripping
things
out,
simplify,
making
implementations
more
direct,
which
hopefully
will
also
improve
performance,
decrease
complexity
and
make
it
easier
to
learn
the
system.
A
However,
we're
going
to
be
really
careful
when
we
add
new
features
and
simplify
existing
systems,
we've
got
to
do
it
without
changing
too
much
of
the
existing
underlying
API.
So
primarily,
we
will
value
the
ability
to
get
from
Drupal
7
to
back
drop
easily
and
if
changing
existing
systems
changes
too
much
simplify
existence
in
the
changes
too
much
we're
not
going
to
be
able
to
do
it
all
once
so,
we
want
to
keep
that
process
of
change,
really
straightforward.
A
Our
timeline
for
getting
backdrop
done
as
I
mentioned
today
we
get
a
preview
version
out.
The
official
release
comes
on
january,
fifteenth,
so
january.
15
2015
will
have
a
version
of
software
that
you
can
download,
install
and
use,
knowing
that
api's
will
no
longer
be
changing
out
from
underneath
you.
A
So
if
you
are
a
contributed
module
author
for
Drupal
7,
now
is
a
good
time
to
start
working
on
getting
your
modules
backdrop
compatible
and
depending
on
the
complexity
of
your
module,
it
could
take
an
hour,
could
take
five
minutes,
but
hopefully,
no
matter
what
it
shouldn't
take
more
than
a
few
days
so,
depending
on
what
you're
doing
should
be
a
fairly
easy
process
to
get
that
module
to
work
on
backdrop.
If
you
are
a
contributed
module
author
and
you
start
working
on
it
on,
you
have
any
feedback
for
us.
A
We
would
love
your
that
because
we
do
a
little
bit
of
time
to
make
some
changes
to
the
API.
So
if
you
have
run
into
problems
between
now
and
January
15,
hopefully
there
won't
be
any
problems.
We've
done
this
a
couple
of
themes
ourselves.
We
have
a
general
idea
of
how
it's
going
to
go,
but
it
is
new
software,
so
feedback
is
definitely
appreciated.
A
A
We
currently
have
rich
text
editing
and
a
couple
of
other
thing:
we're
hoping
to
be
able
to
get
through
all
of
those,
but
if
we
can't
get
them
all
done,
the
one
dot
one
version
will
ship
with
whatever's
in
there
as
bobster
discoverable
fix
the
nice
needed
and
we'll
come
out
with
point
releases,
so
one
dot
0
dot
whatever
as
needed
to
fix
problems
along
the
way.
So
hopefully
we'll
get
a
really
stable
API,
but
we'll
still
be
able
to
add
features
consistently
over
time.
So
you
won't
be
using
software
that
stands
still.
A
It'll
continue
me
being
improved
underneath
you,
but
not
breaking
it
guys
in
terms
of
our
progress.
We
don't
have
any
major
release
blockers
any
of
our
most
important
issues,
so
we
were
working
on
developing
a
configuration
management
tool
which
we've
done.
We
wanted
a
layout
builder
which
we
have
and
we
wanted
a
listing
builder,
which
is
the
views,
module
and
all
of
those
things
are
in
core
and
there
are
no
really
slackers
left
on
any
of
them.
So
that's
really
good.
We
have
follow-up
issues
for
all
of
them.
A
The
follow-up
issues
for
config
management
system
are
for
the
2x
version
of
backdrops
they're,
not
necessarily
worth
discussing
now
our
follow-up
versions
for
the
blocks
and
layout
system.
Our
follow-up
issues
are
related
to
user
interface
and
usability,
so
those
are
things
that
we
are
going
to
need
design
for
we're,
going
to
need
pictures
and
were
going
to
need
to
implement
those
later,
but
because
they're
just
user
interface
to
just
we
should
be
able
to
do
that
at
any
time.
So
those
are
also
not
really
Smuckers,
but
we
would
love
feedback.
A
I
know:
we've
got
someone
working
on
new
designs
for
us,
so
hopefully
we'll
be
able
to
get
those
changes
in
soon
as
well
and
then
same
thing
with
views.
We
don't
have
any
release
blockers
from
her
views
for
for
generating
listings,
but
we
do
have
some
listings
in
core
that
we
would
like
to
convert.
So
if
we
have
anyone
wanting
to
work
on
those
conversions
between
now
in
january,
fifteenth
we
do
still
have
time
to
get
some
of
those
in
we've
got
one
in
we've
got
two
on
the
list
here.
A
B
So
views
conversions
are
probably
like
the
the
most
significant
major
item
that
is
still
being
like
actively
developed
upon,
but
it's
not
not
actually
release
blocking.
If
it
were
really
necessary,
we
could
release
one
point,
0
point
0
without
all
of
the
views
listings,
converted
from
like
hard
coded
listings
in
two
views:
it's
just
that
we're
trying
to
do
those
conversions
beforehand.
We
don't
have
any
real,
serious
blockers
there.
We
converted
admin,
/
content,
/
node
just
this
week,
so
that's
probably
one
of
the
most
complicated
listings
in
court
already
and
it's
it's
converted.
B
B
A
Great,
we
also
have
a
couple
of
other
areas
where
we're
trying
to
stay
up
to
date
with
what's
going
on
with
Drupal,
we
have
a
couple
of
issues
for
Drupal
7
that
we're
trying
to
make
sure
that
all
of
the
bug
fixes
and
improvements
that
are
in
Drupal
7
also
get
poured
it
to
bank
job.
There's
a
handful
of
those
left,
everything
from
Drupal
7.33,
and
we
need
to
review
that
list
and
get
those
into
backdrop.
And
then
we
also
have
two
security
issues
remaining.
A
These
are
security
problems
that
were
fixed
in
Drupal
7
and
also
need
to
be
fixed
in
backdrop.
So
we
need
to
figure
out
what
the
fix
was
for
dribble
and
either
apply
the
same,
fixed,
a
backdrop
or
find
a
different
fix.
That
is
more
in
line
with
our
principles,
but
also
salts
the
security
problem,
and
then
we
also
have
one
issue
remaining
in
terms
of
our
Drupal
8
backports.
We
looked
at
all
of
the
work
that
was
going
on
and
Drupal
8
decided.
That
was
too
much
to
review
and
pulled
out
some
subsets
of
things.
A
We
thought
we're
super
important
for
backdrop.
The
most
important
one,
the
one
that
remains
our
list
right
now
is
related
to
html5
and
I.
Think
we've
gotten
all
of
our
html5
conversions
and
there's
just
one
tiny
template
cleanup
task
left,
which
I
was
working
on
before
this
meeting,
hopefully
trying
to
get
done,
but
didn't
quite
get
it
done.
A
I
only
give
myself
like
10
minutes
so
I'll
get
that
wrapped
up
after
this
meeting,
and
then
we
should
be
done
with
our
Drupal
8
backport
list,
which
is
great
there's
a
couple
of
other
less
important
things
that
we're
working
on
in
backdrop
that
now
we
have
some
time
to
think
about.
Depending
on
you.
A
Number
of
bugs
that
we
get
reported
between
now
and
release
date,
and
that
could
be
things
like
working
on
updating
our
style
guide.
So
this
is
like
making
our
fonts
and
our
color
slightly
different,
so
that
using
backtrack
feels
different
from
using
Drupal
I
know
we
have
someone
who's
asked.
Look
at
that
I!
Don't
think!
They've
actually
looked
at
that
if
we
had
someone
else
that
wanted
to
weigh
in
on
what
our
so
guide
should
look
and
feel
like.
A
We
could
definitely
some
help
in
that
area
and
then
we're
also
cleaning
up
the
team
system.
A
little
bit
big
news
this
week
is
that
we
finally
killed
the
process
layer
and
backdrop
killing
the
process
layer.
Something
worked
really
hard
to
do
in
Drupal.
8
would
do
the
same
thing
in
back
trip
only
we
did
it
in
a
very
different
way,
so
the
process
layer
was
introduced
when
you
needed
to
change
something
later
than
the
pre
process
layer.
A
So
if
you
have
two
things,
for
example,
that
need
to
change
in
the
process
I
er,
but
before
the
template
file,
so
when
you
print
it
in
the
template
file,
you
just
print
it
well,
we
did
in
backdrop,
for
the
most
part
is
take
all
of
that
stuff
that
had
to
happen
late
and
move
it
directly
into
the
template
file.
So
we
don't
call
like
a
Drupal
get
CSS
in
process
and
then
just
print
a
variable
called
CSS
in
the
template
file.
We
print
Drupal
get
CSS,
so
it
just
removes
a
step.
A
It
makes
it
a
little
less
invisible.
What's
actually
going
on.
So
when
you
open
a
template
file,
you
can
see
the
functions
that
are
getting
called
right
there
and,
if
you
wanted
to,
you,
know,
process
those
variables
ahead
of
time.
You
can
move
them
around
in
your
template
file,
but
we've
got
rid
of
that
entire
layer
and
that
give
us
a
tiny
performance
improvement
for
core
alone.
I
think
it'll
be
a
slightly
larger
performance
improvement.
A
If
you
had
a
ton
of
modules
in
your
site
that
we're
using
that
we've,
obviously
gotten
rid
of
a
bunch
of
this
function,
calls
which
is
good
and,
most
importantly,
we've
removed
a
bunch
of
complexity
in
the
same
system,
which
is
a
bit
of
problem
in
Drupal
7
and
making
things
more
transparent,
easier
to
understand
is
going
to
make
them
easier
burning.
People
to
learn
so
I
think
that
that
is
a
good
step
in
the
right
direction.
A
There's
a
bunch
of
other
stuff
related
to
theme
system
cleanup
that
has
been
d
prioritized
most
of
that.
If
we
don't
get
it
done
between
now
and
january,
fifteenth
we'll
have
to
wait
until
backdrop
to,
and
so
we're
just
going
to
try
and
make
the
process
of
creating
things
as
straightforward
as
possible.
We've
done
a
bunch
of
improvements
in
our
markup.
We're
trying
to
do
some
improvements
in.
B
A
I
think
that'll
go
a
long
way
to
making
the
site
a
little
bit
more
approachable
for
friend
endures.
They
won't
be
so
disgusted
by
what
we're
doing
over
here
in
back
to
our
plant,
but
the
most
important
thing
is
to
make
sure
that
it's
really
easy
for
people
with
HTML,
CSS
and
PHP
experience
to
work
with
so
I
think
we're
still
moving
towards
that
end
goal,
which
is
good.
A
Other
things
that
we're
working
on
is
some
user
experience
improvements.
We've
got
some
human
interface
guidelines
under
way
getting
started
in
terms
of
how
people
should
interact
with
our
software,
and
we've
got
some
big
issues
that
we
really
would
like
to
have
results
early
in
dr.
up
like
getting
a
rich
text,
editor
added
decor
fairly
soon.
That's
an
example
of
something
that
we've
pushed
until
after
the
one
point
0
release,
because
we
think
we
can
do
it
without
changing
any
AP
is
there's
a
couple
of
other
minor
ease.
A
Your
experience,
improvement
issues
in
the
queue
and,
if
you're
interesting,
what
those
are
they
all
start
with
square
bracket.
You
x
square
bracket.
So
if
you
want
to
search
the
queue
for
those
issues,
you
can
see
what
working
on
in
terms
of
user
experience,
improvements
III
that
link
in
here
too
for
a
search.
A
If
we
after
this
meeting,
so
we
can,
you
can
reference
that
in
the
meeting
agenda
going
forward
and
then
we've
got
a
couple
of
things
left
that
are
ready
for
a
final
review
before
we
release
having
someone
look
over
all
of
our
CSS
and
make
sure
that
we're
adhering
to
our
own
coding
standards
would
be
super
handy.
If
we
don't
get
that
review
done,
then
there
might
be
stuff
in
there.
That's
a
little
bit
yucky,
but
it
all
works.
A
We
think,
as
it
is
right
now,
so
it's
not
critical
to
get
that
review
done
and
we
did
finally
get
a
review
of
our
layout
markup,
which
was
super
helpful.
That's
been
on
this
agenda.
For
a
couple
of
weeks,
we
were
able
to
get
a
really
thorough
review
and
doing
a
little
bit
debating
over
how
to
use
proper
semantic.
Markup
I
think
we've
come
to
a
couple
of
great
conclusions
about
how
to
name
layout
based
classes.
A
So
it
sounds
like
we're
definitely
moving
in
the
right
direction
in
terms
of
what
we
need
to
change
on
on
layout
markup
and
we'll
just
need
a
pull
request
to
get
those
small
changes
in
so
I
think
that's
a
huge
help
and
I'm
really
looking
forward
to
getting
our
layouts
cleaned
up
and
then
in
terms
of
the
things
that
we're
working
on
their
super
important.
That's
kind
of
it
there's.
Obviously,
a
ton
of
issues
in
the
queue,
a
lot
of
them
of
varying
different
importance.
A
Things
that
are
tagged
with
bug
are
probably
are
highest
on
our
priority
list
right
now.
There's
a
handful
of
those
will
get
try
and
get
those
knocked
out
before
the
official
release,
and
then
obviously,
if
you
guys
discover
new
folks,
you
can
create
new
issues,
search
the
queue
make
sure
they're,
not
that
already
and
let
us
know
so
that
we
can
fix
them
shortly.
A
Other
things
that
we're
working
on
we've
got
one
major
release,
blocker.
That
is
not
actually
related
to
the
code
of
backdrop,
and
that
is
getting
an
update
server
in
some
form
working.
So
the
plan
for
before
we
release
1020
is
to
create
an
update
server
that,
when
contacted
returns,
information
that
says,
there's
no
updates
available
and
I
think
that
that
will
unblock
us
in
terms
of
being
able
to
release
the
software,
because
we
won't
have
anything.
That's
broken
related
to
the
process
of
checking
updates,
but
obviously
that's
not
what
we
want
long-term.
A
We
actually
want
to
be
able
to
check
the
software
and
make
sure
that
it's
up
to
date
in
returni
useful
information.
So
after
we
do
the
software
out
will
then
it's
start
building.
That
will
say:
okay!
Well
now
the
software's
not
broken.
Let's
build
a
system
that
can
actually
check
updates
and
we
have
a
plan
for
how
we're
gonna
update
core
alright,
how
we're
going
to
check
the
status
of
core,
which
is
good
we'll.
A
Do
it
very
similar
to
how
Drupal
handles
that
now
what
we
are
going
to
need
to
think
about
how
we're
going
to
handle
Kim
trib?
That
will
also
involve
creating
a
packaging
script,
because
get
up
right
now
doesn't
have
a
way
to
do
that
for
us.
So,
there's
a
little
bit
more
work
involved
in
making
sure
that
your
contributed,
eight
but
I
think
step
one
get
the
updates
over
returning
something.
A
So
I
think
that
getting
the
not
errors
happening
when
you're
checking
backdrop
is
super
important
and
then
actual
update
information
for
backdrop
followed
by
update
information
frickin
true,
so
that's
pretty
exciting,
I
think
very
straightforward
in
terms
of
our
path
forward.
We
just
need
to
have
people
start
working
on
it.
So
if
I
own
wants
to
work
on
building
an
update
server,
it's
a
little
bit
outside
of
the
skill
set
of
the
average
backpack
developer,
but
it
could
be
something
fun
and
exciting
for
everyone
to
work
on.
It's.
A
You
know
surfer
building
as
opposed
to
module,
building
or
team
building,
but
it
needs
to
get
done
it's
an
owner.
So
if
someone
wants
to
grab
that,
we
would
really
appreciate
that
other
things
we're
working
on
we've
got
our
API
site
under
way.
I
think
it
now
is
set
to
automatically
pull
code
changes,
so
it
should
have
latest
and
greatest
backdrop
code
on
it
at
all
times,
which
is
wonderful,
we've
got
change,
records
going
in
I,
know,
Luke
created
a
ton
of
them,
we've
got
other
people
reviewing
and
updating.
A
We've
got
a
plan
for
how
our
documentation
is
going
to
be
handled
over
there
and
I.
Think
you
know.
Obviously
the
update
or
the
API
information
is
coming
on
a
little
slower
slower
than
the
code
that
it's
describing,
but
I
think
that
that's
fair
getting
the
code
done
versus
is
how
that
goes.
So,
hopefully,
we'll
get
that
completed
fairly
soon
in
terms
of
documentation.
That's
going
to
live
on
the
AP.
B
A
I
side
and
change,
records
and
stuff
like
that,
so
other
things
we've
got
going
on.
It
will
be
great
if
we
could
create
a
github
service.
So
anyone
who
creates
a
backdrop,
module
or
a
backdrop
theme
can
register
that
or
a
set
of
backdrop.
Layouts
can
register
those
things
as
being
projects
for
or
a
backdrop
and
then
backdrops
CMS
org.
A
Having
the
canonical
sources
listed
somewhere,
easily
accessible,
easily
searchable
is
going
to
be
really
important
for
us,
so
we'll
work
on
getting
that
set
up
shortly
too.
I'm
setting
up
a
github
service
again.
This
is
something
that
is
not
in
usually
in
the
standard
library
of
tools
that
a
backdrop
for
drupal
developer
might
have.
But
if
you
want
to
see
how
github
works,
creating
a
service
looks
like
it's
really
straightforward:
there's
some
really
great
documentation
there
and
we
can
use
some
help
on
that
one
as
well.
Now
we've
got
some
other
stuff.
B
A
Our
flagship
website,
the
first
iteration,
is
just
very
simple-
includes
our
logo
and
it's
got
some
very
small
changes
to
fonts
and
button
styles,
and
it's
just
in
preparation
for
our
kind
of
PR
bit
about
hey.
You
know
backdrop
is
coming.
We
need
to
just
kind
of
make
a
little
bit
more
of
a
statement
of
like
why
you
should
care
why
backdrops
relevant
things
will
make
it
important.
We've
also
got
an
issue
on
github,
where
we're
talking
about
the
content
that
we
want
to
use
on
that
page.
A
We've
already
gotten
some
great
feedback
and
made
some
iterations
that
we
get
to
get
that
and
nailed
down
as
well,
so
bike
ship
website
redoing
coming
soon,
and
if
you
want
to
help
us,
we
work
together,
every
Thursday
so
usually
all
day
Thursday,
but
in
particular
after
this
meeting,
and
if
you
can
get
a
couple
of
hours
a
week
from
your
employer
or
if
you
just
want
to
spend
your
lunch
time
with
us,
we're
usually
around
in
IRC.
If
you
want
to
ask
us
questions
directly,
our
IRC
channel
is
pound
backdrop.
A
You
can
tweet
at
us.
You
can
tweet
at
backdrop
CMS
and
we
usually
get
all
of
those
and
respond
to
them
fairly
quickly.
You
can
email
us.
You
can
find
us
obviously,
on
this
google
hangout
every
week.
If
there's
anything
you,
you
know,
you
don't
know
where
to
jump
in.
We've
got
a
couple
of
good
starting
points.
We've
got
a
tag
and
issue
queue.
That's
currently
called
audience
in
office,
which
is
a
great
place
for
people
who
haven't
contributed
before
to
get
started.
There's
a
bunch
of
quick
issues
there
where
it's
the
oh.
A
This
is
a
small
change
or
something
that
doesn't
require
a
poor
press.
It
just
requires
feedback,
we
were
or
reviews
of
things
those
are
all
in
there
and
if
you
have
a
larger
chunk
of
time
or
you
know,
you're
used
to
contributing
through
github
in
the
pull
request
process,
there's
something
bigger
issues
there
too,
you
can
filter
by
if
they're
bugs
to
go
and
help
us
fix
some
bugs
or
anything.
That's
particularly
if
you're
a
design
contribute
design,
there's
a
tag
there
for
issues
that
need
design
help.
B
Yeah,
it's
mostly
just
been
keeping
up
with
a
poll.
Requests
have
been
coming
in,
there's
been
a
whole
hell
of
a
lot
of
activity.
We've
been
having
a
lot
more
people
install
backdrop
and
start
reporting
problems
with
it,
which
has
been
extremely
helpful,
and
a
lot
of
it
is
actually
not
necessarily
bugs,
but
I
mean
getting
familiar
with.
Some
of
the
new
workflows
like
reinstalling
or
even
installing,
for
the
first
time
can
be
a
little
bit
confusing
to
people
because
they're
not
used
to
having
a
files
directory
that
is
required,
like
the
config
files.
B
At
the
same
time,
it's
the
database
so
managing
that
right
now
is
as
brought
up
some
interesting
like
problems
and
solutions
that
that
we
can
probably
address
and
we'll
try
to
get
done
before.
One
point
0
point
0
views,
conversions.
Those
have
been
going
along
great,
so
that's
that's.
What
I've
been
working
primarily
and
see?
There's
some
other
things.
Oh
just
getting
marketing
text
put
together
for
the
website
and
for
the
mailer
that
I
don't
know
like
we're
west
coast
time
by
the
time
that
we
get
this
thing.
Actually
the
release
rolled.
A
B
Good
idea,
but
will
probably
still
be
tagging
the
release
later
today.
That
is
the
quote
preview
release.
You
know
that
it
is
basically
just
you
know:
hey
were
highly
stabilized
and
it's
a
good
time
to
come
and
check
us
out,
but
will
probably
also
start
doing.
I
was
pitching
this
to
cage
and
earlier
was,
will
practically
start
looking
at
converting
the
flagship
site
over
to
backdrop
CMS
as
well,
I
was
looking
at
it
earlier
today.
There's
about
ten
contributed
modules
on
their
link.
B
Google
analytics
view
slideshow
those
sorts
of
things,
but
those
would
be
really
pretty
simple
to
to
port
over.
Oh,
you
know
has
it.
I
think
it
was
yeah
yeah
it
was
this
week.
This
week
I
published
a
video
to
YouTube
that
was
how
to
port
a
module
from
Drupal
7
to
backdrop
and
if
you're,
watching
this
video
you're,
probably
already
on
our
YouTube
channel,
it's
the
video
before
this
one
and
in
that
video
is
25
minutes
of
how
to
port
a
module
and
I.
B
Do
it
all
by
hand
during
that
25
minutes
and
actually
walk
through
the
entire
process
of
porting
a
module
from
triple
72
backdrop,
and
we
also
had
our
first
contributor
jump
in
import
a
module
and
put
it
in
the
backdrop,
contribute
as
well:
yeah
yeah,
BW
panda
ported,
his
simplify
module
from
Drupal
7
22
backdrop.
One
point:
oh,
and
and
put
it
into
the
backdrop
kinship
group
things
are
still
a
little
bit
ambiguous
around
contribs,
so
apologies
there,
but
the
plan
freaking
trib.
B
It's
documented
a
little
bit
on
the
flagship
site,
but
there's
a
group
on
github
called
backdrop:
hyphen
contribs
and
there's
three
modules
in
there
right
now:
devel
external
links,
which
is
the
video
module
that
I
use
for
demonstration
purposes
and
and
the
BW
pandas
simplified.
But
as
we
port,
the
flagship
sight
will
probably
port.
You
know
a
dozen
more
modules
/
they
take
at
least
simple
ones.
B
Take
like
you
know,
20
30
minutes
so
I
mean
that's
still
a
pretty
big
investment
to
you
know,
probably
a
couple
days
or
even
weeks,
potentially
to
do
those
initial
porting
zuv
a
dozen
modules,
but
the
process
so
far
is
really
proven
itself
and
the
viability
of
how
easy
and
quickly
it
is
to
port
modules
over
from
Drupal
7,
so
I'm
really
pleased
with
the
result.
Overall,
we.
B
A
7
theme
to
a
backdrop
theme,
and
that
might
be
a
really
good
place
to
use
a
backdrop.
Cms
torgue's
public
theme
that
we're
using
right
now
poured
it
to
a
backdrop
and
then
also
include
the
changes
that
we
got.
We
just
got
some
new
design
changes
this
week
for
for
our
kind
of
freshly
stuff.
Maybe
we
could
do
that
in
another
video
and
show
that
process
yeah.
B
That
that
process
is
going
to
be
really
interesting.
It's
still
it's
still
highly
compatible
between
Drupal,
7
and
and
backdrop,
but
there's
some
caveats
because
things
like
a
layout,
vanilla
or
sorry
themes
are
no
longer
responsible
for
layouts.
So
moving
stuff
like
you
need
to
basically
take
your
page
template
and
move
it
into
a
layout
template
and
that's
going
to
be
a
tricky
process,
although
once
you
get
familiar
with
it,
it
won't
be
too
much
more
difficult
than
then
porting
a
module
or
anything
else.
So
yeah
I
agree.
A
I
think
that
sounds
great
I.
Think
in
the
process
of
porting
backdrop,
CMS
org
to
backdrop,
there's
a
couple
of
things
we
should
do.
We
should
make
a
video.
We
should
make
a
blog
post.
We
should,
I
think,
if
we
can
make
a
video
of
the
theme
transition.
That
would
be
really
good.
I
also
think
some
of
the
modules
that
we're
using
things
like
link
does
shouldn't
be
ported.
A
We
had
this
meta
of
all
the
issues
that
much
as
it
moved
into
four
and
eight
compared
to
what
we're
doing
with
them
in
backdrop,
updated
that
issue
today
to
show
the
things
that
we're
definitely
not
planning
on
updating
in
backdrop
and
the
things
that
have
been
postponed
to
later
versions
of
backdrop
and
and
I
think
things
like
link
module
like
as
we
come
across
needing
them.
It
might
be
good
to
just
write
that
pull
request.
A
It
says
the
splits
it
in
core
and
then
come
up
with
a
work
process
for
including
the
equivalent
of
a
patched
version
of
core
right
like
that,
there's
a
workflow
we
have
in
Drupal
or
when
you
fix
something
to
dribble.
You
apply
the
patch
and
you
maintain
that
patched
version
yourself
we're
going
to
need
that
same
process
in
backdrop,
land
working
from
a
pull
request
since
I'm
a
patch
or
maybe
starting
from
across
making
a
patch
and
then
keeping
a
patch
version
of
the
software
I'm.
A
B
B
B
A
B
A
A
So
we
can
do
that
same
thing.
I
mean
the
thing
I
want
to
avoid
is
having
a
cluttered
module
page
interface
for
things
like
link.
There's
no
reason
for
that
to
be
a
separate
check
box,
but
we
can
do
the
same.
The
tin
process
we've
done
for
other
ones.
We
can
definitely
follow.
Okay
sounds
like
a
plan.
Sorry,
we
had
to
talk
through
that
on
the
video.
Sorry,
one
watching
figured
it
out
alright.
Well,
I'm
super
excited
about
actually
using
this
thing.
So.
B
Yeah,
it's
it's
really
exciting
to
look
forward
to
it
or
look
look
out
for
it
later
today.
The
preview
release
will
try
to
put
that
up
on
the
front
page
of
fact,
I've
CMS
org
and
then
tomorrow
we're
going
to
be
sending
out
of
mail
there
if
you're
not
subscribed
to
the
mailing
list,
already
sign
up.
It's
it's
at
the
bottom
of
the
home
page
backdrop
CMS
org
and
if
you
are
subscribed,
look
for
the
email
tomorrow,
yay,
okay,
thanks
everybody
for
watching
Thank,
You
Jen
again
for
for
moderating,
okay
I'll.