►
From YouTube: 2022/01/13 - Design/UX Meeting
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
All
right
today
is
thursday
january
13th,
and
this
is
our
design
meeting.
This
is
our
last
design
meeting
before
the
release
of
backdrop
121.0,
which
will
come
out
in
two
days
on
the
15th
which
we're
very
excited
about.
So
if
you
have
any
design
or
user
experience
focused
issues
that
you
want
to
get
in
now
is
the
time
there's
a
whole
bunch
of
activity
in
the
core
queue
which
is
really
exciting.
A
whole
bunch
of
issues
that
have
been
around
for
a
long
time
are
getting
reviewed
and
merged,
which
is
super
exciting.
A
There's
nothing!
Well,
let's,
let's
go
go
through
some
introductions.
First
and
we'll
get
back
to
the
agenda
later
so
I'll
go
ahead
and
go
first,
I'm
jen
lampton,
I'm
joining
from
oakland.
A
I'm
working
on
a
ton
of
backdrop,
projects
right
now
and
I'm
really
excited
because
I
find
an
issue
and
then
I
go
to
report
something
on
it
and
someone
else
is
already
working
on
it,
which
is
fantastic.
So
I
love
seeing
all
the
activity
that's
happening
right
now.
Let's
see,
I
think
I
don't
have
anything
else
exciting
to
share.
So
let's
turn
it
over.
B
Yeah,
I'm
not
sorry,
my
sound
was
cutting
out,
so
I
I
didn't
hear
so.
I'm
robert
lang
but
folder
on
the
internet,
coming
you
from
aladina
california
and
I'm
pretty
excited
about
seeing
all
the
stuff.
That's
gonna
come
out
in
1.21
and
I've
been
working
on
rules
and
uber
cart
to
help
get
new
versions
of
those
out
at
about
the
same
time.
C
Jim
hi,
I'm
kim
erickson,
I
think,
welcome
on
the
internet
and
I
am
in
deerwood
minnesota
and
gosh.
I've
been
well
a
little
bit
recovering
from
a
flurry
of
backdrop
core
issues
stuff
about
a
week
ago,
so
I
haven't
had
too
much
time
this
week
doing
a
lot
of
client
work
though,
but
yeah.
So
it's
good.
Let's
move
on
to
joseph.
E
I
am
martin
from
the
uk
yorkshire
putting
on
the
internet,
I'm
just
generally
interested,
I'm
not
particularly
working
on
anything
ux
at
the
moment.
F
Justin,
I'm
justin,
I'm
in
denver,
colorado
and
just
help
out
with
infrastructure.
Usually
I
thought
I'd
look
in
this
meeting
today.
D
B
In
to
lurk
in
anticipation
of
the
next
meeting.
A
A
Okay,
so
I'm
gonna
pull
a
few.
The
1
20.4
milestone
that
haven't
seen
any
activity
recently,
but
that
I
would
really
like
to
see
get
in.
A
A
It
was
set
that
way
even
12
years
ago,
as
a
potential
mitigation
against
the
security
issue
that
turned
out
to
never
have
actually
been
used,
and
so
drupal
by
default
has
a
bunch
of
forms
that
are
massive
backup
has
in
the
same
form,
so
things
like
the
user
permissions
matrix
has
can
have
hundreds
of
checks
on
it.
Things
like
the
menu
system,
where
you
reorder
your
menus.
A
If
you
have
a
lot
of
items
in
your
menu
that
one
gets
out
of
hand
same
with
taxonomy
term
listings,
and
if
you
want
to
submit
that
form
and
there's
too
many
elements
in
the
form
the
post
variable
that
goes
into
php
will
exceed
that
limit.
And
what
happens
when
that
limit
is
exceeded?
Is
the
post
variable
is
just
truncated.
So,
like
the
bottom,
half
of
your
form,
submission
just
goes
away
and
your
site
doesn't
throw
any
kind
of
error.
It
just
doesn't
work
right,
like
sometimes
half
your
menu
items
won't
be
saved.
A
Sometimes
all
of
them
will
be
put
into
the
wrong
order,
because
the
way
the
menu
order
reordering
works,
if
your
form
had
different
behaviors
based
on
which
button
you
push
like
whether
it
was
the
save
button
or
the
delete
button
and
you've
removed
that
button
from
the
amount
of
data
that's
getting
submitted
to
your
server.
It
can
do
very
strange
things,
and
so
this
is
a
super
dangerous
problem,
potentially
causing
data
loss,
sometimes
causing
data
corruption
and
really
hard
to
diagnose,
because
there's
no
kind
of
error
handling
or
anything
on
the
server.
A
That
indicates
that
there
was
an
issue,
and
so
after
this
got
me
for
like
the
third
time
I
I
went
into
both
drupal
and
backdrop,
and
I
wrote
a
patch
that
adds
some
special
handling
that
can
check
your
maximum
number
of
variables
that
are
allowed
and
then
notifies
you
if
that's
potentially
an
issue.
It'll
put
a
log
in
the
database
log
and
it'll
print.
A
An
error
on
the
screen,
if
that
form
you're
about
to
submit,
is
likely
to
cause
problems
and
request
could
use
good
review
because
in
order
to
get
that
messaging
on
the
screen-
and
you
know
only
once
rather
than
multiple
times
when
you
submit
a
form,
there's
some
custom
handling
in
there
that
like
checks,
the
messages
that
are
going
to
the
screen
and
sees
it
as
duplicate
text
and
only
prints
it.
If
it.
A
Than
most
pull
requests,
I'd
love
to
get
some
eyes
on
that,
and
I
want
to
how
to
adjust
their
maximum
of
input
variables.
A
If
someone
could
reduce
that
down
to
you
know
a
couple
hundred
or
something
in
order
to
generate
those
errors
and
make
sure
they're
appearing
where
they're
supposed
to
that
could
use
some
additional
testing
too,
so
that
variable
is
set
in
php
ini,
which
can,
depending
on
your
development
environment
like
we
aren't
going
to
be
able
to
test
that
in
a
sandbox,
for
example,
you'd
have
to
do
that
in
place
where
you
can
control
that
yourself,
so
that
needs
a
little
review.
So
that's
one.
A
And
I
can
drop
there's
a
link
in
the
agenda.
I
think-
and
I
can
drop
one
into
zulip
if
that's
valuable.
C
G
A
B
All
right,
I
know
that
one
place
to
test
this
is
on
the
modules:
sorry
user
permissions
page
yeah,
which
turns
into
a
massive
form,
that's
usually
where
it
gets
triggered.
C
A
Yeah,
I
think
so
I
mean
it's:
it's
been
in
sort
of
a
ready
state
for
a
while
I'm
running
it
in
many
production
sites
in
both
drupal
and
backdrop,
and
it
hasn't
caused
any
issues.
So
I'd
love
to
see
it
get
in.
I
think
the
issue
is
that
it
needs
it
needs
like
a
sort
of
a
thorough
code
review
on
it
and
then
it's
hard
to
test.
A
You
can't
just
go
into
like
one
of
the
pull
requests,
inboxes
and
test
it,
so
it
needs
local
testing,
which
is
also
sort
of
hard
for
people
in
backdrop
to
do
because
just
pulling
down
the
branch
is
complicated,
so
yeah
it
just
needs.
What's
it.
A
A
All
right
so
there's
another
one
here.
This
is
a
follow-up
from
something
that
went
into
backdrop
115,
which
is
where
we
added
more
options
for
how
to
control
our
responsive,
drop-down
menus.
If
you
want
them
to
open
on
hover
or
on
click,
and
we
had
some
trouble
with
the
language
for
the
checkbox
there
and
spent
a
bunch
of
time
working
on
improving
the
checkbox
text
and
we've
gone
back
and
forth.
I
don't
know
a
ton
of
times
so
we'll
be
good
to
get
some
more
eyes
on
this
issue.
A
It's
number
4253
current
status
is,
it
looks
like
we
have
a
radio
instead
of
a
check
box
where
it
describes
the
two
behaviors,
the
first
one
is
open
menu
with
touch
or
hover,
and
the
second
menu
is
open
menu
with
touch
or
click,
and
we
want
to
make
sure
that
those
descriptive
options
make
sense
to
people.
We
also
changed
the
label
on
that
form
element.
It
used
to
be
drop
down.
Behavior
it
looks
like
some
people
are
looking
leaning
towards
drop
down
opening
behavior
other
people
are
leaning
towards
drop
down
menu
trigger.
A
So
just
what
do
you
call
this
thing?
Naming
things
is
hard,
so
the
more
good
ideas
we
have
in
how
to
do
that.
C
I
have
one
I
can
mention
too
great.
You
wanna
do
yours
next
sure
3339.
It
show
a
message
when
viewing
hidden
page
list,
no
content,
so
we
had
a
pr
that
was
rtbc.
What
this
does
is,
but
it's
not
anymore.
What
this
issue
does
is
just
if
you
have
permission
to
view
pageless
notes
or
hidden
nodes.
It
puts
a
message
on
them,
reminding
you
that
these
pages
are
not
visible
and
it
seems
like
a
really
useful
thing
and
it
seemed
pretty
simple.
C
I
took
over
a
stalled
pr
that
was
mostly
just
text
and
herb
duo
found
some
problems
with
it.
Apparently
we
need
to
add
some
permissions
checks
and
there's
no
way.
I
I
it
sounds
to
me
like
what
needs
to
happen
is
pretty
simple,
but
I'm
not,
I
don't
think,
there's
any
way.
I
can
do
it
the
next
few
days,
so
I
just
want
to
mention.
If
anybody
wants
to
and
is
able
to
help
with
that
one,
it
would
be
great
okay
if.
C
Instructions
of
what
I
needed
to
do,
I
might
be
able
to
try
and
fix
the
pr,
but
I
right
now,
I
I
don't
even
know
where
to
start,
even
though
it's
fairly
simple.
A
I
think
I
can
probably
give
you
some
pointers
on
that.
I
can
add
a
comment
on
the
full
request
and
you
can
probably
take
it
from
there.
Okay,.
A
D
A
C
If
anybody
is
well,
most
of
us
are
all
pretty
experienced
at
this,
but
a
good
thing
to
do
is
to
look
for
is
to
go
through
the
the
bug,
fixed
milestone
and
look
for
issues
that
need
testing
or
or
code
reviews.
If
you're
able
to
do
code
reviews,
I
usually
stick
to
the
testing,
but
that's
a
really
helpful
thing.
I
think
to
do
at
this
stage
a
couple
days
before.
A
A
Oh,
should
we
ask
about
this?
Oh
last
week
we
were
talking
about
the
help
text
for
the
home
page
field
tim.
You
thought
you're
like
I'll,
just
throw
in
this
quick
text
change
and
then
the
incomplete
issue
got
derailed
and
we
managed
to
get
the
we're
like
remove
the
text,
we're
just
going
to
get
the
issue
done
and
then
we
had
to
follow
up
on
the
text.
Do
you
want
to
talk
about
the
follow-up
issue.
C
C
But
the
issue
was
the
sure
we
could
talk
about
that
briefly,
because
potentially
we
could
make
that
better
before
we
could
still
get
an
additional
change
in,
although
there
is
no
pr
yet
this
is
the
home
page.
C
Oh,
I
don't
know
it's
the
on
the
in
the
system
settings
page
right.
It
asks
for
the
path
to
the
home
page
and
there
has
been
a
lot
of
confusion
around
that
and
it
does
some
weird
things.
C
If
you
don't
understand
it,
if
you
understand
it,
it's
pretty
straightforward
and
to
solve
some
of
the
major
problems
we
just
made
that
field
required,
because
in
the
past
we
had
a
situation
where
it
said
like
leave
it
blank
for
x
to
happen,
but
then
x
wasn't
happening,
and
so
we
started
out
trying
to
fix
it.
So
that
x
would
happen,
and
then
we
decided,
you
know
what
there's
just
no
reason
for
anyone
to
leave
this
plane.
C
Let's
just
make
it
required
and
then
that
really
solved
the
problem,
but
we
need
some
help
decks
there
and
I
I
don't
know
what
we're
to
say
without
having
like
it
in
front
of
me
other
than
well.
C
One
of
the
problems
well,
the
the
text
that
I
had
suggested
that
sort
of
started
to
derail.
It
was
something
to
the
effect
that
whatever
you
set,
that
home
that
the
home
page
is
gonna
use,
whatever
layout
is
assigned
to
the
path
that
you
assign
there
and
jen
pointed
out
that
this
is
confusing,
because
in
theory
the
setting
doesn't
have
anything
to
do
with
the
layouts,
and
my
rebuttal
was
but
most
of
the
time
when
you
change
it,
it
does
affect
layouts.
C
A
Sorry,
I'm
looking
for
the
issue.
I
think
the
main
issue
went
into
one.
A
A
If
it's
anything
else,
we
don't
know
whether
changing
that
path
would
change
the
layout
or
not
like
they
could
be
using
in
a
default
layout
on
every
page
on
the
site
they
could
be
using
a
special
layout
for
nodes.
There
could
be
any
number
of
visibility
conditions
on
those
layouts
that
might
make
them
activate
or
not
activate
so
because
that
is
the
most
common
use
case.
For
you
know,
all
fresh
installs
will
start
that
way.
A
A
For
people
who
are
already
confused
about
layouts,
but
there
are
other
use
cases
we
might
also
want
to
test,
for
that
would
get
special
descriptive
text
in
there.
But
I
think
that,
for
starters,
what
we
might
want
to
do
is
add
some
generic
text
that
will
work
for
all
scenarios
and
then
add
that
specific
use
case
where
we
know
it's
home
and
we
know
you're
going
to
be
breaking
the
homepage
layout.
If
you
change
it.
D
A
Then
leave
it
at
that
for
the
first
commit
and
as
we
come
across
other
scenarios
in
the
future,
where
we
think
we
might
have
more
help
text,
we
want
to
offer
people.
We
can
add
additional
checks
for
those
additional
scenarios
and
add
the
descriptive
text
sort
of
in
a
case
case
sensitive
way
where
we
can
check
for
how
your
site's
configured
and
add
that
text.
A
So
yeah.
C
I'm
just
gonna
mention
this
because
other
people
but
sort
of
my
frustration
with
with
this
was
that,
like
I
can
write
a
pr
that
just
adds
some
help
text
that
may
not
be
great,
but
it
it
helps
in
a
serious
situation
and
these
conditional
things
is
harder
for
me
to
do
yeah.
So
when
it,
you
know
it's
it's
frustrating.
But
but
I
understand
why
and
I'm
not
saying
I'm
right,
but
it's
frustrating
when
I've
got
like
something
that
I
feel
like
is
an
improvement.
That's
a
simple
text
and
then
somebody
comes
up
with
well.
C
We
should
do
something
much
better
and
I
can't
do
that
and
then
I
feel
bad,
because
because
I
can't
do
the
thing
that
should
be
done-
and
I
just
want
to
make
it
better
so,
but
I
think
you're
right
that
the
better
solution
is
better
go.
A
Ahead,
I
think,
there's
probably
also
a
better
solution
that
it
doesn't.
It
isn't
dynamic,
but
it
would
need
to
be
really
carefully
worded
to
indicate
that,
like
this
might
be
the
case,
it
might
not-
and
I
think
that
is
also
hard
to
do
so
yeah.
I
feel
like
it's
definitely
much
easier
to
do
nothing
than
to
do
like
incremental
changes,
which
is
why
we
just
sort
of
went
that
way
for
the
initial
pull
request
just
to
get
it
in,
but
I
agree.
D
A
C
C
One
of
the
problems
is
people
are
coming
from
drupal
and
they
think
they
need
to
change
that
setting
and
they
don't
really
need
to
so
bw
panda
at
some
point,
suggested
kind
of
hyping
that
and
putting
it
into
an
advanced
tab,
and
that
would
take
care
of
a
lot
of
the
problem.
If
we
just
made
it
less
obvious
to
people
that
you
know
that
setting
because
really
got
anybody
who
doesn't
understand
what
that
setting
does
probably
is
misusing
it.
C
A
Yeah
yeah,
I
totally
agree-
and
I
did
I
didn't
think
about
hiding
it
until
peter
mentioned
that,
but
I
think
it's
a
great
solution.
I
have
personal
objections
to
using
the
word
advanced
to
hide
things.
D
A
Is
not
over
here
yeah,
okay,.
A
Has
feelings
on
what
that
language
should
be?
I
think
there's
still
time
to
get
that
improvement
into
120,
also
121
1.21.0.
D
E
I've
I've
just
I
don't
know
whether
it's
specifically
ux,
I
kind
of
thought
of
it
as
a
bit
of
a
ux
issue,
even
though
it's
not
labeled
as
such,
but
the
the
comments
and
being
able
to
disable
the
comments.
I
don't
there's
been
quite
a
bit
discussion.
I
think
there's
some
pull
requests
on
it,
but
I
don't
know
if
anything
needs
doing
or
if
there's
decisions
that
need
to
be
taken
on
on
that
before
it
can
go
forward.
H
A
Problem
on
monday-
and
I
saw
it
come
up
today
and
I'm
like
oh-
I
didn't
know
there
was
this
core
issue
or
I
might
have
worked
on
the
core
pull
request.
So
thank
you
for
drawing
my
attention
to
that
martin,
but
the
problem
is
that
we
don't
have
a
content
type
wide
setting
for
enabling
or
disabling
comments.
So
for
my
use
case,
this
is
a
session
event
website
and
people
wanted
to
add
comments
on
sessions,
but
only
for
a
period
of
time,
and
then
they
get
turned.
They
get
turned.
A
Off
and
in
order
to
do
that
for
your
site,
you
have
to
go
through
and
edit
every
single
session
and
be
like
sessions.
Comments
off
comments
off
comments
off
comments.
Often
it's
a
big
pain
in
the
butt,
whereas
if
we
had
a
setting
on
the
content
type
form,
it
would
be
like
enable
comments
now
and
then
all
of
the
comments
for
that
content
type
got
turned
on.
You
could
do
it
all
at
once
same
thing
for
turning
them
off,
and
then
we
were
also
going
to
add
an
option.
A
So
if
you
didn't
want
to
modify
existing
content,
you
only
wanted
to
change
the
behavior
for
all
new
content.
You
could
have
that
option
too,
so
my
use
case
would
be
turning
them
all
on
or
all
off
all
at
once,
but
there
were
other
people
that
had
other
use
cases
in
there
where
they
just
wanted
to
change
the
setting
for
new
posts
versus
current
posts
differently.
C
So,
martin,
just
a
suggestion
when
you
come
on
an
issue
like
this-
that's
been
kind
of
sitting
there
for
two
years.
Sometimes,
what's
really
helpful,
is
to
write
a
summary,
although
it
looks
like
actually
clonos
might
have
done
that
right
before
you,
so
maybe
it
wasn't
necessary
here
yeah
and
this
one
isn't
that
long.
So
it's
not
that
hard
to
go
back
on,
but.
C
It
certainly
seems,
like
a
sense
of
I
think,
I've
been
in
this
situation
before
too,
and
it
seems
like
a
sensible
idea.
C
B
Or
I
think,
there's
still
one
mis
fibo
507,
I
think,
is
still
in
it's
not
merged.
Yet
that
was
there
was
a.
B
Yeah
507,
which
was
it,
needs
both
code
review
and
testing,
and
that
was-
and
it's
got
two
competing
ers.
I
guess
we
needed
to
get
enough
consensus
as
to
which
approach
one
approach
was
to
keep
the
same
label
the
same
order,
one
list
of
layouts.
So
this
is
the
layout
configuration
the
layout
listing
page.
B
One
pr
was
keep
the
same
listing
of
layouts,
but
denote
each
one
individually,
whether
it
was
an
override
or
a
layout
created
page
and
the
second
pr
was
to
segregate
into
two
lists,
one
of
layout
pages
and
the
other
layout
override
pages,
and
we
have,
I
guess,
received
a
diversity
of
feedback
on
those
on
some
people.
Saying.
Oh,
I,
like
the
extra
organization
of
having
two
lists,
and
others
saying
well
that
just
creates
more
structure
that
I
need
to
wade
through.
I
think
there
are
visual
examples
of
both.
B
B
So
I
guess
on
this
one
we
just
need
to
somehow
drive
to
enough
of
a
consensus,
or
else
I
guess
emc
can
say
one
so.
C
That's
but
that's
pretty
much.
The
the
blocker
on
this
is
that
we
just
haven't
kind
of
come
to
a
consensus
on
which
direction
to
go
right.
Yeah.
I
think
we
have
workable
pr's
for
both
well
john,
and
I
both
have
recently
offered
opinions.
Maybe
if
some
more
people
jumped
in
there
and
just
put
a
look
at
those
two
options.
H
A
H
C
I'm
gonna
go
ahead
and
share
my
screen,
quick
if
it's
okay-
and
these
are
the
two
right
yeah.
So
this
is
robert
describe
what
this,
what
is
happening
in
this.
B
Image:
okay,
so
in
this
one
everything
is
in
one
list
and
we're
adding
the
information
next
to
the
path
about.
If
there's
no
information,
it
is
layout
provided
page
like
admin,
dashboard
or
home,
and
if
it
is
an
override,
it's
overriding,
a
page
provided
by
a
module.
Then
we
add
the
parenthetical
module
provided
like
node
slash
percent
and
if
and
if
there
is
no
callback
which
is
possible
to
get
find
yourself,
then
it's
it's
listed
in
red
as
you
see
for
the
admin
structure
contact.
B
So
that's!
That's
the
single
list
version
now,
if
you
scroll
down
a
little
bit,
we'll
see
the
the
double
list
version
which
has
two
categories
of
layout
pages,
which
are
the
ones
that
are
provided
by
the
layout
module
and
then
layout
overrides,
which
are
ones
where
the
page
is
provided
by
some
other
module
and
then
the
but
the,
but
the
layout
will
apply
to
that
or
wrap
the
content
of
that
page.
B
So
it's
possible
to
have
a
path
that
that
the
the
backdrop
I'm
that
you
can
create
you
can
end
up
with
a
layout
that
has
a
path,
but
there's
nothing
in
the
system
that
provides
the
content
at
that
path.
B
B
Ideally,
you
shouldn't
be
able
to
create
a
layout
that
has
no
callback,
but
in
practice
you
can
and
probably
the
easiest
way
to
do,
that
is
to
enable
a
module
that
provides
that
path
create
a
layout
that
overrides
that
path,
then
disable
the
module
and
so
that
so
that
the
con,
the
content
callback
goes
away.
But
the
layout
is
still
sitting
there
with
that
path.
So
it
will
continue
to
show
up
in
the
layout
pages
and
it
can
be
very
confusing.
B
Then,
if
you-
because
if
you
don't
somehow
highlight
that
because
you
think
you
know
I'm
I'm
gonna
fill
put
a
bunch
of
blocks
in
my
layout
and
then
you
try
to
go
to
that
path.
And
you
don't
see
anything.
A
E
A
A
It
is
I
like
this
solution
and
another
thing
too,
to
address
your
question
of
missing
callback.
I
think
that's
something
that
a
lot
of
people
are
gonna,
wonder
about
like
what
does
that
mean?
I
think
the
fact
that
it's
red
is
enough
indication
to
tell
you
that
something's
wrong
callback
is
the
name
for
developers
like
a
menu.
Callback
is
what
happens
when
you
have
a
menu
item
and
then
a
function
is
called
in
order
to
generate
the
content
of
that
page.
A
So
that's
like
if
you're
a
developer
and
used
to
working
with
the
code,
you
might
know
what
that
is.
If
you're,
just
someone
who's
using
backdrop,
you
might
not,
but
this
is
a
like
a
true
statement
of
what's
wrong.
We
can
fix
it
later
in
terms
of
adding
more
description
text,
for
you
know
trying
to
help
people
understand
what
it
means.
A
We
could
also
try
and
fix
it
in
this
pull
request
if
you
felt
strongly
that
we
needed
more
description
there,
but
this
is
sort
of
our
first
attempt
at
being
like
oh
there's
something
wrong
here.
Let's
indicate
that
differently.
So
that's
the
you
know
first
most
obvious
language
to
use
in
that
scenario,
but
it
I
understand
it
is
so
confusing.
C
That's
that
useful
to
me
today,
because
I'm
still
a
little
bit
confused
on
everything.
But
when
I
look
at
this
first
version,
it
really
doesn't
help
me
at
all
other
than
the
red.
I
see
red
and
I
know
something's
wrong,
so
that
is
definitely
helpful
in
either
one
the
fact
that
the
second
one
sort
of
breaks
them
in
these
two
groups
again,
I'm
still
not
quite
sure
how
I'm
going
to
use
that
information,
but
it
at
least
helps
me
think
about.
C
B
I
I
think
this,
the
one
that's
on
the
screen
now
was
my
first
attempt,
and
it
was
just.
I
wanted
to
provide
more
information
to
build
the
mental
model
of
layouts,
because
layouts
right
are
a
very
confusing
thing
coming
from
drupal
and
they
were
very
confusing
to
me
when
it
came
from
drupal
and
because
having
dividing
things
up
into
categories
is
is,
is
a
really
solid
way
of
building
metal
models.
B
I
like
the
second
one
better,
because
even
at
the
cost
of
having
more
structure
on
the
page,
because
it
makes
it
clear,
there's
two
different
types
of
things
going
on
and
and
if
you
don't
understand
those
two
different
things,
it
can
be
really
confusing
as
to
like.
Why
don't
I
have
a
main
content
block
on
the
layout
that
I
just
created,
but
the
one
I
created
10
minutes
ago
had
one-
and
you
know-
and
this
sort
of
division
helps
john
yeah.
A
And
I
think
we
can
definitely
improve
that
like
in
the
help
text
too
in
the
future
tim.
I
think
right.
You
know
this
isn't
supposed
to
be
a
finished
right
project,
but
I
think
this
this
this
idea
came
from
an
earlier
issue
that
phil
raised
where
he
was
also
really
confused
about
layouts.
We
were
trying
to
figure
out
how
to
separate
them,
and
I
think
at
the
time
we
talked
about
like
different
tabs
or
like
there's
a
whole
bunch
of
different
options
for
how
to
separate
different
types
of
things.
A
But
this
was
what
came
in
my
mind
at
that
time
and
I
think
I
accurately
described
it
and
I
don't
think
any
pull
requests
were
written.
So
when
I
saw
robert
approaching
the
same
problem,
I
was
like
wait.
I
had
an
idea
about
this.
What
was
it
and
so
then,
when
I
went
to
write
this
pull
request,
it
was
really
like
I
just
want
to
have
you
know.
A
Was
a
better
a
better
organization
of
the
way
things
work
than
what
we
have
currently,
especially
on
existing
sites
that
get
a
lot
of
layouts.
I
find
it
really
valuable
to
have
those
like
dedicated
landing
page
standalone
layouts
at
the
top,
because
those
are
usually
the
ones
I'm
after
and
then
the
ones
that
are
overrides
for
node
types
and
stuff
get.
I
don't.
D
C
Okay,
just
say
for
those
who
haven't
been
watching
closely,
there's
been
a
number
of
pr's
in
the
last
recently
that
have
that
robert
has
been
behind
a
bunch
of
them
to
help
make
marginal
improvements
that,
hopefully
collectively,
will
add
up
to
big
improvements
in
making
layouts
more
understandable,
just
adding
help
text
in
different
places
and
things
like
that,
any
even
the
one
that
the
one
we
were
just
talking
about,
requiring
the
that
the
home
page
be
set,
I
think,
is
going
to
help
people
understand,
layouts
or
or
at
least
avoid
pitfalls.
C
So
so
this
is
just
one
of
several
prs
and-
and
I
don't
know
if
any
one
of
them
by
themselves
would
make
a
major
impact,
but
together
I'm
hoping
they
will,
that
they'll
make
the
layouts
more
understanding.
C
If
anyone
has
time
go,
look
at
this
issue
and
see
if
you
have
some
thoughts
on
it,
because
I
think
that's
the
only
thing
blocking
this
right
now
is
a
little
bit
more
consensus.
It
doesn't
sound.
Some
people
have
had
a
strong
opinion
towards
the
first
one
properties
towards
that,
and
that's
why
we
haven't
been
able
to
pick.
B
I
could
just
weigh
in
and
say
that
I
like
the
layout
separated
between
the
layouts
and
the
overrides.
It
seems
even
if
that
page
gets
even
if
you
have
10
or
20
layouts.
It's
not
that
much
more
and
it
does
provide
a
pretty
good
visual
indicator
of
what
you're
looking
at
at
a
glance
rather
than
the
first
one.
There's
a
lot
of
information
there.
But
you
can't
pick
it
out
easily.
E
B
E
I
think
the
second
one's,
probably
better,
especially
the
fact
at
first
I
was
like
what's
layout
pages
and
layout
overrides
gonna
mean,
but
you
look
at
the
description
underneath
and
that
makes
that
makes
complete
sense
and
brings
it.
So
I
I
think,
there's
enough
there
that
it
that
it's
clear
and
it
yeah
the
two
are
very,
very
distinct
so
and
I
think,
having
the
the
fact
that
you've
got
the
path
on
on
the
second
one
and.
B
D
B
That
second
layout,
it
still
respects
the
art,
the
hierarchical
override
of
the
layouts.
F
C
A
All
right
we
are
coming
up
on
the
end
of
the
hour.
No
one
has
anything
else
urgent
to
talk
about.
I
don't
recommend
we'll
wrap
this
meeting
and
get
ready
for
the
next
one.
C
Let
me
make
a
follow-up
comment
which
isn't
an
issue
but
robert,
so
robert
and
I
had
a
little
bit
of
offline
chat
about
layout
and
stuff
a
while
back
and
decided
you
wrote
a
blog
post,
didn't
you
yeah
what
I
sent
it
to
you
right
and
I
think
we
kind
of
wasn't
it
sort
of
on
hold
because
of
all
of
this
stuff
that
was
in
flux
or
not.
Is
that
ready
to
go?
Oh.
C
Just
waiting
for
me
to
give
you
feedback
yeah,
yeah,
okay!
Well,
maybe
we
so
we
don't
have
a
draft
on
backdrop.org.
Yet
do
we?
No?
No!
You
just
gave
me
some
text,
so
why
don't
I
get
it
up
on
backdrop.org
or
one
of
us
so
that
other
people
can
look
at
it
as
well
and
maybe
provide
some
feedback?
Maybe
it
would
be
great
to
release
that
right
after
the
release
when
some
of
these
help
text
changes
go
in
not
that
it
needs
to
it's
only
a
few
days
away.
C
Okay,
so
robert
has
a
great
long.
Well,
I
don't
know
if
it's
long,
he
has
a
detailed
blog
post,
that's
sort
of
meant
to
help
people
a
beginner
understand
some
of
these
issues.
C
Okay,
let's
sign
off,
I'm
gonna
hit
the
end
button.
Bye,
everybody
see
some
of
you
in
five
or
ten
minutes.