►
From YouTube: Backdrop Design & UX - Dec 31st 2020
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
C
Okay,
so
today
is
thursday
december
31st
woohoo.
This
is
our
weekly
design
and
oh
usability
meeting.
C
We
should
start
with
introductions.
I
am
jen
lampton,
I'm
running
from
oakland
california.
I'm
really
excited
about
all
of
the
usability
improvements.
We've
made
to
backdrop.
I
have
a
site
launching
today
and
the
people
who
are
using
it
are
really
thrilled
with
how
easy
it
is
to
use
which
is
great,
so
yeah,
I'm
interested
to
keep
moving
in
that
direction
and
see
what
needs
to
get
done
in
today's
meeting.
B
All
right,
I'm
not
muted,
I'm
luke
mccormick,
I'm
a
web
product
manager,
project
manager,
etc
in
san
ramon.
California,
and
I've
got
my
own
things
going,
but
I'm
actually
kind
of
curious
to
see
what
other
design
issues
are
are
relevant
to
the
upcoming
release
of
phil.
D
Hey
phil,
ward
out
of
wichita
kansas,
I
don't
have
anything
specific,
just
kind
of
being
a
fly
on
the
wall
and
kind
of
see.
Where
conversation
goes
tim
I
don't
think
you've
gone
yet.
A
Nope
on
the
last
one,
I'm
tim
erickson,
st
paul
tim
coming
from
deerwood
minnesota,
where
a
quick
deer
report
nothing
outside
my
window.
Right
now
sorry,
so
there
were
two
deer
about
an
hour
ago
outside
the
window
yeah
and
I
got
I'm.
A
I
have
been
sort
of
frantically
busy
with
other
work
the
last
month
or
so,
and
so
I'm
my
I'm
dabbling
in
the
issue,
queue
and
backdrop
stuff
every
day,
but
just
not
having
time
to
sink
my
teeth
in
which
is
a
good
and
a
bad
thing.
So
I'm
here
to
just
help
out
any
way.
I
can
that's
all.
C
Well,
we
have
a
handful
of
issues
on
weekly
agenda.
We
have
theme
initiative,
update
section,
I
don't
know
if
there's
anything
new
there.
One
thing
I
did
want
to
say,
I'm
very
excited
about
is
the
better
help
text
for
the
layout
path
field
as
rtbc.
So
that's
something
that
has
confused
a
lot
of
people
for
a
long
time.
So
I'm
really
excited
to
see
that
change
get
in.
C
On
the
usability
front,
I
think
it'll
be
great.
I
also
just
peaked
at
the
118
milestone,
so
our
feature
phrase
is
actually
not
tomorrow.
It's
gonna
go
until
sunday,
but
if
you
look
at
the
118
milestone,
there's
a
whole
bunch
of
user
experience
issues
in
there
that
are
currently
marked
rtbc,
which
is
great
so
things
like
tim's
issue
for
changing
the
name,
full
html
to
raw
html.
C
A
A
There's
a
couple
of
things
I
mean
that
aren't
urgent,
that
I
could
bring
up
right
that
I
think,
could
benefit
from
a
little
bit
of
quick
talk,
actually
two
of
them
that
are
related
one.
I
I
just.
I
think
it
would
be
helpful
to
clarify
this
changing
front
page
to
homepage
in
corn.
I
think
we
have
a
pr
that
wasn't.
A
It
might
have
been
even
been
rtbc,
but
then
it
some
people
raised
concerns
about
this
translation
and
then
it
got
set
back
to
needs
discussion
and
I'm
not
I'm
just
wondering
if
other
people
have
a
better
understanding
of.
If
that
was
the
intention.
So
I
don't
know
if
this
was
ever
actually
rtbc,
but
it
did
get
the
issue
kind
of
got,
there's
a
pr.
A
It
got
set
back
and
I'm
not
quite
sure
if
the
people
that
are
concerned
about
this
are
like
saying
it
shouldn't
happen,
or
they
just
wanted
to
raise
some
concerns
that
needed
to
be
addressed,
because
that's
one
that
looked
like
it
was
almost
ready
to
go
in
and
but
but
now
I
just.
I
don't
understand
where
the
issue
is
at
right
and
jen.
You
commented
on
it
because
I
asked
the
question
about.
Like
you
know,
is
this
a
have?
A
C
Layout
for
the
home
page,
there
was
a
debate
about
whether
we
should
call
this
a
home,
page
or
a
front
page,
and
it
turns
out
that
the
only
place
you
ever
refer
to
the
homepage
as
a
front
page
is
in
drupal.
And
so
we
decided
to
call
it.
The
homepage.
E
C
That
was
intuitive
to
anyone
with
a
website,
but
in
doing
so
we
introduced
an
inconsistency
where
the
new
thing
is
called
a
home
page
and
there
are
a
whole
bunch
of
places
through
the
rest
of
backdrop
where
you
refer
to
the
home
page
as
the
front
page,
and
so
this
sort
of
brought
those
two
things
in
line.
C
The
issue
with
translation
is
not
something
that's
unique
to
this
issue.
We've
been
running
into
it
ever
since
we
started
making
usability
changes
in
backdrop.
In
the
very
beginning,
we
decided
that
we
weren't
going
to
block
a
usability
improvement
because
it
required
string
translation.
So
this
is
something
that
in
drupal,
once
you
know,
drupal
7
is
released.
C
They're
not
going
to
change
any
strings
in
core
until
drupal
8
is
released
because
it
would
require
re-translating,
and
so
that
means
that
the
user
interface
can't
get
updated
very
easily,
because
there's
a
lot
of
changes
that
would
just
be
text,
changes
that
don't
get
in,
and
so
we
dropped
that
pattern
in
backdrop
and
said:
there's
an
interface
that
we
can
improve,
we're
going
to
improve
it,
even
if
we
can
only
improve
it
in
english,
and
that
does
make
it
much
harder
for
people
who
are
keeping
up
with
translations
to
keep
all
the
translations
for
the
whole
user
interface
available.
C
But
it
does
mean
that
the
interface
in
general
can
get
better
faster,
and
so
this
particular
issue
is
that
you
know
when
we
introduced
the
word
home
page.
We
didn't
break
any
existing
translations
because
we
didn't
change
any
of
the
existing
interfaces
and
now
that
we're
doing
that
it
is
going
to
be
breaking
translations.
I
don't
think
it
will
stop
the
issue
because
it
hasn't
stopped.
Translation
issues
haven't
stopped
anything
before,
but
it
is
important
to
note,
especially
for
people
who
are
using
the
interface
in
different.
C
That
when
you
go
to
the
site
settings
page,
the
section
there
that
lets
you
define
your
front
page
is
now
going
to
say
home
page
and
it
may
not
be
in
the
language
you
selected
it
for
it.
So
I
think
it
was
sort
of
an
asterisk
there
that,
like
for
those
of
us
who
are
using
translations,
this
could
be
a
problem
and
for
those
of
us
who
are
creating
translations,
we
need
to
come
back
and
translate
these
strings.
And
so
we
now
have
this
core
label
for
translation.
C
So
when
an
issue
needs
to
be
translated,
it
gets
that
label
on
it
and
that
should
make
it
so
that
people
who
are
doing
translations
can
search
for
all
the
issues
that
got
in
1.8,
find
all
the
new
translations
make
all
the
new
translations
and
then
make
another
release
or
118
of
the
translation
for
118
on
the
translation
site.
So
we
have
sort
of
a
process
for
doing
that,
although
it
is
pretty
slow.
A
Right
and
the
reason
I
brought
up
this
issue
is
because
this
was
actually
marked
rtbc
back
in
august
and
then
it
looks
like
nate
added.
The
label
needs
morphine
back
but
left
at
rtbc
back
in
september,
and
it
was
just
in
that
mode
for
a
while.
Well,
I
guess
I
guess
a
little
while
after
that,
then
peter
removed
the
rtp.
You
know
some
people
raised
so
when
nate
said
it
needs
more
discussion.
A
Some
people
raise
the
issue
about
translations
and
then
and
then
peter
removed
the
rtbc
thing,
but
I'm
just
confused
about
what
like
what
the
next
step
is
on
this
issue,
because
now
it's
like
a
bunch
of
people
are
saying
yeah,
it's
kind
of
a
problem
for
translators,
but
nobody
said
we
shouldn't
do
it.
I
don't
think.
A
Yeah
he
was
the
one
who
removed
it
and
like
or
added
it
in
august,
and
then
he
removed
it
after
nate
on
september,
in
august,
peter
added
it
and
then,
in
september
9th
the
nate
added
the
needs
more
feedback,
which
I
would
assume
that
if
you're
adding
needs
more
feedback,
you
should
remove
rtbc.
At
the
same
time
or
not,
can
you
have
an
rtbc
issue
that
needs
more
feedback.
C
Yeah
I
mean
it's,
oh
it's,
it's
definitely
like
the
code
status
is
rtbc
and
then
the
question
is
just
like:
should
we
or
not
so
I
could
see
that
being
needing
both
but
yeah.
I
think
for
for
my
preference
would
be
to
change
this
issue
back
to
rtdc
and
say
we've
discussed
it.
We've
decided
that
changing
it
to
homepage
is
an
improvement
it'll
go
in,
but
it
does
now
have
this
label
that
it
didn't
have
before
that'll
indicate
to
people
doing
translations
that
need
to
be
translated.
So
I
think
that's
I
think.
C
A
Well,
indigo
zela,
it
looks
like
actually
does
come
out
in
opposition.
She
said.
Actually
home
page
seems
worse
to
me
than
front
page,
so
there
is
at
least
one
person
that
specifically
after
nate
asked
for
feedback.
I
don't
I
don't
like
this
change,
but
then
herb
dual
pointed
out
well,
haven't
we
already
made
this
decision
to
make
this
change.
C
A
C
So
I
think
it
would
just
be.
You
know
how
how
adamantly
does
indigozola
feel
against
it?
And
people
who
agree?
Is
it
enough
to
say
we'll
change
the
homepage
layout
to
a
front
page
layout,
because
that
would
be
the
other
way
to
go
with
it.
C
All
right,
I
think
the
next
steps
will
be
to
market
rtbc
again
and
say
it
sounds
like
most
of
us
want
to
move
forward
in
the
direction
that
we
had
a
long
time
ago,
and
you
know
there's
nothing
that
says
we
can't
change
our
mind
later.
If
we
try
it
later
and
it'll
be
much
easier
to
change
all
strings
rather
than
have
like
half
one
and
half
the
other.
So.
A
B
That
gives
me
the
the
breakouts
that
can
afford
to
to
integrate
check,
something
which,
which
may
or
may
not
be
off
topic,
which
is
why
it's
a
good
time
to
go
here.
I'm
I'm
just
kind
of
curious,
and
you
know
phyllis
mentioned
things
alongside
too
about
but
kind
of
the
the
overall
issue
of
of
how
how
do
we
track
changes
from
drupal
right
like
like
it
strikes
me
that
there
are.
There
are
a
couple
of
pools
of
usability
issues
right,
but,
like
there's,
there's
the
way
the
net.
B
Does
it
there's
there's
a
way
the
drupal
community
decide
to
handle
it,
which
differs
in
some
sort
of
dramatic
ways
with
the
way
the
internet
went
and
then
there's
ours,
which
is
kind
of
like
a
amalgam
of
those
twos,
a
bunch
of
things.
You
know
most
things
really
we've
stuck
with
how
drupal
does
a
few
things
we've
kind
of
rolled
back
to
the
way
the
internet?
B
Does
it
and
I
think,
there's
some
things
where
we've
just
come
up
with
our
new
things
like
a
third
brand
new
improvement
and
all
seem,
you
know
perfectly
valid
approaches,
but
it
seems
like
it'd,
be
useful
to
have
have
that
documented
somewhere
and
it
might
be
document.
I
just
don't
know
where
it
is
so
that
that's
actually
one
of
the
questions
that
I'll
throw
out
there
is.
Is
that
documented
somewhere?
And
I
just
don't
know
where
to
look
for
it.
A
I
don't
know
my
snarky
answer
when
you
raised
this
question
was
going
to
be
gregory
is
how
we
track
these
things
right.
That
gregory
has
it
all
in
his
head,
and
he
just
tells
us
what
what
drupal's
doing,
what
we're
doing.
B
I
mean
there
there's
there's
even
like
like
another
level
tonight,
I'm
sorry
I'll
I'll,
throw
it
back
to
you
as
soon
as
I
get
this
one
last
thought
out
is
there's
more
than
one
drupal
reality
it's
great,
because
because
there
are
things
that
got
changed,
sort
of
late
in
the
day
of
drupal
7,
for
example
the
reorganization
of
the
modules
page,
where
I
definitely
liked
it
the
old
way
better.
B
I
I
don't.
I
don't,
like
you
know
the
included
modules
to
be
split
into
like
five
different
groups,
but
it's
one
of
those
things.
I
figured
that's
a
battle
for
another
day,
I'm
just
kind
of
curious
how
it
is,
but
sorry
phil.
D
I'm
getting
muted
here,
yeah
no
worries
I
was
kind
of
thinking
about
it.
Maybe
maybe
I'm
out
of
line
and
saying
this,
so
maybe
this
is
just
an
opinion
of
that
that
I
have.
I
don't
know
if
others
feel
this
way
or
not,
but
just
kind
of
think
about
it
over
the
last
few
days.
D
You
know
easier
usability,
some
better
gui
changes,
ui
changes,
ux
changes
etc,
and
it's
like
drupal
was
just
so
stuck
in
the
drupal
4
drupal
5
drupal
6
days
that
a
lot
of
this
stuff
just
never
got
addressed
and
got
fixed
moving
forward
into
newer
versions
of
drupal,
and
so
I
I
kind
of
feel
like
there's.
That's
turned
a
lot
of
people
off
who
would
like
to
use
drupal,
but
they
just
it's
like.
D
When
are
you
guys
going
to
move
forward?
You
keep
doing
things
the
old
way
the
the
web.
The
internet
has
moved
forward.
Like
you
said,
the
internet
has
created
kind
of
their
own
unofficial
standard
way
of
doing
things
and
drupal
lags
behind
that.
So
you
know
I
I.
I
would
love
to
see
backdrop
kind
of
take
the
approach
of
we're
not
going
to
follow
the
web,
we're
going
to
help
create
the
web,
and
I
think,
over
time,
as
the
user
base
grows.
D
I
think
that
that
can
be
something
that
can
happen,
but
it
frustrates
me
to
no
end
that
drupal
always
lag
behind
the
overall
web
in
the
way
things
happen,
you
know
it.
It
was
just
a
very
cautious
low
risk
approach
to
building
the
the
overall
experience
yeah.
Personally,
I
think
that's
why
a
lot
of
folks
kind
of
gravitated
toward
towards
other
platforms.
You
know
platforms
that
were
following
the
standards
and
were
using
newer,
newer
languages
newer,
just
whatever
I.
B
B
Well,
well,
it
it
has
in
my
mind.
Well,
first
of
all,
you
know
I
was
checking
to
see
if
it
wasn't
already
done-
and
I
just
didn't
know
about
it,
because
that
happens
sometimes,
but
but
but
I
I
think
I'll
I'll.
Do
the
quick
recap
for
for
jen,
as
is
I
I
was,
I
was
discussing
backwards,
ui
compatibility,
basically
where,
where
people
using
backdrop
there
there's
lots
of
there's
lots
of
the
way
backdrop
does
things
that
are
inherited
from
drupal.
B
There
are
a
certain
amount
of
things
that
were
changed
from
drupal
from
the
way
drupal
did
it
more
towards
the
way
the
internet
does
it,
which
you
know
the
current
example
of
homepage
front
page
is
example
of,
and
there
there's
some
things
that
are
they're
like
new
they're,
like
hey.
No
one's
done
this
yet,
but
this
is
better,
so
we're
going
to
do
this
way
and
and
they're
all
they're
all
valuable
and
important
things.
B
My
my
concern
is
basically
documentation
is,
is
I
would
I'd
like
to
leave
behind?
Ultimately.
B
Drupal's
decisions
on
things,
but
in
order
to
do
that
in
order
to
to
make
it
comfortable
to
get
there,
that
has
to
be
well
documented,
okay,
group
of
people,
here's
here's!
What
we've
changed!
Here's
a
list!
Here's
some
things
you
need
now
good!
You
know
people
coming
over
from
other
places,
become
a
wordpress
people
coming
over
from
you
know:
new
you're
young
first
website,
you're
building,
you
know:
here's!
B
C
As
far
as
documentation
goes,
that's
interesting,
because
our
intent
is
every
time
we
make
a
change
like
this
is
to
make
it
so
that
you
wouldn't
need
any
documentation
like
we
want
the
interface
itself
to
be
self-explanatory.
So
you
don't
have
to
google
like
what
is
the
front
page
in
order
to
figure
out
how
that
works.
But
if
you're
coming
from
drupal,
7
and
you're
like
where
do
I
set
my
front
page
you're,
going
to
look
for
the
string
front
page?
C
Because
that's
already
in
your
brain,
not
realizing
that,
like
in
backdrop,
we
call
it
a
home
page.
You
know
in
this
case
it's
not
as
important,
because
it's
on
the
same
page
in
the
same
place,
it
was
in
drupal7,
so
you'll
stumble
across
it
accidentally.
C
But
there
are
things
like
that,
where
you
know
we're
trying
to
make
it
intuitive
to
new
people,
but
it
does
break
the
knowledge
of
existing
people
and
a
couple
of
these
places
where
we've
wanted
to
make
really
big
changes
but
been
afraid
to
is
the
views,
interface
and
the
field
ui,
because
everybody
coming
from
drupal
knows
how
to
use
those
and
even
though
they
aren't
great
it's
a
lot
of
existing
knowledge
is
at
stake
there.
But
this
is
a
little
bit
smaller
or
it's
probably
not
as
important
but
yeah.
That's
interesting.
B
So
so
I
mean
I
mean
it
feels
like
there
could
be.
I
mean.
Maybe
this
is
one
of
those
like
2-0
things
right,
one
of
one
of
the
changes
where,
where
you
know
as
a
backdrop
2-0,
it
no
longer
looks
like
drupal
and,
and
you
know
to
get
there,
it
has
to
not
be
as
dependent
on
people
wanting
old
drupal
for
that,
and
but
in
any
case
it
would
we
would
there
would
need
to
be
a
path
for
that,
like
okay,
if
you're
looking
for
this
here's
where
to
find
it
yeah,
maybe
yeah.
D
The
bus
module
getting
it
out
there
in
front
of
people
on
drupal,
drupal,
7
and
trying
to
do
what
we
can
to
bring
those
users
into
backdrop,
and
then,
if
we
can
get
a
good
majority
of
those
drupal
7
users
on
backdrop,
when
2.0
comes
they're
already
familiar
with
backdrop,
and
then
we
can
start
making
changes,
big
changes
because
then
they're
already
familiar
with
how
backdrop
works
and
it's
not
as
drastic
of
change
for
these
guys,
because
they're
already
on
backdrop,
I
agree
with
you
that
if,
if
a
2.0
comes
out
and
we're
still
waiting
for
a
whole
bunch
of
drupal
7
people
to
come
over,
it's
going
to
be
like
apples
and
oranges.
D
What
is
going
on
here,
you
know
it's
like.
I
have
to
completely
relearn
all
this
stuff
and
that's
kind
of
why
I've
been
personally
pushing
pretty
heavy
for
that
that
bus
telemetry.
I
know
that
that's
part
of
outreach,
but
it
goes
into
this
discussion
that
hey.
If
we
can
get
these
people
in
get
them
under
this
umbrella,
then
we
can
start
making
these
changes.
We
don't
have
to
worry
as
much
about
the
overall
user
base,
just
completely
flipping
out
and
not
understanding
this
new
system
and
not
wanting
to
gravitate
towards
backdrop.
B
Well,
I
think
it's
important,
but
I
don't
think
you're
ever
going
to
have
to
not
worry
about
it.
Okay,
because
you're
never
going
to
be
able
to
get
like
everybody
to
switch
and
and
whoever
doesn't
switch
at
that
time
is
going
to
be
a
lot
of
people.
So
so
so
you
can't
ever
abandon
them.
There
has
to
has
to
be
a
path,
even
after
any
particular
change
to
plus.
C
D
Right,
I
think
some
of
these,
though
it's
it's
incremental
changes.
You
know
you
got
to
kind
of
take
a
look
at
the
way.
Apple
has
done
the
stuff
that
they
do
from
from
from
a
ui
standpoint,
their
interface
has
not
changed
in
like
20
years
15
20
years.
D
You
know
the
the
they
make
very
small
incremental
changes
through
each
os
update
it's
their
back
end
that
they
do
a
lot
of
major
stuff
on,
but
they
give
their
engineers
the
the
third
party
people
they
give
them
plenty
of
time
to
make
the
necessary
changes
on
the
back
end.
D
D
A
D
A
B
A
No,
but
I
I
think
what
I
think
we
started
to
do
was
just
look
at
issues.
You
know
how
to
move
some
issues
forward
and
they
weren't
necessarily
super
pressing
issues.
This
home
page
one.
There's
the
that
help
text,
one
john,
that
you
were
excited
about,
there's
another
one,
that
I've
proposed
that
I
haven't
really
gotten
any
feedback
on
pro
or
con,
although
which
is
this
one
about
it's
and
it's
related
to
this
homepage,
issue
is
phil
just
experienced
this
and
I
you
know,
has
proposed
some
bigger
solutions.
A
But
again
I'm
thinking
about
one
of
the
things
we
can
do
sometimes
and
there's
pros
and
cons
right
is
fix.
A
big
issue
you
know
is
is
when
we
run
into
a
usability
issue.
Sometimes
we
can
make
it
better
by
just
adjusting
the
help
text
right
before
we
are
able
to
actually
fix
the
ui
and
there's
always
a
risk.
When
you
do
that,
but
then
you
don't
fix
the
ui,
because
you
feel
like
you
addressed
it
with
the
with
the
help
text
feel
experienced.
A
I've
heard
it
from
one
or
two
other
users
that
they
get
very
confused
about
the
fact
that
if
you
change
that
home
page
path,
the
the
home
page
layout
no
longer
works
and
there's
to
me
that
is
a
super.
It's
like.
I
understand
that
now,
but
it's
like,
I
don't
understand
how
a
new
newcomer
suppose
is
supposed
to
understand
the
fact
that
if
you
change
the
path
for
the
home
page,
that
that
means
the
light,
the
home
page
layout
will
no
longer
work,
and
I
just
like
to
get
a
little
and
I
think
a
little.
C
A
What
I'm
saying
the
default
home
page
setting
if
somebody
changes
that
to
a
node,
so
they
they
want
node
22
to
be
their
their
homepage
phil
and
at
least
one
other
person
have
said.
They
spent
a
lot
of
time
putting
blocks
on
the
home
page
layout
that
aren't
showing
up
on
their
home
page
because
their
home
page
is
node
22,
which
is
using,
which
is
using
the
node
layout.
C
Okay.
Okay,
so
let
me
let
me
cover
this
again,
so
we
have
two
types
of
layouts:
we
have
a
layout
that
wraps
existing
content
and
we
have
a
layout.
That
is
a
standalone
page,
and
I
think
what
you're
getting
at
here
is
people
think
that
the
homepage
layout
will
wrap
whatever
they
put
on
their
homepage,
but
in
reality
I
think
so
long.
A
I
think
so
and
to
me
that
makes
sense
like
if
again
I
totally,
I
wouldn't
have
this
problem
anymore,
because
I
know
how
things
work.
But
if
you
go
to
the
layout
page
and
you
see
there's
a
layout
for
the
home
page,
you
expect
that
to
work
on
the
home
page,
regardless
of
what
it
is,
which
is
not
how
it
is
designed
to
work
at
all-
and
I
experienced
that
recently
and.
C
A
And
my
health
tech
suggestion
has
kind
of
gone
ignored,
while
people
try
to
address
the
big
some
other
issues
like
the
default,
like
is
the
default
node
or
user,
and.
D
I
think
if
we
just
add
some
little
text
there
that
says
you
know
something
like
if,
if,
if
you
plan
on
changing
this
for
something
other
than
home,
why
don't
you
check
out
the
home
layout
first
and
then
have
a
link
to
that
home
layout?
So
that
way
people
know
oh
well.
This
home
path
is
going
to
this
layout.
What
layout?
What
are
they
talking
about
and
then
that'll
kind
of
direct
them
there?
D
Now,
from
the
standpoint
of
what
I
did
in
my
situation,
I
created
a
node
and
I
set
the
path
of
that
node
to
home,
so
that
content
that
node
now
overrode
the
layout
path
of
home
and
so
that
content
type
or
that
that
that
node
was
actually
using.
I
think
it
was
the
default,
the
the
overall
layout,
if
I
remember
right
it
basically
overrode
the
home
layout
path,.
D
Well,
I
I
think,
as
opposed
to
an
error,
I
think
maybe
just
kind
of
a
help,
warning
that
if
you
set
home
in
a
content
path-
and
there
is
a
layout
path
with
the
exact
same
path,
just
a
little
warning
that
says-
hey,
you
know,
there's
a
layout
with
this.
That's
already
using
this
path.
Are
you
sure
that
you
want
this?
This
path.
C
On
this
shouldn't,
let
you
do
that
because
you're,
it's
you're
actually
breaking
the
system
like
you're,
creating
two
menu
entries
where
you
should
only
be
one
that
shouldn't
be
allowed
and
the
fact
that
we
don't
check
that.
I
think,
is
a
problem
like
we
check
when
you
try
and
save
a
node
with
the
same
node
as
another
node
like
we.
Don't
let
you
overwrite
it.
So
I
don't
think
there's
any
reason.
It
should
be
different.
That
sounds
like
a
bug.
E
C
Them
is
this
like
two
kinds
of
layouts
thing:
one
of
them
is
the
user
interface
for
setting
the
home
page,
not
telling
you
what
you're
linking
it
to,
and
now
we
have
another
one
of
the
path
not
telling
you
when
you
set
the
path
that
there's
a
problem.
So
there's
like
three
problems:
we've
got
going
on
here
right.
D
D
The
way
I
look
at
it,
you
know,
you've
got
you've,
got
people
like
sheldon,
cooper
and
big
bang
theory
that
create
the
stuff
and
they
make
it
for
other
people
like
sheldon
cooper,
and
it's
like
you
got
to
look
at
it
from
an
engineering
standpoint
go.
How
can
I
make
this
so
penny
could
use
it,
and
so
sometimes
I
think
that
that's
what
gets
a
little
bit
lost
in
some
of
these
things
is
you
know
you
get
get
an
engineer
that
writes
things
so
that
other
engineers
can
understand
it.
D
C
I
think
better
help
text
on
the
homepage,
setting
that
explains
what
it
is.
So
people
don't
think
it's
setting
a
pat,
it's
like
pointing
to
something
that's
existing,
I
think,
would
be
clear
and
then
fixing
a
bug
that
prevents
you
from
overriding
one
thing
with
another
thing.
I
wonder
if
you
did
it
the
other
way
around.
If
you
created
node
first,
then
you
create
a
layout.
If
the
layout
would
win.
C
Yeah
and
then
yeah
a
longer
term
trying
to
figure
out
how
to
either
clarify
two
different
types
of
layouts
or
let
people
choose
like.
Maybe
they
want
like
giving
them
a
user
interface.
That's
like
wrap
my
node
x
with
this
layout,
like
if
you've
already
spent
time
working
on
the
layout.
That
might
be
a
good
option
too.
C
B
So
so
we
really
need
to
explain
the
out
of
it.
We
need
we
need
to
have
like
so
like
if
you
come
from
anywhere
else.
You
haven't
seen
this
go
ahead
and
try
to
figure
it
out.
That's
cool.
We
try
to
make
it
intuitive,
but
if
not
here's
the
doc.
Here's
like
the
three-page
thing
that
explains
it
in
detail,
so
that
could
otherwise.
You
know.
E
Yes
and
nice
to
meet
you
and
happy
new
year,
and
I
want
to
say
about
page
layout:
it's
neat
to
it's
very
complicated
in
drupal,
so
it's
need
to
figure
out
and
how
it's
possible
to
easy
to
weigh,
understand
and
need
a
proper
documents
and
drupal
has
a
limited
document.
Still
I
think-
and
even
backgroup
has
a
limited
documents
about
that.
So
I
need
we
need
to
proper
documents,
everything
so
user
can
understand
or
developer
can
understand
and
how
to
use
it.
D
One
more
quick
thought
on
that:
the
the
the
groups,
the
layout
groups,
what
are
the
thoughts
on
adding
a
forward
slash
to
the
beginning
of
the
path?
D
I
think
that
was
a
big
disconnect
for
me.
I
completely
overlooked
the
path
was
the
header
of
the
group,
because
when
I
saw
home
it's
just
like,
oh
that's,
the
header
for
home,
sure
yeah,
it's
home,
it
says
default
home
right
here
or
whatever
I
didn't
even
realize
until
tim
and
I
started
talking,
oh
no,
that
that's
the
path
that
that
layout
is
handling,
and
so
I
think,
having
a
forward
slash
in
front
will
be
a
better
indicator
that
no,
this
is
a
path.
This
is
not
a
header.
D
A
D
It
would
create
even
more
distinction
between
you
know,
your
your
about
page,
your
home
page,
your
contact
page
versus
hey.
This
is
a
services
layout
that
is
going
to
handle
the
manipulation
or
the
output
of
multiple
servers
pages.
I
I
just
coming
in
kind
of
looking
at
it.
I
feel,
like
everything
is
jumbled
together,
I
don't
know
what
I'm
looking
at.
Nothing
is
organized
and
that
was
kind
of
my
big
beef
with
it.
So.
A
C
A
C
A
C
A
So
I,
in
response
to
phil's
concern,
I
created
a
a
specific,
no
a
node,
slash
three
layout
and
that
is
listed
after
the
node,
slash
percentage
layouts,
but
it
takes
precedence
over
them
and
that
surprised
me.
I
thought
that
if
it
was
if
it
took
precedence
over
the
main
node
layout,
it
would
appear
before
them
in
the
list,
and
I
don't
know
if
that's
a
bug
or
if
that.
C
A
C
And
if
you
have
two
things
that
can
be
ordered,
a
button
shows
up
that
says
reorder,
but
if
you
don't
ever
have
them,
you
would
never
know
that
you
know
if
you
never.
If
you
never
create
anything
that
needs
an
order.
You'll
never
even
know
that
there
are
things
that
can
have
an
order.
So
it's
one
of
those
chicken
and
egg
things
where
you're
like
I
wish
there,
but
it's
there.
You
just
can't
see
it.
Yeah,
there's
a
lot
of
like
hidden,
hidden
gems,
like
that
that
right.
B
I
I
actually
want
to
throw
in
into
this
because
this
actually
feeds
into
a
problem
we've
inherited
with
from
drupal
and
that
we
can't
solve
until
we
like,
I
think,
address
the
bigger
ui
issues.
I
was
talking
about
about
changes
from
drupal,
because
I
think
one
of
the
one
of
the
things
that
the
problems
that
drupal
had
that
we
inherited
is
the
interface
out
of
the
box.
The
day
one
you
turn
it
on
is
pretty
complicated,
there's
like
a
million
different
things
and
that's
confusing
on
day
one.
B
A
B
E
D
C
B
C
E
A
C
Yeah,
although
it's
a
multi-page
layout,
can
affect
one
page
right,
you
can
have
a
node
template
for
node
three,
so
I
don't
think
that's
the
right
terminology,
but
yeah.
I
don't.
I
don't
think
I'm
using
the
right
terminology.
A
So
phil
raised
the
issue
and
I
just
opened
a
ticket
to
talk
about
that.
I
it
wasn't.
E
C
C
The
layout
list
is
a
little
easier
to
tell,
because
I
don't
know
I
mean
you'd
have
to
know
what
you're
looking
at.
I
suppose,
but
the
the
single
pages
have
a
link
to
the
page
right
and
the
things
that
are
wrappers
have
a
pattern
that
they
apply
to
that
can't
link.
So
it's
just
the
heck,
that's
link
or
not
link.
C
D
So
you
bring
up
kind
of
a
interesting
question
for
me:
are
you
saying
that
a
wild
card
template
or
I'm
sorry,
a
wild
card
layout,
is
going
to
take
precedence
over
a
single
page
layout
or
is
it
the
other
way
around.
C
I
don't
know
I
have
never
tried
to
target
the
same
page
in
two
different
ways
for
me.
If
I
want
a
standalone
page,
I
make
a
standalone
page,
and
if
I
want
a
node
to
have
a
template,
then
I
use
a
node
template,
but
I've
never
tried
that
thing.
That
tim
said
where
he
tried
to
overwrite
node
three
with
a
standalone
page
by
putting
in
that
path,
and
I
think
that
might
also
be
another
bug
just
like
you're
allowed
to
accidentally
overwrite
the
homepage
with
a
node.
C
I
don't
think
you
should
be
allowed
to
accidentally
overwrite
a
notable
layout
just
because
it's
going
to
create
a
bunch
of
confusion
for
people.
If
you're,
you
know,
node
three
disappears.
Now
you
have
something
else
there.
In
the
same
way,
your
home
page
might
disappear.
D
It
might
be
worth
kind
of
looking
at
that
from
the
standpoint
of
ordering
and
set
it
up
to
where
the
default
layout.
That's
that's
your
base.
That's
at
the
very
bottom
of
the
list.
The
next
one
up
would
be
your
wild
card,
layouts
those
take
precedence
and
then,
if
you
want
to
override
an
individual
page
that
takes
precedence
so
basically
a
hierarchy
to
where
the
base
layout
or
the
default
takes
care
of
everything.
C
But
I
think
it's
supposed
to
do
what
you're
asking
for
already
but
tim
found
this
loophole
where
he
was
able
to
overwrite
node
three
with
a
standalone
layout
and
it
showed
up
below
the
node
percent
section.
And
I
think
that's
something
that
we
didn't
ever
envision
happening
when
this
was
designed.
C
And
so
it's
probably
something
that's
allowed.
That
isn't
intended
to
be
allowed,
but
works.
But,
like
we
didn't
know
if
it
would
work
because
nobody's
ever
tested
it.
So
I
think
we
just
need
a
little
more
examination
into
that
and
the
thought
process
that
people
have
to
make
them
create
that
and
maybe
when
they
try
that
we
create
the
thing
they're
supposed
to
create
instead
through
the
same
ui
so
like.
C
E
Okay,
my
question:
please:
what's
the
problem
with
drupal
7
solution,
because
it's
node
or
font
is
okay
now,
but
why
need
to
go
with
slash
home
or
like
that?
Yeah.
C
C
So
if
you
don't
want
to
use
a
standalone
layout
for
homepage,
you
don't
have
to
it's
just
the
most
common
use
case
for
a
panel
in
drupal
7
is
the
home
page,
and
so
because
backdrop
is
using
panels,
it
made
sense
to
do
the
standalone
most
common
use
case,
for
that
layout
was
the
home
page,
but
it
doesn't
there's
nothing
wrong
with
doing
a
drupal
7
way.
If
you
liked
that
you
can,
you
can
do
that.
In
backdrop
too,.
D
I
think
most
people
they're
going
to
replace
that
block
anyway,
so
that
they
can
put
in
a
content
type
or
a
block
to
add
content,
and-
and
it
could
be
that
this
is
something
that,
if
we
move
forward
on
some
profiles
that
are
more
out
of
the
box
experience
profiles
that
you
know
we
can
handle
this
within
the
profile.
D
C
Means
you
can
remove
the
block
and
you
can
put
whatever
you
want
in
there,
so
that
was,
I
think,
you
know
one
of
the
main
reasons
to
use
a
layout,
but
also
it
gives
you
the
ability
to
customize
like
what
you
want
in
that
river.
So,
like
I
agree,
the
old
blog
style
homepage
isn't
great,
but
it
all
those
posts
are
promoted.
And
so,
if
you
wanted
to
just
show
like
latest
news
on.
C
Could
do
that
by
like
only
promoting
news
items,
you
might
also
just
make
a
different
view,
but
it
sort
of
gives
you
the
flexibility
to
figure
out
how
you
want
to
solve
that.
If
you
don't
want
to
touch
the
layout,
you
can
do
it
in
other
ways
by
curating
your
content
into
the
you
know
the
that
is
only
the
content,
that's
promoted.
So
if
you
don't
ever
promote
any
content,
there
won't
be
anything
there,
but
yeah
flexibility.
E
Yes,
I'm
trying
to
say,
because
drupal
everything
is
known
and
it's
possible
to
change
like
create
a
homepage
with
without
page
layout,
to
create
a
another
page
type
like
here
is
article
basic
package
or
news,
so
we
can
do
that
through
through
our
content
on
node
base.
So
why
need
to
make
a
panel?
I
cannot
understand
that,
because
here
is
already
a
solution.
D
A
C
A
Yeah
to
me,
one
of
the
big
advantages
of
the
things
I
got
excited
about
layouts
right
away,
was
that
I
didn't
have
to
like.
I
was
always
jumping
through
hoops
to
customize
the
front
page
in
drupal
and,
in
backdrop
like,
I
was
excited
about
the
fact
that
we
had
this
home
page
layout.
It's
like
I
can
do
anything
I
want
with
my
home
page.
I
don't
need
to
default
to
something
else.
D
Yeah
something
else
that
I
think
would
be
a
huge
benefit
to
the
the
user
experience
on
this
is
to
go
ahead
and
have
we.
We
have
the
view
and
the
edit
tab
also
add
a
layout
tab
and
at
first
I
thought
it
was
a
great
idea
and
then
I
realized
that
you
can
override
the
same
path
with
two
different
layouts
that
creates
problems.
D
D
Well
now
I
have
to
figure
out
that
I
have
to
go
to
the
layout
page,
the
layout
list
page
and
then
edit,
the
layout
for
that
home
layout
group,
in
order
to
do
what
I
want
to
do,
if
we
had
the
layout
tab
up
there
at
the
top
on
every
page,
and
it
takes
you
to
the
layout
list,
the
exact
group
that
you
need
to
manipulate
for
that
pass
then
obviously
for
some
wild
cards,
I
mean
yeah
now
even
on
wild
cards.
D
It
would
work
out
too,
because
you
know,
if
you're
on
a
services
page
and
that's
a
wild
card
for
services
for
that
content
type.
Well,
it.
C
Would
take
that
group
in
a
way?
That's
invisible
if
you
click
the
contextual
link
on
any
block
on
any
page,
it
will
take
you
to
that
layout.
That's
being
used
to
render
that
page.
But
again,
this
is
another
thing
that
if
you
know
it's
there,
you
use
it
all
the
time,
because
it's
really
helpful
and
if
you
don't
know
it's
there,
you'll
never
discover
it
because
it's
invisible
but
yeah,
and
that
issue
you
mentioned
about
having
one
page
that
can
be
managed
by
two
layouts
is
not
supposed
to
be
possible.
D
A
C
But
that's
still
two
distinct
layouts.
It's
never
going
to
be
one
layout
governing
two
paths.
It's
just
not.
It
doesn't
work
that
way
and
the
fact
that
there
are
a
couple
of
interfaces
that
allow
you
to
set
that
up
is
a
bug.
So
there
are
lots
of
different
ways.
You
can
set
up
the
scenario
describing,
but
none
of
them
would
have
one
url
that
two
layouts
can
affect.
C
The
layout
manager
will
only
ever
select
one
and
render
it
through
one
there's
just
some
tricks
there
as
to
how
it
chooses
that
one
that
maybe
aren't
working
as
expected.
C
I
do
think
that
this
layout
ui,
though,
needs
more
discussion,
so
maybe
I
mean
I
don't.
I
don't
know
if
we
have
a
meta
for
it
already,
but
it
might
be
the
kind
of
thing
where
we
take
the
discussion
online
and
brainstorm
ideas
like
phil.
If
you
could
write
down
your
ideas
about
cards
for
that
layout
or
how
you
think
that
organizing
that
layout
list
might
be
better,
I
think
that
would
be
really
useful.
D
C
C
I'm
gonna
go
ahead
and
stop
the
recording.
Does
anyone
have
anything
they
want
to
add
before
I
do.