►
From YouTube: Backdrop UX/Design - 2021/09/23
Description
This meeting dealt almostly exclusively with the idea of providing a new path-less node in core by default and changes to the default content on the home page.
A
All
right
we
are
live
today
is
thursday
august
23rd,
and
this
is
our
fortnightly
design
meeting
before
we
get
into
the
agenda.
I'd
like
to
go
around
and
do
some
quick
introductions.
So
if
anyone
would
like
to
share
something,
that's
not
on
the
agenda
now
is
the
time
to
do
that,
but
also
where
are
you
from
and
what
your
name
is?
I
can
go
first,
my
name
is
jen
lampton,
I'm
joining
from
oakland,
california.
A
B
C
G
My
name
is
tim
erickson,
I'm
st
paul
tim,
I'm
in
deerwood
minnesota,
where
the
leaves
are
starting
to
change.
You
can
come
here.
Luke
we
have
colorful
leaves
too
and
some
great
mountain
biking
by
the
way-
and
I
am
so
this
week
I've
been
doing
a
little
bit
of
playing
a
little
bit
with
screencasts
and
later
today
I
have
a
brand
new
microphone
coming.
So
that's
the
excitement
in
my
life.
So
I
guess
that's
it.
A
G
Well,
olaf
may
be
here
because
of
this
agenda
item
I
don't
know,
maybe
he
would
have
come
anyways,
but
I
know
he
the
the
the
node
lists.
What
do
we
call?
The
pathless
node
title
I
just
a
couple
weeks
ago
thought
there's
a
lot
of
a
flurry
of
activity
around
this
right
before
the
launch,
and
then
it
became
clear.
It
couldn't
happen.
G
G
G
That
would
be
great,
and
I
think
in
my
own
opinion,
that
this
this
issue
started
as
nodeless
or
paid
pathless
nodes,
and
then
it
became
as
much
about
sort
of
content
on
the
front
page
right
because
we're
actually
placing
some
default
content
which
isn't
necessary
to
add
novice
or
pathless
pages,
but
it
did
sort
of
help,
explain
it
and
I
thought
it
might
not
hurt
to
do
a
little
brainstorming
on
just
like.
Are
there
other
front
page,
just
design
issues
that
we
should
be
thinking
about
in
conjunction
with
this.
A
Yeah
I
mean
so
in
general,
I
feel
like
they're
a
bit
like
five,
really
good
ideas
that
we've
landed
on
and
we're
trying
to
figure
out
how
to
solve
them
and
if
any
of
them
can
be,
salt,
like
multiples
of
them,
could
be
solved
by
the
same
solution
and
if
I
remember
correctly
and
tim
feel
free
to
correct
me.
If
I
don't
have
this,
one
of
the
things
we
wanted
to
do
was
add
a
piece
of
content
as
a
existing
content.
So
we
had
an
example
of
that
sort
of
reference
functionality.
A
A
A
We've
identified
even
more
possible
solutions
for
them
and
we're
just
trying
to
figure
out
what
might
be
the
best
scenario
for
core
with
the
particular
issue
that
we
were
working
on
for
120,
I
believe,
where
we
landed
was
that
we
tried
to
create
a
new
page
list,
node
type
called
promobox
and
we
had
a
little
confusion
about.
Maybe
we
shouldn't
do
that
and
then
decided.
A
Maybe
we
liked
the
idea
of
card
better,
but
didn't
ever
actually
create
a
pull
request
using
cards,
we're
still
using
the
promo
box,
pull
request
and
then
what
tim's
sharing
right?
Now
I
don't
know,
do
you
want
to
talk
about
this,
I'm
happy
to
describe
what
you're
pointing
at,
but
you
might
be
better
at
it.
A
Okay,
so
yeah,
but
what
we're
looking
at
right
now,
I
think,
is
the
the
latest
pull
request,
which
shows
three
promo
boxes,
one
two
three
in
a
grid
layout
placed
onto
the
home
page-
and
this
was
inspired
a
little
bit
by
a
screenshot
that
greg
posted
in
the
issue
that
showed
the
home
page
of
govcms,
where
it
had
a
bunch
of
little
blocks.
I
think
there
were
five
or
something
across
the
home
page,
and
we
saw
that
and
thought.
Oh,
we
could
do
that
too,
and
the
benefit
of
doing
it.
A
A
A
There
are
probably
better
ways
to
do
grid
layouts.
If
you
were
going
to
build
this
to
yourself
and
each
individual
promo
box,
p
piece
of
content
here
is
not
placed
as
an
existing
piece
of
content,
which
was
something
that
we
did
want.
It's
placed
the
same
way.
Other
content
is
placed
as
appearing
in
views
and
blocks,
so
we
only
solved
some
of
the
problems
we
wanted
to
solve
and
not
all
of
them.
I
don't
know
that
we
need
to
solve
all
of
them
in
one
solution,
but
there
there
was
some
discussion
about.
B
G
G
There
might
be
somebody
in
the
call
that
has
some
objections
that
aren't
in
the
issue
yet,
but
I
haven't
seen
any
objections
to
the
idea
of
a
path,
a
hidden
path,
content
type
and
I'm
not
sure
if
there
are
objections
to
to
sort
of
this,
you
know
kind
of
a
layout
change.
A
lot
of
the
discussion
has
been
around
the
specifics
right.
It's
been
about
what
should
it
be
called?
G
What
should
the
sample
content
be,
and
if
somebody,
if
I'm
wrong
about
any
of
those
things
now,
would
be
a
good
time
to
speak
out
I'll.
Just
also
point
out
that
olaf
has
provided
this
slightly
more
updated,
a
screenshot
of
sort
of
a
mock-up
that
would
include
actually
an
image
and
a
slightly
more
styled
version
of
the
of
these
pathless
notes.
C
I'll
I'll
jump
in
first
of
all,
just
viscerally,
I'm
excited
by
the
layout
that
I
see
I'm
like.
Oh
hey,
that's
that
that
looks
good.
So
so
I
I
like
that
idea,
I'm
I'm
surprised!
I
it's
not!
Obviously
why
pathless
notes
and
homepage
layout
are
so
intricate
intrinsically
linked
like
why.
Why
are
they
not
two
separate
issues?
A
I
think
the
only
reason
we
have
them
as
this
together
now
is
like
we
could
create
a
pathless
content
type
called
card
and
put
it
in
core,
but
if
we're
not
using
it
anywhere,
then
it
becomes
confusing
to
people
rather
than
an
educational
tool,
and
if
we
can
give
them
a
real
life
example
of
how
that
could
be
used,
it'll
be
like
okay,
it'll.
It's
there,
you
can
edit
something.
That's
there.
A
You
can
see
it
change,
you'll
understand
how
it
fits
together,
but
if
we
just
put
it
in
core
they'll
be
like,
I
don't
know
what
that
is
or
why
I
should
use
it
and
they
might
ignore
it.
So
the
homepage
is
like
sort
of
the
most
common
use
case
for
pathless
content
on
real
sites.
It
also
could
go
on
any
landing
page.
It
could
go
anywhere
else,
but
we
know
we
have
the
home
page
in
backdrop.
C
Okay,
so
so
bifurcating
to
those
issues,
you
know
I
I
don't
have
any
opinion
about
pathless
nodes
other
than
you
know
not
not
being
against
them.
For
any
reason,
I'm
I'm
strongly
in
favor
of
tutorial
content
and
sort
of
you
know
creating
and
promoting
and
improving,
like,
I
think,
that's
all
just
wonderful
stuff.
So
so
this
is
the
tip
of
the
iceberg
of
like
other
things
like
that.
That
all
sounds
wonderful.
A
I
would
just
say
that's
another
thing
that
I
didn't
mention
in
our
like
list
of
things
we
want
to
solve
is
a
little
a
little
better
way
to
present
instructions,
and
we
haven't
done
this
anywhere
else
in
core
yet.
But
this
is
an
example
where,
if
we're
going
to
put
three
pieces
of
content
here,
we
could
use
the
text
in
the
content
to
be
more
information
heavy
rather
than
like
our
our
pager
post.
Just
says
like
this
is
what
I
am.
It
doesn't
explain.
A
C
Well,
I
I
love
the
idea
of
the
initial
install
being
something
obviously
that
if
you're
experienced,
you
could
just
ditch
it,
but
if
you're
not
experienced-
and
you
don't
know
what
you're
supposed
to
do
next,
you
know
a
little
thing
says:
here's
what
you
should
do
next.
It
kind
of
looks
like
this
and
here's
a
link
to
how
to
do
more
of
this,
and
just
you
know,
having
that
be
more
of
a
of
a
welcoming
path,
seems
like
a
very
positive
thing.
E
E
E
So
there
were,
there
were
some
people
that
thought
that
this
was
a
good
idea,
but
even
the
same
people
thought
that
this
is
a
difficult
thing
to
implement
and
not
only
difficult,
but
it
had
some
other
issues
like
we
needed
to
figure
out
how
to
ship
a
slideshow
library
with
core.
So
this
is
the
things
that
we
were
trying
to
avoid.
E
So
what
I
was
trying
to
say
is
that,
despite
the
fact
that
it
might
have
been
a
good
idea
to
add
a
slide-
and
it
made
better
sense
to
say
you
know
that
slides
are
pageless
content,
the
slider
itself
is
what
you
put
you
used
to
put
the
slides
together,
and
people
would
probably
understand
that
better,
but
it
had
implementation
implications.
So
we
avoided
that
and
that's
why
we
landed
on
these
cards
card
things
and
initially
I
didn't
know
like.
E
I
didn't-
have
good
ideas
about
it,
but
thanks
team
for
putting
that
text
together
and
I
think
it
solves
the
problem.
The
one
thing
that
I
would
like
us
to
add
is
like
point
the
differences,
because,
as
from
an
end
user
point
of
perspective,
like
I
see
three
pieces
of
text
with
a
title
and
then
I
see
a
fourth
one
underneath-
and
I
would
like
the
fourth
one
to
explain
why
it's
not
the
same
as
the
three
top
ones
and
like
it
still
says,
hey.
E
A
I
think
I
think
tim
did
have
an
early
version
of
a
pull
request
that
did
change
the
text
of
the
other
ones,
but
since
we
were
trying
to
figure
out
how
to
get
as
little
change
as
possible
to
get
approval
and
we
mixed
it.
But
I
do,
I
think,
that's
a
good
point
and
I
think
that
you
know
if
we
spend
some
time
on
the
text
of
each
of
these
things.
That
would
be
a
good
improvement.
E
Yes,
so
so
here's
is
what
I
think.
We
all
agree
that
this
is
visually
more
pleasing
than
what
we
had
before.
So
let's
go
ahead
with
that
and
and
tweak
the
text
to
get
it
to
do
what
we
wanted
to
do
to
communicate
the
things
we
want
to
communicate
and
then
we
can
see
what
problems
we've
solved
and
what
problems
are
left
to
be
solved.
These
can
be
separate
issues,
otherwise
we
can
be
discussing
all
those
issues
endlessly.
So
that's
what
I
was
thinking.
E
G
Just
forgot:
can
I
oh,
if
you're
next,
I'm
going
to
say
one
or
two
things
they
they.
We
also
tried
two
posts
on
the
front
page
just
and
that
was
originally
to
show
what
a
view
does
better
than
one
post,
but
then
we
that
was
too
busy.
So
we
pulled
that
back.
But
all
of
you
go
ahead
and
talk.
You've
had
a
lot
to
say
about
this
issue.
A
D
D
How
do
I
do
this
or
I
don't
want
it
at
all
for
the
other
content
types
you
just
say:
okay,
I
delete
it
and
that's
it,
and
here
you
have
to
delete
three
items
or
you
can
remove
the
block,
but
you
have
still
the
content
on
your
content
page
and
then
you're
not
sure
what
do
I
do
with
it?
And
so
it's
it's
not
so
simple
as
before,
and
that's
my
that's.
D
A
A
What
I
was
envisioning-
and
I'm
not
sure
I
wrote
this
in
a
comment
anywhere-
is
that
I
still
want
to
use
the
reference
existing
content
block.
But
I
thought
that
we
could
put
that
somewhere
else
on
this
page
so
that
we
would
have
both
an
example
of
cards
in
a
view
and
an
example
of
a
referenced,
existing
content
block
and
we
could
put
it
somewhere
like
maybe
underneath
the
list
of
posts
or
we
could
create
another
stripe
and
the
more
things
we
can
put
on
this
home
page.
A
The
more
this
homepage
starts
to
look
like
a
real
website
and
it
does
increase
the
complexity
right,
we're
adding
more
things
that
probably
people
aren't
going
to
want,
but
I
do
think
it
also
increases
the
first
impressions
for
people
who
are
evaluating
backdrop,
because
we
now
they
install
it
themselves
and
they're
like
oh,
I
can
see.
This
is
a
real
website,
rather
than
you
know
the
typical
drupal
station,
where
I
see
a
header
and
a
footer,
but
I
don't
actually
see
a
functioning
site
so
yeah.
A
F
F
F
It's
not
bad
that
it's
text
that
has
a
lot
of
text,
but
I
would
like
to
see
more
photographs.
There
should
be
a
photograph
for
each
of
the
three
examples,
and
the
hero
image
should
be
something
so
inviting
it
looks
like
a
real
website,
and
this
is
going
to
be
a
really
powerful
system
to
work
with
the
little
cloud
image
doesn't
do
anything
for
us.
A
E
A
A
Making
it
look
like
a
card,
looks
really
great
one
of
the
reasons
we
haven't
included
images
in
backdrop
core
before
now
is
that
trying
to
figure
out
what
to
do
with
those
files
is
hard
backdrop
treats
files
as
content,
and
we
would
now
be
shipping
files
that
aren't
content
like
they
would
be
in
the
code,
and
so
it's
just
a
I
mean,
there's
no
reason
we
can't
think
about
it
and
figure
it
out
and
do
it
right.
We
just
haven't
done
it
before
so.
A
Chris,
like
the
example
of
the
hero
image
is
something
that
is
done
in
css
in
the
theme.
So
it's
not
content
where
I
think
if
we
had
a
photo
there,
that
was
more
compelling.
It
would
be
content,
so
that
was
just
a
way
to
skirt
that
issue
of
figuring
out.
You
know
how
to
how
to
handle
it,
but
I
I
think
that
it
makes
a
big
difference.
I
think
it's
a
worthwhile
problem.
C
To
solve,
I
think
I
think
it's
worthwhile
in
kind
of
a
long-term
thing.
Not
anything
that's
like
gets
solved
super
fast,
but,
but
I
feel
like
this
is
something
that
the
drupal
always
missed
is
that
for
a
content
management
system,
it
sucks
at
managing
content
and
it'd,
be
it'd,
be
good
for
us
to
sort
of
like
not
not
just
push
that
off
because
there's
you
know
like
solve
that
problem,
content's
important,
you
should
be
able
to
bring
it
in
and
get
rid
of
it.
E
The
plan
is
to
make
the
rest
as
that,
it's
just
it
was
a
quick
mockup,
basically
and
all
that
without
without
wanting
to
dismiss
what
you
just
said
about
the
complexity,
I
realized
that
that
is
what
it
is,
but
user
user
case
user
studies
have
shown
that
it's
easier
for
people
to
remove
things
than
to
add
them
and
by
a
like
a
big
difference
there.
So
it's
easier
to
find
and
delete
things
then
try
to
figure
out
how
to
do
things
or
what
they
do.
E
Yeah
delete
everything,
wipe
everything
it's
like
whatever
clean,
clean,
stat
or
whatever,
and-
and
this
is
very
trivial
and
we
can
go
on
about
bike
shading
about
the
text
that
will
go
in
and
the
the
images
that
will
go
in
in
the
in
the
actual
issue
queue.
But
I
would
like
everyone
to
to
have
a
little
bit
of
a
homework
of
what
the
industry
calls.
These
things
like
ask
web
developers
or
people.
E
That's
that
what
they
call
these
things,
because
at
least
the
the
government,
the
people
in
the
government,
the
content
editors
in
in
wcms,
which
I
have
experience
with.
They
call
these
things
styles
and
they
wouldn't
understand
cards,
but
people
might
be
calling
it
anything.
So,
instead
of
having
opinionated
think
of
what
it
is,
I
would
like
us
to
know
what
the
industry
calls
these
things
more
often,
so
that
it's
not
confusing.
F
E
Yes,
is
it
a
promo
tile
or
a
promo
box,
or
a
promo
whatever
or
front
page
card
or
whatever
they
call
it,
but
yeah?
We
need
to
figure
it
out.
I
don't
want
us
to
do
that
now,
but
we
can
like
said,
but,
but
do
we
do?
We
at
least
have
a
sort
of,
like
general
consensus
of
on
the
fact
that
this
is
heading
to
a
place
where
we
think
it's
better
than
what
we
have
now
and
we
should
proceed
with
that.
F
And
I
think
I
agree
with
you
that
it's
easier
for
somebody
to
click
on
something
and
say
I
want
to
replace
this
image
or
I
want
to
replace
this
text
or
I
want
to
delete
this
image
and
text
it's
easier
to
click
on
something
to
get
rid
of
it
than
to
figure
out
how
to
put
up
a
third
image
on
something
or
second
image
on
some
layout
that
they
don't
understand.
Yet.
B
F
D
D
D
A
A
A
I
mean
it's
not
the
same
as
giving
them
a
tool
that
makes
backdrop
seem
like
it's
broken.
It's
like
a
you
know,
they're
like
okay.
Well,
I
can
see
that
somehow
I
can
edit
this,
but
I
don't
know,
but
if
it's
like
here
edit
this
and
they
click
it,
they're,
like
oh
backed
up,
doesn't
work.
I
think
it's
a
more
serious
problem.
E
There's
ways
around
it:
you
can
say
if
you
log
in
and
you
have
the
right
permissions
you
will
be
able
to
edit
and
delete
them
and
or
buttons
will
appear
that
will
allow
you
to
to
edit
and
delete
it
or
things
like
that,
but
we
can
fix
it.
It's
not
like
these
are
trivial
things
that
should
be
relatively.
A
This
also
might
be
solved
by
another
problem
where,
right
now,
our
contextual
links
are
not
discoverable
like
you
have
to
know.
They
exist
and
move
your
mouse
over
the
right
place
in
order
for
them
to
appear,
but
if
those
were
like
a
little
edit
icon,
that
was
always
visible,
people
would
know
they
were
there
and
they
could
discover
the
fact
that
there
is
an
edited
and
delete
link
and
those
links
are
aware
of
your
permissions.
What
you're
allowed
to
do
so?
There
could
be
like
some
other
things
we
can
fix.
E
Yeah,
I
think,
I'm
not
sure
if
I
filed
a
an
issue
in
our
queue
for
it,
but
there
are
issues
for
that
already
in
drupal
land
and
I
think,
there's
a
module
where
you
click
a
single
button
at
the
top
of
the
the
admin
bar
and
then
everything
that's
editable
gets
one
such
icon.
So
you
know
that
these
are
the
things
that
you
generated
or
tweaked,
but
yeah
yeah.
These
are
all
nice
follow-ups.
We
can.
We
can
follow
up
with
that.
G
I'm
gonna
jump
in
quick
and
one
thing
I'm
hearing
a
little
bit,
though
some
criticism
that
there's
too
much
text
and
too
much
stuff
and
then
also
like
how
can
we
add
more
clarity
and
add
more
stuff?
I
don't
know
that
confuses
me
a
little
bit
like
how
we're
gonna
do
both
or
right
I
mean
I'm
not
sure
we
can't
so
we
might
have
to
make
a
choice.
G
Sure,
let
me
really
quickly
do
something
else,
though
I
did
this
is
I
started
playing
around
with
sarvashri
with
softaculous,
and
I
was
excited
to
actually
see
that
how
backdrop
is
presented
in
the
interface
and
one
of
the
things
I
did
is
went
to
the
demo
that
they
provide,
and
I
thought
my
initial
reaction
was-
and
it's
just
not
really
exciting.
If
I'm,
if
I'm
on
so
calculus
and
I
hit
demo,
this
is
kind
of
boring,
but
then
I
looked
at
some
of
our
competitors
and
these.
These
are
this.
These.
G
This
is
triple
eight.
This
is
the
way
you
click
when
you
click
on
the
demo
button
on
softaculous.
That's
what
you
get!
Here's
wordpress,
if
you
click
on
the
demo
button
on
wordpress,
if
you
click
on
the
demo
button
on
joomla,
that's
what
you
get
so
we're
actually
not
doing
too
bad
compared
to
some
of
our
competitors
in
terms
of
just
attractiveness
of
the
front
page
like.
G
C
D
G
Well,
survivor,
I
I
think
there's
some
I
mean
I
don't
disagree
with
you,
but
I
think
there's
some
debate
about
whether
or
not
we
want
it
to
look
like
a
great
looking
web
page
or
or
we
want
to
just
provide
the
raw
framework
of
a
tool.
So
I
or
does
any.
Does
anybody
disagree
that
we
want
this
to
look
like
a
web
page?
A
A
Gonna
choose
content
to
make
it
look
real.
We
can't
make
it
look
so
specific
to
one
audience
that
another
audience
says.
That's
not
for
me.
That's
like
why
we
chose
this
like
blue
image.
It
doesn't
have
people
in
it.
It
doesn't
show
anything
related
to
anything
else,
so
it's
completely
non-offensive
and
yet
not
compelling.
At
the
same
time,.
E
Well,
I
need,
I
can
remind
you
guys
that
the
welcome
to
bankrupt
thing,
which
might
not
be
so
welcoming-
and
I
know
that
this
is
adding
text-
it's
basically
a
block
and
that's
the
title
right.
The
block
can
have
a
text
that
say
hey,
you
can
change
the
background.
If
you
want
all
the
text,
that's
it.
E
F
I
like
that
idea,
I
don't
think
we
have
too
much
text,
it's
just
that
the
text
needs
to
be
functional.
It
needs
to
describe
what
people
can
do
with
this.
That
you
know
I
I
have
this
text
on.
This
block
means
that
this
is
what's
happening.
Text
on
this
next
block
means
that
this
is
what
this
can
do.
This
is
how
it
can
work
for
you,
here's
how
to
change
it.
F
I
think
you
could
have
more
text
if
the
text
is
educational
and
then
I
really
like
the
idea
of
the
link
to
the
documentation,
click
here,
to
learn,
to
learn
all
about
backdraw
and
and
then
learn
how
to
replace
these
photographs
with
your
own
photographs
that
sort
of
thing,
so
it
really
gives
people
a
chance
to
click
on
something
and
see
what
it
will
do,
click
on
something
and
change
it,
how
they
want
to
change
it,
it
gets
them
invited
to
do
something
with
it.
The
original
just
doesn't
give
anybody
any
inspiration.
F
E
Yeah,
so
actually
that's
a
good
point
and
and
the
combination
of
what
service
we
just
said
and
what
team
showed
the
before
about
drupal
having
a
link
to
the
user
guide.
Instead
of
having
too
much
text
we
can
have,
which
is
preferable
because
then
see
yeah.
I
know
what
you're
saying
then
it's
like
great
minds
exactly.
E
Yes,
so
the
the
the
another
bad
thing
from
a
developer
perspective,
point
of
view
and
a
translator
point
of
view
is
that
if
you
have
too
much
text,
then
this
needs
to
be
in
a
translatable
string
thing
that
works
for
every
language.
So
we
need
to
minimize
it
anyway.
So
another
thing
is
that
we
we
should
keep
these
things
to
a
minimum
and
say
hey.
A
And
the
same
thing
about
the
layout
like
I
feel
like
this
is
the
kind
of
thing
we
could
really
make
a
lot
of
use
of,
because
you're
right
I
mean
you
log
into
the
website.
You
want
to
do
something.
It
would
be
great
if
we
had
a
page
dedicated
to
that
task.
Like
that.
First
instinct
of
the
thing
you
want
to
change
when
you
install
backdrop-
and
we
might
not
have
those
pages-
and
that
would
be
a
great
reminder
to
us-
that
we
need
to
document
all
that
stuff.
So.
E
But
it
has
worked
very
nicely
during
the
last
dev
cycle
for
us
like
there
were
people
that
built
it
we're
building
on
top
of
other
people's
tool
requests
and
at
the
end,
we
because
we
have
the
pull
request
sandboxes,
we
got
to
test
every
pull
request
and
decide
which
one
was
best
and
improve
it.
So
everyone
that
has
ideas
and
can
actually
file
pull
requests.
Let's
actually
file
pull
requests,
get
people
to
test
it
and
see
which
one
they
like
better.
So
I
liked.
A
G
E
D
D
A
E
G
E
A
D
A
Yeah,
no,
I
wasn't
recommending
that
we
translate
it
differently.
I
was
just
thinking
when
we
create
the
node.
If
you
had
installed
the
site
in
german,
the
node,
the
the
first
node
that
was
created
would
be
in
german
and
there
would
be
no
english
version.
It
would
just
be
only
in
german,
and
so
then
that
way.
A
F
G
Yeah
anyways,
I
I
think
we
need
to
stop
that.
We're
we've
got
five
minutes.
You
know
cut
that
discussion
short.
We
can
talk
more
about
it
later.
We've
only
got
five
minutes
left
in
the
meeting,
and
I
would
like
to
talk
about
just
next
steps
because
yeah
I
didn't
expect
to
answer
any
questions
today.
I
think
the
discussion
has
kind
of
went
the
way
I
would
have
hoped,
which
is
just.
We
got
a
bunch
of
ideas
out
there.
G
So
what
is
sort
of
the
next
step-
and
this
is
a
little
bit
unusual,
because
a
lot
of
these
things
could
be
broken
out
into
a
bunch
of
issues,
but
I
don't
know
how
dependent
they
are
on
each
other.
Like
you
know,
we
could
break
out
the
the
pathless
nodes
completely
from
any
of
this
display
stuff
as
a
separate
pr,
but
I
don't
know
if
that's
a
good
idea.
G
F
I
have
another
suggestion
too,
and
that
is
as
we
are
giving
them
backdrop.
We
could
also
give
them
a
fully
fleshed
out
little
website.
Like
tim,
and
I
were
working
on.
You
know
this
farmers
market
website
give
them
a
website,
that's
been
built
so
that
they
can
load
that
one
and
see
how
it's
all
put
together
and
that
website
could
be
deeply
explaining
how
it
was
made
and
that
could
that
could
combine
with
the
documentation
go
along
with
the
documentation
of
a
website.
E
G
I
haven't
yet
I
I
really
we
have
three
minutes
left.
I
want
to
focus
on
next
steps.
What
what
what
happens?
Now
I
mean
I,
you
know
one
vision
would
be
to
say:
let's
look
at
all
of
this
for
the
next
release,
1.21
and
then
you
know
sort
of
trying
to
coordinate
it
in
some
kind
of
a
like.
I
say
initiative
or
continue.
You
know.
Maybe
we
continue
talking
about
these
in
the
design
meetings.
D
G
D
Okay,
because
I
think
we
are
nearly
very
near
exactly-
we
don't
need
much
more
and
if
we
on
the
way
doing
this,
it
polishing
now
the
design
and
so
on
and
the
texts
and
if
we
run
then
identify
a
thing
which
is
completely
stands
on
his
own
feet
has
to
stand
on
his
own
feet.
Then
we
could
do
that,
but
otherwise
I
wouldn't
split
it
up
now.
G
G
It
could
be,
but
should
it
be
right,
should
we
be
making
these
decisions
independently?
Where
should
we
be
trying
to
come
up
with
a
final
layout
and
then
make
everything
work
together?
That's
sort
of
my
question
is:
do
we
want
to
break
it
apart
so
much
that
we're
making
a
bunch
of
independent
decisions
that
don't
necessarily
die
together.
E
This
is
becoming
way,
scope
creepy
after
that,
because
the
the
issue
we
can
start
a
separate
issue,
but
the
the
title
of
this
issue
specifically
is
provide
a
new
hidden
path,
content
type,
which
is
what
we're
doing
providing
that
plus
some
styling
for
it,
which
is
basically
the
gray
area.
That's
all
that
we're
adding
and
that's
what
I
think
we
should
keep
it
focused
on.
Anything
else
should
be
separate
issues,
follow-ups
or
separate
issues.
G
I
will
be
pretty
shocked
if
there
is
an
additional
creep
and
this
discussion
goes
on,
so
I
I
think
the
idea
that
this
is
clearly
neatly
packaged
already,
and
we
just
need
to
finish
it.
It's
deceptive,
because
there's
so
many
unanswered
questions
about
exactly
how
the
links
are
going
to
work,
and
I
don't
know
it
just
feels
to
me
like
it's
going
to
start
to
creep
but
we'll
see
okay,
where
it's
four
o'clock
or
it's
in
in
minnesota.
It's
four
o'clock:
it's
it's
on
the
hour.
B
A
E
Yeah
and
the
way
that
you
summarize
it
theme
is
like
really
helpful.
So
if,
instead
of
putting
it
in
playing
comments,
maybe
you
can
add
your
comments
or
anyone
actually
add
it
on
the
top.
Like
the
the
first
comment
of
the
issue,
so
we
have
the
summary
of
what
was
discussed
over
time
and
what
we're
heading
at
currently.
So
that's
helpful,
usually.
G
E
G
E
It
was
so
okay,
one
thing
until
next
time.
One
thing
for
next
time,
just
just
for
the
next
time
thing,
because
we
consumed
the
entire
meeting
for
this
specific
issue
is
how
we
clarify
sorry
how
we
bring
the
enabling
the
telemetry
into
the
installer
thing
without
screwing
people
away,
but
that's
for
the
in
two
weeks
from
now
good.