►
From YouTube: Backdrop Design - 2021/06/17
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
C
June
17th
2021-
and
this
is
our
weekly
design
meeting-
apologies
in
advance.
If
there's
any
strange
noises,
there's
road
construction
happening
outside
the
window
and
they
just
started
the
road
roller.
So
hopefully,
that's
not
bothering
you
guys
too
much
before
we
get
started
on
design
issues.
I'd
like
to
have
us
go
around
and
introduce
ourselves.
So
if
you
want
to
share
what
your
name
is
where
you're
from
and
if
there's
anything
exciting
going
on,
you
want
to
share
with
dr
community.
That
is
also
welcome.
C
I
will
start
I
am
jen
lampton
joining
us
from
oakland
california
and
I'm
very
excited
about
all
of
the
work.
I
did
on
the
backdrop
events
website
this
morning,
which
I
might
talk
about
in
the
next
meeting,
how
about
tim.
A
Okay,
my
name
is
tim
erickson,
saint
paul
tim,
I'm
in
deerwood
minnesota.
I
am
back
outside
for
our
meetings.
Tell
me
if
this
is
too
distracting.
Last
summer
I
was
not
as
a
practice
I
just
worked
at
my
laptop.
It
was
really
easy
to
sit
outside
over
the
winter.
I
tethered
myself
to
two
external
monitors
and
now
it's
a
little
harder
to
just
move
outside,
but
I
decided
today
was
a
good
perfect
day
for
it.
So
anyways,
that's.
B
It
robert
I'm
robert
lang,
bug
folder
on
the
internet,
I'm
in
altadena
california.
Lately
I've
been
spending
a
lot
of
time
on
documentation.
D
Hi,
my
name
is
greg,
I'm
usually
in
australia
now
in
greece,
yeah
just
taking
in
to
see
what
design
tasks
we
have
and
how
I
can
help.
I
haven't
worked
on
any
design
issues
recently
so
eager
to
do
that
again.
C
C
I'm
in
church-
I
guess
so.
Our
normal
weekly
agenda
has
a
section
for
theme,
initiative
update
and
though
the
theme
initiative
is
officially
wrapped,
we
still
have
a
handful
of
issues
that
might
be
useful
to
talk
about,
but
maybe
we
should
just
move
them
into
some
like
other
category,
just
maybe
like
product
improvement
or
something
like
that.
C
I
think
we
have
a
bunch
of
changes
to
project
module
for
package
signing
going
in
soon,
so
it
will
be
nice
if
we
could
combine
and
deploy
with
that
with
something
that
might
help
this.
I
don't
know
if
that's
gonna
help
motivate
people
ahem
myself
to
try
and
get
some
work
done
on
that
anytime
soon.
But
it
is
something
I'm
thinking
about,
and
then
we
also
have
a
style
guide
that
we
thought
we
could
use
to
help
determine
whether
a
theme
could
become
recommended
or
not.
C
We
can
recommend
that
module
or
theme
will
show
up
on
the
themes
page.
So
there
is
a
list
of
items
there
that
the
style
guide
should
contain
in
order
to
make
sure
that
that
theme
meets
all
the
requirements
that
we
want
for
a
recommended
module
and
I
don't
know
like
we
could
go
way
overboard
on
that
and
maybe
not
require
all
of
them,
because
the
style
guide
could
contain
anything
but
there's
a
good
sort
of
starting
point
there.
C
So
if
anyone
wants
to
work
on
the
style
guide,
that's
a
contrib
module
and
a
little
easier
to
fuss
around
with
than
core
itself,
and
then
we
have
this
issue.
I
think
I'm
going
to
remove
this
from
the
agenda
after
today,
but
that
was
how
do
we
make
it
easier
for
people
to
try
a
theme
and
right
now.
The
only
way
you
can
do
that
is
to
actually
install
it
on
a
website.
C
If
you
don't
want
to
install
it
on
your
own
website,
you
can
install
it
on
a
demo
website,
but
most
of
our
demo
sandboxes
have
no
content
that
doesn't
necessarily
give
you
a
feeling
for
what
that
theme
would
look
like.
We
talked
about
having
an
example
site
full
of
content
that
people
could
just
go
flip
themes
around
on,
and
I
think
luke
made
a
good
start
on
that.
Where
there's
a
bunch
of
themes,
you
can
see
switcher
that
write-up
should
be
in
his
blog
post
on
that,
but.
D
I
had
an
idea
on
that
I
was,
I
haven't,
touched
simplytestme.org
or
simplytest.me
in
a
while,
and
I
review
sorry,
I
visited
it
this
week
and
I
remembered
that
you
could
generate
links
that
could
spin
the
sides
automatically
with
the
modules
or
things
that
you
pointed
all
the
patches.
If
we
can
get
our
demo
sites
to
do
that
with
things,
it
would
be
a
great
idea
to
have
a
try
this
before
you
install
it
link
on
things
that
would
actually
spin
the
same.
D
The
demo
side
install
the
theme
and
set
it
as
I
don't
know,
the
default
or
whatever
that's
another
idea,
but
that
belongs
in
the
court.
Queue
I'll,
probably
write
something
create
a
new
issue
for
it.
D
Oh
yeah,
you're
right
that
information
is
actually
being
pulled
from
bid.org,
so
it
should
go
there
and
the
link
should
be
there.
Yeah,
yeah
you're
right
indeed,.
C
Yeah-
and
I
think
infrastructure-wise
like
that
could
be
part
of
tugboat,
like
maybe
tugboat-
has
already
has
a
command.
That
could
do
something
like
that,
because
it
doesn't
talk
about
run
through.
C
Solution
now
too,
I
don't,
I
don't
know
how
tightly
they're
integrated,
but
it
seems
like
we're
on
tugboat
they're
on
tugboat.
They
have
that
feature
should
be
pretty
easy
to
set
up
for
us,
and
so
it
could
just
be
part
of
the
tugboat
module
or.
D
D
I
think
that
they're
moving
to
version
two,
whatever
that
is
and
they're
having
issues
with
the
current
one,
and
I
can
confirm
that
because
I
used
it
last
week
and
it's
been
my
experience
in
the
past
one
and
a
half
year,
but
now
they're
moving
to
version
two
which
uses
composer,
which
we
don't,
I
think
so
yeah
might
be
a
little
bit
different.
A
So
can
I
interject
that
luke
and
I
had
slightly
different
visions
about
what
this
sort
of
demo
site
would
be.
I
think
his
was
a
little
bit
more
ambitious
than
mine,
but
I
just
posted
in
in
zula
the
the
the
theme
switcher,
the
site
I
made,
which
is
a
functional
theme,
tester
site,
and
I
you
know
I
don't
know
if
there's
a
way
we
could
better,
promote
or
use
that,
or
you
know
people
think
if
other
people
think
it's
useful
to
me.
It's
already
useful.
A
I
had
ideas
about
how
to
make
it
better.
I
haven't
had
time
to
work
on
them,
but
there
is
in
the
footer.
You
can
switch
between
themes.
I
have
some
sample
content.
The
content
is
pretty
lame.
It's
good!
It's
okay,
but
like
I'd
like
to
know
like
what
more
would
need
to
happen
for
this
to
be
useful
part
of
it,
it
was
figuring
out
like
what
elements
to
include
that
are.
This
is
a
little
bit
like
the
testing
it
like.
A
Right
well
sure,
right
now,
it's
not
I
mean
yes,
it's
not
set
up
that
you
can
actually
change
the
content.
It's
it's!
You
can
try
it
out
with
a
fixed
set
of
content,
so
an
anonymous
user
right
now
can
go
to
the
footer
and
can
change
the
theme
and
they
can
browse
around
the
site,
the
current
site,
but
they
can't
edit
it
that
would
be
figuring
out
how
to
do
that
sort
of
safely
and
is
another
issue.
So
so
a
tugboat
version
is
better.
I'm
not
disputing
that.
D
Yeah,
I
think
that
phase
one
would
be
to
link
to
that
site,
as
is
now
from
somewherembi.org.
Maybe
the
theme
spades
and
phase
two
could
be
moving
it
into
a
backdrop,
cms.org
domain
yeah
and
then
phase
three
could
be
trying
to
automate
it.
Then
you
know,
you
know,
move
it
to
tagboat,
but-
and
this
is
where
see
how
we
we
mentioned
in
the
previous
weeks-
that
we
are
unblocked
sort
of
for
the
recipes.
D
If
we
can
get
even
like
a.
What
do
you
call
it
demo
content
module
which
actually
theme
demo
content
module,
which
actually
installs
all
that
all
that
all
the
content
that
you've
created,
then
it
would
help
with
the
tugboat
intonation
but
yeah.
This
is
a
good
start
and
as
as
is
like
it's
it's
better
than
what
we
have
now,
which
is
nothing.
A
Besides
going
all
the
way
I
mean
like
doing,
the
full
tugboat
thing
would
be
best.
Maybe
we
just
want
to
you
know,
focus
on
that
john.
What
do
you
think
is
this?
Is
this
something
that
you
think
we
can
make
use
of,
or
should
we
be
holding
out
for
them.
C
I'd
be
a
little
concerned,
I
mean,
I
think
it's
it
is
useful.
It
shows
you
right
now
that
most
of
these
things
aren't
good
enough
to
be
featured.
F
C
But
that
would
be
my
concern
for
putting
it
like
directly
on
backdrop.
Cms.Org
is
that
it's
not
a
good
sales
tool
yet,
but
I
think
that.
C
Good
tool
for
like
helping
me
decide
which
one
of
these
things
I
would
want
to
use
like
how
close
is
it
to
my
design,
intent
like
how
much
work
do
I
have
to
do,
which
is
probably
why
tim
you're
finding
it
useful,
so
I
think
that
there
might
be
like.
Maybe
we
put
it
in
the
forum
where
people.
C
It
you
could
even
have
a
special
topic
for
it
if
you
wanted
and
then
that
way,
if
people
have
themes
they
want
to
see,
you
have
sort
of
a
place.
You
could
talk
about
it.
I
don't
know
how
many
things
you're
planning
on
putting
on
there.
If
someone
asked
for
one
if
you'd
add
one
or
not
but
yeah,
I
think
that
way.
C
If
you
can
solve
this
one
thing
that
I
saw
on
tim's
site
and
we
can
make
you
a
featured
theme
and
then
you'd
become
exactly
the
same
thing
on
like
an
official
site
and
if
we
can
get
like
10
of
those
ready,
we
could
even
leave
your
site
as
the
official
site
and
just
have
them
all
be
there,
and
then
you
can
go.
Maybe
you
log
in
to
see
the
unofficial
themes
or
something
like
that.
Yeah.
D
I
think
this
was
one
of
the
subtasks
of
the
initiative
to
figure
out
a
list
of
what
what
did
they
call
them
not
recommended,
but
the
list
of
themes
approved
things
or
something
like
that
with
which
then
like
all
right,
we'll
we'll
get
like
20
of
them
say
here,
but
in
the
future
this
will
need
to
be
done
again.
So
this
is
overhead,
and
this
is
where
the
the
tagboard
demos
would
come
would
become
helpful
because
we
wouldn't
have
to
manage
that
curated.
I
think
it
was
a
list
of
things.
D
Of
course,
there's
danger
that
people
will
try
a
thing
that
is
basically
sorry
crap,
but
they
can
try
another
one.
It's
still
going
to
be
as
easy.
You
know
as
spinning
a
attack
boat
demo
right,
but
I
think
that
we
should
move
these
two.
How
are
you
managing
this
currently?
Do
you
have
a
repo
for
it
in
github
team.
A
Or
right
right
now
I
have
a
repo,
but
it's
a
it's
a
private.
This
is
on
my
simplo
site,
so
I
would
I
mean
to
be
clear.
I
would
be
happy
to
turn
this
site
if
it
were
helpful
over
to
backdrop.org,
but
I
understand
what
jen
was
saying
the
I
think
the
best
solution
might
be
for
now.
For
I
like
the
idea
of
just
making
a
forum
post
like
with
this
in
the
subject
line,
then
people
can
give
feedback.
They
can
comment
on
it.
We
can
get
a
discussion
going
about
it.
A
It
can
be
a
private
thing
right,
it's
informal,
it's
it's
something!
I'm
just
posting
and
if,
at
any
point
you
know
people
feel
like
it's
something
that
you
know
the
project
could
use
in
a
more
official
way.
I'm
happy
with
that,
but
I
think
jen's
right
it's
a
little
bit.
It's
not
really
quite
at
that
stage
where
we
probably
would
want
to
make
it
a
backdrop
thing
does
that
make
sense.
D
I
I
really
like
how
you
have
the
faq
section,
which
says
which
modules
have
been
used
to
build
this.
My
only
comment
is
that,
in
order
like
we
call
it
the
theme
display
or
whatever
going
to
want
to
call
it,
but
you
don't
get
actually
to
switch
things
unless
you
click
on
one
of
the
nodes
that
are
in
the
home
page.
So,
basically,
if
you
are
either
in
home,
faq
contact
us
you're,
trapped
without
a
theme,
selector
blog,
I'm.
A
There's
no
doubt
that
it
needs
improvement,
but
so
what
I'm
here
so
so
far
this
has
been
up
for
six
months
and
but
I
haven't
like
shared
it
outside
of
like
this,
these
meetings.
So
maybe
it's
time
to
just
do
what
I
just
said:
create
a
forum
post
share
it.
Let
people
use
it
informally,
give
feedback,
and
then
that
might
help
us
inform
you
know,
figure
out
how
useful
it
is
and
or
how
to
make
it
better.
D
Yeah,
for
example,
the
recent
content
block
in
certain
themes
renders
empty
empty
cells
on
the
on
the
table
where
they
were
supposed
to
be
links
for
people
that
have
permission
to
do
whatever
they
want
to
do
with
that
content,
but
set
in
others.
They
work
perfectly.
So
we
can
tweak
things
like
that,
either
on
that
one
or
in
each
individual
thing
like
fix
it.
If
it's
a
theme
issue
yeah.
A
D
C
C
Closer
to
the
window
and
farther
away
anyway,
the
that
was
the
end
of
the
theme
of
initiative
related
stuff
on
the
agenda.
I
think
we've
reached
a
good,
suitable,
short-term
solution
with
putting
stuff
in
the
form,
so
I'm
gonna
remove
that
from
the
agenda
and
we
won't
talk
about
it
in
two
weeks.
C
But
hopefully
conversation
will
continue
in
the
forum
and
if
we
need
something
back
in
the
agenda,
we
can
edit
okay,
I
don't
have
any
design
related
stuff
for
backdrop,
cms.org
that
we
need
to
address
and
there's
a
handful
of
issues
in
the
queue
of
course,
but
nothing
on
the
agenda.
For
today,
product
itself,
we
have
a
section
on
usability.
C
We
haven't
updated
this
in
a
while.
There
are
a
lot
more
recent
usability
issues.
I
know
greg
probably
has
50
of
them
right.
D
I
have
a
list
of
four
or
five
of
them
that
I
can
bring
up
so
that
people
that
people
that
are
interested
in
ux
can
start
reviewing,
because
some
of
them
are
in
like
they
actually
have
pull
requests,
and
maybe
they
need
feedback.
So
so
first
one
is
issue
3293,
which
is
tagged
as
ux.
It's
not
designed
it's
ux,
but
also
design
the
exposed
file,
name
filter
for
media
library,
dialogue,
which
we
are
also
mentioning
in
the
weekly,
the
that
meeting
yeah.
So
the
state
of
it
is
now.
D
We
had
some
feedback
about
the
the
fact
that
there's
still
two
forms
rendered,
but
we
are
really
close
with
that.
What
we
need
is
people,
testing
it
and
writing
feedback
see
again,
which
issue
that's
three,
two,
nine
three.
D
That
one
is
is
marked
as
a
task,
which
means
that
it
can
go
in
any
version
in
any
bug,
fixed
version
and
not
necessarily
wait
until
the
120,
which
is
for
september,
then
the
other
one
that
is
more
recent
and
help
do
worked
on.
It
is
5095
which
is
about,
oh
actually,
that
one
is
fixed.
It's
committed.
D
What
do
we
have
do?
We
need
a
change
record.
Oh
yeah,
all
right
cool,
that's
that
was
just
the
task
to
measure
back
into
the
patch
yeah
ignore
this.
This
has
actually
been
fixed,
yeah.
All
right,
then,
moving
on
there's
issue,
four
five
double
zero,
which
is
automatically
clear
caches
when
making
changes
to
who
can
register
accounts.
D
And
this
is
one
of
the
issues
actually
that
we
had
new
people
coming
joining
the
issue
queue
and
they
suggested
that
they
would
like
to
work.
They
implied
that
they
would
want
to
start
working
on
it,
not
necessarily
code
wise,
but
maybe
reviewing
it.
That
was
six
days
ago,
but
yeah.
For
starters,
it
would
be
nice
to
get
someone
to
to
just
confirm
that
this
is
an
issue
for
them
as
well
and
ideas
on
how
we
could
sort
it,
because
it
doesn't
have
a
pull
request
or
anything,
maybe
I'll,
add
the
needs
feedback.
D
And
I
just
added
that
needs
more
feedback,
so
basically
in
in
a
few
words,
if
you,
if
you
change
the
who,
can
register
user
account
settings
and
you
save
the
form,
this
is
not
reflected
straight
away
and
then
it
can
lead
to
weird
404s
or
access
denied
errors
with
the
login
form.
D
And
I
understand
that
this
is
not
something
that
people
will
be
changing,
often
like
they
will
most
likely
configure
it
once
or
twice
over
the
course
of
a
you
know,
lifetime
of
a
site.
So
I
don't
think
that
clearing
cases
is
that's
a
bad
thing
like
those
one
or
two
things
so
that
things
work
out
of
the
box
then
another
one
that
I
have
is
is
that
one
of
mine
yep?
D
That's
the
one,
that's
four
five,
eight
five
and
that's
a
a
request
for
a
feature
request
for
providing
a
report
page
that
lists
all
paths
that
have
been
configured
in
different
fields
of
thing.
Who
was?
It
was
anyways.
It
came
as
a
request
from
another
issue.
It
was
sitting
there
for
a
while.
So
I
just
I
filed
the
pull
request.
D
I
think
that
the
last
comment
from
nate
was
that
you
would
like
to
make
this
extend
extensible
by
other
modules
and
the
way
it's
implemented
now
is
if
your
module
uses
the
storage
system.
Like
the
backdrop
storage
system,
it
uses
one
of
the
file
systems
that
are
specified.
It
should
be
added
there,
but
I
don't
know
how
a
module
would
like
the
only.
The
only
way
that
I
can
think
of
is
that
the
storage
systems
are
being
accessed.
It
said
it
is
via
cdns
and
this
will
not
provide
local
parts.
I.
D
D
D
And
then
the
next
big
one
is
the
three
one:
five
seven,
which
is
a
safe
draft
module
in
core.
D
Does
anyone
else
remember
off
the
top
of
the
head?
If
the
issue
that
was
splitting
the
the
help
text
for
the
the
options
for
the
publishing
options
got
merged,
no
I'll
try
to
find
it.
So,
basically,
in
order
to
sort
of
like
start
with
this
issue,
three
one,
five,
seven
from
a
clinton
state.
We
need
to
fix
that
other
timing
task,
which
was
pretty
close
to
completion
I'll,
try
and
find
out.
B
D
So
this
one
is
pr
ready
to
be
committed
so
that
basically
this
needs
core
committer
eyes,
and
last
comments
were
two
to
three
weeks
ago.
C
C
Yeah,
I
think
I
think
they
just
status
just
well.
He
added
the
needs
feedback.
Okay,
that
was
for
me,
okay.
I
will
remove
that
and
add.
C
D
To
remove
the
field
set
that
we've
added
around
the
form,
so
that
so
I
think
that
that's
the
last
meet
that
was
yeah
all
right,
cool
that
shouldn't
take
very
long.
D
D
I'll
quickly
see
if
there's
any
issues
tagged
with
design
in
the
queue
there
should
be
quite
a
few
of
them.
There's
one
where
we
were
discussing,
whether
to
add
an
icon
font
to.
D
D
So
so,
basically
the
way
that
it
so
this
this
has
to
do
with
the
consolidated
updates
page
that
we
introduced
in
the
last
release
119
and
basically,
if
you
tick
the
checkbox,
where
you
disable
or
enable
the
manual
disable
the
automatic
updates
for
core,
then
that
bit
gets
split
into
a
separate
table
on
the
same
page.
D
Yeah
and
then
related
to
that
now
that
I
saw
the
more
listing,
I'm
gonna
try
to
find
the
yes.
So
it's
the
very
next
one
50
90,
which
is
consider
replacing
the
more
or
less
toggle
legs
with
details
element,
that's
a
good
one
as
well,
and
it
works
pretty
well.
D
C
This
is
the
more
or
less
toggle.
Yes,.
D
D
No,
it
didn't
because
so
so
we
had
a
debate
there,
because
that
issue
started
as
a
replace
field
sets
with
details,
which
we
said
we
are
not
going
to
do,
because
it's
going
to
cause
breakages
yeah,
I'm
not
sure
if
it's
worth
it
revisiting
it
now,
where
there's
better
browser
support,
but
yeah
that
could
be
another.
You
know.
C
And
mark
the
other
one
as
duplicate,
and
if
that,
if
the
previous
one
was
like
replace
field
sets,
is
too
crazy
because
people
are
focused
on
replacing
field
sets.
We
might
use
this
one
and,
if
you
like,
add
details,
element
replace
this
more
or
less
toggle
and
then
now
details
is
in
core
and
we
can
revisit
the
field
set
replacement
later.
D
D
C
It's
not
actually
like,
there's
no
input
involved
in
it.
It's
just
a
display
of
information.
So
that's
the
same
thing
like
a
container
element
right
which
so
it's
the
same
thing
like
if
you
or
a
help
element
like
you.
C
To
forms
when
you
have
stuff
on
a
form,
but
it's
just
a
renderable
array
and
you
can
use
it
on
not
a
form,
unlike
a
like
input
field,
which
you
can't
use
on,
not
a
form,
so
I
think
it's
the
same
like
do
the
same
thing
in
court
with,
like
a
theme,
function
that
outputs
stuff
and
then
it's
just
where
you
put
where
you
put
it.
Is
it
a
pound,
type
or
a
pound
theme,
and
it
works
the
same
way.
C
So
I
think
I
think
the
what
the
task
we
do
on
the
back
end
is
going
to
be
the
same,
regardless
of
whether
we
call
it
a
form
element
or
a
render
element.
C
D
Yeah,
it
could
be
you,
it
might
be
easier
to
find
it
if
you
limit
the
sets
by
2.x
things
that
we
added
to
two
point,
something
as
a
milestone.
D
D
Yeah
and
actually
indie
godzilla
has
provided
a
pull
request
for
it.
D
Which
one
you
tried
to
you.
A
A
A
Okay,
are
we
done
with
that
issue?
Are
we
looking
for
more
issues.
D
A
Well,
I
could
bring
up
what
I
think
is
kind
of
a
ux
issue
just
for
feedback
that
I
ran
into
recently.
It's
not
that
it's
critical
or
anything,
but
I
I
ran
into
it
recently.
It
started
with,
and
I'm
just
curious
on
feedback,
because
this
is
kind
of
a
confusing
area.
It's
a
permissions,
I
think
gregory,
you
might
have
seen
my
issues.
A
The
first
one
was
around
the
fact
that
I
had
a
user
that
had
permission
to
administer,
to
to
access
the
contextual
links
and
to
access
custom
blocks,
but
they
couldn't
get
the
contextual
link
and
I
realized
that
they
have
to
have
permission
to
edit
the
layout,
which
might
make
total
logical
sense,
but
it's
still
confusing,
because
I
didn't
really
want
them
to
change
the
layout.
I
just
wanted
them
to
be
able
to
use
the
contextual
link
to
edit
the
block
and
that
might
be
a
little
bit
complicated
to
to
to
fix.
A
But
as
so
that's
one
issue,
and
so
again
I
don't
know
what
the
solution
to
that
is,
but
it
just
seemed
weird
and
that
led
me
to
realize
another
thing,
which
is
that
if
you
have
permission
to
administer
layouts
but
do
not
have
permission
to
edit
contextual
custom
blocks,
you
can
still
you
can
still
edit
custom
blocks.
You
just
don't
have
access
to
the
the
list
of
custom
blocks.
A
And
again
I
don't
know
if
this
is
a
big
gender
muted.
If
you're
trying
to
say
anything,
I
don't
know
that.
There's
a
big
use
case
for
this.
It
might
be
a
case,
that's
just
so
fringe
that
it
doesn't
matter,
but
I
just
stumbled
across
it
and
it's
like
okay,
I
don't
have
permission
to
edit
edit
custom
blocks
or
to
administer
custom
blocks,
but
I
can,
I
think
that
you
know
our
proposed
solution
would
be
simply
to
be
more
specific
about
what
that
permission
is
so.
C
You're
not
supposed
to
be
able
to
edit
that's
a
security
issue,
it's
an
access
bypass
problem
and
we
need
to
address
it.
I
think
it's
definitely
reasonable
to
say
these
people
can
move
blocks
around
on
the
page,
but
they
can't
edit.
The
text
of
the
block.
The
use
case
is
very
small.
I
think
I
agree.
There
are
probably
very
little
people
who
are
limited
in
access
to
something
like
editing
a
blog
but
allowed
do
something
as
dangerous
as
create
a
page.
C
So
I
think
the
number
of
people
are
affected
by
this
problem,
we're
small,
but
I
still
think
it's
important
that
we
use
the
permission
since
it's
there,
the
other
way
around,
so
in
drupal
8,
I'm
working
on
for
now
drupal
9,
working
on
a
core
patch
for
the
last
two
and
a
half
years
that
gives
people
the
edit
block
permission
without
needing
anything
else,
so
they
can
just
edit
the
content
of
a
block
and
it's
fairly
straightforward
to
send
them
to
a
dedicated
page
with
a
form
to
edit
the
blog
and
then
back
to
the
page.
C
They
started
from
via
contextual
link
rather
than
right
now,
when
you
say
configure
layout,
you
go
to
the
layout
page,
but
we
could
have
a
edit
block
link
or
configure
block
link
or
something
that's
more
specific.
That
goes
specifically
to
a
block
page,
and
that
would
be
really
clear.
Then,
when
you're
assigning
permissions,
you
want
someone
to
edit
blocks,
you'll
only
give
them
edit
books.
They
won't
see
that
configure
layout
link
they'll
only
see
the
configure
block,
link
and
they'd
get
to
a
dedicated
page.
C
For
that,
the
trick
there
is
that
there
are
settings
that
are
associated
with
the
layout
and
the
content
is
associated
with
block
so
like
they
would,
for
example,
be
able
to
change
the
text
of
the
block
if
it
was
like,
because
it's
stored
in
configuration.
If
this
block
is
only
placed
on
this
page
and
that
content
is
saved
in
the
layout
configuration
and
they
don't
have
access
to
the
layout,
it
gets
a
little
complicated
in
terms
of
how
you
save
things.
C
But
the
user,
the
user
interface
in
the
path
for
how
to
get
from
like
the
front
end
to
an
edit
form
back
to
the
front
end
without
needing
access
to
the
layout
is
straightforward.
Just
have
to
like
figure
out
how
to
update
that
part
of
the
layout
configuration
right.
A
Exactly
but
just
to
be
clear,
I
thought
right
now.
The
contextual
link
is
configure
block
right,
that
that
is
what
the
link
is
too
and
when
you
click
configure
block.
It
opens
up
the
layout
page
with
the
block
on
top
of
it,
which
is
why
the
problem
is
there,
but
the
you
know,
the
the
the
actual
link
looks
correct
right.
It's
you're
not
asking
for
access
to
edit
the
layout
you're,
just
asking
for
access
to
edit
the
block.
C
So
one
thing:
that's
also,
I
don't
know
if
you
were
going
to
say
this
great
one
thing.
That's
also
really
dangerous
by
allowing
people
to
edit
things
from
the
front
end
of
the
site.
Is
that
people
don't
understand
how
content
management
systems
work?
C
They
think
that
it
works
like
a
page
builder
and
that
this
block
only
exists
on
this
page,
and
then
you
go
to
another
page
inside
the
blog
on
that
page
and
so
by
giving
them
access
to
only
the
block
content,
we
are
sort
of
giving
them
a
tool
that
allows
themselves
to
shoot
themselves
in
the
foot
because
they're
gonna
be
like.
I
just
changed
this
on
the
home
page.
D
I
had
to
step
away
from
the
computer
for
a
couple
of
minutes,
so
I
missed
a
bit
of
the
discussion,
but
I'm
imagining
that
the
same
thing
happened.
So
I
read
the
description
that
you
added
tim
and
then
right
before
indie
gazelle
ever
responded,
which
made
me
actually
nod
and
say:
yes,
you
can
use
notes
as
blogs.
D
D
The
the
problem
that
we're
trying
to
solve
there
is.
It
is
an
ux
issue
in
this
case,
but
you
have
to
sort
of
like
two
groups
of
people,
the
ones
that
know
how
the
cms
internals
work
and
what
blocks
are
and
that
they're
components
on
that
page,
reusable
components
and
the
ones
that
jen
said
that
you
know
they
think
that
the
whole
page
is
a
single
thing,
and
this
is
where
we
stack
on
the
other
issue.
D
I
think
that
doc
wilmer
had
a
pull
request
and
then
the
other
thing
is,
if
you
disable
javascript.
I
think
that
editing
a
block
from
the
ui
actually
gives
you
a
drop
down
menu
which
allows
you
to
pick
the
region
and
change
the
region
where
the
block
is
placed.
D
So
we
would
have
to
lock
that
on
the
form
it
would
have
to
be
a
separate
form
so
because
that's
layout
editing,
basically
it's
not
the
block,
editing
so
yeah.
We
need
to
figure
out
a
way
to
allow
them
to
edit
only
the
content
of
the
block
and
then
also
warn
them.
As
then
said,
I
don't
know
it
could
be
a
message
or
something
that
hey.
This
block
is
being
used
in
this
this
in
that
place.
So
no
by
changing
it
here,
you're
changing
it
everywhere.
Sure.
C
This
is
a
much
simpler
solution
in
drupal
9
because
they
decided
blocks
for
content
and
we
decided
to
keep
blocks
as
configuration.
So
for
us,
there's
much
clear
like
all
of
the
stuff
is
just
configuration
and
if
you're
not
allowed
to
configure
the
site,
but
with
triple-a
they're
like
well,
it's
content.
C
So
now
your
content
editor
just
need
access
to
edit
it,
and
so
you
can't
get
to
it
from
the
content
listing,
in
spite
of
it
being
content,
but
with
us
we
have
a
blog
listing,
so
we
sort
of
have
the
same
problem,
but
we've
just
sat
down
yeah
an
opposite
solution.
I
don't
know
so
it
gets
messy.
I
think
the
last
time
we've
been
talking
about
this
for
years.
I
remember
all
of
this
issues,
but
it's
a
good
one.
C
Let's
see
if
ken
tripp
wants
to
add
a
block
edit,
because
there
there's
a
block
edit
module,
I
think
for
drupal
sex
or
something
I
don't
know.
I
looked
at
porting.
That's
part
of
that.
I
was
like.
Maybe
just
do
that,
just
a
different
interface
for
it.
A
Well,
in
summary,
there
there
might
be
technical
solutions
to
the
problem
I
described,
but
at
the
minimum
I
think,
and
maybe
I'll
try
to
make
suggestions
there.
We
could
just
provide
better
contextual
help
to
make
it
more
the
descriptions
more
accurate,
what's
actually
happening,
like
those
permission,
names
right
like
in
the
case
of
the
permission
to
access
any
custom
blocks.
If
we
can't
solve
that,
we
should
at
least
say
that
the
permission
is
really
just
to
access
the
the
custom
block
page.
E
C
C
But
yeah,
I
do
think
that,
like
if
the
permission
to
edit
a
block
doesn't
work
on
the
front
end
of
the
site,
we
could
change
that
to
say
something
like
edit
blocks
through
block
listing
right,
but
that
doesn't
yeah.
I
don't
know.
A
C
Still
think
more
more
information
is
useful.
I
create
an
issue
in
the
security
queue.
I
haven't
added
any
steps
to
reproduce
that
yet
I'll
push
that
out
later,
but
tim.
If
you
could
document
somewhere
everything
you
just.
A
C
A
E
But
on
that
note,
should
we
end
our
end,
our
video
sure
yeah?
We
are.