►
From YouTube: Moving from Drupal 7 to Backdrop CMS
Description
You have a perfectly good Drupal 7 site that does everything you need it to do, but Drupal 7 is nearing its end-of life. If you haven't considered moving to Backdrop CMS, you may be surprised to learn that Backdrop could be your most affordable option -- especially if you've invested heavily in custom code.
Come watch a live upgrade (not a migration) of a Drupal 7 website to Backdrop CMS. You'll get a chance to experience everything that is familiar after the upgrade, and see some of the areas that have been improved. We'll also cover some of the similarities and differences between the Drupal and Backdrop
communities.
A
A
Guess
we'll
go
ahead
and
get
started
today.
I'm
gonna
talk
a
little
bit
about
moving
from
Drupal
7
to
backdrop
CMS.
So
this
is
specifically
for
people
who
might
already
have
Drupal
7
sites
and
are
wondering
what
to
do
in
the
coming
years.
With
their
current
site,
I
am
Jen.
Lampton
I
am
primarily
developer.
A
I
work
with
nonprofits
government
agencies,
higher
education,
smaller
businesses,
essentially
not
the
enterprise
I'm,
a
one-person
development
company,
and
so
that
means
I
end
up
working
a
lot
with
in-house
teams
at
heritage,
different
places
and
sometimes
on
smaller
teams,
with
myself
and
maybe
several
other
contractors.
So
it's
not
the
kind
of
place
where
Drupal
8
would
be
a
perfect
fit
in
a
lot
of
instances,
especially
for
nonprofits.
A
They
end
up
having
lots
of
volunteers
that
they
want
to
give
tasks
like
updating
the
website
same
thing
with
educational
institutions,
there's
often
a
lot
of
students
available,
and
so
you
need
to
have
a
system.
That's
ready
enough
to
give
to
them
to
take
over
that.
They
don't
need
to
have
a
lot
of
previous
understanding
with
the
platform
how
to
update
so
I've
spent
a
lot
of
time.
A
The
past
few
years
in
Drupal
trying
to
create
that
experience
for
people
where,
when
you
log
in
you,
don't
have
to
know
very
much
about
Drupal,
you
can
just
do
what
you
have
to
do,
and
so
I'm
gonna
talk
a
little
bit
from
my
experience
in
creating
that
for
people.
I'm
assuming
everybody
here
has
probably
heard
of
backdrop
CMS
before,
but
if
not
I'll
just
give
you
the
quick
elevator
pitch
back
up.
Cms
is
essentially
a
modernized
version
of
Drupal
7.
A
A
But
it
includes
a
lot
of
the
features
that
I
think
you
couldn't
have
a
new
CMS
today,
without
so
some
things
that
your
blade
includes,
like
a
built
in
rich
text,
editor
the
configuration
management
system
that
allows
us
to
use
you
have
one
live
site
and
be
working
on
development
changes
and
deploy
those
changes
without
disrupting
the
content
near
live
database.
That's
something
that
people
really
love
about
Drupal,
and
it
also
includes
a
lot
of
the
top
features
that
were
in
Drupal
7,
so
just
as
Drupal
8
included
things
like
see
tools
and
views
dr.
A
past
that
we've
also
included
a
ton
more
feature.
So
we
have
there's
actually
74
Drupal
7
kinship
modules
that
have
been
included
in
dr.
up
core,
some
of
them
just
gonna
move
straight
in
and
some
have
been
integrated
more
closely.
The
rest
of
the
system
in
general.
We're
trying
to
make
a
less
complicated
piece
of
software,
so
backed
up,
should
be
easier
to
use
than
Drupal
7.
A
It
will
sit
somewhere
between
WordPress
and
Drupal
8
in
terms
of
complexity,
and
it
needs
to
be
faster,
so
backdrop
is
faster
than
Drupal
7
today
and
we're
gonna
keep
working
on
making
it
faster
with
each
release
in
the
future.
So
that's
once
something
that
we're
pretty
focused
on
changing
about
it,
backed
up
is
also
focused
on
the
experience
of
the
people
have
to
use
it
so,
rather
than
being
really
focused
on
making
the
API
is
really
great.
We
don't
care
so
much
about
what
developers
have
to
do.
A
We
care
more
about
what
people
are
using.
The
software
has
to
do
so
from
user
experience
perspective.
It
should
be
a
lot
closer
to
WordPress
in
terms
of
your
ability
to
just
log
in
and
do
what
you
need
to
be
able
to
do
so.
A
lot
of
the
features,
including
and
backdrop,
are
also
features
that
were
standard
in
WordPress
that
we're
missing
from
Drupal.
A
So
in
case
you're
wondering
who
should
move
to
backdrop
if
you're
already
on
Drupal
7,
that's
easiest.
If
you're
coming
from
Drupal
6
I've
done
a
bunch
of
upgrades
from
6
to
backdrop,
you
don't
have
to
admit
it
out
loud,
it
does
still
happen
and
that's
perfectly
fine
to
go
from
Drupal
6.
You
would
just
go
to
Drupal
7
first
and
I
go
to
backdrop.
So
the
hardest
part
of
that
upgrade
is
6
to
7,
which
is
not
super
easy
in
the
first
place,
if
your
current
happy
with
your
current
website.
A
So
if
you're
not
happy
with
your
current
website,
you
could
build
a
brand
new
one
and
you
could
just
do
that
on
any
platform.
So
there
might
not
necessarily
be
a
huge
advantage
and
choosing
backdrop
unless
you
needed
the
features
that
are
provided,
which
I'm
hoping
to
show
you
in
a
little
bit.
But
if
you
have
a
Drupal
7
website
that
you
are
perfectly
happy
with,
you
want
all
the
same
features
you
have
now.
A
You
want
the
software
to
continue
to
get
updates,
but
you
don't
want
to
invest
a
lot
of
time
or
money
into
moving
it
onto
a
different
platform.
Backdrop
might
be
a
really
great
option
for
you,
because
it's
so
similar
to
Drupal
7,
to
start
with
so
in
general,
upgrading
to
backdrop
can
be
done
in
five
steps.
The
first
thing
you
do
is
clean
up
your
Drupal
7
site,
and
that
usually
includes
removing,
for
example,
modules
that
you've
turned
on
but
never
used.
A
If
you
have
features
on
there
that
you
built
five
years
ago,
but
I've
never
actually
used,
you
could
turn
those
off
just
a
general
sort
of
overview
clean
up.
What
is
it
from
the
site
that
I
want
to
carry
on
into
the
future?
Once
you
have
that
ready?
You
can
export
your
database
and
files
from
Drupal
7,
set
up
a
new
backdrop,
site
import
your
database
and
files
from
Drupal
into
backdrop
and
then
run
an
update
script
so
backdrop
has
an
update
script.
A
The
same
way
that
Drupal
6
upgrades
into
Drupal
7
backdrop
considers
Drupal
7
its
previous
version.
So
when
you
drop
your
code
and
it'll
automatically
be
able
to
convert
all
of
your
sharable
7
stuff
to
backdrop
for
you
before,
you
start
with
the
actual
upgrade
I.
Also
recommend
you
do
a
lot
of
research,
so
I'm
gonna
go
through
a
couple
of
the
steps
that
I
usually
follow.
One
I
do
an
upgrade,
and
hopefully
you
guys'll
get
a
lot
out
of
that.
So,
let's
see
here
browsers.
Okay,
can
you
guys
see
this?
A
Yes?
So
what
we're
looking
at
right
now
is
the
website
that
I'm
gonna
work
on
this
is
a
website
that
was
built,
I,
don't
know
eight
years
ago
or
something
in
Drupal
seven.
At
the
time
it
was
an
e-commerce
website.
They
raise
fancy
pigs
in
California
for
the
purpose
of
being
eaten
for
dinner
and
at
the
time
there
was
a
way
that,
as
a
restaurant,
you
could
go
to
their
website
and
you
could
order
your
pork
delivery
direct
from
them.
A
Since
then,
they've
stopped
using
this
e-commerce
service,
they've
partnered
with
a
larger
agency
that
handles
all
that
for
them,
and
so
the
website
has
been
reduced
to
a
much
simpler
set
of
what
it
was
before
today.
It's
more
of
a
brochure
where
say
something
that
could
be
built
pretty
quickly
anything
on
any
platform.
A
But
what
I
wanted
to
prove
for
this
client
was
that
moving
from
Drupal
to
backdrop
would
be
a
more
affordable
option
than
anything
else,
because
they
already
have
a
Drupal
site
and
they
can
use
it
all
again,
in
fact,
rack.
So
the
cleanup
step
involved
turning
off
all
of
the
commerce
stuff
they
weren't
using
or
removing
the
modules
have
been
turned
off
for
years
and
just
making
sure
the
site
was
clean
and
ready
to
go.
A
As
this
part
of
my
research
phase,
when
I
was
trying
to
figure
out
what
it
would
cost
forget
to
get
them
to
move,
is
I
go
through
all
the
modules
that
they
have
on
their
site
and
I
take
a
look
at
all
of
those
that
are
available
or
ready
for
backdrop
and
I
throw
them
all
into
the
spreadsheet,
and
if
you
guys
are
interested
in
more
of
the
details
in
this
spreadsheet,
it
is
linked
from
the
session
on
the
Stanford
webcam
page.
So
you
can
look
at
this
later.
A
You
don't
have
to
try
and
read
it
all
now:
tiny
font,
but
essentially
there's
just
a
list
of
all
the
modules
that
they're
using
currently
the
status
and
backdrop
if
it's
been
ported
already,
if
it's
included
in
core,
if
you
don't
need
it
anymore,
what
an
alternate
module
might
be.
So
if
we
use
like
node
reference
or
any
reference
in
Drupal
7,
you
might
want
to
switch
to
reference
in
backdrop
any
of
the
steps
that
I
think
are
availa,
quired
and
part
of
the
moving.
A
So
if
we
had
to
like
uninstall
module
from
Drupal
7,
that
would
be
fine.
If
we
had
to
test
and
upgrade
because
I
wasn't
sure
it
was
gonna,
work
correctly,
I've
note
that
in
here
too,
and
that
would
help
me
come
up
with
an
idea
of
how
long
I
think
it
would
take
to
do
this
upgrade
for
more
complicated
websites.
I
also
often
will
review
the
layouts
in
terms
of
what
content
is
in
position
on
which
page
content
types
and
the
amount
of
content
in
any
given
type.
That'll.
A
Give
me
an
idea
of,
what's
the
most
important
for
any
given
website.
What
are
they
actually
using
a
lot
of
them?
What
are
they
not
using
so
much
of
I
might
document
fields.
This
isn't
actually
from
this
website.
It's
just
an
example.
So
if
I
think
there's
something
that
might
be
problematic
and
a
change,
I
would
want
to
note
that
here
and
have
some
idea.
A
If
I'm
gonna
have
to
do
any
custom
work
on
that
or
not
usually,
you
don't
have
to
and
you'll
see
that
a
minute
and
then
for
the
theme
also
trying
to
get
an
idea
of
like
how
many
template
files
or
CSS
files
or
JavaScript
files,
so
they
have
just
in
terms
of
if
I'm
gonna
copy
them
over
how
much
testing
am
I
going
to
have
to
how
much
find
and
replace'
my
gonna
have
to
do.
Just
leave
me
a
general
idea
and
for
a
very
complicated
website.
A
B
A
What
happens
you
can
do
a
live
upgrade
and
then
modules?
Okay,
so
this
is
my
Drupal
7
site
of
the
stone
Valley
farm,
the
pig
site,
which
was
always
good
to
big
site.
This
is
the
Drupal
7
version
of
it.
If
I
go
to
the
modules
page
I
have
installed
a
module
on
my
Drupal
7
site
called
backdrop
upgrade
status,
and
this
module
will
show
us
which
modules
from
terpil
are
available
for
backdrop
than
what
the
current
status
of
that
module
is.
So
there
is
a
upgrade
status.
Module
for
Drupal
that'll.
A
Tell
you
if
your
Drupal
6
site
is
ready
for
June
7
on
your
Drupal
7
sensually.
Fortunately
that
sort
of
thing.
This
is
exactly
the
same
thing.
We
took
that
module
and
adapted
it
to
work
for
backdrop.
Instead,
so
it'll
tell
you
what
modules
you're
currently
running
and
if
they're
ready
or
not,
and
if
you
have
one
that
doesn't
have
a
stable
release,
yet
they
don't
indicate
that
there's
a
version
of
it,
but
it
doesn't
have
a
person
out
yet
I'm
in
the
process
of
updating
this
right.
A
Now
it
includes
information
about
all
of
the
modules
that
are
in
backdrop
core
and
will
note
if
there's
something
that's
missing
from
the
drupal
version
that
got
included
in
fact,
Job
Corps
and
if
there's
tricky
things
that
need
to
be
changed
as
I
might
be
noted
in
here
too.
So
here's
like
see
Jules
closely,
what's
included
and
what's
not,
but
it's
not
done
yet.
It
doesn't
include,
like
the
module
versions
are
obviously
a
Drupal
7
members
and
that
backdrop
numbers
so
get
those
updated,
but
in
general
it
will
really
help.
A
You
fill
out
your
spreadsheet,
let
you
know
whether
those
columns
need
to
be
addressed
or
not,
and
if
you
have
a
module
that
doesn't
have
a
version.
Yet
it
will
have
a
big
red
line
and
say
that
it's
not
ready
for
that
droplet.
So,
hopefully
I
don't
help
with
that.
I
would
also
like
to
expand
this
module,
and
we
were
just
talking
about
this
this
week
to
include
some
of
the
other
statistics
that
I
put
into
my
spreadsheet.
A
So
it'll
have
like
a
tab
for
your
content
and
it
will
tell
you
how
much
content
you
have
a
niche.
Each
type,
what
fields
you
have
if
there's
something
that
isn't
going
to
upgrade
smoothly
we'd,
have
a
place
to
document
that
in
here
too,
so
it
will
start
to
be
a
more
complete
report
of
how
your
site
we'll
translate
into
backup
geez.
Okay,
all
right,
so
here's
my
Drupal
7
site,
so
once
I
got
it
ready,
and
in
this
case
this
side
is
almost
already
ready.
A
Cuz
I've
done
a
little
cleanup
on
a
book
floor.
What
I
would
do
is
export
the
database
to
create
a
new
backdrop
site
which
I
happen
to
have
one
right
here:
import
the
Drupal
7
database
and
then
run
this
update
script.
And
so
what
we're
looking
at
right
now
b2
is
just
backdrop
core
and
all
of
the
contributed
modules,
which
is
usually
the
first
or
a
second
upgrade.
A
All
do
you
want
to
say,
I
might
do
core
by
itself
just
make
sure
nothing
explodes
they
don't
do
it
for
in
the
controls
is
what
we're
gonna
do
right
now,
just
to
see
what
will
happen
so,
just
by
pointing
my
backdrop,
say
a
database
that
used
to
be
a
Drupal
7.
You
can
see
that
it
recognizes
it
and
tells
you
that
there's
211
updates
it
needs
to,
and
that
might
sound
like
a
really
big
number.
A
But
it
really
only
takes
a
couple
seconds
because
most
of
what
backdrop
does,
when
it's
doing
that
update,
isn't
actually
changing
the
database
structure
around
it's
exporting
configuration
that
was
previously
in
the
database
and
saving
it
as
flat
files,
which
is
how
backed
up
in
Drupal
8
work
with
configuration,
so
the
entire
upper
it
goes
really
fast.
It
just
tells
you
what
it's
done
here
and
it
gives
you
a
chance
to
visit
the
site.
So
if
I
go
ahead
and
I've
got
a
login
block
right
here,
login.
A
All
right,
you
don't
remember,
my
passwords
are
ever,
and
the
first
thing
you'll
notice
is
that
some
of
the
configurations
are
missing.
So,
for
example,
in
the
Drupal
7
site,
which
is
over
here,
the
way
the
site
was
built
was
using
panels.
So
I
have
a
couple
pages,
like
my
home
page,
my
recipes
page,
my
blog
page.
A
These
are
all
standalone
panel
pages
and
then
I
have
some
other
pages
that
are
nodes,
like
the
contact
form,
the
About
section,
and
so
immediately
after
an
initial
upgrade,
the
configuration
isn't
gonna
be
here
for
things
that
death
panels
don't
have
an
exact
migration
path
from
Drupal
to
back
or
the
backdrop.
Yet,
although
we
are
working
on
it,
so
the
pages
that
are
content
are
gonna
work,
just
fine,
but
you'll
notice.
A
The
other
ones
are
missing
from
the
navigation,
so
usually
after
running
the
first
upgrade
I'll
log
in
and
look
around
I'll
take
a
look
at
the
list
of
content.
This
you
guys
will
probably
recognize
from
Drupal.
Only
difference
is
that
this
is
a
view
now,
so
you
can
configure
it.
However,
you
want
the
content.
Editing
experience
is
very
similar
to
Drupal.
A
We've
got
a
couple
of
different
changes
like
the
ability
like
schedule
things
for
the
future.
We
include
URL,
aliases
and
redirects
if
necessary.
So
it's
just
all
the
stuff
you're
used
to
it's
just
more
poor
than
was
there
before
and
I'll.
Take
a
look
at
it
make
sure
this
is
all
working.
How
I
expect
I
might
check
out
I
don't
know,
are
all
my
people.
There
are
all
my
techs
on
me.
There
things
the
way
I
expect,
but
anything
that
needs
to
be
configured
will
need
to
be
reconfigured.
A
Anything
like
a
panel
will
need
to
be
reconfigured.
Most
of
your
module
settings
and
stuff
is
all
moved
over
use
of
all
moved
over
one
thing,
I
have
use,
we
do
okay,
so
if
you
had
any
views
in
Drupal,
7
they'll
all
come
over
as
use
in
backdrop.
So
that's
one
one
thing:
that's
gonna
be
a
huge
time-saver.
A
If
you
had
use
configured
before
it's
nice
once
I'm
sure,
all
of
everything
that
I
want
to
be
here
is
here
then
I
might
send,
spend
some
time
working
in
things
in
backdrop
that
are
new,
for
example
our
layout
system.
So
this
is
something
that's
new
for
backdrop.
There
are,
rather
than
placing
blocks
into
regions
that
are
controlled
by
your
theme.
A
We
place
blocks
into
regions
that
are
controlled
by
the
layout
system,
and
that
makes
it
so
that
you
can
change
your
themes
without
needing
to
worry
about
breaking
where
your
blocks
might
have
been
placed
on
your
site.
The
theme
will
work
with
all
a
outs
layouts
with
all
themes.
Your
block
placements
stay
regardless
of
what's
going
on
so
here,
but
has
I
imported
from
a
previous
site.
A
It's
tried
to
figure
out
where
to
place
all
of
the
things
that
it
had
anything
that
doesn't
exist
in
a
backdrop
but
existed
in
Drupal
7
might
not
work
and
it'll
tell
you
it's
broken
and
it'll
tell
you
why,
which
is
really
nice.
This
is
essentially
the
panels
module
from
Drupal
7.
It
has
drag-and-drop.
We
wrote
an
entirely
new
user
interface
for
it,
so
it
should
be
less
confusing,
but
that's
that's
that,
let's
see
so
once
I've
got
everything.
Working
I'll
spend
some
time
setting
up
new
layouts.
A
So
things
like,
if
I
had
any
custom
modules
I
might
want
to
get
my
site
all
the
way
from
Drupal
7
into
that
trap.
Before
I
should
I
working
on
the
custom
modules
or
if
I
want
to
update
my
theme,
I
would
want
to
have
my
entire
site
and
all
this
configuration
ready
and
backdrop
before
I
work
on
the
theme
and
so
any
of
that
stuff.
A
I
just
do
and
I'll
start
with
Bartok
or
something
and
then
might
make
my
theme
and
then
I
do
the
final
upgrade
I'll
upgrade
from
my
human,
all
its
like
to
my
team
in
the
new
site.
So
there's
kind
of
an
intermediary
step
here
where
everything
is
halfway
done,
then
you
spend
some
time
clicking
stuff
together
and
then,
when
you're
happy
with
it,
you
can
do
it
again.
So
the
snapchat
working
at
right
here
I
have
a
document,
so
many
browser
types,
I'm,
sorry
guys.
A
Okay,
I,
have
a
document
that
the
upgrades
the
entire
process
for
this
particular
site.
So
if
you
want
to
see
this
in
more
detail,
you
can
definitely
look
at
it.
It
has
some
information
about
what
goes
into
the
spreadsheet
and
some
resources
for
to
find
them
on
my
local
computer
right
here.
I
have
four
versions
of
the
site
set
up.
One
of
them
is
only
core.
One
of
them
is
corn
kinship,
which
is
when
we're
looking
at
right
now.
A
One
of
them
is
a
version
of
court
and
contribute,
and
then
my
last
one
is
core
and
kinship
and
configuration
and
a
theme
and
the
way
that
I
do
my
data
imports
when
I
run
them
is
I,
usually
have
a
version
of
Drupal
7
with
disables
that
I
do
before.
I
have
my
custom
theme
and
then,
once
my
theme
has
been
ported
over
I'll,
do
the
final
upgrade
with
everything
enabled
so
that
was
the
Drupal
7
site
and
sort
of
the
pristine
state.
It
was
before
I
started.
So
I
have
lost
my
navigation
here.
A
Ok,
so
this
is
the
version
of
Drupal
core
and
all
of
its
contributed
projects.
So
if
we
went
to
the
modules
page,
you
could
see
things
like
add
just
field
and
node
reference
like
modules
that
you
they're
not
they're.
Not
all
of
these
are
in
batch.
Of
course,
these
are
ones
that
I've
added
once
this
upgrade
works
and
I've
got
all
of
my
configuration
committed
to
code.
I
would
do
the
same
thing
again.
So
I
have
an
example
here
of
backdrop,
site
plus
modules,
plus
configuration
and
I'll
show
it
happen.
A
A
A
Okay.
So
if
you
go
to
the
config
sync
page,
it
should
show
you
all
the
differences
between
the
clothes
that
you're
currently
running
and
the
code
that
you're
about
to
pull
in
so,
for
example,
on
this
site.
I
added
a
new
layout
for
my
blog
and
it's
got
a
configuration
file
here
for
configuration
files
and
backdrop
are
in
Jason,
so
they
should
be
pretty
clearly
formatted.
If
you
understand
Jason,
you'll
know
what
you're
looking
at
here.
Let's
do
see
a
difference.
A
Changes
if
I
wanted
to
see
like
what
I
changed
in
my
course
that
are
variables,
you
could
feel
it
like.
Disabled
CSS,
pre-processing
I
turned
on
the
theme,
debug
mode
and
I've
added.
It
looks
like
a
bunch
of
default
settings
for
that
were
only
there
for
that
job.
So
you
can
review
those
if
you
want
in
general,
because
I
know
I
just
made
them
I'm
gonna,
assume,
they're,
safe
and
I
will
do
an
import
here,
and
this
will
just
take
all
of
the
configuration
apply
it
to
the
site
and
run
anything
necessary
database
updates.
A
So
if,
for
example,
I
changed
a
field,
there
are
database
tables
that
control
your
data
for
those
fields.
So
the
configuration
has
mentioned
a
file,
but
it
still
needs
to
make
change
to
the
database.
So
this
synchronized
that
was
really
important
for
vector
to
be
able
to
handle
that,
for
you
know
once
the
sink
is
done,
I
can
then
go.
Oh
my
gosh
this
watch,
my
caches
I,
can
go
and
check
out
the
new
pages
on
my
site.
So
I
now
have
a
home
page.
A
I
have
a
products
page
at
the
recipes
page,
which
is
new,
I
have
a
blog
page,
which
is
new,
and
all
of
my
layouts
are
now
in
place.
So
if
I
go
to
the
structure
layout
section,
you
can
see
a
blog
homepage,
no,
no
to
read
on
this
particular
site
there,
a
couple
of
blocks
that
are
placed
on
individual
note
pages,
so
you
guys.
Let
me
see
that
later.
Do
that,
but
I
want
to
do
the
last
step,
which
is
most
exciting.
A
A
Okay,
after
you
have
a
theme
setup
for
your
site,
instead
of
showing
up
in
Bartok,
which
is
the
default
Drupal
themes,
also
in
available
and
backed
up
with
you're
moving
from
Drupal.
You
can
update
to
your
theme
too.
So
this
is
the
backdrop
site
with
the
Drupal
7
theme
slightly
modified.
It
looks
very
similar
to
Drupal
7.
It
has
who
we
are
pages,
the
product
pages,
the
recipes
layout,
with
the
view
on
it,
a
blog
layout
with
a
view
on
it,
contact
form
which
is
just
a
web
form.
A
This
site
has
my
images
on
it,
which
looks
much
nicer,
and
there
were
a
couple
of
things
that
were
a
little
tricky
that
I
wanted
to
spend
some
extra
time
testing,
like
my
references,
I,
wanted
to
make
sure
those
work
correctly.
I
need
to
spend
a
little
bit
extra
time,
making
sure
that
these
accordion
upgraded
appropriately
so
I
think
that
was
on
me,
like
our
team
page.
There
was
a
section
here.
A
Yeah
update
a
lot
of
fine
and
replace
IDs
with
glasses,
nah
not
required,
but
just
follow
me
so
I
did
anyway.
So
this
site
is
not
running
backdrop.
It
is
took
less
than
day
to
do
it,
so
it
was
proved
to
myself
that
I
could
get
them
from
Drupal
7
to
backdrop
pretty
easily.
It
had
one
custom
module
that
was
essentially
a
bunch
of
form
alters
that
didn't
need
any
changes.
It
had
one
module
that
needed
to
be
ported.
It
was
the
taxonomy
formatter
module.
A
All
I
had
to
do
to
get
that
working
on
backdrop
was
change,
one
line
and
profile,
and
it
had
a
theme
that
had
the
all
these
changes.
The
majority
of
my
time
was
spent
updating
the
theme
which
I
think
is
probably
two
or
three
hours
and
then
running
the
update
over
and
over
again,
which
probably
took
you
know
another
hour.
So
once
you
get
into
backdrop,
backdrop
does
offer
some
new
features,
so
you
notice
this
little
red
dot
on
my
admin
bar
here.
It
tells
me
there's
something
wrong
with
my
site.
A
One
of
them
is
access
to
update
dot
PHP,
which
obviously
I
just
ran
the
update.
So
that's
why
that's
turned
off
I
would
go
and
change
that
in
my
code
and
turn
it
back
on
this
other
one,
and
this
is
a
good
example
of
a
difference
between
the
way
back
up,
solves
the
same
problems
that
Drupal
sucks.
This
is
utf-8
character.
A
Support
are
emoji,
so
if
you
want
emoji
on
your
sites
may
be
able
to
like
copy/paste
one
into
a
comment
form
if
you
were
running
an
old,
triple
7
site
and
you
haven't
updated
your
database.
That
would
cause
a
problem
in
Drupal
7.
There
is
a
solution
to
fix
that,
but
involves
running
a
Direction
command.
So
it's
sort
of
the
solution
to
that
problem
is
very
developed
or
focused.
A
It's
a
terminal
command
that
you
run
in
order
to
fix
it,
but
in
backdrop,
we're
more
focused
on
making
this
a
tool,
that's
usable
for
people
using
the
software
so
rather
than
running,
address
command.
We
give
you
a
button
on
the
user
interface,
so
here
there's
just
a
button.
It's
baked
in
you
can
say:
upgrade
your
database
I,
don't
switch
all
those
tables
over
for
you,
so
we
both
had
the
same
problem.
A
A
Okay,
so
yeah
there's
also
you
probably
only
notice.
The
administrative
interface
looks
very
similar
to
what
was
here
before
it's
a
modified
version
of
the
Drupal
7
admin
theme
so
that
we
tried
to
make
it
be
really
familiar
to
people
who
already
know
Drupal
but
be
slightly
more
welcoming
to
people
who
don't
know
what
your
boys
yet
so
I'm
with
my
tubs
down
here,
just
a
little
weird.
But
it's
it's
the
same
exact
thing
that
you
you've
seen
work
with
before
so
yeah
I,
don't
know
it's
it's
all
the
same,
but
it's
all
different.
A
A
So
I
actually
did
it
four
times
in
the
this
demo.
I
did
it
twice
mostly
because
if
something
goes
wrong,
I
want
to
know
exactly
where
it
goes
wrong.
So,
when
I
do
an
upgrade,
I'll
do
first,
just
core
to
make
sure
that
that
works
and
then
I'll
do
core
and
all
the
can
share
projects
to
make
sure
that
works.
Oh,
so
that's
all
of
the
stuff!
That's
like
not
really
my
problem.
If
it
breaks
it's,
not
something
that
I
wrote
and
I
know
that
I've
cost.
A
So,
for
example,
one
of
the
things
we
do
in
backdrop
is
we
store
all
of
our
like
user
roles
in
configuration
files
in
Drupal
7.
They
were
in
the
database.
So
if
you're
running
a
change
on
your
site
that
requires
knowing
those
roles,
you
can't
do
a
database
query
to
get
access
to
them
anymore,
because
they're
now
in
configuration
files,
so
you
would
want
your
upgrade
hook
to
run
before
the
hook
that
deleted
those
files
from
the
database
and
so
that
they
have
to
go
in
a
very
specific
order.
A
So
you
have
to
run
them
all
at
once,
and
the
system
knows
what
order
they
need
to
be
in.
So,
if
you
do
like
do
it,
piecemeal
upgrade
like
I,
did
first
decor
and
then
I
do
clean
trip
and
then
I
do
my
custom
stuff
I'm
changing
that
order,
and
it
might
not
work
correctly.
So
in
a
rule
of
thumb,
you
need
to
do
them
all
at
once,
but
because
I
like
to
know,
if
I
did
them
all
at
once
and
it
broke
I,
wouldn't
know
where
it
broke.
A
A
Has
a
couple
just
as
Drupal
has
a
couple,
and
we
have
a
copy
Bluebird
cart.
So,
if
you're
running
a
broker
in
Drupal
7
that
will
upgrade
smoothly,
we
have
a
couple
of
other
ones.
Like
basic
cart,
I
think
is
available.
We
also
have
modules
that
integrate
directly
with
payment
processors
like
there's
a
striped
module.
A
So
if
you
just
had
like
a
webform
and
wanted
to
take
donations
or
something
that's
pretty
easy
and
we
do
not
have
a
copy
of
Drupal
commerce,
although
someone's
working
on
that
Ryan's
dorama
is
one
of
the
creators
of
Drupal
commerce
also
started
creating
a
project
called
back
shop
which
was
supposed
to
be
a
back
drug
specific
version
of
Drupal
commerce.
Drupal
commerce
is
a
lot
like
Drupal
8
and
that
it
is
very
powerful
and
very
sophisticated
and
also
very
complicated,
and
so
Ryan
thought
that
there
might
be
a
better
way
to
do
that
problem.
A
For
the
backdrop
landscape,
that,
instead
of
involving
a
bunch
of
complexity
and
a
bunch
of
different
modules,
would
be
a
slimmed
down
version
that
included
the
most
important
stuff
so
that
it
wouldn't
be
so
overwhelming
for
new
people.
So
the
new
project
called
back
shop,
is
not
available
yet
there's
a
github
repository
where
he's
been
working
on
it,
but
it
could
be
interesting
to
see
what
happens
to
that
in
the
future.
A
So
if
you're
coming
from
Commerce
in
Drupal,
7
and
you're
really
happy
with
your
commerce
solution,
they'll
probably
be
best
for
you
to
go
to
Drupal
8,
because
there
is
a
solid
upgrade
path
for
that
and
the
kinds
of
features
that
you're
getting
now
are
going
to
be
available
in
the
future
Nate
where
they
might
not.
You
might
be
the
only
one
if
you
chose
spectra
to
be
running
a
really
complicated
commerce
site
on
a
platform
like
backdrop
it's
possible,
but
I,
don't
know,
but.
B
A
Yeah,
so
any
there's
lots
of
systems
like
that,
like
webform,
has
a
bunch
of
a
different
plug
on
models.
Modules
feel
like
if
you
want
a
special
kind
of
table,
clicker
or
whatever,
like
modules,
can
have
modules
too,
and
that's
totally
fine
and
the
complexity
isn't
necessarily
determined
by
the
number
of
modules
that
are
included
in
the
package.
A
It's
more
in
the
underlying
architecture
of
the
system
itself
and
Ryan
was
also
involved
in
uber
cart
at
the
beginning,
and
he
sort
of
re-architected
the
whole
thing
when
you
started
working
on
triple
commerce
with
oh
there's
lot
about
other
people
in
both
of
my
only
no
right
in
them,
so
he
sort
of
had
a
chance
to
say
how
could
I
do
this
in
a
way
that
would
be
more
flexible
and
landed
on
a
tool
that
was
more
complicated
and
so
backdrop
is
sort
of
that.
It's
the
same
thing
where
it's
like?
A
Okay,
so
you
have
Drupal
6,
is
pretty
simple.
Drupal
7
was
pretty
complicated.
Drupal
8
is
very
more
complicated.
Back
trip
is
sort
of
in
the
middle,
where
it's
like
some
of
the
things
in
triple
7,
where
each
each
complicated,
so
it
took
a
step
back
and
some
of
the
things
that
need
to
increase,
or
maybe
not,
increase
in
complexity
of
an
increase
in
feature
set.
A
Very
much
about
the
backdrop
philosophy,
but
if
you
guys
are
interested
there's
a
page
on
vector,
CMS
organ
that
talks
about
it,
we
have
a
set
of
guiding
principles.
One
of
them
is
making
this
offer,
as
I
did
mentioned
before.
In
order
to
make
it
fast,
it
means
to
be
less
complicated
in
order
to
be
easier
to
use,
it
needs
to
be
less
complicated
in
order
to
have
more
people
contribute
to
it.
A
B
A
A
To
build
a
new
architecture
on
your
existing
content,
library
is
a
great
way
to
do
it,
but
if
you
have
like
a
completed
site
in
Drupal,
6
I
would
actually
recommend
doing
the
Drupal
6
suitable
size,
an
upgrade
path,
or
you
actually
get
to
keep
all
of
your
content.
We're
sorry
all
of
your
configuration
changing
for
your
content.
There
are
some
sticky
spots
with
that,
but
because
the
Drupal
7
6
to
7
upgrade
track
has
been
around
long
enough.
There
are
don't
you
workarounds
to
that
I've
done
I.
A
My
all
of
my
first
upgrades
to
batch
job
we're
actually
coming
off
of
Drupal
6.
There
people
have
shipped
people
by
then,
and
so
I
have
a
github
repository.
That
includes
like
the
most
common
things
like
getting
more
rich
text
data
into
the
right
format,
because
the
way
we
did
things
like
this
is
different
than
the
way
we
do
things
from
blackjack.
A
Like
he's
saying,
finger
tags
or
any
images
and
caption
types
and
stuff
like
that,
and
so
there's
just
some
common
things
that
work
across
all
sites
and
then
there's
some
tricky
things
like
if
you're,
using
like
the
video
module
in
Drupal
6,
that
would
have
to
be
made
like
a
video
field
type
in
Drupal
7
and
there
are
upgrade
paths
for
whichever
way
you
choose.
You
have
to
kind
of
wrap
your
rape
brain
around,
what's
different
from
how
it
was
in
six
and
Thailand
I
think
that's
so
much
the
hardest
fit.
So.
D
D
A
A
So,
if
you're
worried
about
minor
versions,
that
gets
pretty
easy.
So
let's
see
available,
updates
settings,
there's
a
status
update.
So
if
you
want
back
trip
to
update
itself,
you
know
have
the
ability
like
push
a
button
on
your
site
and
it
will
replace
core
an
update
core
and
run
the
update.
So
it's
working
a
little
bit
more
like
WordPress.
A
We
haven't
got
this
working
for
major
versions
yet
so
we
don't
have
a
major
version
or
all-male
backed
up
one,
but
when
backed
up
to
comes
out,
we
do
want
to
make
this
button
work
there
too.
So,
rather
than
being
the
kind
of
thing
where
you
have
to
worry
about
a
old-style
upgrade
where
you
have
to
run
copy
your
database
into
a
new
system
or
whatever
this
should
be,
you
should
have
a
button
to
push
to
make
that
range,
that
Oh
that'll
be
much
easier.
A
This
I
doesn't
have
any
available
updates
right,
show
you
the
button,
but
there
is
not
going
to
do
that
here.
So
upgrading
should
be
easy.
We
already
feel
like
moving
from
Drupal
to
backdrop
is
the
hardest
upgrade.
You
should
ever
need
to
do
so.
We're
gonna
focus
on
making
that
process
it's
getting
better.
Every
month
it
gets
easier
and
because
we're
putting
in
backwards
compatibility
so
anytime,
we
find
something
that
isn't
easy.
Now
we
try
and
build
them
something
to
maybe
see
in
the
future
and
I.
A
Don't
know
that
if
I
have
an
example
here,
but
in
the
log,
if
you
call
something,
that's
deprecated,
there's
a
name
here:
it'll
actually
log
a
deprecated
messaging,
your
watchdog
log,
with
a
link
to
the
API
documentation.
That
says
why
it's
changed
so
it'll
still
work,
but
then
it'll
try
and
help
developers
get
to
the
next
version
so
rather
than
being
broken,
and
you
have
to
go
figure
out
why
it'll
still
work
and
then
tell
you
why
whatever's
changed
you.
A
Site
will
be
perfectly
fine,
so
if
you're
not
a
developer,
it
doesn't
matter,
but
if
you
are-
and
you
want
to
get
it
up
to
the
latest
version-
you'll
have
the
ability
to
make
that
change.
In
terms
of
why
you
might
want
to
choose
backdrop
over
Drupal
7
to
start
with,
it's
faster,
that's
number
one
good
reason
it
is
responsive
out
of
the
box,
so
you
don't
have
to
worry
about
trying
to
figure
out
how
to
get
a
non-responsive
system
to
be
responsive
using
some
kind
of
fancy
base
theme.
A
A
Under
updating
from
Drupal
7
there's
a
list
here
of
features
out
of
decor
that
includes
72
modules,
so
there's
a
bunch
of
stuff
that,
as
a
Drupal
7
site
owner,
would
be
your
responsibility
to
keep
up
to
date
with
what's
going
on
in
Kim
trip
and
make
sure
your
site
stays
up
to
date.
All
of
this
stuff
is
in
core
now,
so
it'll
all
be
included
in
your
next
core
update
and
you've
got
that
button
to
push
to
bring
your
site
up
to
date
to
get
it.
A
So
it
also
should
be
easier
to
use
if
you're
focused
on
content,
editors
or
volunteers
working
on
your
site
and
not
wanting
them
to
have
a
whole
bunch
of
work
in
terms
of
learning
on-ramp
to
get
familiar
with
it.
That
might
be
a
good
reason,
also
as
a
architect
like,
if
you're,
not
a
coder
but
you're,
more
advanced
than
someone
who
just
logs
and
edit
pages
you're
building
the
site
architecting
the
site,
it's
also
a
lot
faster.
A
So,
for
example,
if
I
was
going
to
make
a
new
content
type,
it's
a
good
example
when
I'm
building
a
page
or
if
I
don't
know,
maybe
not
a
page,
whatever
kind
of
content
type.
It
is
there's
a
bunch
of
stuff
that
we
put
all
together.
So
just
if
you
wanted
to
find
like
permissions,
we
do
that
on
a
tree,
creating
content
type
of
URL,
alias
pattern.
A
You
do
on
the
place
tree,
creating
a
content
type
all
of
the
kinds
of
things
that
you
used
to
have
to
bounce
all
over
the
navigation
order
get
set
up
because
it's
all
in
core.
We
were
able
to
integrate
all
of
the
configurations
to
a
single
place,
so
it
makes
it
much
faster
to
build
that
site
in
the
first
place
than
if
you
were
to
build
a
Tundra
chol.
Seven.
Another
reason
is
just
having
a
rich
text.
Editor,
you
don't
have
to
fight
with
that's
already
all
set
up.
It's
got
some
good
buttons
on
it.
A
I
don't
know
how
this
site
was
set
up
in
Drupal
7.
We
can
take
a
look
at
it.
So,
here's
to
see
Canada
options
for
sort
of
limited
options
on
this
site,
but
we
could,
you
know,
add
people
it's
an
image,
the
image
uploading.
You
can
also
upload
starkly
in
the
rich
text,
editor
image
upload
and
you
can
do
like
copy
paste
to
put
images
in
there.
That's
something
that's
hard
to
do
in
Drupal.
A
It
works
even
from
a
phone
like
if
you
click
the
image
upload
button,
it'll
open
your
camera.
So
you've
been,
you
know,
post
an
image.
Let's
write
a
blog
post,
while
you're
on
the
road
yeah
I
just
find
it
takes
a
lot
less
time
to
administer
my
backdrop
site
than
in
Drupal
site,
just
bouncing
on
the
image,
great
interface
and
coming
out
of
work.
Do
you
have
to
do
to
keep
it
up-to-date?
That's
right!
It's.
B
E
A
So
we
I
don't
know
that
we
had
much
of
a
conversation
around
this.
It
just
kind
of
happened
initially,
but
because
all
of
our
development
is
happening
on
github
we're
using
semantic
versioning
and
there's
has
to
be
like
a
special
integration
between
our
github
system
in
our
website
in
order
to
get
modules
to
appear
up
on
the
website.
So
we
had
sort
of
a
big
thought
about
how
is
developer
going
to
indicate
when
this
module
is
ready
for
to
show
you
know
for
everyone
to
use.
A
It
and
backdrop
also
has
an
additional
feature
on
the
modules
page:
the
Installer
module
to
turn
on
it
horizon
user
interface'
lets
people
install
modules,
and
so
because
we
have
interface
here
that
lets
you
pull
a
module
in
from
anywhere
without
needing
to
leave
your
website.
That
sort
of
assumes
a
specific,
like
you,
don't
want
to
give
somebody
a
button
to
install
their
module.
A
That's
going
to
break
their
site
if
they're
not
capable
of
like
getting
access
to
the
files
and
removing
them,
for
example,
they
might
not
have
to
have
to
be
access
to
the
site,
but
they
can
still
install
the
module
using
this
button.
So
you
don't
you
don't
want
to
give
them
something
that's
broken.
A
So
if
it's
not
a
stable
release,
you
can
get
hub
forever,
but
it
won't
show
up
here
so
there's
sort
of
an
incentive
there
for,
like
you,
want
to
make
sure
your
module
is
stable
enough,
that
someone
can
install
it
without
needing
access
to
the
code
and
as
soon
as
it
reaches
that
benchmark,
you're
gonna
want
it
to
have
that
virtual
number
on
it.
So
it
sort
of
happened
naturally,
that
you
know
also
having
the
extra
bug
fix
release
version
that
you
can
have
a
1.0
for
forever.
A
Now,
just
15
releases
at
once,
I
know
so
I
think
it
gives
developers
a
little
bit
more
confidence
in
terms
of
I
can
really
say
1.0
and
can
still
make
bug
fixes
all
the
time.
So
it's
sort
of
it
came
out
that
way.
We
don't
have
there's
nothing
on
here,
dev
beta
alpha.
It
won't
show
up
on
the
site.
That
way.
Thank.
E
C
C
A
I
mean
if
it's
doing
it
in
Drupal
7,
it
can
do
it
in
backdrops
you
without
any,
like
specific
examples,
it's
hard
to
say,
but
like
we
have
a
copy
of
rules
module.
So
if
your
site
dependent
on
that
I
can
do
that,
our
site
runs
cron
in
the
same
way
that
triple7
does.
It
actually
runs
it
more
frequently,
because
we
have
this
automatic
publishing
feature
built-in,
so
it
has
to
run
it
every
five
minutes.
B
Much
it's
3:50
I
think
we
should
yeah.
We
want
to
thank
you
very
much
presentation.