►
From YouTube: 2021/08/26 Backdrop Design/UX
Description
Feature freeze is coming up.
Agenda: https://bit.ly/2Y2fICv
During this meeting we talk about:
* Better default position for Breadcrumbs - https://github.com/backdrop/backdrop-issues/issues/4113
* Add a new pageless node above "Promoted Content" block - https://github.com/backdrop/backdrop-issues/issues/4849
* Adding styling for Flexible Layouts Block UI https://github.com/backdrop/backdrop-issues/issues/5149
* Add a new core theme (brief discussion) - https://github.com/backdrop/backdrop-issues/issues/5175
A
A
Yourselves,
if
you
could
say
what
your
name
is
where
you're
from
and
if
you
have
something
exciting
to
share
with
the
group,
that
would
be
great.
I
am
jen
lampton
joining
from
oakland
california.
A
I
am
so
excited
about
all
the
activity
in
the
issue
queue
this
week,
everybody
seems
to
be
going
pedal
to
the
metal
on
usability
issues,
user
enterprise,
improvements
that
might
not
be
usability
focus,
but
just
making
things
consistent,
making
things
better.
It's
my
favorite
thing
about
backdrop
is
how
much
all
of
that
stuff
gets
improved.
So
I'm
really
excited
to
work
on
that
stuff.
This
week,
greg.
C
Hi
I'm
greg
I'm
joining
from
greece
and
also
excited
about
the
future
phrase
coming
up
and
working
on
all
the
excuse,
the
dog.
Sorry,
I
have
a
bargaining
dog
at
the
background
yeah,
so
I've
been
one
of
the
people
being
really
active
in
the
queue
after
being
in
a
hiatus
for
a
month
and
a
half
really
excited
hope
to
get
most
of
the
things
that
are
really
close
in
and
let's
go
to
team.
D
Hi,
I'm
tim
st
paul
tim,
I'm
in
deerwood
minnesota.
I
have
also
sort
of
dove
into
the
issue:
q,
after
being
absent
from
the
issue
queue
at
least
for
several
months,
hardly
doing
anything.
So
I'm
trying
to
push
a
few
issues
forward
and
I'm
excited
about
this
yeah
I'll.
Just
leave
it
at
that.
Surashree.
D
So
sorry,
I
don't
know
maybe
next
week
when
you
and
I
talk-
I
could
show
you-
I
think
you
might
not
know
how
to
be
helpful
at
this
stage.
In
the
like
the
release
cycle
and
one
of
the
things
you
could
be
doing
if
you're
interested
is,
there
are
a
lot
of
sort
of
design
issues
in
the
issue,
queue
that
are
tagged
and
we
have
sandboxes
that
are
all
set
up
and
you
can
just
go
in.
D
A
I
don't
know,
should
we
just
go
down
issues
from
the
queue
oh
greg's
excited.
C
Well,
I
don't
have
mine,
I
have
a
there's
a
as
I
said
before,
before
the
reporting.
I
I
filtered
the
list
by
design
label
and
it
shows
me
81
tickets
here.
So
there's
plenty
to
pick
from
there's
a
couple
of
ones.
I'm
gonna
pick
them
randomly
as
they
come
up
in
the
in
the
queue.
D
No,
actually
it's
it's
not
that's
the
more
count.
I
want
to
start
with
an
easier
one:
okay,
easier
easier,
not
to
necessarily
get
done,
but
to
get
a
clarification
john.
This
is
that
and
I'm
going
to
specifically
talk
to
you,
because
I
need
your
input.
It's
41.13.
D
I
was
just
going
to
quickly
summarize,
where
it's
been
left
off
right.
Is
that
my
current
pull
request
just
in
the
default
in
the
install
profile,
basically
disables
that
or
enables
the
the
page
title
block
and
then
moves
the
breadcrumbs
above
it,
and
you
have
raised
some
concerns
about
enabling
the
the
page
title
block
and
one
I
just
don't
know
how
not
to
do
that
and
still
solve
this.
D
One
of
your
things
was
to
also
you
had
suggested
that
we
do
this,
I
think
in
basis
instead
of
in
the
install
profile,
but
I
don't
know
how
to
do
that
without
backward
compatibility
issues,
yeah
and,
and
also
I'm,
not
sure
why
it's
a
problem.
You
know
to
enable
that
page
title
block,
because
again
it
seems
to
me
that
that's
a
more
background
way
to
do
it,
anyways
or
if
you
had
a
better
objection
to
that
like
why
that's
a
bad
thing.
A
A
What
I
was
thinking
is
that
we
don't
want
to
put
too
many
blocks
on
the
page,
because
then
every
time
you
like
clone
a
layout
there's
just
more
to
do,
but
the
page
title
is
also
something
that
is
really
confusing
to
people,
because
it's
not
a
block
by
default.
Only
if
we
were
to
make
it
one,
it
would,
I
think,
be
more
intuitive
for
people,
but
there's
a
bunch
of
other
stuff.
A
So
I
ran
into
this
problem
recently
with
someone
who
is
new
to
layouts,
where
they
overload
the
page
title
but
then
like
they
couldn't
figure
out
where
the
messages
and
the
breadcrumbs
were
coming
from,
because
all
of
that
is
sort
of
done
by
default.
And
then,
if
you
place
the
like
combo
block,
you
get
all
of
them.
If
you
don't
place
the
combo
box,
you
don't
get
all
of
them
and
there's
still
some
confusion
around
that
I
mean.
A
I
think
that
if
all
we
wanted
to
do
was
place
the
breadcrumbs
block,
you
know,
I
think
we
have
that
example
in
core
already.
I
think
it
might
even
be
in
the
default
template
like
there's,
there's
some
stuff
that
I
think,
makes
sense
by
itself.
I
don't
I'm
so
I
need
to
look
at
it
again
to
see
what
it
looks
like
in
the
pull
request.
I
was
recommended
to
see
if
I
still
have
an
objection
to
it.
A
C
I'm
sure
that
I
would
have
thoughts,
but
this
specific
issue
is,
I
want
to
see
how
github
has
this
blue
mark
when
you
haven't
have
unread
comments-
and
I
know
that
I
haven't
touched
that
issue
for
for
quite
some
time,
so
there's
a
lot
of
catching
up
to
do
and
I'm
already
in
the
middle
of
a
lot
of
things.
So
the
summary
is
that
I
need
the
same.
As
you
said
I
have
to.
I
have
to
take
a
closer
look.
I
I
wasn't
prepared
for
this,
but
I
appreciate
the
the
the
feedback.
C
I
don't
think
that
the
concerns
that
you
raise
are
any
different
from
the
ones
that
have
been
raised
initially
and
also
the
the
technical
challenges
that
that
team
mentioned
I'll
have
to
have
a
thing
and
chime
in
yeah
I'll
probably
do
that
over
the
weekend,
yeah.
A
I
think
that
my
original
thought
was
like.
Oh
rather
than
doing
this
in
configuration,
we
should
just
do
it
in
code,
but
tim
you're
exactly
right
that
I
don't
think
that's
possible
without
with
backwards
compatibility,
or
at
least
it
would
be
really
messy
if
we
did
it
that
way
like
there
would
have
been
some
kind
of
theme
setting
or
something
that
would
be
like
override
my
blog
placement
or
whatever
some
layout
setting.
I
don't
know,
and
I
think
that
I'm
not
sure
that
belongs
in
core
the
fancy
overriding
thing.
A
So
I
don't
know
I
feel,
like
my
personal
preference,
would
be:
let's
wait
until
backdrop
two
and
move
everything
around
into
the
right
place
in
the
template,
but
there
isn't
anything
that
says:
we
can't
set
the
block
now
and
then
move
everything
around
the
template
and
backdrop
two
and
remove
it
then
so
yeah.
I
need
to
look
at
it
again
and
see
if
I
still
actually
have
objections
to
it
or
if
I've
come
around,
I'm
just
placing
that
down.
C
I
have
I
have.
I
have
two
comments
to
make
one
related
to
this
issue
and
then
the
other
one,
more
broadly,
my
pet
peeve
all
the
time,
and
I
would
be
very
interested
to
get
input
from
the
the
grace
hopper
guys
that
I
will
be
working
in
accessibility.
C
But
my
maybe
this
is
a
personal
preference.
But
when
I
think
of
breadcrumbs
I
always
unless
the
the
final
crumb
is
the
page
title
with
which
some
people
have
a
preference
to
not
include.
I
always
make
make
a
mental
image
of
where
I
am
at
by
having
the
breadcrumb
at
the
top
and
then
the
page
title,
and
some
people
prefer
the
page
title
and
then
the
breadcrumb
beneath
the
title.
So
I
think
that
this
is
a
bit
backwards.
C
If
you
are
reading
the
the
page
from
top
to
bottom,
it's
sort
of
like
first
see
where
you
are
and
then
it
takes
you
back
to
the
breadcrumb,
which
starts
from
the
sort
of
like
top
of
the
hierarchy
of
the
pages.
I
don't
know
it
just
seems
backwards
to
me,
but,
as
I
said,
it
might
be
a
bit
personal
preference,
thingy.
A
I
can
I
can
speak
to
the
accessibility
of
that,
and
I
do
know
that
in
breadcrumbs
it
is
best
to
include
the
page
title
at
the
end
and
even
if
it's
not
visually
there,
they
still
like
to
have
it
in
a
like
screen
reader,
only
mode
that
when
you're
navigating
your
page,
not
visually,
you
can
tell
that
those
pages
are
the
parent
of
the
page
you're
on.
A
So
I
don't
know
if
that
necessarily
affects
the
position
of
breadcrumbs
above
title
or
not
because
of
the
titles
in
the
breadcrumbs
it
may
be
less
of
an
issue,
but
I
do
see
your
point
about.
If
you're
not
going
to
have
the
title
in
the
breadcrumbs,
you
should
have
the
title
immediately
following
breadcrumbs
and
then
it'll
read
the
same
way.
C
Yeah
and
when
it
comes
to
spring
readers,
we
can.
We
can
specify
the
top
bit
dicks.
So
if
they
expect
that
the
the
red
crop
or
top
and
then
the
title-
and
we
have
it
the
opposite
way,
we
can
just
mess
with
a
tab
index
and
then
it
will
sort
of
like
take
them
in
the
right
order.
But
I
would
prefer
if
the
tab
index
and
the
actual
order
were
the
same.
A
C
Enough
and
then
and
then
the
other,
the
other
sorry
I
have
about
dog
barking
at
the
background,
so
the
other
one
was
the
more
broadly
and
I'll
just
drop
it
on
the
floor
and
then
let
I
think
it's
one
of
team's
favorite,
so
tim
started
a
new
issue,
because
that
was
brought
up
about
backdrop.
2.0
he's
smiling
already,
so
we've
been
struggling
with
how
we
make
changes
that
are
breaking
when
it
comes
to
themes,
layouts
and
we
just
sort
of
like.
D
I
just
opened
an
issue
that,
if
we're
not
going
to
figure
out
a
way
to
if
we
can't
figure
out
a
way
to
make
css
changes
to
basis
that
I
I
you
know
to
me,
then
the
next
best
option
would
be
to
add
a
new
theme
and
that
could
possibly
become
the
default
theme
and
there
are
a
few
different
strategies
to
take.
A
Another
thought
what
we
could
do
is
take
basis
and
put
it
in
contrib
and
fix
it
all
there
and
then,
when
vector
2
comes
out,
we
take
the
contrib
version
and
put
it
in
core,
and
that
way
we
like
every
change
we'd
be
making
to
the
theme
would
be
future.
It
would
be,
you
know,
be
there
in
the
future.
We
wouldn't
have
to
do
it
again.
So
I
don't
know
this
of
course
assumes
we're
happy
with
basis
like
it
might.
A
C
C
No,
what
I
wanted
to
say
is
that,
of
course,
we
cannot
get
this
done
by
the
feature
phrase
as
you
mentioned
team.
It's
just
that,
because
mentioned
jen
mentioned
yet
another
time
that
you
know
we
can
do
this
in
two
point
x
and
this
sort
of
like
often
seems
way
too
far
ahead
in
time.
I
I
just
thought
that
you
know
maybe
for
another
discussion
but
yeah.
I
thought
it
was
like
relevant
not
to
solve
in
this
meeting,
though.
D
Okay,
well,
I
I'm
the
breadcrumb
issue.
I
think
the
the
status
is
that
greg
and
jen,
and
anybody
else
who
wants
to
can
take
a
look
at
it.
This,
I
think,
for
me,
it's
sort
of
my
last
like
push
on
this
and
if
it
just
doesn't
go
anywhere,
I
probably
won't
worry
about
it
anymore,
but
I
thought
I'd
see
one
more
time
if
we
could
resolve
it.
Let's
move
on
to
something
else,
though,
and
greg
if
you
want
to
move
on
to
that
hidden
node
thing
that
could.
C
Be
an
interesting
one:
it's
not
it's,
not
my
favorite,
my
the
ones
that
I've
been
working
on,
but
it's
at
the
top
of
the
list.
It
comes
as
a
mostly
recent,
most
recently
updated.
It's
issue
4849
in
which
we're
trying
to
add
a
page
list
node
above
the
promoted
content
block
on
home
page
and
there's
sort
of
like
a
related
issue
to
that
which
I'm
not
sure
it's
typed
as
design.
D
So
well
really
quickly.
This
the
history,
for
this
is,
is
how
this
issue
came
about.
Was
we
were
having
there's
this
other
issue
about
the
problem
with
the
path
for
the
home
page
and
how
that
gets
changed
and
one
of
as
we
were
talking
about
that
it
occurred
to
us
that
a
lot
of
people
think
they
need
to
change
the
homepage
path
and
they
don't
so.
D
A
proposal
was
raised
to
replace
the
the
promoted
content
block
with
a
about
just
a
static
content
block
or
a
an
existing
node
block
on
the
front
page
to
better
help.
People
understand
how
the
home
page
works
and
then
that
evolved
into
well,
if
we're
going
to
do
that,
we
we
have
this
idea
about
creating
adding
a
new
content
type
for
pathless
nodes,
and
we
should
add.
You
know
if
that
became
a
new
issue
and
and
so
those
that
that
was
sort
of
the
chain
that
got
us
here.
D
C
Yeah,
I
see
I
see
both
of
these
issues
as
related
the
other
one
is
4903
to
provide
a
new,
hidden,
bypass,
funding,
type
out
of
the
box.
There's
a
few
ideas
that
came
up
that
I
haven't
fleshed
out
completely,
but
I
sort
of
like
I
would
like
us
to
explore
them.
Someone
could
it
be
wilmer
mentioned.
C
I
can't
remember
who
it
was
that
now
that
we
are
getting
closer
with
recipes,
maybe
that
can
be
a
recipe
instead
of
a
core
thing,
although
I
would
still
like
we
have
this
feature
in
core,
which
is
really
cool
and
people
should
start
using
it,
but
it's
not
obvious
to
people
without
having
a
a
use
case.
C
We
had
some
discussion.
We,
we
sort
of
like
this
decided
to
quickly
sort
of
like
for
the
purposes
of
putting
something
together,
something
tangible
together,
we
decided
to
go
for
with
a
promo
box,
but
one
once
I
saw
that
implemented.
I
my
first
thought-
and
I
saw
the
homepage
with
that
there.
My
first
thought
was
that
we
have
two
very
similar
ways
of
presenting
content.
C
C
I
do
want
it
to
be
on
the
front
page
on
the
homepage,
but
I
want
it
to
be
visually
different
from
the
view,
and
I
want
it
to
be
something
that
that
fits
nice
into
the
page
list
nodes.
So,
like
example,
like
it's
a
it's
a
good
use
case
that
that
people
understand
immediately
so
again.
A
So
I
I
was
looking
at
that
all
the
activity
on
that
issue
recently
and
I
think
all
of
the
ideas
we
have
in
there
are
good
ideas,
and
so
maybe
we
need
to
figure
out
like
what
our
priorities
are
like.
If,
if
we
want
to
find
a
feature,
that's
good
for
120,
then
I
think
promo
box
is
the
way
to
go,
because
that
isn't
going
to
require
a
decision
about
a
javascript
library
or
whether
we
want
accordions
on
the
homepage
or
any
of
the
other
complexities
that
come
from
that.
A
The
one
downside
that
I
thought
about
this
morning,
when
we
were
talking
about
promo
box,
is
that
people,
without
any
context,
aren't
going
to
know
immediately
what
a
promo
box
is
or
some
of
the
other
things
like
faq.
Everyone
knows
when
faq
is
even
if
they
don't
want
one
on
their
own
website.
They'll
understand
that
immediately
or
even
a
slide
in
the
slideshow.
I
think
it's
a
little
bit
more
intuitive
than
a
promo
box.
That
said,
once
you
know
what
a
promobox
is,
it's
really
useful
right.
D
A
I
just
installed
or
removed
a
module
called
image
block,
that's
someone
who
put
on
a
backdrop
site-
and
I'm
like
you-
can
do
this
with
the
page
in
this
pages
node,
and
they
just
didn't
know
that
that
was
a
thing
right,
because
in
drupal
you
installed
a
module
to
put
an
image
on
a
block
now
you're
like
we
can
do
blocks
out
of
nodes.
I
don't
know
it's
just
it's
something
that
I
think
if
we
had
a
good
example
for
people
might
want
to
use
more.
A
So
I
I
don't
I
mean
I
know
we
have
a
pull
request
from
promo
box
dude.
Does
anyone
have
strong
feelings
about
moving
that
forward?
I
mean
greg.
A
I
know
that
it's
confusing
to
have
multiple
things
on
the
home
page,
but
I
think
if
there's
one
of
them
is
a
view
and
one
of
them
is
a
block
and
the
block
doesn't
have
any
links
and
the
view
does
have
links
that
should
be
a
pretty
clear
differentiator
between
the
two,
I
think
with
slides,
it's
a
little
bit
more
ambiguous
because
now
you've
got
more
than
one
item
in
that
area,
whereas
you
know
you've
got
a
view
with
multiple
items.
A
C
If
we
go
so
first
of
all,
I
expressed
these
concerns
multiple
times
on
that
issue.
If
we
go
with
a
slider
which
is
yeah,
it
provides
a
lot
of
value
out
of
the
box.
We
need
a
javascript
library
and
then
how
do
we
pick
one
that
is
accessible?
That
is
popular,
that
people
can
use
and
how
do
people
like
how
does
contrib
override
it
if
they
want
to
use
another
library,
so
you
get
into
this
whole
mess
and
and
the
maintenance
that
we
had
in
core.
C
So
it's
a
bit
of
a
hairy
situation
and
then,
if
you
add,
on
top
of
that
that
you
know
we
have
the
project
browser,
so
people
can
install
a
slider,
so
it's
sort
of
like
yeah.
I
don't
want
the
overhead.
I
was
refraining
from
doing
that.
What
I'm
gonna
do
is
I'll,
let
you
let
other
people
chime
in
just
one
final
thought.
If
we
go
with
a
promo
box,
I
would
like
I
would
like
us
to
go
with
something
that
is
visually
different.
C
I
was
refraining
these
days
from
posting
a
screenshot,
so
what
I'm
gonna
do,
while
you
guys
discuss,
is
I'm
gonna?
Take
a
screenshot
of
the
default
out
of
the
box,
gov
cms
theme
and
the
homepage
that
it
has,
and
it
has
a
series
of
boxes
that
are
horizontally
aligned
instead
of
vertically,
which
is
what
we
have
now
with
a
feed.
C
Maybe
if
we
style
them
different,
it
would
differentiate
them
from
the
other
thing
and
the
reason
why
I
haven't
posted
it
so
far
is
that
the
way
that
it's
presented,
these
are
not
a
good
fit
for
they're
visually,
a
good
fit
but
they're
not
a
good
fit
for
a
headless.
D
Yeah,
well,
I
I
just
want
to
raise
the
the
the
the
visually
distinct
that
bumps
us
into
the
problem
of
updating
basis,
although
it
might
not
be
a
problem,
if
it's
something
new,
if
we're
not
re-theming
something
that's
already
there,
then
it
might
be
possible,
but
that
you
know
one
of
my
concerns.
D
You
know
part
of
the
original
replacing
the
the
promoted
content
was
because
it
was
simple
and
it
didn't
require
like
a
lot
of
css.
It's
like
we're
taking
one
thing
off
we're
putting
another
on
and
boom
it's
done,
and
then
the
next
idea
was
well
hey.
Let's
have
that
and
the
promoted
content-
and
I
just
am
kind
of
stuck
on
how
to
do
that
and
make
it
look
good.
Now
olaf
has
said
he
has
some
ideas
and
he
hasn't
elaborated
on
those.
D
C
Yes,
yeah,
so
so
so,
if,
if
you
look
at
the
the
actual,
the
last
comment
on
the
on
the
ticket,
4849
is
the
screenshot
that
you
provided
team.
It's
the
screenshot
of
the
home
page
as
you
provided
it
and
from
from
from
an
outsider
point
of
view,
I
don't
see
any
difference
between
the
section.
That
is,
the
block,
the
the
your
homepage
block
and
the
selection
below
it's
just
a
a
waterfall
of
text
which
could.
C
C
What
do
we
do
with
it?
Yes,
exactly
so
how
about?
If
you
look
now
in
issue
4903,
I
posted
a
screenshot.
Sorry,
I
didn't
have
time
to
crop
it
to
the
section
that
I
wanted
it's
the
screenshot
of
the
homepage
of
wcms
right.
So
it
has
all
the
basic
elements
that
we
have
in
basis,
which
is
the
header
with
the
menus
and
then
the
big
hero
box,
but
then
it
has
a
set
of
vertically
sorry
horizontally,
aligned
boxes.
C
C
What
I
like
about
this
is
that
it's
visually
different
from
the
rest
of
the
elements
in
the
page
or
if
you
had
a
different
background,
color
like
the
the
green
ribbon
that
sits
above
that
those
boxes
in
that
I
want
it
to
be
different.
I
want
people
to
understand
that
this
is
something
different
than
the
rest
of
the
text
on.
A
I
also
think
this
solves
a
problem
of
how
do
you
put
more
than
one
thing
on
the
homepage
if
it's
one
promo
box
and
then
one
column
of
articles,
they
do
get
really
similar,
but
if
you
split
them
into
three,
our
current
layout
is
a
one
column
layout.
We
could
do
that
with
the
views
grid
and
drop
it
into
v3.
It
could
be
whatever
that
was
six
or.
However
many
was
on
your
example.
A
Page
two,
I
don't
know
more
than
one
right,
it'll
look
visually
different,
that
horizontal
bar
for
the
where
the
views
grid
goes,
gives
us
something
to
put
color
on.
If
we
wanted
to
add
another
color
background
in
there,
we
could.
I
think
it
gives
us
a
lot
more
options.
I
think
it
gives
us.
You
know.
Ability
to
you
know,
provide
a
feature
that
other
people
could
override
too.
A
I
think
if
I
were
to
build
the
page,
I
would
do
it
with
a
layout
with
three
regions,
but
because
we're
adding
it
to
core.
We
already
have
one
page
layout.
This
gives
us
a
workaround
for
that
which
I
think
is
also
good.
I
think
tim
that
adding
css
for
something
new
is
gonna
be
much
easier.
We
could
target
the
view
we
could
target
the
node
type,
all
that
stuff
isn't
in
core
yet
so
I
think
it
would
be
safe
to
add
to
basis
and
yeah.
A
I
think
this
gives
us
a
path
forward.
The
only
question-
and
we
can
fix
this
after
code
phrase-
if
we
need
to
is
if
we
need
to
add
any
special
language
around
like.
Are
we
happy
with
the
name
promo
box?
Do
we
need
a
description
on
it?
That's
gonna
explain
what
that
is
and,
of
course
naming
things
is
the
hardest,
but
I
do
think
that
you
know
we
can
start
with
what
we
have
and
get
something
to
like
a
rtpc
status
and
worry
about
adding
more
description
text
later.
If
we
need
it.
C
Yeah
so
so
yeah
we
can
discuss
if,
if
people
decide
to
sprint,
we
can
discuss
this
further
and
maybe
we'll
bake
something
before
feature
freeze
but
yeah.
That
was
my
main
concern.
Otherwise
I
like
the
idea
of
the
promobox
in
the
sense
that
we
don't
have
to
depend
in
javascript
or
whatever
I
just
wanted
to
be
distinct,
as
it
said.
That's
it.
Can
you
say
the
issue
number
again
that
for
the
the.
C
C
4903
and
then,
and
then
to
compare
it
to
the
screenshot
that
other
people
sort
of
like
requested
team
to
implement
things,
has
the
other
issue
is
48.49.
So
compare
the
last
screenshots
on
those
two
issues
and
you'll
see
what
I'm
talking
about
48
48.49.
C
D
C
D
That,
probably
we've
gotten
as
far
as
we
can,
I
mean
this
has
been
a
useful
discussion
and
talking
about
it
on
saturday
or
over
the
weekend
will
be
good,
so
I
think
we
could
move
on,
although
I
think
we
should
at
least
acknowledge
the
because
doc
willmon
is
here,
the
concern
he
raised
and
get
some
quick
feedback
on
that
joseph
might
also
have
thoughts
on
the
issue
of
tests.
So
what
are
the
the
test?
Testing
implications
for
adding
a
new
content
type
joseph?
Are
you
did
you
see
the
discussion
about
this.
G
D
This
is
just
a
separate
issue
about
adding
a
new
content
type
to
core,
which
will
help
illustrate
some
features
but
doc
wilmot,
which
back
feel
free,
feel
free
to
chime
in
raised
the
concern
that,
if
we
add
a
a
content,
type
that
there
might
be
a
huge
overhead
in
terms
of
additional
tests
that
need
to
be
written
and
we're
not
sure
if
that's
really
true
or
not-
and
I'm
just
wondering
if
you
have
any
opinions
and
adding
a
content
type,
what
what
the
implications
are
for
testing.
G
G
D
A
But
I
would
envision
as
adding
a
test
that
would
make
sure
that
the
pageless
node
appeared
on
the
home
page
or
on
the
home
page
in
the
view,
so
that
we'd
also
be
testing
the
node,
the
view
and
the
placement
in
the
layout
I'm
sort
of
in
one
fell
swoop,
and
that
way
we
make
sure
the
feature
we're
adding,
doesn't
get
broken
in
the
future
by
anything
else.
But
I
don't
think
we
need
to
retest
anything
about
nodes
or
about
pageless
nodes
or
about
node
types
or
about
field
ui
or
all
the
other
stuff.
A
Dog
beaumont
pointed
out,
though,
that
there's
a
bunch
of
places
in
core
where
we
run
one
test
against
both
existing
node
types,
and
it
could
be
useful
to
update
some
of
those
to
include
okay.
Well,
let's
run
this
test
against
all
three
instead
of
two,
but
I
don't
think
we
have
to
update
all
of
them.
I
think
if
we
wanted
to
update
some
of
them,
we
could,
but
I
don't
think
it's
going
to
be
a
huge
amount.
C
Yeah
right,
I
think
that
we
could
also
iterate.
So
we
can.
We
can
grab
the
ones
that
we
find
on
the
first
pass
and
then,
if
we
find
more
and
we
run
out,
then
we
just
add
them
sequentially
or
eventually
somebody.
C
H
Okay,
so
just
to
jump
in
here,
I
wasn't
specifically
speaking
about
adding
tests
for
this
function
and,
to
be
honest,
my
concern
was
it's
not
really
a
concern.
H
H
So
if
we
add
another
content
type,
instead
of
thinking
of
only
two
types
of
nodes,
we're
now
going
to
have
to
be
thinking
about
three
types
of
nodes,
so
that
would
increase
our
just
the
amount
of
thinking
you
have
to
do
both
now
in
the
existing
code
and
any
code
in
the
future
that
you
have
anything
to
do
with
nodes.
So
that
would
increase
our
workload
a
little
bit
and
that's
something
I
think
we
should
just
make
sure
we
consider
for
the
future.
H
That's
all
it
might
be
that
I
am
completely
you
know,
you
know
exaggerating
and
it
will
have
a
little
impact,
but
I
think
you
know
even
a
little
for
a
small
team.
We
have
to
be
sure
that
the
benefit
that
we
get
out
of
this
is
worth
the
even
a
little
bit
of
increase
in
work
that
is
necessary
now
and
in
the
future.
That's
that's
my
point.
C
Yep,
no,
no,
it
was
a
legitimate
concern,
but
I
just
don't
think
that
we
have
to
change
all
tests
to
account
for
all
content
types
or
that
we
have
to
do
it
with
this
change.
We
can
do
it
in
the
future,
like
we
can
make
sure
that
all
of
them
are
there.
It
will
add
some.
I
guess,
execution
time
to
the
tests,
depending
on
how
many
we're
writing
but
yeah.
C
I
think
that
also
we
need
to
address
I'm
trying
to
find
who
mentioned
that
that
couldn't
that
be
implemented
as
a
as
a
recipe
and
to
my
understanding
it
could
once
we
get
those
working
as
expected,
because
it's
basically
configuration,
but
I'm
not
sure
if
the
rest
of
it
like
the
placement
could
be
possible
like
to
put
it
in
a
specific
layout
could
be,
but
you
have
to
be
they
had
to.
You
would
have
to
figure
out
some
logic,
but
then
styles
or
themes
does
do
recipes
now.
D
D
This
in
the
first
place
was
to
have
it
there
out
of
the
box
right.
So,
yes,
we've
only
got
10
minutes
left
in
this
meeting
and
I'm
wondering
if
we,
you
know
we've
gotten.
We
should
we.
There
seems
to
be
some
momentum
here
and
some
next
steps
and
if
we
should
see,
if
there's
any
other
issues-
and
I
I'll
just
say
I
sort
of
resurrected
this
issue,
partly
because
it's
sort
of
a
splashy
issue-
it's
not
like
functionally
critical
to
background,
but
I
feel
like
it
would
have
an
impact
and
really
show
you
know.
D
I
don't
know
just
be
a
visible
change
when
people
open
up
the
next
issue
or
the
the
new
release
of
backdrop,
they'll
see
something
different
and
to
me
that
has
marketing
value.
Is
there?
Are
there
any
other
issues
that
we
can
just
talk
about
today?
That
sounds
like
be
good
marketing
or
good,
or
just
important
to
get
into
go
ahead.
G
So
one
more
thing
before
we
move
on
just
in
relation
to
tests,
I
personally
don't
think
we
should
have
any
tests
that
depend
on
the
default
content
types,
except
maybe
the
standard
profile
test,
because
if
we,
if
we
have
a
feature
that
breaks,
if
you
delete
the
page
content
type,
then
that
feature
is
broken
so
yeah
and
then
the
other
thing
is
that
if
we
have,
if
it
we
do
depend
on
those
default
content
types,
then
we
by
implication
depend
on
the
standard,
install
profile
and
one
of
the
things
I've
been
working
on
to
make
our
test
framework
faster
is
converting
all
the
tests
to
use
the
test
profile,
which
installs
very
few
modules
by
default.
C
C
Yeah
yeah,
actually
you
make
a
good
point.
Can
I
be
selfish
now
more
selfish
than
usual,
so
the
other
thing
that
I
would
like
to
discuss
is
issue
50,
90,
so
5090,
which
is
the
details
replacing
the
more
or
less
stubble
with
details.
C
We're
really
close
with
that.
I
think
that
the
only
task
that's
left
there
is
adding
the
the
polyfill
for
other
browsers.
C
And
related
issues
is
there's
a
few
issues
in
the
queue
with
updating,
outdated
icons,
the
sorting
icons,
the
structure
icon,
I'm
not
sure
if
these
are
features
or
attackers
features
or
tasks,
but
I
would
like
to
see
them
get
in
at
some
point.
These
are
the
things
that
come
off
the
top
of
my
head
and
now
I'll
leave
some
time
for
the
rest
of
the
people
to
another
five
minutes
to
bring
their
favorite
issues.
D
Gregory,
so
what
what
needs
to
happen
on
this
issue?
Are
you
looking
for
feedback?
You
just
need
more
input.
What
will
we
need.
C
I
need
I
need
to
know
that,
a
that
it's
up
to
standards
and
that
no
one
has
any
other
objections,
because
what
really
remains
is
to
make
sure
that
we
support
all
the
browsers
which
is
sort
of
like
a.
It
is
a
task.
It
needs
to
get
done
and
test
it.
But
I
need
to
know
before
I
start
doing
that.
I
need
to
know
that
the
feature
as
is
now
is
ready,
if
you
disregard
that
fact
that
it
won't
work
without
a
polyfill
in
all
the
browsers.
A
A
C
C
Okay,
so
yeah
then
do
you
have
any
favorite
design
or
ux
issues?
How
about
the
oh?
We
have
the
flexi.
F
A
D
C
D
A
Essentially
when
flexible
templates
went
in
it
was
so
exciting
everybody's
like
it's
great,
get
it
in,
but
we
I
didn't
really
do
a
lot
of
design
comparisons
between
other
pages,
which
is
fine.
It
was
a
great
feature.
So
all
this
full
request
does
is
take
the
css
from
the
like
manage
blocks
page
and
apply
some
of
the
same
elements
to
the
manage
flexible
layout
page.
A
So
it's
got
draggable
icons
in
the
header
row
and
I
don't
know
like
a
visual
indicator
of
the
row
itself,
so
that
when
you
pick
it
up,
you
can
see
where,
like
which
element
it
is,
I
don't
know
it's
it's
cleaner.
I
guess
but
yeah.
Thank
you.
I
don't
know
how
many
people
were
helping
me
iterate
on
that
there
was
like
six
or
seven
people
helping
with
feedback
on
that,
and
I
was
just
like.
I
don't
know
what
to
do.
A
D
A
Yeah,
it's
currently
both
needs
code
review
and
needs
testing.
So
if
anyone
hasn't
seen
it
yet
and
wants
to
get
tickets.
A
C
One
thing
that
is
not
a
feature,
but
it's
a
task,
but
it's
I
think
it's
sort
of
like
blocking
the
rest
of
the
things
is
peters
3402,
which
is
the
standardized
label
and
machine
name
for
admin
listings.
We
are
so
close
with
that.
That's
34.02.
A
Oh
yeah,
this
is
a
good
one,
that
one's
really
close
too.
Isn't
it.
C
C
A
I
document
that
one
to
the
agenda
too.
If
anyone
is
working
on
that
wants
to
see
it.
A
Ahead,
it's
it's
2p,
it's
well,
it's
the
end
of
the
hour
various
hours,
depending
on
where
we
are,
which
means
it's
time
for
deaf
meeting.
I
know
this
meeting
has
become
not
only
about
design
but
about
all
of
the
stuff
we're
excited
about
for
one
funny
which
I
think
is
still
valid,
but
maybe
we
should
stop
the
recording
and
start
the
one
for
the
weekly
meeting.
C
Sure,
yeah
and
close
by
saying
that
we
a
lot
of
us
plan
to
sprint
over
the
weekend
for
the
days
before
the
first.
So
the
best
I
guess
a
place
to
align
on
that
is
zulib,
and
if
anyone
is
around
and
sprinting
just
let
us
know
so
we
can
jump
in
those
of
us
that
have
time.
H
Yep
can
I
just
say
one
thing:
a
little
late.
Sorry,
we've
had
a
bit
of
talk
about
exposing
functionality
to
to
new
users.
I
was
just
looking
through
the
country
modules
and
seven
years
ago
I
ported
drupal's
tour
module.
I
think
there
was
a
plan
at
some
point
for
drupal
to
include
tour
module.
If
you
remember,
I
don't
think
that
that
went
ahead.
H
A
Tour
module
is
in
drupal
core
and
it
has
failed
in
its.
H
C
C
We
everybody
loved
their
idea,
like
the
the
fact
that
you,
because
a
lot
of
software
uses
it
out
there,
but
but
if
we
could
find
a
way
to
decouple
the
content
from
the
feature
so
that
we
can
update
the
content,
because
it's
translated
strings
as
well,
and
things
like
that,
if
we
could
find
a
something
like
the
localization
server,
that
would
pull
the
core
tours
and
we
could
independently
update
those
or
if
people
think
that
that's
a
good
idea,
then
it
could
get
in
like
and
it's
not
something
that
we
could.
A
Yeah,
I
think
that
I
think
the
reason
it
wasn't
as
successful
in
drupal
core
is
because,
in
order
to
do
a
really
good
tour,
it
takes
a
lot
of
content
on
whatever
thing
you're
trying
to
do
or
tour
on
and
content
is
what's
hardest
for
developers
to
produce.
I
also
think
that
that
will
be
something
that's
perfectly
suited
for
kintrib,
because
then
we
can
get
fewer
people
that
have
to
be
core
developers
to
work
on
it.
I
love
this
idea
greg
of
having
like
a
central
content
repository.
That's
not
in
the
module
itself.
C
A
I
also
think
that
this
is
something
that
would
could
be
really
useful
on
our
sandboxes
on
the
try
demo
button,
even
if
it
doesn't
end
up
in
core
putting
it
something
that
will
be
front
and
center
for
people
who
are
testing.
Backdrop
could
be
really
useful
too.
So
I'd
love
to
see
some
progress
on
that
somehow.