►
From YouTube: Backdrop Design/UX - 2021/09/09
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).
B
A
All
right
we
are
live
today
is
september,
9th
2020..
This
is
our
weekly
or
fortnightly
design
and
usability
focused
meeting
before
we
get
into
issues
for
this
week.
Let's
go
around
and
do
some
quick
introductions,
but
everyone
can
share
what
their
name
is
where
they're
from
from
and
something
fun.
If
you
want
that,
other
people
might
want
to
know
about
I'll
start.
I'm
jen
lambton,
I'm
fighting
from
oakland
california,
and
I
have
so
much
backdrop
work
to
do
right
now.
A
C
I
am
greg,
I'm
joining
from
greece.
I
have
so
much
work
during
that.
My
like
my
normal
work,
and
I
also
have
so
many
things
that
I
need
to
review
and
work
on,
but
I
tried
to
sort
of
like
filter
the
milestone
with
the
label.
That's
for
features
that
can
only
get
in
120
just
in
an
effort
to
sort
of
like
keep
myself
focused,
but
yeah
super
excited
about
the
upcoming
release
and
I'll
pass
it
on
to
robert.
D
I'm
robert
lang,
a
bug
folder
on
the
internet,
coming
to
you
from
altadena,
california
and
I've
been
doing
other
things
for
a
couple
weeks,
just
got
back
to
backdroppy
stuff
and
then
wrapping
up
getting
layout,
wildcard
module
ready
for
release
along
with
1.20..
D
E
Now
I'm
unmuted,
I'm
luke
mccormick,
I'm
in
san
ramon,
california,
where
currently
it
seems
like
it's
less
than
100
degrees,
which
has
been
recently
I'm
coding
these
days,
so
go
figure
and
maybe
I'll
do
a
little
coding
at
some
point.
I'm
interested
in
actually
trying
to
kind
of
tie
together
marketing
for
the
upcoming
release.
So
so
I'm
looking
for
for
the
list
of
of
milestones
and
issues,
and
things
like
that
which
I'm
sure
will
come
at
my
eye
on
that
and
have
we
done
tim
yet
nope.
B
Oh,
I
can
go
and
look
you
were
hard
to
hear
at
the
beginning
and
then
you
got
louder
at
the
end.
Just
so
you
know
I'm
tim
erickson,
I'm
st
paul
tim,
I'm
in
deer
with
minnesota
and
yeah.
I've
been
a
week
ago,
was
really
focused
on
the
the
release,
but
in
the
last
week
of
got
back
into
client
work,
so
I've
been
really
busy
but
have.
B
Of
things
I
still
want
to
talk
about
and
some
things
we
can
still
get
into
the
next
release.
So
that
is,
is
that
all
of
us
we
got
you
robert
yeah.
We
just
got
you.
Okay,
we're
good.
A
All
right
so
tim,
I
saw
your
tweet
earlier
about
recipes.
Do
you
want
to
jump
right
into
that
off
the
bat
or
sure
you're,
muted,.
B
Yeah,
I
got
some
noise
in
the
background.
It
shouldn't
be
done,
but
I'll
go
ahead
and
talk
the
question
I
wanted
so
really
quickly.
We
got
this
bug
fix
the
background
into
the
next
release
of
drupal,
which
makes
it
possible
to
enable
a
config
only
module,
which
is
in
a
sense
could
be
used
in
a
sense
as
a
recipe.
Although
there
was
still
some
limitations,
I
think
it's
as
we've
discussed
it's
a
little
too
premature
to
like
have
a
big
announcement
that
we
have
necessarily
that
we
have
recipes.
B
We
still
need
to
think
a
little,
and
there
is
some
discussion
about
whether
or
not
modules
is
the
best
way
to
do.
Recipes
is
working
on
or
has
another
proposal
out
there
that
I
think
we
should
at
least
look
at,
but
in
the
meantime
I
have
a
couple
of
config
recipes
that
work
on
my
own
github
repo
and
I'm
just
wondering
if
it
makes
sense
to
get
them.
B
I
mean
it
would
be
possible
for
people
to
test
them
out
like
through
the
back
the
sandbox
sites
on
backdrop.org
if
they
were
projects
on
backdrop.org
right,
if,
if
I
release
them
as
modules,
but
I'm
still
not
quite
sure,
if
we're
to
the
stage
where
we
want
config,
only
recipes
listed
as
modules
and
backdrop.org,
and
if
I
did
do
that
like
should
I
title
them
in
a
certain
way,
or
you
know
I
don't
know
so
we
could
just
kick
this
cam
down
the
road,
but
I'm
wondering
what
people
I'm
just
looking
for
feedback.
A
I
have
an
idea,
so
I
saw
this
and
I
got
all
excited
about
more
things
than
I
wanted
to
do.
A
They
don't
have
time
to
do
so,
thanks
tim,
but
one
thing
that
I
thought
is:
if
we
start
off
by
creating
them
as
modules,
we
could
add
a
new
line
into
the
info
file,
something
that
like
could
be
changed
at
a
later
point
in
time,
and
then
we
could
write
a
contrib
module
that
could
provide
a
user
interface
that
would
just
list
all
the
items
that
happen
to
have
that
line
in
info
file.
A
So
it
wouldn't
be
something
that
would
be
actively
supported
by
core
yet
which
would
give
us
time
to
change
that
if
we
didn't
like
it,
but
it
would
also
give
us
a
way
that
we
could
manage
the
recipes
in
a
different
place
than
modules.
A
Obviously,
for
now
we
know
it'll
work
if
you
turn
them
on
like
a
module.
Just
like
a
feature,
if
you
turn
on
a
feature
from
the
modules
page,
it'll
turn
on
and
it'll
work
that
does
buy
us
some
time
to
figure
out
what
we
want
that
other
listing
page
to
do.
But
I
thought
what
could
be
a
good
first
step
was
just
have
a
page
that
lists
them
without
anything
else,
and
just
that
way
you
would
know
if
you
go
to
that
list.
You're
like
okay.
A
A
You
can-
and
you
know
you
can
put
in
the
description
or
whatever
that
it's
a
recipe,
but
if
people
download
and
use
it
as
a
regular
module
by
itself,
no
problem
it'll
still
work,
but
it
also
gives
us
opportunities
to
choose
in
the
future
if
we
want
to
have
more
functionality,
specifically
around
recipes.
C
I
also
have
some
thoughts,
I'm
not
sure,
like
I
haven't,
put
every
thought
together
or
thought
everything
through,
but
I
was
going
through
all
their
comments
because
I
was
on
a
long
vacation,
so
I'm
catching
up
with
zulip.
There
were
discussions
about
resurfacing
the
minimal
installation
profile
on
the
sats,
and
then
we
have
some
long-standing
issues
where
we
sort
of
like
want
to
make
it
so
that
profiles,
installation
profiles
can
run
post
installation
and
I
think
that
recipes
might
be
a
way
to
sort
of
like
achieve
that
or
some
of
that.
C
But,
as
I
said,
I
haven't
attempted
to
do
it.
So
I
don't
know
if
there's
any
blockers
with
regards
to
that.
So
I'm
I'm
really
excited
that.
We
are
slowly
solving
all
the
problems
around
those
recipes
because
it
opens
up
pathways
to
be
doing
such
things.
There's
there's
an
issue
that
says
we
should
be
adding
recipes
like
you
know,
forums
and
things
like
that
things
that
can
be.
C
I
don't
know
automatic
combination
of
it
could
be
themes,
layouts
modules
and
configuration
that
can
be
automatically
sort
of
like
put
together
and
present
or
or
sort
of
like
implement
in
a
quick
way
in
a
quick
or
automated
way,
things
that
now
people
have
to
either.
You
know,
follow
manually
and
do
one
task
at
a
time
but
but
yeah
I
sort
of
like
in
my
head.
I
think
that
it
opens
the
pathway
to
to
you
know
a
lot
of
possibilities.
B
Yes,
there's
a
lot
of
opportunities
there.
I
think
jen,
what
you
the
most
important
thing
you
just
or
that
you're
addressing
it's
like.
I
think
my
biggest
concern
about
just
releasing
these
as
a
module
is,
you
know
like
what
am
I
doing
that
might
not
be
easily
reversed
if
we
make
that
change
in
policy-
and
you
know
anything
from
like
naming
them
should.
B
I
include
the
word
recipe
and
the
name-
and
you
know
if
I
do
it's
not
gonna
and
we
end
up,
you
know
creating
a
different
project
type
and
then
we
don't
really
need
it
in
the
name.
Is
that
a
problem?
Should
I
worry
about
that
right
now,
or
is
that
fixable
later
and
the
other
thing
is
like
yeah?
Is
there
something
in
the
dot
info
file
that
I
can
put
there?
That
would
be
helpful,
but
not
irreversible.
B
E
B
I
have
drums
or
something
I
have
two
simple
working
recipes.
I
posted
their
links
in
a
few
places,
including
in
the
forum,
if
you
go
to
the
forum
agenda
item
for
today
or
the
the
we're
creating
a
post
every
week
for
topics
for
the
agenda-
and
I
put
some
details
in
there
so
but
they're
both
very
simple
in
the
other
case
yep
well
one
more
question,
because
maybe
you
can
answer
that
which
is
the
the
other
thing
would
be.
B
I
could
envision
a
recipe
pack
module,
that's
just
one
module
that
has
like
eight
or
ten
sub
modules,
each
of
which
is
a
recipe
they're
pretty
small
and
simple,
and
I
just
want
to
get
feedback
if
that
would
be
a
better
module
or
if
we
should
have
an
faq,
which
is
really
like
three
or
four
config
files.
You
know
in
a
module
all
by
itself,
go
ahead.
C
So
I'm
not
I'm
not
sure
about
the
second
question,
but
for
the
first
question
we
recently
allowed
what
was
the
name
of
the
issue
exactly?
I
think
it
was
allow
for
support
more
things
in
dot
info
files,
so
we
could
add
a
line
that
says
recipe
equals
true
for
now
and
then
later
on.
Maybe
the
project
browser
can
prepend
a
stuff,
have
a
prefix
in
modules
that
are
recipes
which
says
recipe
called
the
name
of
the
thing.
So
that's
that's
one
idea,
but
yeah
jen
has
raised
her
hand,
go
got
him.
A
So
many
buttons
to
push
okay,
so
tim.
To
answer
your
question,
I
don't
think
it's
bad
to
put
the
word
recipe
into
the
name
of
the
project,
but
I
would
not
put
it
into
the
machine
name
or
like
the
directory
name
and
that
way
it'll
give
us
the
ability
to
change
that
later
freely
if
you
want
to,
but
we
won't
have
to
worry
about
like
changing
the
github
repositories
or
messing
with
people's
ability
to
update.
A
I
think
that
I,
like
gregory
the
idea
of
adding
something
into
the
info
file,
whether
it's
supported
or
not.
We
can
decide
that
later.
At
any
point,
change
our
mind.
One
thing
I
think
we
should
do
is
for
the
package
grouping
because
that
is
currently
supported
by
core.
We
should
maybe
standardize
on
that,
so
the
package
is
always
recipes
and
then
that
way,
we'll
already
have
it
grouped
on
the
modules
page
and
that'll,
make
things
a
little
bit
easier.
But
beyond
that,
I
don't
know
that
anything
else
is
required.
A
I
think
if
you
come
up
with
a
suite
of
six
recipes,
that
you
end
up
putting
on
all
of
your
sites-
and
you
want
to
group
them
together
in
one
module-
that's
totally
fine.
I
also
think
people
will
probably
want
to
pick
and
choose
which
recipes
they
put
on
their
own
site
and
so
having
them
individually
is
also
fine.
F
C
Too
one
of
the
things
one
of
the
things
that
we're
suggested
for
additional
things
in
dot
info
file
is
we
already
have
dependencies,
but
there
was
another
thing
that,
if
I'm
not
mistaken,
I
think
that
drupal
core,
like
supports
that
is
supplements
or
suggests.
C
So
basically,
you
have
modules
that
depend
on
other
ones
that
cannot
be
installed
unless
those
dependencies
are
met,
but
there's
there's
modules
that
base
the
basically
say
this
module
works
well
with
that
module,
but
it's
not
required.
So
I'm
not
sure
if
it's
implemented
in
triple
core,
but
it
was
one
of
the
things
that
we
wanted
to
support
through
that
issue
that
we
solved
the
the
support
more
things
in
dot
info
files.
So
that's
another
idea
of
how
you
could
handle
it.
C
B
Okay,
anna,
so
just
one
more
question
and
that's
tangential,
I
guess
is
so
the
the
my
basic
recipes
were
just
config
files
right
and
then
I
so
I
did
decide
to
experiment
a
bit
with
a
css,
adding
some
custom
css
and
the
basic
config
recipes
right.
Now
you
enable
them
they
enable
a
bunch
of
config.
There
is
no
disable
uninstall
possibility
right
and
you,
if
you
did
disable
them,
it's
just
not
going
to
matter.
Nothing's
gonna
happen,
at
least
I'm
pretty
sure.
B
But
if
I
I
realized,
I
right
I
could
add
some
css
to
the
to
the
recipe.
But
if
I
do
that,
the
traditional
module
way
that
would
require
that
you
keep
the
module,
enabled
right
if
I
disable
the
module
now,
of
course
the
css
will
no
longer
get
loaded.
B
C
B
Yeah,
but
that
that
won't
work
yet
joseph.
What
so,
the
the
I
think,
one
of
the
next
steps
in
getting
that
kind
of
thing
working
in
recipe.
My
understanding
is
the
problem
right
now
is
that,
if
I
add
a
dependency
to
the
module
before
to
the
to
the
recipe
for
a
module,
the
module
installs
first
creates
a
config
file
and
then,
when
the
module
uploads
its
own
config
files,
it
does
not
overwrite
the
existing
one.
I
believe
that's
what
happens
okay,
so
we
can't
so
we
can't
just
create
a
dependency.
B
What
we
could
do
is
instruct
the
user
to
turn
on
the
dependence,
the
the
the
the
css
injector
module
first
includes
the
the
the
the
config
and
then
it
would
if
the
module's
already
in
no,
but
that
won't
work
either.
B
C
One
thing
that
I
can
I
thought
of
other
use
cases
with
that
would
would
be
useful.
So
maybe,
if
you
can
file
a
an
issue
in
the
queue
team
where
we
we
make
sure
that
the
order
of
thing
is
when
a
when
a
recipe
module
is
enabled,
we
make
sure
that
the
dependencies
are
enabled
first
and
then
config
importing
happens
last
after
all,
dependencies
have
been
enabled,
which
means
that
basically,
we
inject
configuration
into
existing
modules
or
required
modules.
Maybe
maybe
that
would
be
a
solution
but
yeah.
B
B
One
of
the
reasons
I
was
eager
to
do
this
quickly
is
because
I
think
people
will
test
it
if,
if
somebody
can
go
to
the
sandbox
site
and
download
a
recipe
and
test
it
they're
much
more
likely
to
sort
of
get
a
sense
of
like
oh,
this
is
how
recipes
work.
This
is
what
I'd
like
and
start
talking
about
them,
rather
than
if
they
have
to
you,
know,
set
up
their
own
sandbox
site
and
and
download
it
from
my
repo
and
whatever
so.
C
Unless
anyone
else
wants
to
bring
up
any
other
topic,
I
noticed
that
andy
is,
I'm
not
sure
if
he's
watching
now
the
us
streaming
but
he's
active
in
the
zulu
q
chat,
I
mean
there's
a
a
mention
about
drupal,
so
so
andy
had
an
idea
of
whether
it
would
be
useful
to
generate
stub
whatever
what
he
calls
stub
projects
or
sub
projects,
and
this
ties
to
the
long-standing
issue
of
how
we
implement
css
changes
on
core
themes
without
breaking
backwards
compatibility.
C
So
I'm
glad
that
he
brought
it
up
now
recently.
Prior
to
this
meeting,
because
you
know,
drupal
brethren
are
actually
they've
added
in
drupal
9.
I
think
maybe
it's
a
drupal
8
as
well
through
the
ui
and
I
think,
through
through
via
the
command
line,
but
also
via
the
ui.
C
C
C
B
What's
next,
should
we
should
we
focus
on
you
design,
ux
issues
that
we
can
still
get
in?
Well
definition,
all
of
them
can
still
get
in.
So
again.
We
I
think
we
were
saying
this
before
the
meeting
started.
While
future
freeze
has
happened
and
we
can't
get
any
new
features
into
1.20,
we
can
still
get
ux
improvements
and
tasks
and
bug
fixes.
A
A
Backdrop
issues
hue
in
the
top
there's
a
bunch
of
buttons.
One
of
them
says
milestone
bones
and
if
you
click
on
milestones,
it'll
show
you
a
bunch
of
stuff.
In
there
the
120
milestone
should
include
only
new
features.
So
if
you
look
at
119.4
that
will
include
other
stuff
that
can
get
in
between
now
and
then
so
you
can
look
at
the
120
features.
Those
probably
need
to
clean
up
on
in
various
ways,
but
most
of
them
have
follow-up
issues
that
you'll
find
in
119
or
1
21.
E
C
Yeah,
you
can,
you
can
filter
for
things
that
have
already
been
decided.
Yes,
you
do
what
just
then
just
described
so
we
have
a
process
where,
if
someone
thinks
that
a
feature
is
worthy
for
the
next
release,
they
add
a
label
which
says
milestone
candidate
minor,
so
you
can
filter
by
that
label
as
well,
but
it
will
get
you
things
that
will
they're
potentially
for
the
next
minor
release.
If
you're
looking
for
120,
then
you
should
do
what
jen
just
described
to
get
a
list.
C
So
when
I'm
filtering
by
milestones
by
the
120
milestone,
I
see
eight
closed
issues
and
five
open
currently
of
those
five
issues.
Two
are
feature
requests
and
in
theory
they
wouldn't
be
able
to
get
in
because
we're
past
feature
freeze.
But
these
are
merely
open
because
we
have
follow-up
subtasks
there
there
they
actually
have
the
status
fixed
label,
so
the
main
pull
requests.
The
main
code
change
has
already
been
merged.
It's
in
120.
The
reason
why
they're
open
is
because
they
need
a
change
record,
there's
more
tasks
to
be
done
or
yeah
subtest.
C
As
I
said,
the
other
two
that
are
slated
for
120,
the
other
three
two
of
them
are
tasks.
One
of
them
can
be
excluded
because
it's
basically
the
preview
release
checklist
and
the
other
one
is
a
bug
fix
now.
Bug
fixes
normally
get
into
minor
releases.
The
reason
why
that's
in
120
is
because
it
it
it
fixes
something
that
was
added
added
only
in
the
120
brands.
If
that
makes
sense,
so
it
doesn't
apply
to
the
previous
119
brands.
C
For
the
purposes
of
this
meeting,
because
we
discuss
design
and
ux
issues,
what
you
can
do
is
you
can
filter
all
issues
by
the
label
design.
So
we
can
discuss
things
that
could
get.
There
could
be
tasks
and
they
could
get
in
before
this
release,
or
we
can
generally
discuss
like
for
the
future,
but
still
keep
for
design
related
tasks.
E
So
I'm
looking
for
the
one
I
made
did
is
that
somewhere
in
the
in
the
flow
of
things.
C
A
C
So
so
the
point
look
is
that,
even
even
if
120
was
not
upcoming,
your
fix
got
in
the
bug
fix
really.
So
even
if
119.4
was
coming
out
now,
it
would
be
included
in
that
as
well.
C
C
Its
birthday
will
be
because
I
guess
we're
planning
to
release
one,
if
not
nothing,
critical
comes
out
like
a
security
release.
Before
that
we're
planning
to
release,
I
guess
119
for
at
the
same
time
or
the
same
day
with
120.
So
the
way
things
are
going.
So
it's
going
to
be
the
same
as
like
september
15th.
I
guess
you
can
mark
that
day.
G
B
Well,
I
mean
I,
I
don't
want
to
hug
the
show,
but
if
another
issue
I'll
mention
is
that
the
dashboard
or
the
the
breadcrumbs
one,
because
I
know
you
commented
on
that
greg
this
week.
If
we
wanted
to
talk
about
that,
that
could
still
get
in.
I
think
so.
There's
interest
in
it,
but
I'm
just
not
sure
if
there's
interest
in
it.
B
C
Yeah
yeah,
so
so
I
had
a
look
as
I
said,
and
I
think
this
there
might
be
another
issue
filed
by
me,
some
place
where
I
didn't
find
the
the
the
order
that
these
things
were
being
rendered.
I
didn't
find
it
reasonable,
but
then
jen
has
provided
some
screenshots
in
that
issue
where
the
like
the
design
just
makes
sense
or
it
works.
I
won't
say
it
makes
sense,
but
it
just
works.
C
C
So,
instead
of
trying
to
force
a
thing
because
your
change
basically
was
changing
the
hard-coded
thing
into
something
that
can
be
more
easily
out
of
the
box
sort
of
like
changed
to
fit
one's
needs,
I
thought
that
maybe
that
would
be
a
compromise,
but
then
I
noticed
that
in
one
of
the
previous
messages
by
jen
she
was
opposed
to
changing
the
the
hardcore
title
to
the
multiple
sort
of
like
blocks
thing.
So
maybe
it's
a
good
idea
to
discuss
that
so
jen.
A
Yeah,
so
I
I'm
not
sure
my
voice
is
the
best
one
to
listen
to
here,
because
I
build
most
of
my
backdrop
sites.
The
way
factor
was
intended
to
be
built
before
we
added
all
these
nice
features
into
it.
So
things
like
the
flexible,
layouts
and
placing
blocks
all
over
the
place.
A
I
don't
do
so
for
me,
I'm
like
wow,
I
don't
know
we
should
be
placing
blocks
everywhere,
because
that
just
makes
a
mess
of
your
user
interface,
whereas
I
feel
like
there's
a
lot
of
good
features
provided
by
these
tools,
and
maybe
my
concerns
here
are
not
as
valid,
and
I
think
if
there
are,
you
know,
there's
seven
people
in
this
room
and
if
two
of
you
think
this
is
a
good
idea,
and
I
don't,
I
think
that
the
good
idea
wins
so
yeah.
C
So
so,
if
you're,
not
a
backdrop
user
that
has
followed
the
history
of
backdrop,
you
don't
know
that
the
thing
that
we
now
call
title
block
is
actually
a
combo
thing
that
has
multiple
that
affects
how
multiple
things
are
presented.
So
you
need
to
have
internal
knowledge
so
that
I
think
that
we're
making
a
knowledge
assumption
there,
whereas
if
I
was
a
new
user-
and
I
was
looking
at
the
layout,
if
these
are
components,
I
would
expect
them
to
be
there.
C
H
B
What
it
does
it?
Basically,
you
can't
I'm
I'm
doing
a
screen
share,
because
I
just
think
yes
that
helps
right.
So
we
can't
put
the
breadcrumbs
above
the
page
title
unless
we
place
the
page
title
as
a
block.
So
that's
all
it
does
is
it
adds
the
page
title
and
we're
not
looking
at
the
actual
pull
request
right
now,
I'm
just
looking
at
a
regular
sample
site,
so
it
just
adds
the
the
title
block
into
the
the
top
region,
and
then
it
puts
the
breadcrumbs
above
it
so.
A
If
you
open
the
pool
it's
a
good
question
yeah
I
can,
I
can
have
a
look
at
it.
I
think
so.
So
the
page
title
is
for
sure
weird,
and
there
are
some
reasons
why
it's
weird
and
a
lot
of
it
has
to
do
with
just
the
you
know:
there's
there's
it's
special,
but
there's
other
things
on
the
page,
like
messages
and
tabs.
A
The
backdrop
will
be
broken
if
they
didn't
end
up
on
the
page,
and
so
we
built
layouts
in
a
way
we
looked
at
all
the
stuff
that
was
in
the
page,
template
and
we're
like
what,
if
this
needs
to
remain
in
the
template
and
what,
if
this
should
be
a
block
at
the
very
beginning,
we
decided
the
page
title
needs
to
remain
in
the
template,
the
tabs
and
the
messages
need
to
frame
and
templates.
They
aren't.
A
If
they
aren't
there,
the
site
will
be
broken,
but
that
doesn't
mean
that
you
know
we
now
have
the
ability
to
also
add
them
as
other
things.
So
the
question
is
the
page
title
I
think,
makes
sense
as
a
block,
because
people
are
going
to
understand
what
that
is.
But
things
like
messages
and
tabs
like
people
are
new
to
backdrop.
A
I
don't
know
if
you're
going
to
think
of
that
as
a
page
element
that
needs
to
appear
on
the
page,
so
I
don't
know
I
could
get
behind
adding
the
title
block.
But
then
the
question
is:
did
the
messages
and
the
breadcrumbs
come
out
in
a
weird
place?
If
we
do
that.
J
C
Exactly
what
I
do
yes,
so
my
my
take
on
that
is
that
the
title
is
basically
a
remnant
of
d7
and
how
we
inherited
things
or
how
we
adapted
it
and
because
we
didn't
have
the
features
that
were
added
very
lately,
namely
the
combo
box,
and
you
know
splitting
those
things,
that's
how
we
sort
of
like
left
it.
But
now
we
have
a
much
better
way
of
doing
things.
So
why
not
do
it
for
new
sites
yeah.
A
I
mean
so,
I
think,
like
we,
we
can't
get
around
the
way.
We
have
it
like
that.
Wasn't
a
mistake.
We
did
it
correctly,
but
we
didn't
figure
out
how
to
also
provide
the
block
feature
until
later,
and
so
the
question
is
now
we're
like
okay,
so
we
have
the
original
like
safe
implementation
done,
but
we
also
have
this
optional
block
implementation.
A
I'm
fine
with
us
putting
the
optional
implementation
in
there.
I
don't
think
we
can
ever
get
rid
of
having
the
fallback
page
title.
I
think
that's
always
going
to
remain
there,
but
is
it
going
to
be
really
weird
for
people,
and
this
is
weirder
than
it
is
now
to
go
in
their
edit
their
layout
and
remove
the
page
title
and
have
the
page
title
reappear
on
the
page?
Is
that
a
weirder
experience
than
having
it
be
there
by
default
and
having
to
add
a
block
in
order
for
it
to
disappear?
A
Yeah
then
your
title
won't
end
up
on
your
page.
If
your
title
doesn't
end
up
on
your
page,
it
doesn't
set
your
your
like
page
title
and
the
header
tag,
but
there's
a
bunch
of
stuff
that
doesn't
happen
if
there's
no
title
on
the
page,
so
I
think.
D
D
A
A
I
think
we
could
make
a
non-deletable
block
in
backdrop
one,
but
there's
just
a
bunch
of
stuff
that,
like
you,
create
a
node
and
you
hit
save
and
there's
no
title
on
the
page
you're
going
to
be
really
confused.
A
A
I
just
use
regular
block,
but
and
style
it
like
a
hero,
just
use
the
regular
title
block.
A
J
C
G
G
A
I
don't
think
there's
a
use
case,
for
that
I
mean
I
think
you're
always
going
to
either
want
a
title
on
the
page
or
you're
going
to
want
to
say
in
this
particular
instance.
Don't
show
a
title
you
don't
ever
going
to
say.
I
never
want
a
title
on
my
website
because
the
title
pulls
like
depending
on
what
type
of
page
you're
on
is.
It
can
be
anything
it
can
be.
A
no
title
could
be
a
term
title.
It
can
be.
You
know,
custom.
A
On
a
layout
and
wherever
that
comes
from
it's
the
same
block,
but
it's
a
different
data
source,
and
so
I
think,
if
you're
going
to
be
ending
up
to
replace
your,
you
know
default
page
title.
A
You
you've
got
to
have
something
there
instead,
but
that
doesn't
mean
we
can't
have
other
options
for
how
to
display
your
page
header,
like,
I
think,
a
module
that
gives
you
a
page
title.
Hero
block
is
an
excellent
idea.
I've
seen
that
done
a
lot.
I
think
it's
pretty
common,
but
I
wouldn't
I
couldn't
imagine
an
in
a
scenario
where
you'd
have
a
site
that
never
had
a
page
title.
C
A
A
I
think
it's
gonna
involve
some
more
fiddling
around
like
there's,
also
like
weird
use
cases
where
like
what,
if
somebody
went
like
edit
their
configuration
file
and
deleted
the
block,
did
we
like
automatically
edit
the
configuration
file
and
save
it
put
the
block
back
in
first
on
the
page
surrendered
of
weird
stuff
where
right
now,
because
the
page
title
is
added
in
the
template,
you
just
check
and
say
like?
Is
there
a
block
there?
If,
yes
remove
the
title
from
the
template?
A
What
what
do
we
call
the
pseudo
block
yeah
so
tim?
I
wasn't
looking
when
you
did
your
demo
to
figure
out
whether
it
was
the
combo
block
or
the
regular
page
title
block.
But
I
can
look
at
that
after
this
meeting.
A
The
question
is
it
weirder
to
delete
the
block
and
have
a
weird
title
show
up,
or
is
it
weird
to
have
a
weird
title
in
the
first
place
and
have
to
figure
out,
you
have
to
add
a
block
to
do
it
and
I
think
joseph
you
said
it's
weirder
the
way
it
is
now
than
the
current
proposed
solution,
which
is
to
add
the
block.
I
think
I
think
someone
else
said
they
wanted
to
add
the
block.
To
was
that
you
gregory
or
robert.
C
Yeah,
let
me
just
say
that
this
is
another
example
of
developers
manifesting
their
ideas
into
the
ui.
Without
you
know,
it's
like
it
doesn't
make
sense
to
simple
users,
so
we're
trying
to
to
communicate
the
underlying
technology
and
php
logic
into
a
ui
thing
which,
ideally,
we
shouldn't
be
doing
but
yeah.
Oh,
we
can't
break
the
api,
yes
exactly,
but
so
long
as
we're
not
breaking
the
api
yeah,
provided
that.
C
So
yeah
I
would
like.
I
would
like
to
at
least
when
I
say
explore
the
idea,
at
least
because
in
my
head
I
can't
think
of
the
blockers
before
I
actually
start
working
on
it.
So
if
we
start
working
on
it
and
it
turns
out
that
we
don't
like
it
breaking
api
or
existing
templates
and
so
on,
we
could
do
it.
If
we're
breaking
things
yeah,
we
can
implement
only
sorry
go
ahead.
A
All
the
current
pull
request
does
is
place
this
block
on
new
installs.
So
what
we
could
do
is
like
where's.
The
pull
request:
try
it
for
six
months.
If
everybody
freaks
out,
we
just
do
it
so
all
new
sites,
six
months
from
now,
don't
have
it
like
this,
isn't
the
kind
of
change
that
I
think
is
gonna.
You
know
be
irreversible,
we're
not
introducing
anything
new.
That's
gonna
cause
problem,
we're
just
trying
a
new
default
configuration
yeah.
So
exactly
yeah.
A
C
G
Minor
point:
I
think
that
if
I
didn't
know
how,
if
I
didn't
have
the
experience
of
knowing
how
themes
work
in
drupal
and
came
into
this
system
and
saw
that
page
title
was
a
special
thing:
that's
not
in
a
region
that
can't
be
dragged
around.
I
would
assume
that
that
that
there
was
not
a
page
title
blocked
somewhere
else.
G
A
B
C
C
So
this
was
dependent
on
the
addition
of
the
details,
form
api
element.
C
So
this
is
in
core
now
right
or
it's
not
it
is.
It
is
yeah
so
permission
to
reclassify
that
as
a
task
and
work
on
it
over
the
weekend
so
that
it
can
get
in
and.
A
I
think
we
we
need
to
ask
a
quark
motor
about
that.
I
think
there
it
there
was
some
nervousness
about
potential
ramifications
of
that
issue.
I
was
really
pleased
to
see
how
simple
the
code
looked
in
order
to
make
that
change,
but
I
think
we
need
to
focus
our
eyes
on
it
in
order
to.
C
Sure,
having
said
that,
I
need
to
mention
I'll
actually
change
the
works
for
me,
and
so
the
pull
request
needs
to
be
rebased
now,
okay
and
it
and
the
code
will
be
even
simpler
because
all
the
form
api
things
have
already
been
merged,
so
the
change
will
be
even
more
minimal.
C
Last
time
when
it
was
reviewed,
it
was
rtbc
depending
on
because
we
sort
of
like
forgot
that
we
needed
to
first
get
the
api
thing.
The
form
api
thing
in
and
the
only
request
was
that
we
had
a
polyfill.
I
don't
feel
that
the
polyfill
now
is
part
of
this
issue.
It
can
be
a
follow-up
for
the
main
issue,
which
is
you
know
in
general,
adding
a
polyfill
for
or
not
or
details
elements.
C
So
over
the
weekend,
I
plan
to
work
on
this
on
this
basically
and
see
how
simple
the
code
is
not
or
not,
and
also.
I
think
that
the
the
resistance
was
that
my
css
selectors
at
the
time
were
too
generic,
so
they
would
affect
more
things.
I
will
try
to
specifically
target
those
things
now.
A
I
want
to
add
one
issue
too:
if
people
are
interested
in
reviewing
stuff,
we
have
this
block
consistency,
issue
between
layout,
flexible
layout,
template
builder
and
the
regular
block
you
like.
I
saw
you
posted
a
comment
with
one
issue
with
right
to
left
button
placement
or
something
like
that
I'll
look
at
that
today,
but
I
think
that
one's
pretty
close
too
and
we
could
probably
get
120.
C
A
A
A
Also
tim
made
me
too
excited,
so
I
made
a
recipes
module.
I'm
gonna
keep
working
on.
It
doesn't
list
anything
yet,
but
it's
gonna
list
everything
that's
in
the
package
recipes
for
now
you
can
adjust
as
needed.
B
I
don't
know
oh
yeah,
I
can
I,
when
I
shared
my
meeting
my
whole
zulu
or
my
zoom
thing
kind
of
crashed
where
dang
it.
Where
do
I
stop.
A
Okay,
here
we
go,
I
can
stop
it
all
right,
we're
stopping
the
stream
we'll
be
back
in
a
minute.