►
Description
This webinar gives a brief intro to the Backdrop CMS, which forked from Drupal 7 in 2013. Their prime difference from Drupal is their emphasis on backward compatibility. The session also focuses on the all new Layouts module in Backdrop, with a comprehensive demo to illustrate this unique functionality.
A
Hello,
this
is
Alana
and
I.
Welcome
you
all
to
the
surgeon
and
stay
webinar
if
you
are
joining
us
for
the
first
time.
This
is
a
community
initiative
by
student
technology.
We
used
to
tune
into
some
great
sessions
on
topics
changing
from
strands
and
technologies.
You
want
us
to
mobile
apps
to
media
on
the
ownership
community
building
industry
marketing.
Today
they
have
a
dozen
eight.
How
name
should
be
talking
about
the
back
of
EMS,
which
is
a
dual
support?
A
If
you
take
us
through
a
big
history
as
to
how
backdrop
came
about
moving
on
when
you
focus
on
backdrop,
unique
layout
module
and
need
business,
a
short
demo
to
illustrate
it
better,
a
bit
of
all's
needs
before
we
start
main
sent
mean
a
major
google
contributor
for
over
ten
years
and
was
the
original
author
of
Google
Ajax
framework,
the
maintainer
profile
and
image
modules
in
the
circle
and
the
Creator
for
you
to
eight
ckeditor
module
in
September.
2013
key
form
is
useful
to
create
to
the
back
of
CMS,
which
we
will
explore
today.
A
Thanks
for
joining
us
me
before
we
begin
with
the
section.
I
will
discuss
all
body
systems
to
c7
any
questions
that
you
have
during
the
presentation
and
we'll
take
them
up
in
the
last
15
minutes
of
the
session.
Also,
please
don't
forget
to
take
the
conversation
live
on
Twitter
using
our
hashtag,
which
in
ww
we
can
share
your
thoughts
by
tagging
our
and
needs
in
your
crease,
using
our
handle
at
the
rate
clicking
and
a
great
quick
tip,
so
without
taking
up
any
more
of
your
time.
Let's
get
that
me
over
to
you.
B
All
right
thanks
so
much
I'm
really
happy
to
be
here
and
be
talking
about
backdrop
with
you
guys
here
today.
So
I'm
gonna
be
talking
about
backdrop,
this
little
guy
at
the
bottom
of
my
slide
here
he's
our
mascot.
His
name
is
is
drop
but,
as
you
guys
may
know,
backdrop
is
a
fork
of
the
Drupal
project.
We
did
this
back
in
September
2013,
so
backdrop
has
been
around
now
for
quite
a
while.
B
But
primarily,
the
main
reason
why
backdrop
CMS
exists
is
a
matter
of
a
difference
in
philosophy
from
the
Drupal
project.
There's
definitely
some
some
reasons.
Code-Wise,
like
a
backdrop,
is
very,
very
similar
to
Drupal,
7
and
there's
reasons
for
that.
But
the
primary
reason
why
backdrop
exists
is
because
we
have
a
different
project
philosophy
from
Drupal.
B
B
If
you
look
over
the
history
of
Drupal
and
pretty
much
every
major
release
of
Drupal
Drupal
has
a
strong
philosophy
of
basically
ignoring
backwards,
compatibility
or
actually
just
having
an
outright
disregard
for
it.
Basically
saying
like
backwards.
Compatibility
is
something
weeks
basically
do
not
do
in
between
releases,
and
this
has
been
the
case
for
every
major
release
of
Drupal,
since
it
was
created
in
between,
like
Drupal
4.6,
our
four
point:
seven
and
five
five
and
six
six
and
seven
each
one
of
those
releases
introduced
major
API,
breaking
changes
and
basically
the
way
development
works.
B
Is
that
any
change
you
want?
You
can
get
into
the
next
version
and
you
don't
have
to
provide
any
sort
of
compatibility
layer
with
the
previous
version
of
Drupal
that
changed
a
little
bit
more
in
Drupal
8
in
that
in
previous
versions,
there
was
always
an
upgrade
path.
The
policy
was,
we
maintained,
upgrades
for
your
data,
but
not
your
code
and
in
Drupal
8.
That
shifted
a
little
bit
to
be.
B
There
is
no
upgrades
or
compatibility
at
all
between
versions,
so
from
Drupal
7
to
Drupal,
8,
there's
no
longer
even
an
upgrade
path,
but
instead
now
just
a
migration
path.
So
the
idea
is,
instead
of
upgrading,
maintaining
your
site
for
a
long
period
of
time
after
three
or
four
years,
when
you
upgrade
your
site
to
the
next
upgrade
your
site
to
the
next
version
of
Drupal,
you
actually
build
an
entirely
new
sites
and
then
migrate.
B
So
the
primary
thing
that
we're
trying
to
do
with
backdrop
is
drive
the
cost
of
owning
a
website
down
we're
trying
to
make
it
less
expensive
for
people
to
run
websites,
and
so
some
of
the
rest
of
the
items
on
these
principles
we
share
with
Drupal.
Some
of
them
are
a
little
bit
different
writing
code
for
the
majority.
B
It's
basically,
we
have
a
policy
of
like
an
80/20
kind
of
situation,
about
what
kinds
of
features
that
we
include,
including
features
for
the
majority.
Ensuring
backdrop
can
be
extended.
This
is
an
idea
that
you
know
really
Maps
strongly
to
Drupal
like
we
want
to
make
sure
that
the
things
that
have
made
Drupal
really
powerful
and
popular
in
the
past.
We
maintain
that
flexibility
within
Drupal
through
or
start
within
backdrop
through
our
hook
system,
the
theme
layer
and
all
of
the
other
ways
to
make
Drupal
extensible.
B
We
really
want
to
make
sure
that
we
have
lo
system
requirements.
Backdrop
has
a
broader
spectrum
of
hardware
that
it
will
run
on
because
it
basically
right
now
our
low
end
is,
is
PHP
5,
3,
2,
I,
think
and
the
high
end
is
is
PHP
5
7,
so
we
support
every
version
of
PHP
in
between
those
and
a
wide
spectrum
of
my
sequel
versions.
B
We
plan
in
scheduled
releases,
so
backdrop
runs
on
a
four
month,
continuous
release
cycle
where
every
four
months
like
clockwork,
we
will
make
another
release,
and
this
has
been
the
case
already
we're
now
on
or
a
next
release
will
be,
will
be
May
15th
and
that's
that
will
be
a
fourth
release.
After
January
15th
was
their
first
one,
then
September,
then
May
and
every
one
of
those
sort
of
trimesters.
B
The
other
big
change
from
Drupal.
Besides
our
philosophy,
is
the
direction
of
the
project.
We
have
a
really
strong
set
of
goals
that
we
try
to
accomplish
within
backdrop
that
we
are
targeting
ourselves
at
a
particular
audience,
and
we
really
believe
that
targeting
ourselves
at
a
particular
audience
will
make
a
more
focused
product
that
is
more
appropriate
for
that
group
of
people
in
the
dribble
world.
B
Backdrop
is
kind
of
taking
that
same
approach
where
we're
trying
to
target
for
a
lower
budget
website,
but
that
doesn't
mean
that
it
couldn't
be
flexible
to
go
like
downstream
into
the
blogging
market
or
upstream
into
the
enterprise
market.
There's
a
huge
amount
of
flexibility
in
any
tool,
but
what
we're
trying
to
do
is
make
a
tool
that
is
more
appropriate
for
a
certain
segment
that
Drupal
might
be
kind
of
falling
out
of
Vogon.
B
So
our
mission
at
backdrop,
CMS,
is
to
enable
people
to
build
highly
customized
websites
affordably
through
collaboration
and
open
source
software,
and
the
key
word
in
our
entire
mission
statement.
Is
this
word
affordably,
where
every
decision
that
we
do
we
try
to
evaluate
like?
Is
this
going
to
make
websites
less
expensive
to
run?
Is
this
going
to
save
people
time?
Because
time
is
money
and
if
your
system
isn't
saving
you
time,
then
it's
not
a
system
that
you
should
be
using
so
making
it
affordable
is
our
primary
idea
behind
everything
backdrop
out
of
the
box.
B
Basically,
my
elevator
pitch
the
really
short
version
of
like
what
is
backdrop
as
a
software
product.
You
can
sum
it
up
really
pretty
quickly
and
say
backdrop
is
just
like
Drupal
7,
with
views
and
core
configuration
management
in
core
and
panels
in
core,
but
that
doesn't
quite
tell
the
entire
story.
We
also
have
all
of
these
other
modules.
These
are
the
top
bond
modules
on
drupal.org
and
you
can
see
that
most
of
them
have
been
integrated
into
a
backdrop
core,
including
some
that
haven't
quite
made
it
into
the
triple-eight
world
yeah.
It's
like.
B
We
have
the
token
UI
built
into
core
pathauto
built
into
core,
but
some
other
ones
that
are
injured
late
as
well.
Obviously,
I
did
work
on
the
ckeditor
module
in
Drupal
8.
All
of
that
functionality
is
also
in
backdrop
as
well
as
some
things
you
might
expect
like
more
fields,
like
date,
module
link,
module,
email
module
like
these
modules
that
provide
additional
fields.
All
of
these
things
are
also
in
backdrop.
B
Court
backdrop
is
largely
fairly
feature
equivalent
to
Drupal
8,
but
all
built
upon
a
Drupal
7
like
architecture,
because,
again,
like
our
philosophy
of
backwards
compatibility
is
starting
with
Drupal
7
that
there's
an
upgrade
path
and
you
can
run
update
dot
PHP
and
it
will
upgrade
your
sites
with
the
same
modules
from
Drupal
7
to
backdrop
so
backdrop
acts
as
though
Drupal
it
acts
as
though
it
is
the
next
version
of
Drupal.
You
pointed
out
of
Drupal
7
website.
B
It
will
upgrade
it
to
a
backdrop
website
and
the
concept
code
wise,
is
that
the
code
is
similar
enough
and
familiar
enough
that
you
should
be
able
to
port
no
module
from
Drupal
7
to
backdrop
within
a
really
short
amount
of
time
say
like
typical
port
takes
about
an
hour
or
so
like
the
most
complex
supports
a
couple
of
days
or
maybe
a
week
so
backed
up
out-of-the-box
lots
of
modules.
We
also
have
configuration
management,
which
will
do
a
little
bit
of
in
the
demo,
that
we
store
everything
in
JSON
files.
B
So
you
can
move
configuration
between
different
in
fire,
but
that's
not
the
topic
of
this
particular
presentation.
I
really
want
to
focus
on
today
is
release.
There
is,
is
layouts.
Layouts
are
an
all
new
tool
that
we've
built
within
backdrop
that
replaces
the
traditional
block
system.
It's
super
similar
to
the
panels
in
Drupal
7,
except
that
panels
in
Drupal
7
only
controlled
a
small
portion
of
the
page,
the
middle
part
of
the
page.
B
And
then
you
switch
from
one
theme
to
the
other
and
unless
those
two
themes
have
the
exact
same
region
names,
all
of
your
block
positions
are
simply
discarded
and
it
makes
it
so.
That's
you're
at
your
appearance
of
your
site
or
your
structure
of
your
site,
really
is
highly
tied
to
the
theme
that
you
are
using
in
backdrop.
B
What
we've
done
is
we
have
changed
this
from
being
tied
to
the
theme
to
being
tied
to
layouts
instead,
and
this
makes
it
so
that
there's
no
longer
and
of
a
concept
of
themes
that
have
like
a
three
column
theme
or
a
two
column
theme.
There's
no
such
thing
as
themes
having
layout
anymore.
Instead,
you
have
layouts
module,
provide
all
the
layouts,
and
then
the
theming
community
provides
the
styling
around
the
layouts.
B
This
has
some
really
cool
advantages
and
some
really
neat
side
effects.
That's
every
page
on
your
site
now,
because
we
have
separate
layouts,
every
page
on
your
site
can
have
a
different
layout
and
you
can
have
as
many
different
layouts
as
you
want
on
your
entire
site.
So
you
don't
need
to
try
to
make
one
single
template
somehow
accommodate
for
every
single
layout
on
your
site.
If
you've
got
certain
pages
that
have
a
right,
sidebar
and
some
they
have
a
left
sidebar
and
some
that
are
just
a
single
column.
B
You
don't
need
to
do
the
magical
like
disappearing
regions,
trick
that
we
had
to
do
in
Drupal
7
and
try
to
lay
out
all
of
your
blocks
for
your
entire
site,
all
within
one
interface.
Instead,
every
single
page
can
be
laid
out
individually
with
the
same
layout
as
the
rest
of
the
site,
or
than
entirely
different
layouts.
B
We
also
have
this
amazing
ability
of
contexts.
Context
basically
take
the
URL
on
which
you
are
visiting,
and
it
takes
that
information
out
of
the
URL
and
makes
certain
additional
information
available
to
your
blocks.
This
allows
us
to
do
all
sorts
of
things
with
conditionals,
saying
that
we,
you
can
only
show
or
hide
things
based
on
certain
properties,
of
the
context
that
are
available
or
to
pull
out
certain
information
of
things
that
are
available.
B
We
also
have
really
cool
things
that
you
can
handle.
It
can
handle
multiple
contexts
like
if
you've
got
multiple
wild
cards
in
your
URL,
then
it
can
take
one
and
say
that's
a
node
and
take
another
one
and
say
that
that's
a
user
and
you
have
multiple
contexts
available
from
which
you
can
pull
and
do
conditionals.
B
Creating
a
new
layout
templates:
this
is
basically
another
front-end
task
in
in
Drupal
7.
If
you
previously
had
the
role
of
a
theme
er,
you
probably
also
were
responsible
for
doing
your
layouts,
but
your
layout
was
primarily
controlled
by
the
page,
TPL
dot
PHP
file
in
backdrop,
land
we've
simply
separated
them
so
that
you,
if
you're
a
front-end
developer,
you're
likely
make
both
the
theme
and
the
layouts,
and
so
a
layout
directory,
looks
a
lot
like
this.
It's
very
similar
to
a
theme
within
the
layouts
directory.
B
We
have
a
new
top-level
concept
of
a
layout
templates
and
inside
of
it
is
a
dot
info
file,
a
CSS
file,
a
preview
for
the
little
image
on
the
layouts
page,
and
then
the
template
file
that
actually
contains
the
regions
of
your
particular
layout.
The
dot
info
file
should
look
really
familiar.
This
is
just
like
theme,
dot
info
file
without
all
of
the
other
information,
and
it
only
has
the
regions.
This
also
means
that
there
won't
be
regions
listed
in
your
theme.
Dot
info
file,
you'll,
essentially
just
copy
them
into
into
your
layout
template
file.
B
B
Backdrop
is
similar
to
Drupal
7,
but
more
powerful,
so
in
Drupal
or
sorry,
an
in
backdrop,
we've
added
a
couple
of
extra
powers
to
hook
block
info,
one
of
which
is
setting
required
contexts,
and
this
makes
it
so
that
you
can
say
that
a
block
will
only
be
available
when
you're
in
a
certain
context,
and
so
this
is
a
good
example
like
the
book
navigation.
If
you
are
on
a
book
node,
then
you
want
to
show
the
navigation
for
that
book
and
in
Drupal
7.
It
would
just
check
on
every
single
page.
B
Like
am
I
on
a
book
URL
am
I
in
a
book
URL?
Am
I
on
a
book
URL
and
it
just
would
hide
or
show
the
block
based
on
the
URL
at
which
the
visitor
was
was
on,
but
in
backdrop.
Instead,
we
have
at
the
higher
level.
We
know
contextually
that
this
block
should
never
be
called
unless
you're
on
a
node
in
the
first
place.
B
So
we
prevent
calling
any
module
level
code
because
we
already
know
contextually
that
if
you're
not
on
a
node
page,
we
shouldn't
even
start
calling
that
blocks
callbacks
and
in
Drupal
7.
When
you
want
to
display
a
block,
you
would
frequently
have
an
implementation
of
hook,
block
view
and
it
would
take
a
delta
parameter
for
which
block
ID
you
wanted
to
display,
and
then
you
would
print
out
or
you
would
return
an
array
of
a
subject
and
content.
This
is
similar
again
in
backdrop
land,
but
we've
changed
a
couple
of
things.
B
We've
made
it
so
that
this
hook
block
view
takes
two
additional
parameters:
one
for
settings
and
one
for
contexts,
because
when
you
configure
a
block
or
layout
and
backdrop,
it's
all
saved
into
our
configuration
management
system,
we
don't
use
variables
anymore.
So
no
more
variable
get
variables
set
in
your
block
configurations.
Instead,
they'll
be
saved
automatically
for
you
into
into
the
configuration
management
system
as
JSON
and
then
passed
back
into
your
implementation
of
hook,
block
view.
B
We
also
pass
in
the
list
of
contexts
so
again
if
your
block
is
dependent
upon
a
node
or
a
user
or
term
or
some
other
entity
type
object,
then
that
information
is
passed
into
you,
so
you
don't
need
to
load
it
from
the
URL
or
do
a
node
load
or
use
men.
You've
got
object
or
any
of
those
old
approaches
that
previously
would
kind
of
pull
the
information
from
from
the
URL.
B
So
it
really
makes
it
so
that
all
of
your
code,
for
your
block
can
be
all
nicely
contained
in
a
single
place
and
you
don't
have
to
have
it
mess
with
all
of
the
other
blocks
that
might
be
in
your
module
all
right.
Well,
that's
it
for
kind
of
the
introduction.
I
know
it's
a
little
bit
rough.
If
you
haven't
seen
the
backdrop
in
action
before
to
know
a
whole
lot
about
what
I
was
talking
about
so
I'm,
hoping
that
the
demo
here
a
backdrop
will
kind
of
clear
things
up
a
little
bit.
B
Okay,
so
here
we
are,
this
is
a
backdrop
site
kind
of
out
of
the
box.
I've
used
devel
generated
to
generate
a
little
bit
of
content
to
populate
it,
but
you'll
notice
that
it's
really
pretty
similar
to
Drupal
7.
There
are
a
couple
of
new
things
in
backdrop
or
in
in
this
that
we're
not
in
Drupal
7,
though,
like
things
like,
if
I
turn
on
the
mobile
view,
then
we
can
see
that
certain
things
like
backdrop
is
responsive
out-of-the-box,
which
is
something
you
would
absolutely
expect
with
any
system
these
days.
B
But
it's
really
nice
that
some
things
like
we've
built
in
admin
bar
from
Drupal
7,
the
most
popular
tool
for
doing
administration,
and
we
have
certain
things
like
we
have
this
nice
search
ability.
That
makes
it
so
that,
if
you
don't
know
where
certain
things
are
within
backdrop,
you
can
just
type
into
the
admin
bar
your
particular
task
that
you
want
to
accomplish,
and
then
it
will
take
you
to
those
particular
pages.
B
B
B
And,
of
course,
let's
see
one
thing
that
all
of
that
I
mentioned
during
the
presentation.
All
of
this
configuration
that
I
do
on
my
sites
is
saved
into
configuration
management
and
in
backdrop,
land
that
means
that
they
are
saved
into
into
JSON
files.
So
that
view
that
I
just
assembled,
for
example,
is
called
recent
content.
Here's
the
JSON
representation
of
that
view
and
as
you
as
you,
configure
anything
on
your
site,
that's
not
content!
So
things
like
your
tax
or
your
node
types,
your
views,
your
layouts.
B
All
of
these
things
are
all
stored
immediately
into
JSON
files.
So
let's
talk
about
layouts
themselves.
So
if
I
were
to
go
to
the
layouts
section
at
of
the
box,
backdrop
comes
with
two
layouts,
the
default
layout
that
will
be
used
for
your
entire
site.
That's
like
the
equivalent
of
Drupal
7,
or
you
only
had
a
single
layout
that
was
controlling
your
sites
and
in
admin
layout
that
controls
the
backend
part
of
your
site.
So
out-of-the-box
backdrop
uses
a
two
column
layout
for
your
front-end
and
for
your
back-end.
It
just
uses
a
single
column.
B
You
know
for
the
administrative
interface,
which
is
what
we're
seeing
right
now.
So
if
you
wanted
to
modify
your
entire
site,
you
can
do
so
by
modifying
the
default
layout
like
I
could
do
something
like
I
can
take
that
block
that
I
just
created
called
recent
content,
actually
I'm,
not
sure
that
was
the
right
one.
B
Well,
anyway,
you
could
take
a
block
like
this
recent
content
block
and
plop
it
in
the
right-hand
sidebar
and
then
I'll
go
to
the
home
page,
and
you
can
see
here's
that
recent
content
block
here
in
the
right-hand
sidebar,
but
if
I
wanted
to
on
my
entire
site
change
from
let
one
layout
to
the
other
I
go
here
to
the
settings
page
flip
the
entire
layout
around,
and
so
now
my
entire
site
has
a
left
column
layout
instead
of
a
right
column
layout.
But
all
of
that
is
not
particularly
more
powerful
than
Drupal
7.
B
What
makes
things
really
exciting?
Is
the
ability
to
have
per
page
layouts,
so
I
can
do
something
like
if
I
wanted
to
make
a
customized
front
page
or
something
like
that
I
can
go
to
layouts.
I
can
hit
add
a
new
layout,
make
a
layout
for
front
page,
and
let's
say
the
front
page,
should
just
be
a
one
column.
Layout
I
can
make
up
a
path
like
front.
B
And
then
I
start
with
an
entirely
blank
slate,
where
I
can
do
any
sort
of
content.
That
I
want
like
again
like
that
recent
content
block-
oh
I,
think
I,
know
what's
going
on
here,
because
I
actually
really
want
to
make
sure.
Oh
yeah,
so
I
made
this
as
a
page
and
I
should
have
made
it
as
a
block
here.
That's
why
that
isn't
showing
up
okay.
Here
we
go
sorry
about
that.
So
now,
I
can
actually
add
that
view
that
I
created
there.
B
We
go
recent
content
as
a
view
and
save
that
here
save
the
layout
and
then
what
that's
done
is
that's
made
a
new
path
on
my
site
at
slash
front,
which
I
then
would
make
the
front
page
of
my
website
that
is
different
from
the
rest
of
my
site
and
that
the
rest
of
my
site
uses
a
two
column
layout,
but
this
particular
page
only
uses
a
single
column
layout.
So
you
can
take
any
path
you
want
on
the
site
and
just
make
one
up.
B
In
addition
to
being
able
to
make
new
paths,
though,
you
can
also
overwrite
any
existing
path
on
the
site.
So
a
good
example
of
this
would
be
like
these
posts
that
we
have
here
like.
Currently,
this
is
a
a
two
column
situation
where
the
theirs
column
over
here
on
the
left-hand
side
and
then
the
main
content
is
on
the
right-hand
side.
But
if
I
wanted
to
I
could
make
a
layout
specifically
for
posts,
so
I
could
say
like
post
layout,
node
posts
and
then
I
specify
an
existing
path
on
the
site.
B
Conditions
I
only
want
this
layout
to
be
used
if
I'm
on
a
particular
node
type
like
if
I'm
on
a
particular
node
type
of
post,
for
example,
and
then
I
can
hit
create
layout,
and
this
will
make
it
so
that,
if
you're
on
a
post
piece
of
content,
then
this
layout
will
be
used.
But
if
you're
on
a
different
type
of
content
like
page,
then
it
will
fall
back
to
the
default
layout.
B
You
can
also
set
up
if
you
want
to
multiple
layouts
at
the
same
path
with
different
conditions
and
whichever
set
of
conditions
matches
first
will
be
the
layout
that
is
used
on
that
page.
So
in
this
case,
I'm
going
to
remove
that
recent
content,
block
and
I
might
do
something
like
take
the
image
field.
B
It's
also
really
cool
some
things
you
can
do
with
the
styling
or
the
the
mark-up
that
is
on
the
page.
If
you
want
to,
you
can
add
block
or
add
classes
to
blocks
that
are,
in
the
in
add
classes
to
the
wrappers
that
are
around
your
blocks,
but
you
also
could
customize
the
entire
block
markup
individually,
like
tagged.
My
tag
like,
if
you,
if
it
makes
more
sense
for
your
for
your
block
to
use
in
the
side
tag
rather
than
a
div,
then
you
can
do
that.
B
You
can
also
just
setup.
You
know
your
classes
for
what
you
want
to
be
on
the
wrapper
or
whether
or
not
you
want
to
have
wrappers
at
all.
You
can
customize
your
headings
content
tag.
You
can
do
anything
you
want
in
here
so
and
if
you
wanted
to,
you
can
also
set
up
like
certain
situations
where
it's
like
this.
B
This
particular
element
should
only
be
shown
based
on
a
certain
permission
or
certain
role
or
or
something
like
that.
You
could
also
set
up
those
sorts
of
things
like
you
know.
This
block,
maybe
should
only
be
available
under
certain
situations,
but
we
don't
need
to
have
those
here.
We
want
this
to
be
shown
to
everybody
and
then
we'll
hit
save
and
now,
when
I
go
back
here
to
this
post
piece
of
content.
B
Here
you
can
previously
it
was
using
the
default
layout,
reload
and
then
now
it's
using
that
right
hand
block
is
now
the
primary
image.
Of
course,
the
primary
image
is
also
shown
here
at
the
top
of
the
post.
So
this
isn't
you
wouldn't
be
done
here.
You
would
also
probably
want
to
go
over
to
your
post
content
type,
manage
your
display
and
take
out
that
image
field,
so
that
so
that
we
don't
have
it
displaying
twice.
So
you
could
do
this
for
any
field.
B
This
is
an
example
of
how
the
dot
info
file
for
the
two
column
layout
they
were
using.
This
is
how
it
looks
in
person.
The
template
file
contains
nothing
in
here
other
than
adjust
the
layout
itself.
The
layout
regions
essentially,
and
then
the
CSS
is
responsible
for
actually
doing
the
layout
of
that
particular
order,
or
the
structural
CSS
for
that
particular
page
for
that
particular
layout.
B
I
think
that's
pretty
much!
Does
it
as
far
as
our
demonstration
goes
like
the
the
coding
portion
of
layouts
is
really
simple.
The
way
that
blocks
work
are
very
similar
to
Drupal
7,
but
just
sort
of
improved
slightly
with
some
new
powers
and
the
addition
of
block
classes
and
then
from
a
site
builders.
Standpoint
layouts
should
be
much
more
friendly
than
panels
in
Drupal
7,
but
much
much
more
powerful
than
the
traditional
block
system
of
Drupal
7.
B
A
Was
a
pretty
comprehensive,
general
deck
today
and
also
to
our
attendees.
If
you
guys
have
any
questions,
this
would
be
the
time
stamp
amount
and
we
just
take
them
up
one
by
one.
So
right
now
we
have
a
popular
question
set
up.
So
a
podsnap
is
how
to
layout
compared
to
what
Drupal
8
is
moving
for
size
billion.
B
I'd,
say
the
big
difference
between
backdrop
and
Drupal
8
is
that
as
far
as
I
know,
there's
not
contextual
information
passed
into
blocks,
so
you
can
still
pull
it
out
of
the
page
URL
that
you
were
on
to
do
some
thing
that
kind
of
imitates
context,
but
it's
not
built
in
quite
in
the
same
way,
and
also
primarily
in
Drupal
8.
There's
no
idea
of
these
of
a
layout
top-level
concept.
Interpolate.
A
B
So
the
first,
the
first
question
is,
you
know:
could
a
module
create
additional
layouts
if
it
wanted
to?
Yes?
Actually
it
could,
although
primarily
the
the
main
mechanism
for
making
additional
layouts
is
that
so
this
is
my
at
my
backdrop,
site
just
like
the
the
root
directory
of
it,
and
it's
it's
pretty
similar
here
to
Drupal
7,
except
all
of
the
all
of
the
core
functionality,
like
core
modules
and
stuff,
like
that,
it's
been
put
into
the
core
directory
custom
modules
and
controls
would
go
here
into
this
modules.
B
Directory
and
layouts
are
a
whole
new
top-level
concept
so,
rather
than
having
a
module
or
a
theme
provide.
Let's
the
most
common
way
to
get
additional
layout
templates
is
just
to
make
new
top-level
layout
template.
Our
templates
I
mean
it's
just
a
whole
new
top-level
concept
like
a
theme
or
a
module,
there's
now
additionally
in
a
layout,
but
if
you
wanted
to,
you
can
also
use
there's
a
hook
and
I
think
that
it
is.
Let
me
check,
so
we
have
an
API
websites
similar
to
triples
API
website.
But,
okay,
oh
it's.
B
If
that's
what
the
question
was
rather
than
a
layout
template,
that's
also
possible
with
any
configuration
and
backdrop
if
you
want
to
have
your
module
include
some
kind
of
configuration
like
here's,
an
example
of
project
module,
there's
a
config
directory
in
here
and
you
just
throw
in
any
configuration
files.
You
want
to
be
included
with
your
module
in
in
your
config
directory.
B
So
if
you
wanted
to
set
up
a
layout
like
a
front
page
layout
or
something
like
that,
let's
see
then
I
could
go
into
my
config
directory
like
that
front
page,
one
that
I
have
layout
here
we
go
layouts
to
do
fronts
here
we
go
so
this
is
that
front
page
layout
that
I
set
up
again
in
a
JSON
representation.
I
could
take
that
JSON
file
and
just
copy
into
my
modules.
B
Config
directory
and
when
my
module
is
enabled
it
will
automatically
also
deploy
that
configuration
of
of
the
layout
configuration,
so
it's
like
instead
of
using
like
in
Drupal
7.
If
you
wanted
to
ship
a
default
view,
you'd
use
hook
views
default
views,
but
in
backdrop,
what
you
would
do
is
you
would
simply
take
the
views.
Configuration
file
like
this
recent
comments,
view
and
just
copy
that
into
your
modules,
config
directory,
and
then
it
will
be
installed
automatically
when
your
module
is
turned
on.
A
I
think
you've
answered
that
question
pretty
well,
I
think,
but
we
have
a
follow-up
question
Google,
which
is
asking,
or
it
seems
like
it's
a
requirement
for
a
team
to
support.
Unlimited
types
of
layouts
could
actually
make
it
more
difficult
for
in
Google
to
get
what
they
expect
out
of
the
team
right.
B
Yeah
there
we
have
had
that
as
a
challenge
that
I
think
that
is
totally
accurate
to
be
concerned
about
that
because,
like
let's
take
a
look
at
a
theme
that
is
in
core,
for
example
like
let's
take
a
look
at
the
Bartek
layouts
or
sorry,
the
parts
of
thing,
and
so
the
Bartik
theme
template
wise
is
well.
Okay,
there's
no
page
template
here,
but
if
I
were
to
actually
find
the
page
template
in
core
it's,
it's
there's
nothing
in
it
anymore.
B
So,
let's
see
if
I
open
up
sorry
core
modules
system,
I
think
is
where
the
page
template
is,
and
so
the
page
template
now
doesn't
have
anything
in
it
anymore.
It's
just
you
know
the
HTML
tag,
the
head
tag
and
then
the
body
tag,
and
that's
it.
This
print
page,
is
the
entire
portion
of
the
page
that
is
responsible
that
that
the
layouts
are
responsible
for,
and
so
you
do
end
up
with
a
little
bit
of
overlap
between
the
display
side
of
things
and
the
layout
side
of
things,
and
so
in
the
Bartik
theme.
B
B
So,
for
example
like
on
this
home
page,
let's
see
if
I
can
find
a
page
yeah
finding
a
page
that
actually
isn't
long
enough
might
be
a
little
bit
of
a
challenge,
but
yeah
there's
a
little
bit
of
code
to
push
this
footer
down
to
the
bottom
and
in
the
event
that
the
page
isn't
long
enough
and
you're
right
that
there's
a
little
overlap
there
between
themes
and
layouts.
They
can
make
that
a
little
trickier,
but
there's
the
trade-off
there
of.
B
Basically,
you
can
use
any
grid
system.
You
want
with
any
theme
you
want
and
they're
just
entirely
separated
now.
So
if
you
wanted
to
use
a
theme
that
you
found
off
the
internet,
but
you
wanted
to
use
the
Twitter
bootstrap
grid
system,
then
you
could
do
that
and
you
can
use
grid
systems
that
are
separate
from
the
theme.
So
you
can
use
any
grid
system
with
any
theme
now
like.
If
you
want
Zen
grids
or
Susy
or
bootstrap,
you
can
choose
your
grid
system
independently
of
the
theme.
They're
no
longer
restricted
to
each
other.
B
Yeah
we're
actually
we're
working
on
some
things
to
make
it
so
that
there's
less
layout
information
needed,
for
example,
like
right
now
in
so
in
some
things
you
can
do
already
to
mitigate
these
problems-
is
that
you
can
do
things
like
you
can
configure
per
block
like.
If
you
know
you
can
can
set
block
classes
that
make
it
so
that
you
will
have
something
consistent
to
work
with
what
in
the
next
version,
actually
there's
there's
a
patch
that
it's
probably
going
to
be
done
in
the
next
couple
of
weeks.
B
Actually,
in
addition
to
being
able
to
add
blocks
into
regions,
we're
also
making
it
so
that
you
can
configure
regions.
So
this
would
turn
into
a
drop
button
like
this
configure
link
is,
and
you
could
configure
a
region
and
add
classes
to
a
particular
region,
and
that
makes
it
so
that
in
like
our
you
know
in
in
this
code
here
and
in
part
aquarii
ii,
all
of
these
region
names
based
on
the
classes
that
we
know
are
in
the
layout.
B
You
wouldn't
necessarily
need
to
do
that
anymore,
because
he
would
have
the
ability
to
use
either
configuration
and
put
in
classes
on
your
individual
regions,
or
you
could
use
as
a
theme.
You
could
use
pre
process
functions
to
pre-process
in
classes
on
to
on
to
regions
to
make
it
so
that
you
would
have
something
consistent
to
work
with.
So
that's
some
examples
like
some
ways
that
that's
being
hubs.
B
Yeah,
it's
it's
they're,
not
required.
Actually,
what
should
be
happening
here
is
that
any
any
theme
really
should
work
with
any
layout.
If
I
were
to
pull
up
some
examples
here,
like
any
I,
don't
have
any
other
themes
on
my
local
host
here,
but
any
theme
that
you
find
like
so
this
is
backdrops
I
started
work.
This
is
our
list
of
themes
so
far
that
we
have
available
for
the
project.
B
It's
pretty
well
in
line
that
you
can
use
any
layouts
you
want,
and
you
can
use
any
theme
you
want,
and
you
can
just
click
them
together.
Basically,
some
examples
of
layouts
that
are
in
the
contribute
to
a
layout.
Yet,
for
let's
see,
there's
a
little
little
bit
too
bad
that
it's
not
out
here
yet,
but
there's
a
the
radix
project
is
also
available
for
Mac
choppers,
it's
available
for
drupal
as
well.
B
So
so
multi-site
advantages,
so
there
are
some
differences
in
backdrop,
land
that
you
should
be
aware
of.
Really
it's
really
similar
to
to
Drupal
in.
In
the
the
regard
of
multi
sites
configuration,
there
is
a
sites
directory
just
like
in
Drupal
7
and
in
Drupal
8.
We
do
have
some
differences
in
that.
B
We
assume
that
out
of
the
box,
that
the
most
likely
configuration
is
a
single
site
situation,
and
so
like
the
settings
that
PHP
file
now,
instead
of
being
in
sites
default
settings,
dot
PHP
is
just
in
in
the
root
and
in
addition
to
that,
like
there's,
no
sites
all
directory
the
sites.
All
directory
now
is
just
the
the
root
layouts,
the
root
modules,
the
roots
themes
directory,
like
all
of
those
things
that
used
to
be
in
site.
Salt
now
are
all
just
directly
in
the
roots
and
in
the
site's
directory.
B
Out-Of-The-Box,
there's
nothing
in
this
directory
at
all.
However,
you
still
can
use
this
for
multi-site
set
up
its
all
of
that
functionality
is
all
still
there.
It's
documented
here-
and
this
read
me
how
multi-site
works
in
backdrop
in
Drupal
7,
you
used
to
just
create
a
folder.
That
would
be
the
name
of
your
site
like
example.com,
or
something
like
that,
and
then
you
would
have
like
inside
of
here
another
setting
stuff
PHP
file
and
any
modules
that
you
wanted
for
this
particular
site.
B
And
then,
if
the
URL
was
dub,
dub,
dub
example.com,
then
this
setting
stop
PHP
would
be
used
in
a
different
database
would
be
used,
but
it
would
share
all
the
modules
in
backdrop
you
have
to.
This
is
a
requirement
you
have
to
do.
Mapping
like
this,
where,
if
you
had
a
bit
of
example.com,
you
would
have
to
map
it
to
a
to
the
directory
here
that
example
that
come
so
this
is.
This
has
got
some
advantages
and
that
it's
a
lot
more
efficient.
For
example,
that's
in
Drupal
7,
every
single
page
load.
B
The
first
thing
it
does
is
check
7
different
permutations
of
what
directory
it's
looking
for
and
then,
if
it
doesn't
find
one
that
it
falls
back
to
default.
So
it's
doing
for
no
reason
on
every
single,
every
single
page
request
its
checking.
If
seven
different
directories
exist
and
then
it
falls
back
to
using
sites
defaults
in
backdrop,
what
it
does
instead
is.
It
looks
first
for
the
site's
PHP.
B
If
you
had
a
dev
site,
you
could
map
all
of
them
to
the
same
directory,
and
you
wouldn't
need
to
worry
about
making
some
links
all
over
the
place,
which
is
the
most
common
approach
in
Drupal
7.
Although
you
can
do
this
in
Drupal
7
as
well
like
in
backdrop.
This
is
required
from
an
efficiency
standpoint
and
a
consistency
stand
and
also
probably
say
that
multisite
is
also
going
to
be
well.
B
Any
site
really
is
is
is
going
to
be
helped
along
by
configuration
management
by
the
ability
for
you
to
store
all
of
your
site
configuration
all
of
the
settings,
all
the
content
types
all
of
the
fields,
all
the
views,
all
the
layouts.
All
the
configurations
of
all
these
things
are
all
in
JSON
files
and,
if
you're
doing
a
multi-site
installation,
you're,
probably
dealing
with
a
lot
of
different
code
bases,
and
this
makes
it
so
that
you
can
track
your
code
or
your
configuration
on
these
different
sites
more
consistently.
B
So
you
can
use
version
control
like
get
to
control
or
to
keep
track
of
all
of
these
different
files,
and
when
people
are
modifying
code
on
individual
sites,
you'll
be
able
to
see
in
your
version
control
system
which
files
have
been
changed
on
which
sites
and
if,
in
a
multi-site
situation,
you
would
have
multiple
config
directories.
Of
course,
just
like
you
would
have
multiple
files
directories
like
they're
all
they
should
all
be
separate
from
each
other
and
as
a
best
practice.
B
What
you
also
should
do
is
like
we
have
this
hash
in
the
config
directory
by
default
in
the
files.
As
a
files
subdirectory,
but
if
you
were
running
this
in
production,
what
you
would
want
to
do
is
move
your
configuration
directories
outside
of
the
web
route
and
then
have
all
of
your
configuration
directories
all
all
in
one
place,
one
per
site.
So
the
same
thing
same
as
you
would
have
the
site's
directory
here,
you
would
have
one
config
directory
for
each
site
in
your
multi-site
install,
so
I
hope
that
I
hope.
A
B
So
database,
wise,
like
the
database
structure
between
Drupal
7
and
backdrop,
is,
is
really
close.
It's
almost
identical.
If
you
have
a
simple
site,
you
can
do
the
same
thing.
You
used
to
be
able
to
do
with
traditional
Drupal
installs,
where
you
can
visit,
update,
dot,
PHP,
and
if
your
database
is
pointed
you're
setting
stuff
PHP
file
is
pointed
at
a
Drupal
7
database.
B
Then
it
will
upgrade
your
entire
Drupal
7
database
with
all
of
the
things
that
it
knows
how
to
do
so
fields,
content
types
use
vocabularies:
it
will
pull
all
that
stuff
from
your
Drupal
7
site
into
a
backdrop
site,
and
it
takes
a
couple
of
seconds
truth
be
told,
because
the
the
database
schema
between
backdrop
and
Drupal
7
is
is
very
similar.
There's
almost
no
work,
that's
necessary
to
get
your
data
out
of
a
Drupal
7
site
and
into
a
backdrop
site,
because
they're
stored
the
same
way.
It's
a
really
similar
code.
B
If
you
do
want
to
rebuild
your
website,
we
are
working
on
a
port
of
migrate
module,
so
you
would
do
the
same
thing
that
you
did
in
Drupal
7.
If
you
wanted
to
take
that
route,
you
could
install
the
migrate
contributor
and
then
set
up
a
migration
path
between
a
Drupal
7
website
and
back
to
our
website,
and
that
also
goes
for.
If
you
want
to
upgrade
from
Drupal
6,
you
know
like,
if
you
have
a
Drupal
6
website
it
traditionally
like
in
backdrop.
B
A
B
B
The
migration
system
right
now
isn't
complete,
though
I
think
that
they're
planning
on
on
getting
some
more
of
it
out
in
8.1,
but
right
now
like
as
far
as
I,
know,
upgrades
from
from
Drupal
7
into
Drupal.
8
really
aren't,
aren't
it's
like
it's,
not
it's
not
automated
in
any
in
any
real
fashion.
At
this
point,
like
even
doing
an
upgrade
right
now,
I
wouldn't
say
it's
not
possible,
but
it's
it's
difficult
like
it's,
not
a
built-in
system
of
Drupal
8.
At
this
point,
so
there
is
no
upgrade
right
now
from
Drupal
7.
B
A
B
Yeah,
so
okay,
yeah
there's
some
things
so
backdrop
can
triage,
so
sowed
rush,
isn't
natively
compatible
with
backdrop.
If
you
try
to
used
rush
on
a
backdrop
website,
it
just
won't
find
it
will
just
be
like
this.
Isn't
a
Drupal
install
I,
don't
know
how
to
work
with
this,
but
we
do
have
Josh
integration
as
ad
rush
extension,
and
so,
if
you
download
rush,
it
needs
to
be
drush,
eight,
the
latest
version.
A
Alright,
so
you
reach
the
end
of
this
session
and
attendees.
If
you
have
any
questions,
we
could
probably
take
one
last
question:
if
anybody
has
any
infection,
and
also
of
the
movie
go,
I
will
protect
us
at
what
point
like
during
the
development
of
the
AIDS.
Did
you
think
that
it
would
like
what
may
know
exactly
what
is
that
a
meaningful,
strong
feedback,
yeah.
B
So
so,
on,
a
personal
note
like
where
this
came
from
was
I
was
really
involved
in
Drupal
8
development.
Earlier
on
in
the
cycle
like
I'm,
a
really
passionate
Drupal
developer
I've
been
doing
it
for
over
a
decade
now,
10
years
that
I've
been
in
in
the
Drupal
community,
writing
Drupal
code
and
like
I,
love
the
software
and
I
love
the
community
like
it's.
This
is
basically
I
was
really
frustrated
with
the
Drupal
8
code.
At
one
point,
I
was
working
on
ckeditor
module
and
I
wrote
the
original
CK
editor
module
and
I.
B
Remember
when
I
put
up
the
module-
and
it
was
just
about
to
be
committed-
it
was
just
about
ready,
but
then
before
it
could
be
committed,
it
was
stated.
Well,
we
don't
actually
write
code
that
way
anymore,
hang
on.
Let
me
rewrite
this
entire
module
to
use
plugins
instead,
and
it
was
like
just
moved
everything
around
like
in
a
really
drastic
way
and
thanks
to
the
people
that
actually
did
that
rewriting
because
I
didn't
know
how
to
do
that
at
the
time.
But
it
really
hit
me
that
I
was
like
wow.
B
This
thing
is
totally
different.
Like
I,
don't
know
how
to
write
Drupal
8
code
and
during
the
DA
development
cycle,
things
were
changing
all
the
time.
As
very
frustrating
experience
like
trying
to
trying
to
write
any
code
at
all
because
code,
you
wrote
one
week,
just
wouldn't
work
the
next
week
and
things
were
constantly
changing.
B
Obviously,
that's
settled
down
quite
a
bit,
but
the
big
change
is
still
there
that
the
Drupal
8
code
is
entirely
different
from
Drupal
7
code
and
that
hit
me
as
wow.
This
is
going
to
be
a
lot
of
work
for
a
lot
of
people
like
there
are
millions
of
a
million
Drupal
web
sites
out
there,
and
all
of
those
websites
will
need
to
go
through
the
same
process.
That
I'm
feeling
right
now
of
none
of
my
old
code
works.
B
I
need
to
write
all
new
code
to
upgrade
my
website
and
I'd,
been
through
a
couple
of
reasonably
painful
Drupal
upgrading
experiences
in
the
past
from
triple
five
to
triple
six
six
drupal,
seven
and
I
saw
the
triple
seven
Drupal
8
shift
and
the
amount
of
like
frustration
and
cost
that
that
was
going
to
put
on
to
all
of
the
users
of
Drupal
and
I.
Just
basically
I
couldn't
accept
that
anymore,
and
so
that
was
that
was
the
real
driver
there.
B
That's
that
the
cost
of
the
change
was
too
high
and
by
making
backdrop,
we've
provided
something
that
provides
all
the
functionality
and
the
familiarity
of
Drupal,
but
has
that
shift
where
we're
trying
really
hard
to
make
it?
So
that's
the
the
chain,
like
will
still
be
delivering
new
features
and
new
functionality,
but
we'll
be
trying
to
limit
the
change,
because
that
those
changes
for
changes
sake
really
just
increased
the
learning
curve
and
the
the
ownership
cost
of
your
website.
So
that's
that's
the
the
basic
explanation
right
there.
B
It
was
in
in
the
middle
of
the
Drupal
8
cycle,
ckeditor
module
when
it
was
rewritten
and
I
just
couldn't.
I
did
I
didn't
know
how
to
update
the
code
that
I
had
originally
written.
I
tried
for
several
more
months
before
I
gave
up,
though,
and
and
then
I
laid
low
for
a
little
while
and
then
and
then
we
announced
back
job.
A
That
was
pretty
good
back
story
to
know
and
it
just
to
understand
back
drop,
all
the
more
so
yeah.
That
sounds
great
to
know
so
with
that
we
come
to
the
end.
This
webinar
and
thank
you,
Mike
Foley
technique
for
leading
such
a
wonderful
session,
and
you
sure
everyone
found
your
presentation
very
interesting
and
insightful
and
who'd
like
to
try
our
backdrop
pretty
soon
and
a
big
thank
you
to
all
of
our
attendees
for
joining
us
today
and
you
all
have
been
afraid
audience
with
all
the
specials.
A
I
would
also
like
to
announce
that
our
next
webinar
is
on
need
former
2.8
and
it
will
be
hosted
on
9th
of
March
2016
and
will
be
led
by
max
lemon.
Who
is
the
youth
he
need
for
commerce
sites,
for
it,
searching
and
no
details
educating
in
age
from
earthdome
each
18,
and
thank
you
again
for
joining
us
today
and
hope
to
see
you
at
our
next
webinar.
Thank
you
and
good.