
►
From YouTube: Virtual Backdrop User Group: Layouts
Description
Layouts!
B
A
B
Thinking
we
did
that
now,
but
whether
you're
right
it's
too
late
now,
isn't
it
everybody
on
the
air?
So,
but
that's
the
way
this
user
group
is
supposed
to
work.
You
can't
watch
it
anonymously
via
YouTube,
but
we're
live,
and
this
should
be
interactive.
I'm
going
to
go
ahead
and
introduce
gentle
or
just
going
to
started.
I
would
just
I,
don't
know
if
everybody
knows
each
other.
A
B
I
mean
it's
a
general
practice
for
these
user
groups:
I'd
like
us
to
start
with
quick
introductions.
So
if
you
don't
have
a
mic-
and
you
want
to
say
hello
and
something
about
yourself
in
the
chat-
go
ahead,
we,
this
is
our
second
user
group.
We
had
the
first
one
on
config
management.
Today
we're
going
to
talk
about
layouts.
These
are
intended
to
be
interactive,
so
please
ask
questions:
we're
going
to
try
and
save
a
little
bit
of
time
at
the
end
for
questions
that
might
not
be
lay
out
specific.
B
A
C
C
A
Jen
I've
done
a
lot
of
stuff
with
backdrop
I'm
currently
working
on
a
site-
it's
probably
the
one
I'm
gonna
demo
for
you
guys
today,
although
you
want
to
see
different
once
we
could
do
that
too.
I'm.
Currently
work
and
I
said
that's
an
upgrade
from
Drupal
6,
so
I
went
from
Drupal
6
to
triple
7
in
Drupal
7
to
backdrop
and
a
lot
of
the
stuff
is
exactly
the
same.
A
Some
of
the
views
carrying
right
over
and
a
lot
of
this
stuff
is
entirely
new,
so
called
layout
stuff,
for
example,
is
replacement
of
things,
I've
been
doing
panels
and
Drupal
6,
but
sort
of
throughout
and
started
over
so
yeah,
it's
been
kind
of
fun
to
go
through
that
process
of
how
do
you
do
a
layout
in
backdrop?
The
way
you
did
a
panel
in
Drupal
6,
this
you're,
not
exactly
coming
from
the
white
pants,
which
isn't
Drupal
7
either.
B
A
A
Like
trying
to
get
all
the
windows
out
of
the
light,
maybe
I'll
just
leave
it
right
now.
We're
looking
at
it's
called
fashion,
schools
and
we're
looking
at
layout.
Landing
pages
is
a
taxonomy
term
page,
and
it's
got
like
the
page
title
up
top
that
has
some
featured
content.
This
is
actually
in
a
slideshow.
um
Some
of
the
view
notes,
look
like
they
haven't
been
set
up
yet
just
sign
slideshows
huge
on
this
page
and
then
underneath
that
we
have
a
custom
content,
type,
adblock
sort
of
thing.
A
A
This
is
great
site
in
the
middle
of
development
and
then
some
like
widgets
that
lead
to
some
custom
lead
generation
tools,
so
they're
gonna
go
on
here
later,
so
this
is
kind
of
came
from
a
Drupal
6
site
that
followed
the
same
general
pattern
and
we
are
using
so
there's
a
little
kind
of
taxonomy
pages,
so
raising
taxonomy
may
need
to
build
all
of
our
menus.
Every
one
of
these
is
a
vocabulary
Carioca
program,
so
can't
wait
for
people.
A
So
all
these
landing
pages
are
taxonomy
term
pages,
the
same
pattern
for
close
across
the
entire
site,
which
hopefully
will
make
it
consistent
and
easy
to
manage.
And
then
every
individual
piece
of
content
has
a
separate
layout
preview,
something
one
column.
So
it's
got
two
columns
and
so
there's
some
different
layouts
for
content
type
stuff
going
on
too
so
I
want
to
show
you
what
that
looks
like
from
the
layouts
interface.
A
You
can
see
here.
I've
got
a
bunch
of
different
layouts.
Going
on
my
default
layout
is
just
that
one
column,
one
that
we
saw
on
a
taxonomy
term
page
and
then
I've
got
a
couple
of
specific
overrides
for
like
the
locations
page
itself
and
then
one
of
the
February's
which
I
haven't
filtered
down
yet
will
also
have
a
different
layout.
Look
where
we've
got
three
columns
of
links
in
the
in
the
middle
of
it.
You
have
an
example
of
that
page.
A
A
And
so
here
I'm
using
a
selection
criteria,
for
which
term
it
is
it's
just
one
term,
and
here
I'll
have
a
selection
criteria
for
which
vocabulary
it
is
which
I
don't
I've
set
up
yet
and
I
have
a
bunch
of
standalone
pages.
That
just
have
paths
like
scholarship
was
just
when
I
built
it.
One
URL
programs
is
one
another
one,
people
is
one
another
one,
and
these
are
going
to
be
landing
pages
for
the
vocabulary
so,
rather
than
having
a
taxonomy
term
page,
this
is
going
to
show
all
of
the
content
in
a
given
cab.
A
You
Larry
and
then
I
have
a
couple
of
overrides
for
the
node
path,
so
there's
a
general
one
that
will
work
on
every
content
type,
which
is
the
two
column
one
and
then
I
have
a
couple
of
types
of
content
that
just
use
the
one
column
layout.
So
it's
a
page
in
web
form
and
then
I
have
homepage
layout,
which
is
a
little
different
for
everything
else,
as
you'd
probably
expect
and
a
couple
of
other
sample
pages.
So
some
these.
How
much
you
want?
You
talked
about
this
page,
some.
A
Are
custom
I'm,
usually
pretty
good
about
making
different
icons
for
my
custom
layouts
than
the
ones
that
are
in
core
so
like
you
can
see
the
home
page
one
and
the
category
page
layout
is
different
and
then,
although,
though
I'm
just
using
court,
layouts
and
they've
overridden
the
template
files
for
those
in
some
cases
in
let's
see
which
we
look
at,
maybe
the
X
on
anyone's
is
very
exciting.
When.
B
A
Like
usually
I,
try
and
start
with
a
core
layout
and
like
oh
yeah,
this
design
like
this
design,
closely
matches.
You
know
something
that
we
have
in
core
and
then
oh,
it's
a
Oh.
Actually
it's
a
little
different,
because
I'm
gonna
have
an
extra
stripe
somewhere
and
so
then
I'll
just
take
the
core
layout
copy
it
and
add
the
name
region,
and
then
it's
you
know
it
still
starts
from
something
that's
really
similar
to
the
core
layouts,
but
I
end
up
with
a
copy.
A
A
Okay,
so
this
is
the
category
page
layout,
which
maps
to
this
California
page,
for
example,
where
top
we
have
the
slide
show,
and
we
have.
This
is
just
a
bunch
of
a
list
of
all
schools
in
California.
This
is
the
taxonomy
term.
This
is
the
other
stuff.
So
we
look
on
the
back
in
the
header.
That's
all
the
stuff
that
we
have
on
every
page
school
finest
fashion,
school
logo
find
school
button.
A
I
have
a
search
thing
in
here,
I'm,
not
sure
if
you
guys
saw
that
this
is
kind
of
fun,
something
my
designer
came
up
with
when
we
put
on
all
these
bgp
sites
and
then
there
is
the
main
menu.
This
is
just
the
standard,
smart
menu
that
comes
in
backdrop
core
got
the
normal
page
title
up
there.
At
top,
we
just
styled
it
and
then
featured
articles.
This
is
the
slideshow
school
data.
A
This
is
just
this
list
of
schools
and
we
have-
and
this
is
the
other
school
data
here-
is
one
column,
and
here
it's
three.
This
is
just
styled
with
CSS
to
be
a
three
column
list,
so
not
actually
layout
related.
Here's,
the
extra
column
or
extra
row
that
I
have
on
some
pages
and
then
I
have
this
three
column.
This
is
what
made
it
the
Geary
history
column
section
where
every
taxonomy
term
has
the
ability
to
add
sub
cues.
A
So
if
you
had
three
different
sets
of
lists
you
wanted
for
like
California,
you
can
curate
the
content
that
would
appear
there
and
you'll
get
the
three
listing.
So
that
was
what
the
you
might
have
seen
in
the
design
right
here.
He
could
have
like
here's
school
information
for
California
program,
information
or
settings
whatever,
and
you
can
link
to
all
articles
and
so
managing
that
with
note
Q
sub
queues
and
they
just
appear
in
the
Conoley
at
so
that's
where
the
three
columns
are
the
queue
titles.
A
What
you
saw
in
the
editing
where
I
added
left
center
and
right
and
then
this
is
this-
is
Buse
for
the
sub
cues
for
left
center
right
and
then
the
content.
This
is
main
page
hunt
is
just
the
taxonomy
term
description
and
any
fields
added
to
it
like
a
torn
image
and
then
featured
schools
is
the
custom
content
type.
The
Quinn
Street
co-listing
isn't
live
right
now,
but
there's
a
12-point
Street
that'll
give
you
a
legion
source,
which
we
use
on
some
sites,
taxonomy
term
listing.
A
That's
the
one
that
says
recent
articles
and
then
the
promo
at
the
bottom,
which
is
gonna,
be
any
animation.
It's
not
it'll,
be
some
other
kind
of
contest,
but
and
then
the
find
school
widget
bar.
So
this
page
has
a
lot
of
rows,
right,
footer
and
then
all
of
this
stuff.
So
all
of
this,
like
footer
above
bottom
above
this,
is
all
stuff
that
I
added
to
the
BGP
layout
middle
above
the
top.
A
So
there's
a
bunch
of
additional
rows,
so
we're
added
just
to
compensate
for
the
stripe
being
in
the
layout,
but
you
wouldn't
normally
need
those
except
for
that
I
find
it
easier
to
do
the
striping
across
the
whole
pages
are
oh
look
if
this
is
a
bleed
I
like
to
add
a
proud
to
trying
to
like
style,
a
block
to
go
all
the
way
to
that.
Just
the
page
like
a
hero.
A
One
layout
that
was
all
full
bleed
had
blocks
that
went
all
the
way
across
the
top,
but
because
on
a
lot
of
pages,
that's
not
the
design.
I
was
working
with
I.
Just
figured
I
would
do
one
lamp
that
had
a
row
for
each
color
and
then
it
would
be
easy
to
color
each
row
like
all
this
bottom
ones,
always
blue
and
it's
always
full
bleed,
but
I
had
some
pages.
A
Where,
like
the
middle
one
wasn't
fully,
it
was
just
white
all
the
way
through
so-
and
this
is
another
thing
it's
like
really
depends
on
what
your
designer
wants
and
what
the
person
building
this
site
like
there's
any
way
any
number
of
ways
to
do.
This
I
just
choose
to
do
a
row
for
each
background.
Color.
A
A
Flexibility,
oats,
which
is
really
similar
to
the
layout
builder
layout
from
panels
and
I
noticed
recently
after
I,
think
we
talked
last
time
about
the
Leon.
What
was
working
on
there's
a
theme
called
WordPress
called
divvy.
That
is
a
visual
layout
builder
that
allows
you
to
add
rows
and
column
some
place
blocks
in
them,
which
I
think
this
is
an
example
of
a
front-end
interface.
Where
you
can
do
it.
They
also
have
a
back-end
interface.
A
That
looks
a
little
bit
more
like
our
layout
system,
but
it's
something
I,
think
everybody
in
well,
not
everybody
in
the
WordPress
community,
but
a
whole
bunch
of
people
in
the
WordPress
community
really
love
this
tool
because
it
allows
them
to
take
advantage
of
layouts
without
needing
to
you
know,
code
their
own
write
everything
you
want.
You
just
add
a
new
row
from
the
front
end
and
so
I
think
having
something
like
them.
On
till
the
top
element
worked
on
that
allowed.
A
It's
not
very
exciting,
so
this
is
the
BGP
Erie
layout
I
was
talking
about
I
added
like
the
top
below
region
middle
above
region,
bottom
above
and
footer
above
so
I
added
like
for
roasts,
just
to
get
those
four
different
colors
and
then
in
the
template
itself.
There's
just
a
bunch
of
sections
that
say
you
know
if
content
top
content
top
if
content
top
to
content
talk
to
you.
A
So
it's
exactly
just
a
copy
of
the
row
that
was
already
there
they're
just
with
different
CSS
identifiers
and
obviously
printing
the
different
content
and
so
having
the
outer
wrapper.
And
then
the
inner
wrapper
means
that
I
can
have
a
full
bleed
background
stripe
and
then
the
content
still
nerd,
along
with
everything
else
on
every
break
point.
So
I
looked
at
this
recently.
Hopefully
it's
not
broken
so
like
the
content
is
a
specific
width.
A
Sorry
to
stop
my
screen
sharing.
Is
there
anything
else
you
guys
wanted
to
see
in
particular
I
know
you
want
it
Tim
you
mentioned
you
wanted
to
save,
sometimes
the
end
to
talk
about
things
that
weren't
layout
related,
so
I
don't
spend
too
much
time
nattering
about
layouts,
but
I
did
want
to
see
if
there
was
anything
in
particular,
you
guys
were
curious
about
I'm
handling,
layouts
I'm,
just
kind
of
showing
you
how
I
build
sites
is
maybe
not
the
best
use
of
our
time,
but
maybe
you're
finding
it
interesting.
Well.
B
I
so
I
recall
that
when
I
did
my
first
back
drop
sites
that
let
the
layout
system
was
one
of
the
hardest
things
to
adjust
to
from
coming
from
Drupal
7.
Yes,
it
was
the
biggest
paradigm
shift
right
and
so
I'm
trying
to
remember
like
what
were
some
of
those
things.
I
mean
part
of
this.
This
may
be
always
could
be
kind
of
a
tutorial,
a
bit
or
introduction
for
beginners.
So
beyond
the
people
here,
there
might
be
some
beginners
looking
at
it.
I
think
we
should
not.
B
A
Okay,
so
in
my
layout
list,
I
have
two
taxonomy
term
layouts
and
two
new
layouts.
So
these
are
the
confusing
ones
for
most
people,
because
the
path
you
enter
has
a
percent
in
it,
which
is
something
that's
kind
of
mind-boggling
for
people
that
you
put
in
a
percent
to
indicate,
like
all
notes,
that
little
bit
note
slash
anything
doesn't
quite
work
like
a
wildstar
like
if
you
created
a
page
and
went
note
slash
for
like
the
word
floor,
it's
not
going
to
look
the
same
as
the
internal
system
path.
A
A
Where,
like
you,
have
to
figure
out
what
order
you
want
them
to
come
in
and
then
even
when
you
know
order,
you
want
them
to
get
them
and
like
finding
this
with
the
order
button
on
the
top
right
in
order
to
change.
That
is
also
like,
maybe
not
very
intuitive,
for
people,
so
for
me,
I
always
start
when
I'm
building
a
site
I
always
start
using
the
default
layout
and
I
choose
my
most
basic
design
to
start
from.
A
So
here
I'll
say:
if
the
content
type
is
one
a
page
web
form
use
this
layout
and
then
it'll
stop,
and
if
it's
not
paid
your
web
form,
it
will
fall
through
to
a
node
in
the
in
the
same
way
that
it'll
go
through
all
of
these
layouts
on
the
top,
and
if
none
of
them
match
it
will
fall
through
to
default.
The
same
thing
happens
for
any
given
path
match,
so
the
only
condition
I
have
here
is
the
one
per
page
and
web
form
and
then
for
taxonomy
terms.
A
It
looks
like
the
way
I
have
this
set
up
right
now
that
it
won't
work.
If
anyone
noticed
it's
that
so
my
first
one
has
no
conditions
the
category
layout,
my
person
has
no
condition
set,
so
it'll
always
be
used.
My
second
one
has
a
condition
set,
but
doesn't
matter
because
there's
nothing
that
will
ever
stop
the
first
one
from
working,
and
so,
if
I
wanted
the
locations
layout
to
be
used,
I
would
need
to
reorder
them.
I
haven't
actually
set
up
my
locations
layout.
A
Yet
so
I
don't
know
what
will
happen
if
I
do
this?
It's
fun
we'll
do
it
anyway.
So
this
is,
it's
gonna
have
different
content,
because
this
on
my
site,
the
locations
taxonomy
term
page,
is
a
parent
of
all
of
the
terms
in
that
section.
So
I
think
on
my
site.
Locations
is
flows
on
colleges
and
it's
gonna
have
like
a
map
on
it,
and
the
map
will
be
different
from
everything
else.
So
I
don't
know
it's
gonna
go
on.
Here
looks
like
right
now,
that's
probably
where
the
map
goes.
A
There's
nothing
different
about
this
layout
yeah,
except
for
this
big
blank
hole
in
the
page
that
isn't
built
but
yeah.
If
I
want
this
to
actually
be
used
on
the
school
and
college
locations,
they
need
to
be
in
the
right
order.
So
if
I'd
done
it
before
and
I've
gone
to
this
page,
this
wouldn't
have
been
here.
It
would
have
been
the
same
as
the
other
pages,
which
I
think
is
nothing
there
right
now.
A
A
A
Conditions
on
individual
blocks,
I
know
you
can
do
this
and
I
think
when
I
first
started
something
at
backdrop,
sites
I
would
try
and
use
as
few
layouts
as
possible
and
on
each
layout,
I
would
add
a
ton
of
blocks
in
each
region
and
then
each
block
would
have
visibility
conditions.
You
can
do
that
if
that
works
better
for
your
model,
but
I
found
that
um
working
with
a
site.
A
It
just
made
more
sense
to
me
to
have
a
separate
layout
with
different
blocks
placed
than
it
did
to
have
one
layout
with
different
blocks
appearing
and
not
appearing
and
I.
Don't
know
if
that's
how
other
people
do
it
too
or
not,
but
yet,
like
I
could
have
had,
rather
than
having
two
layouts
under
taxonomy
term
I
could
have
chosen
one
layout
and
then,
in
that
section
on
you
know
sub
pages,
it
would
say
schooled
out
of
category
pages
and
then
on
the
parent
page.
A
It
would
have
been
the
mat
and
then
each
of
the
blocks
would
appear
in
one
instance
and
not
on
the
other,
and
you
can
use
the
same
visibility
condition
here
for
adding
a
taxonomy
term
ID.
As
you
can
on
the
parent
layout,
but
for
some
reason
it
didn't
make
as
much
sense
to
me
when
I
was
managing
them
to
do
it
that
way,
so
I
chose
to
do
it.
The
other
way
the
both
would
work
I.
B
A
Yeah
and
I
don't
know
that.
There's
any
reason
to
do
one
or
the
other
I
think
it's
all.
Just
preference
and
my
preference
ended
up
being
having
more
layouts
I,
think
that
might
have
also
been
for
a
configuration
import/export.
It
made
more
sense
for
me
to
be
like
okay.
Well,
if
I'm,
just
gonna
make
one
change
to
one
page,
I'll
just
export
and
import
that
one
config
file
rather
than
being
like
okay.
A
Well,
if
I
export
this
config
file,
it
might
affect
other
pages
as
well,
so
it
might
have
just
been
something
that
matched
my
like
deploying
changes
better
than
having
one
that
affected
many
pages,
I,
don't
know
I,
don't
know
why?
That's
just
what
I
decided
to
do
to
be
a
year
from
now,
I
changed
my
mind
and
start
getting
it
the
other
way.
A
Maybe
it's
different
for
each
project,
so
turbo
I
have
been
so.
A
lot
of
the
sites
have
been
working
on
for
the
past
few
years,
sort
of
matched
this
same
model
they're
all
on
these
bgp
sites,
where
they
all
are
very
taxonomy
base.
They're
all
several
content
types
that
fit
into
the
same
tax
on
these
across
the
whole
site
and
they're
all
sort
of
lead-gen
sites,
and
they
do
the
same
kinds
of
things,
and
it
could
be
that
as
I
start
doing
different
kinds
of
sites.
A
A
I'm
sure
there
are
I
haven't
run
into
any
issues.
I
know
labs
themselves
are
cached,
so
once
you
have
a
layout
given
for
specific
paths,
it
that
gets
faster.
Just
like
the
first
thing
you
set
it
up,
it'll
be
like
oh
hold
on
there's
a
layout
here
and
then
after
that,
I'd
be
like
I
know
actually
up.
It
is
for
that
I.
Don't
think
it
makes
any
difference
whether
you
have
ten
layouts
or
two
total,
because
there
is
always
cash
to
that
path.
A
I
think
the
only
the
real
thing
will
be
like
the
number
of
config
files.
You're
working
with
right
here
have
100
layouts,
that's
a
hundred
layout
config
files
and
then
yeah
just
managing
managing
the
visibility
rules.
I
think
for
me,
another
thing
that
makes
it
a
little
easier
is
that
when
you
look
at
the
layouts
page,
it
lists
the
conditions
right
there.
A
Yeah
I,
don't
know
it's
just
why
I
chose
to
do
I
think
that
there
are
I
do
have
some
sites
that
get
slower
than
others,
but
I
think
the
main
thing
that
causes
my
slower
sites
to
be
slow
is
the
size
of
the
menu
like
the
menus.
Get
really
big.
If
I
have
all
of
my
articles
look
in
the
menu
if
it
have
a
1,000
taxonomy
terms
that
are
all
in
the
menu
system
when
you
go
to
render
your
main
menu
and
it's
drop-down
menu
and
it
shows
every
page
on
the
site.
A
That's
the
slowest
part
of
the
render
process.
It's
just
building
the
menu,
especially
if
you
have
you
know,
you're
logged
in
and
you
have
different
permissions
like
it's
gonna,
be
rebuilding
that
menu.
Often
so
I
have
been
working
on
a
module
called
when
you,
when
you
block
cache
or
something
like
that,
I'm
trying
to
figure
out
like
all
the
different
places,
I
can
safely
cache
that
menu
and
see.
If
that
all
speed
things
up.
But
it
hasn't
been
super
successful.
B
If
anybody
any
questions,
ask
them
I
mean
I,
wonder
if
it
would
make
sense
to
spend
a
few
minutes
looking
closer
at
the
different
like
conditions
or
either
layouts
or
blocks
I
mean
you
mentioned
a
couple
of
them
pretty
quickly,
but
it
might
be
interesting
to
look
at
what
all
the
options
are
that
we
have
available
to
us.
Does
that
make
sense,
could
you
do
you
want
to
do
that
again
for
us
sure.
A
D
A
A
Okay,
so
I'm
on
the
home,
page
layout
and
I
just
opened
the
visibility.
I've
done,
ad
visibility,
condition
modal
and
you
can
see
that
the
options
here
pretty
limited,
because
there's
no
context
on
this
page
so
I
could
say
you
know,
show
if
it's
the
front
page
show
based
on
a
specific
language.
So
if
I
have
a
multilingual
site,
they
can
just
language
I
can
do
based
on
URL
path.
A
This
is
actually
when
I
end
up
using
a
lot,
because
sometimes
I
find
that
the
visibility
condition
that
I
want
doesn't
exist
like
there
isn't
a
tool
for
it,
but
I
have
a
path
pattern
that
I
can
match,
and
so
I
will
often
use
this
as
a
kind
of
a
workaround
I.
Can't
think
of
any
examples
of
that.
I
could
show
you
right
now,
but
I
will
see
if
one
comes
to
mind.
um
So
something
like
if
I
wanted
to
limit
this
to
a
file
path.
D
A
A
Let's
see
user
account
UID,
so
this
is
something
I
usually
only
use
on
the
user.
This
would
be
like
for
logged
in
user.
Yeah.
I,
don't
know,
I,
don't
know
that
I'm,
a
racist,
I
use
the
user
account
UID
visibility,
Kishen
condition
only
on
a
user
profile
page
like
if
I
wanted
to
have
a
special
dashboard.
For
you
know
one
particular
user
who's.
My
like
hotshot
super
admin
and
I
want
to
put
a
whole
bunch
of
special
admin
blocks
on
their
page.
A
I
might
be
like
ok,
if
UI,
if
user
ID
is
four,
then
do
something
different,
but
I
haven't
used
other
than
that.
um
Then,
let's
see,
there's
also
your
permission.
User
role,
these
they
use
a
lot
I
find
that
I
use
user
role
more
than
user
permission.
Although
I
know
user
permission
is
safer,
this
is
very
specific.
A
User
role
is
a
little
loose
because
you
can
change
permissions
on
stuff
and
that
page
might
still
show
up,
even
if
there's
stuff
on
that
page
they're
supposed
to
see
but
I
find
that
in
site
building
I
find
to
use
your
role.
um
Oh
I,
it's
a
much
better
match
to
what
I'm
actually
thinking,
rather
than
technically
building.
B
A
So,
for
example,
let's
take
like
a
news,
article
Rainey
you're,
looking
at
news
article
and
when
anyone
is
doing
that
article
say
it's
like
a
one
lay
out
centered
with
you
know,
just
a
long
bleed
of
text,
but
if
I'm
an
editor
for
this
site,
maybe
I
want
to
see,
like
other
articles
by
the
same
author,
I
could
put
a
block
in
a
sidebar.
That
is
other
articles
by
the
same
author
and
then
I
could
have
the
news
layout
appear.
A
You
know,
note
slash
percent,
where
type
is
news
for
everyone
and
then
above
that,
I
would
have
another
one
that
said,
node,
slash
percent
type
is
news,
user
role
is
editor
and
then
there
would
be
a
specific
column
added
or
specific
layout
use.
That
has
an
extra
column
when
editors
are
looking
at
that
page
and
that
way
they
can
say:
okay,
here's
this
article
and
then,
if
I
need
to
refer
to
other
stuff,
this
person's
built
there's
a
handy
list
right
there,
which
will
get
me
straight
to
them.
A
Maybe
that
list
will
have
like
edit
links
or
if
you're
using
um
you
know
some
kind
of
moderation.
It
could
have.
You
know
show
whether
the
articles
published
or
not
or
a
published
date
or
whatever
your
editors
need
for
your
workflow.
You
can
just
kind
of
plunk
it
right
there
and
they
can
see.
Okay,
this
person
has
six
articles
pending.
B
A
Other
thing,
I
just
want
to
say,
like
that.
The
number
of
conditions
you
get
for
a
page
without
context
is
very
limited.
But
if
you
look
at
like
the
node
context
here,
there
are
more
visibility
conditions
because
you
have
the
node
properties
available.
So
here
you
have
like
content
type
and
content.
Node
ID
I
also
have
a
couple
of
sites
where
I've
built
additional
custom,
visibility,
conditions
and
those,
you
might
add,
a
specific
field
value,
is
something
that
I
doing
where
it's
like.
A
Oh,
you
know,
I
need
the
news
article
to
have
a
different
layout,
whether
it's
a
press
release
or
whether
it's
a
news
story,
and
so
sometimes
that's
a
field
on
a
news.
Content
type
and
I
could
have
chosen
the
different
different
content
types.
The
one
called
press,
really
someone
called
news
story,
but
my
workflow
didn't
exactly
match
that
like
I
had
editors
that
wanted
to
create
new
stories
and
I
want
it,
you
know
all
of
the
fields
to
be
the
same
on
those
two
content
types,
so
it
made
more
sense,
just
add
another
field.
A
Let
them
choose
what
kind
of
news
it
was
so
then
I
would
add
a
visibility
condition
here
for
this
and
that's
um
a
little
bit
more
complicated
I
had
to
you
know,
write
a
custom
module
that
included
that,
but
it
is
possible
and
it's
the
kind
of
thing
where
I'm
like
I,
don't
really
know
if
this
needs
to
be
in
core
not,
but
there
probably
should
be
a
contribute.
Shoes
like
how
to
do
that,
just
and
really
complicated
to
get
from.
A
My
like
add
one
fields
to
build
the
UI
to
let
people
choose
which
fields
somebody
to
do
is
but
yeah
so
there's
all,
even
though
in
here
you
can
see
how
like
some
additional
things
are
added.
You
really
do
have
a
lot
more
power
here,
like
you
can
access
anything
on
the
node,
where
the
context
is
available.
A
Not
really
I
mean
there's
so
much
there's
so
much
to
talk
about
and
I,
don't
know.
What's
like
super
intuitive
and
what's
useful
like
I,
don't
know
if
the
way
I
do
things
is
any
different
from
the
way
guys
you
guys
have
sort
of
like
after
playing
with
it,
for
a
little
bit
just
landed
on
the
same
solutions
or
not
so
I,
don't
know,
I,
don't
know.
What's
the
best
use
of
our
time.
D
E
A
A
If
you
have
two
different
paths,
they
have
to
be
separate
and
I
would
rather
have
there
be
like
one,
and
you
have
a
reorder
thing
where,
if
you
wanted
to
control
the
order
you
can
or
if
you
want
to
just
get
to
work
on
all
of
them,
that
to
work
that
way
too
so
I
definitely
think
there's
room
for
improvement.
I
find
that
building
these
sites
is
really
fun,
but
then
managing
them.
You're,
like
oh
I,
have
to
make
it
change
to
for
layouts.
That's
not
so
much
fun,
but
yeah.
A
Having
the
reorder
thing
only
work
when
there's
a
shared
path,
I
think
is
confusing.
Some
people
don't
even
know
it's
there
at
all.
um
Yeah
I
think
there's
this
interface
isn't
or
take
some.
It
takes
some
getting
used
to
it's
better
than
panels,
but
you
know
it's
a
complicated
tool
and
trying
to
build
an
intuitive
interface
for
complicated
tool
is
hard.
B
So,
in
our
discussion
about
config
management,
we
asked
the
provocative
question
of
just
I:
don't
know
if
Luke's
listening
for
how
just
how
what
people's
experience
has
been
using
it
and
that
led
us
down
the
whole
path.
There's
anybody
else
is
iÃve
already
mentioned
that
I.
You
know.
I
love
the
the
layout
system
and
I
find
it
really
powerful,
but
it
was
the
biggest
paradigm
shift
from
Drupal
7,
so
it
took
a
while
for
me
to
wrap
my
head
around
it
I'm
curious
what
other
people's
experiences
were.
B
E
Typically
I
was
using
Omega
and
Celina
display
suite
so
with
Omega.
You
could
completely
you
right,
you
know,
have
reagent,
it
didn't
show
up
in
the
UI
and
you
could
also
like,
if
I
had
a
wanted
to
have
three
or
four
by
or
four
regions
at
the
top
I
could
put
more
reagent
at
the
top
in
that
zone
and
then
use
displace
week
to
do
a
lot
of
fancy
stuff
along
with
context
and
rules,
and
things
like
that,
so
a
layout
system
is
just
has
some
limitations
or
some
things
that
displace
we
could
do
that.
A
I
used
panels
in
Drupal
7,
instead
of
oh,
my
god
and
I,
found
that,
because
this
is
support
of
panels,
it
matched
almost
exactly
to
what
I
was
doing
before
in
terms
of
mental
model.
But
I
have
a
couple
of
sites
that
I
inherited
that
were
using
Omega
and
the
way
that
you
saw
promised
Omega
is
sort
of
like
the
inside
out
version
of
the
way
that
you
saw
some
panels,
and
so
there's
a
lot
of
power
there
in
terms
of
like
starting
with
the
region
and
then
adding
more
stuff.
A
That
way,
and
it
all
kind
of
fits
into
the
layout
and
I
think
that
we
need
to
kind
of
take
a
look
at
this
stuff.
That
is
missing
that
you
were
able
to
do.
You
know
my
get
in
particular
of
choosing
like
a
layouts
for
individual
view
modes
and
figuring
out
how
to
get
that
integrated
in
with
the
layout
system
that
we
have
in
backdrop.
I
don't
know
how
I
got
integrated
with
rules.
That
would
be
really
interesting
to
see.
A
A
Yeah
so
I
found
um
also
I
think
if
we
can
get
that
layout
builder
tool
that
we
talked
about
at
the
beginning,
that
Andy's
been
working
on
in
court
that
might
solve
some
of
those
same
problems
like
I,
just
want
to
add
another
row
or
I
just
want
to
add
another
column
to
this
region.
um
I
think
we
can
get
that
in
then
that
would
sort
of
fill
that
site
builder
instinct
of
like
I
need
to
change.
My
I
have
an
existing
that
I
just
need
to
change.
One
thing:
I
want
to
drop
it
in.
A
um
That's
something
that
you
know.
If
you
have
to
custom
cook
your
layouts,
um
you
have
to
make
that
change.
You
have
to
custom
code
that
change
in
and
that's
a
very
different
perspective
than
like
just
having
all
those
schools
in
the
user
interface,
and
one
thing
I
think
backdrop
was
really
good
at-
is
giving
people
tools
and
user
interface
and
then
getting
to
a
place
where
you
say.
Oh
sorry,
you
have
to
get
in
code,
isn't
it
doesn't
really
fit
with
the
rest
of
it?
A
E
A
In
this
place,
and
only
fonts,
you
want
in
the
row
and
I,
don't
know
with
display
suite
I,
don't
remember
it's
a
different
distinction.
I
know:
I've
had
Omega
themes,
I've
had
to
maintain
I,
don't
remember
the
differences
between
display
suite
in
panels
um
other
than
what
you
can
do
with
view
modes.
E
A
Well,
I
think
that's
kind
of
direction,
we're
going
in
anyway,
with
the
walk
um
you
know,
control
over
your
markup,
you
can
do
with
walks.
um
I
would
love
to
see
more
of
that
I.
Don't
know
how
much
of
that
needs
to
be
in
court
like
I
think
if
we
could
get
something
like
fences
module
where
it
lets,
you
control
the
markup
on
all
of
your
fields
or
if
we
could
get
something
like.
um
Even
if
we
had
a
display
suite
for
backdrop,
we
could
figure
out
how
to
get
those
line
up.
A
B
So
we're
talking
about
this
place,
we
I
use
display
Suites
a
lot
with
Drupal,
7
and
I.
Think
I'm,
just
gonna
mention
this.
It
may
or
may
not
be
obvious
to
people,
but
one
of
the
things
that
I
found
really
helpful
about
the
layouts
right
was
the
ability
to
create
blocks
field
blocks
sort
of
right
out
with
core
right,
so
I
could?
What
I
would
do
in
display?
B
Suites
right
is
create
a
layout
and
put
fields
and
different
in
different
blocks
in
the
layout
and
that's
right
there,
and
you
can
do
that
with
with
layouts
and
backdrop
core.
So
I
don't
know.
If
anybody
else
has
done
that
or
how
obvious
it
is
I,
don't
think
it
was
odd,
I'm,
partly
mentioning
it,
because
I
think
it
took
me
a
while
to
realize.
I
could
do
that.
Well,.
A
E
7
we
had
some
things
that
had
I
had
a
couple
of
content
types
had
50
fields
on
them.
That's
a
lot.
Yeah
didn't
have
a
single
column
form
and
have
to
scroll
all
the
way
down.
The
page
was
just
with
all
you
needed
to
do
is
have
little
mock's
put
this
put
this
and
then
submit
any
references
at
auto-filled.
You
know
the
scroll
down.
50
fields
is
a
lot,
so
that
was
a
real
handy
tool.
Yeah.
A
A
A
Have
an
admin
theme
where
I
took
all
of
my
taxonomy
fields
and
I
was
like
display:inline-block
and
then
background
calling
knows
it.
So
it's
a
mess
like
they're
all
together,
I
want
you
to
go
through
and
like
organize
them,
but
since
I
figured
a
to
know
what
order
they're
supposed
to
be
in
or
anything
now
it
it's
a
slight
improvement
it
doesn't.
It
doesn't
need
a
little
polish.
B
C
Know
I
didn't
I
didn't
I
have
hardly
any
content
on
this
side.
I
just
stood
it
up,
and
so
your
description
of
the
layout
builder
was
really
I,
get
it
now
and
I
I
wouldn't
know
if
I
wouldn't
have
stumbled
upon
that
so
cuz,
it's
kind
of
a
different
paradigm
than
I'm
used
to
working
with
so,
but
then
that
that
makes
a
lot
of
sense
and
I
think
that
Divi
tool
will
be
interesting
or
something
like
that
to
build
to
build
things
out
in
that
layout
builder
would
be
interesting.
So.
C
So
yeah
I
didn't
I
I,
just
I
just
tried
to
I
just
redid
the
front
page
layout
and
now
I
see
that
it's
exactly
how
you
laid
it
out,
grab
the
base
layout
and
then
this
they
start
of
each
other
and
they
they
kind
of
cascade
down.
You
get
the
first
one
and
then
you're
out
it
matches
and
then,
if
it
doesn't,
it
keeps
going
till
it
gets
to
the
base
layout
at
the
bottom.
C
A
Yeah
context
is
also
something
that
is
really
confusing
for
people
who
are
new
to
gerbil,
um
at
least
in
with
panels,
because
you
have
to
define
it,
which
is
people
are
like
I,
don't
understand
how
to
tell
it
what
context
and
you
so
backdrop
we
tried
to
make
it
automatic
like
as
much
as
we
could
look.
If
you
know
notes,
last
percent
is
in
the
system.
We
can
add
that
context
automatically
we're
hoping
that'll
help
kind
of
train
people.
A
What
context
is
so
if
you
go
to
create
a
path,
it's
something
that
back
trip
doesn't
know
about
like
something
you
can
trip.
You'll
see
it
needs
to
go.
You
know
the
%
is
in
the
second
position
and
so
I'm
going
to
tell
if
that's
a
no
paragraph
idea
whatever
it
is,
that
you're
adding
but
yeah,
it's
definitely
something
it's
a
little
bit
magical
and
adding
those
contexts
is
what
currently
makes
all
those
lots
of
here
so,
like
all
the
field
blocks
only
appear
when
you
have
a
note
that
has
fields
on
it.
A
It
is
a
context,
that's
why
you
couldn't
find
them
initially
Timmons,
because
they
don't
show
up.
If
you
don't
have
the
contacts
there,
and
so
there
is
an
issue
that
Gregory
is
working
on,
that
would
make
all
of
the
blocks
available
so
that
when
you
go
into
that
thing
and
you
search
for
it,
it
will
tell
you.
A
It's
just
not
there
until
you
get
it
and
then
you're
like
oh
it's
there
and
I
think
that
we
could
do
a
better
job
of
sort
of
guiding
people
to
I
want
to
feel
block.
How
do
I,
where
do
I
put
it?
How
do
I
get
ax
to
it
and
so
Gregory's
working
on
that
and
I
think
initially
we
didn't
have
all
of
those
things
appear
in
the
blacklist,
because
we
thought
we
would
be
trying
to
show
people
the
whole
blacklisted.
A
D
B
B
So
I'm
gonna
mention
one
last
thing,
then
about
layouts.
That
I
was
excited
about.
Was
that
I
I'm
trying
to
remember
the
exact
context?
Why
but
I
know
in
both
Drupal
7
and
Drupal
8
I've
tried
to
create
front
pages
that
are
completely
custom
right,
that
there's
nothing
on
them
and
then
put
my
own
just
drop
my
own
blocks
on
them
and
that
turned
out
to
be
way
more
difficult
than
I
thought.
It
would
be
and
a
backdrop.
That's
not
a
problem
right.
We
just
you
have
a
front
page
layout
and
you
can
take.
B
You
know
things
like
the
page
title
or
the
login
block
I
want
to
say
it
was
like.
The
login
block
was
super
hard
to
get
rid
of
on
in
Drupal.
It
was
like
built
into
the
default
template
or
something
right
with
I
mean
you
could
you
could
solve
it
with
a
custom
template,
but
you
had
to
do
:
right
and
you
don't
have
and
I
think
that
you
don't
have
to
do
that
in
backdrop.
I.
A
Don't
know
about
the
login
block
in
particular,
but
I
do
know
that
one
of
the
things
we're
trying
to
solve
is
layouts.
Was
they
just
want?
A
page
like
I
just
want
a
page
on
my
site
and
I
want
to
put
stuff
on
it
and
something
in
Drupal
forever
has
been
really
hard.
It's
like
you
can't
you
have
to
make
a
note
and
not
put
any
content
in
it
or
you
can
make
like
a
view.
It
returns
nothing.
A
You
can
make
a
panel
like
all
these
things
are
very
complicated
solutions
and
we
just
thought
it
would
be.
You
know,
that's
it.
That's
a
very
common
use
case.
Every
site
needs
home
page
right
and
in
that
home
page
I've
seen
a
whole
bunch
of
sites
have
like
a
content,
type
called
home
page
with
only
one
note
in
it
right
like
what
it's
just
the
easiest
thing
for
people
to
do,
and
we
wanted
to
make
that
easier.
So,
I'm
glad
that
you
felt
the
joy
of
being
able
to.
E
A
A
good
question:
we
are
still
trying
to
figure
out
what
backdrop
to
is
gonna
look
like
there
are
a
bunch
of
people
who
are
thinking
that
all
backdrop
to
will
do
is
remove
everything.
That's
marked
is
duplicated
and
there
won't
actually
be
any
API
changes,
but
we
do
have
a
list
of
things
that
we
want
to
do
that
require
API
changes,
so
we're
trying
to
figure
out
like.
Is
it
possible
to
do
those
things
in
a
backwards
compatible
way?
A
And
if
not,
we
will
at
some
point
have
to
have
breaking
changes
and
we'll
need
to
figure
out
what
the
thrush
look
like
like
how
we're
gonna
do
that,
but
what
we
found
it
was
in
the
first.
You
know
four
years
of
backdrops
existence
is
that
we're
able
to
do
an
awful
lot
without
breaking
it?
Yes,
just
by
adding
things
like
all
of
them
using
features.
We've
gotten
since
backdrop,
1.0
went
in
without
breaking
any
of
the
existing.
A
If
you
guys
are
at
least
unintentionally
breaking
them,
there
were
in
some
bugs
introduced
that
we
hopefully
have
fixed,
but
yeah,
and
so
I
think
you
know
just
living
in
this
world
where
we
can
add
new
API
additions.
It's
really
easy
to
say:
oh
we'll
just
add
a
new
age,
my
old
one
is
deprecated
and
then
it's
not
broken
and
then
it's
somewhat
we
can
remove
it,
and
so
it
gives
us
a
lot
more
freedom
in
terms
of
what
we
can
do
and
so
there's
also
been
talk
with
Nate
I.
A
Don't
know
how
serious
this
is.
When
is
this
crazy
idea
of
like
what,
if
we
just
dropped
the
one
from
backdraft
and
so
like
right
now
we're
on
backdrop?
12
next
backdrop
will
be
backed
up
13,
because
if
we're
never
going
to
have
a
breaking
change,
why
I
have
the
indicator
that
we're
gonna
do
that?
So
I?
Don't
think
that
the
Drupal
7
end-of-life
date
will
correlate
to
anything
in
particular,
the
backdrop
is
going
to
do.
A
I
don't
think
we
need
to
have
a
deadline,
because
we
have
much
closer
deadlines
where
we're
doing
a
bunch
of
other
stuff.
I.
Think
what
the
Drupal
7
end-of-life
jate
will
do
is
kind
of
be
like
okay.
This
is
the
point
where
all
of
the
people
who
are
under
full
7
will
have
to
make
a
decision
about
what
they're
gonna
be
doing
in
the
future
like
are
they
waiting
to
play
backdrop?
A
Are
they
throwing
out
their
website
they're,
just
gonna,
let
it
sit
and
so
between
now,
and
then
that's
our
chance
to
say
how
do
we
make
this
upgrade
path
as
easy
as
possible
like?
What
are
the
pain
points
right
now
and
upgrading
put
your
stuff
in
the
backdrop,
and
can
we
iron
that
out
so
that
when
they
have
to
try
it
it's
as
painless
as
possible,
so
that's
kind
of
our
whole
goal
right
is
to
make
it
upgrade
less
painful.
A
That's
the
you
know,
that's
where
we
started
here
and
then
maintenance
less
painful
once
you're
on
it,
so
that
I
think
it's
what
we
should
be
focusing
on,
focusing
on
to
be
known
in
end-of-life
and
I.
Don't
think
we're
in
any
hurry
to
figure
out
what
backdrop
to
needs
to
look
like
I
think
if
something
comes
along
that
we
absolutely
need
and
we
need
to
have
breaking
changes
and
we
can't
do
it
a
backwards
compatible
way.
That
would
be
a
driver
to
having
a
backdrop
to,
but
there's
so
much.
A
We
can
still
do
to
make
it
better
without
that,
but
I
think
that
we
should
just
sort
of
carry
on
in
the
way
we
have
been
in
terms
of
adding
new
features
and
making
everything
we
have
better
and
more
usable
and
more
affordable
and
see
how
much,
how
much
better
we
can
get
it
for
people
coming
from
Drupal
7,
but
yeah.
It's
a
good
question.
I
know.
Just
in
the
last
few
days,
we've
gotten
a
huge
increase
of
people
trying
back
drug
people
asking
questions
people
joining
the
forum
um
just
because
they
got
the
email.
A
There's
like
oh,
it's
coming.
I
need
to
do
something
and
I
think
that
you
know
everyone
has
had
it
in
their
back
their
minds,
their
websites
kind
of
old,
but
when
they
got
that
email,
it's
kind
of
a
motivator
for
everyone
to
start
exploring
other
options.
So
I'm
expecting
next
to
continue.
We'll
probably
have
you
know
it
continued
spike
for
a
while,
then
they'll
get
quiet
again
in
the
middle.
E
About
a
suggestion
for
the
next
one
of
these
that
we
do
to
do
one
on
14
modules,
sure
I
think
from
Drupal
I
have
played
around
a
little
bit.
I
had
one
that
loads,
but
I
think
I'm
thinking.
The
problem
is
just
not
finding
the
path
to
the
JavaScript.
That's
for
my
to
say
that's
for
another
leader,
so
otherwise.
B
Sure
I
think
that's
a
great
topic.
I
think
we
have
a
list
of
others
and
well
after
this
call
will
we'll
look
at
the
list,
but
that
seems
like
a
really
good
option:
Enterprise
we're
at
about
an
hour,
so
we
should
wrap
up
in
terms
of
future.
These
future
user
groups.
I
know
Gregory,
for
those
who
you
know,
Gregory
I
think
everybody
here
probably
does
is
in
Australia
and
it's
4
a.m.
B
there
or
well
now
it's
5:00,
but
he
has
asked
that
we
try
and
diversify
our
time
slots
so
that
he
doesn't
have
to
get
up
at
4
a.m.
so
I,
I'm
tempted
to
and
I'm
welcome
to
feedback
on
ER
after
the
call
about
I.
Don't
know
I'm
not
like
a
regular
user
group
benefits
a
lot
from
being
at
the
same
time
on
a
monthly
basis
and
I'm,
not
sure.
Given
we've
got
people
from
around
the
world
in
different
time
zones
that
you
know.
B
A
We
can
alternate
them
so
like
one
month,
it's
at
this
time
and
then
the
next
month,
it's
like
eight
hours
later
or
something
and
then
I
could
alternate
that
way.
We
might
get
like
some
people,
one
time
so
cool
in
the
next
I.
Don't
know
if
that
would
help
like
the
topic.
I
think
maybe
like
I
want
the
topic.
You
did
it.
When
I
was
asleep,
we
could
try.
It
know
what.