►
From YouTube: 2022/02/10 - Backdrop UX/Design
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
D
Yeah,
maybe
maybe
I
can
go
next-
I'm
greg
I'm
joining
from
greece
in
general,
excited
about
anything
related
to
backdrop
in
any
way
that
I
can
help
and
I'll
pass
it
on
to
martin.
E
I'm
martin
in
the
uk
and
just
yeah
I'm
building
building
a
few
sites
in
backdrop
at
the
moment
and
also
trying
to
contribute
wherever
I
can
I'll
pass
it
over
to
joseph.
B
I'm
tim
erickson,
I'm
saint
paul
tim
in
the
forums
and
on
the
internet,
and
I
am
in
deerwood
minnesota,
where
we
got
a
a
small
snowstorm
happening
right
now
and
also
getting
irena
is
getting
me
excited
about
backdrop.
Live
he's
been
really
pushing
us
to
get
going,
which
is
great.
I
love
that
anyways,
let's
jump
right
into
our
meeting
this
week.
B
We
are
talking
about
design
ux
issues
and
greg
has
some
things
he
wants
to
talk
about,
but
let's
first
see
if
anybody
else
had
any
other
sort
of
issue
issues
that
they
needed
help
with
or
need
unblocking
does
anybody
else
bring
anything
to
the
meeting.
I
didn't
have
anything
today:
no
okay!
B
D
Yeah
at
some
point
I'll
share
my
screen
as
well.
Just
let
me
just
do
a
prologue,
so
I,
from
time
to
time,
I
just
happened
to
come
across
either
old
posts
or
videos
from
presentations
in
drupalcon's,
and
I
happen
to
come
across
two
two.
Two
different
presentations
from
the
same
person
for
the
same
project
were
the
same
goal
or
subject.
D
I
should
say
one
was
from
back
in
2014
and
the
other
one
I
think
was
somewhere
around
20,
21
or
so,
and
it's
about
a
around
the
ecosystem
about
a
project
which
is
an
installation
profile.
Is
my
understanding
and
a
set
of
satellite.
I
call
modules
called
tasty
back
end
I'll.
Actually,
let
me
just
I'll
post
a
link.
Oh
there's,
already
a
link
in
the
zulu
chat,
but
I'll
post,
another
one
in
the
zoom
chat
here
so
yeah.
D
I
was
watching
this
presentation
and
a
lot
of
things
made
sense
from
for
me
from
a
user
experience
standpoint
just
specific
to
content
authors
though
so
a
little
bit
of
context.
D
I
the
the
questions
that
I
get
and
the
feedback
that
I
get
from
newcomers
that
are
interacting
for
the
first
time
either
people
that
have
some
previous
experience
with
other
cmss
or
first
time
that
they
ever
heard
of
the
term
cms
or
dribble
right
and
the
the
pain
points
and
the
frustrations
are
seem
to
be
the
same
for
the
newcomers
and
then
randomly.
D
It
just
happened
right
after
the
training
the
day
after
the
training
to
to
come
across
these
video
sessions,
and
I
said,
look
that
person
delivering
the
the
like
doing.
The
presentations
has
is
so
spot
on
because
they
were
hitting
the
the
points
that
the
the
the
attendees
in
the
training
were
trying
to
make
that
no
matter
how
much
you
train
them
and
how
good
the
trainer
and
the
training
material
is
and
how
much
attention
and
love
you
give
them.
It's
still.
D
The
learning
curve
for
drupal
and
inherently
backdrop
is
still
steep.
Like
there's
terminology,
there's
ux
issues
that
you
know
there
might
not
be
problems
or
very
obvious
problems,
but
they
are
still
pain,
points
that,
as
chronic
users,
do
not
see
them
like.
We
have
gotten
used
to
them
and
we
are
making
knowledge
assumptions
so
I'll
share.
My
screen
now
give
me
two
seconds.
D
Everybody
see
my
screen,
so
basically,
this
is
a
a
screenshot
of
the
the
admin
interface
in
drupal
8,
I'm
assuming
with
the
difference
that
it's
it
has
gone
through
the
installation
profile
of
this
project,
tasty
back
end
and
the
thing.
If
you
see
this
from
a
content
editor
perspective,
you
will
see
that
things
like
taxonomy
and
menus
are
not
hidden,
underneath
a
structure
menu
which
has
all
these
other
things
that
are
irrelevant,
and
I
understand
that
certain
of
these
things
that
are
under
the
structure
menu
can
be
hidden
via
permissions.
D
I
understand
all
that,
but
another
thing
that
I
have
noticed
being
in
the
support.
The
application
support
team
is
that
digital
agencies,
because
the
permission
system
is
so
granular.
D
I
know
it's
not
a
right
practice
or
right
method,
but
instead
of
trying
to
properly
tweak
all
permissions,
they
they
either
give
user
one
access
to
the
site
owner
and
the
content
editors,
or
they
just
create
a
role
which
is
way
too
permissive
like
it
gives
access
to
people
to
things
that
either
could
lead
to
them
breaking
their
site.
If
they
do
a
mistake
or
if
they're,
very
cautious
people,
and
they
they
are
very
careful
with
what
they
do
and
they
take
backup.
D
So
they
don't
touch
things
that
they
don't
need
to
still
there's
too
much
too
many
controls
too
many
options
too
many
menus
in
front
of
them
that
confuse
them
and
make
the
the
user
experience
less
ideal
right.
Whereas
this
thing
has
exactly
the
the
the
menu
items
that
content
editors
would
need
plus
another
item
for
users,
which
would
be
specific
roles
in
your
organizations
for
only
those
people
that
are
tasked
with
adding
and
managing
users
on
the
site-
and
I
I
this
idea
just
makes
sense
to
me.
D
D
I
don't
know
how
much
of
that
belongs
in
core
or
if
it
could
be
another
installation
profile
available
in
core
or
it
could
be
just
a
recipe
I
don't
know,
but
but
it
makes
sense
to
me
like.
I
almost
want
to
create
a
blog
article
with
instructions
on
how
to
get
there
right
so
yeah
there
you
go
discussions.
E
So
there
is,
I
don't
think
it
necessarily
goes
into
the
menu,
but
there
is
a
a
module
called
simplify
that
take
strips
away
quite
a
number
of
the
admin
options
that
you
that
people
don't
need
to
see,
but
I
think
that's
actually
on
the
on
the
forms
themselves.
E
D
So
there's
a
few
modules
like
you
mentioned
in
drupal
land,
and
maybe
most
of
them
might
have
already
been
ported
in
bankrupt
right.
There's
this
specific
I'll
try
to
remember
that
it's
called
something
like
admin
menu
context.
D
Let
me
just
admin
administration
menu
source
right,
which
is
a
solution
that
allows
you
to
specify
different
menus
to
be
used
for
the
admin
menu
right,
and
I
just
like
small
things
that
maybe
they
could
be
import
like
allowing
people
to
clone
a
menu
easily
right,
so
they
can
take
the
admin
menu
as
it
is
now
clone
it
and
then
strip
out
things
that
they
don't
want
for
their
contact.
Admins
and
then
either
have
permissions
per
menu
or
the
ability
to
assign
roles
per
menu
right.
D
So
these
two
simple
things
in
my
head,
like
I'm,
imagining
that
code
wise,
it
should
be
very
simple,
but
then
again,
as
I
said,
I'm
not
I'm
not
sure
if
these
belonging
poor
or
people
do
not
agree.
But
since
we
have
this
whole,
you
know
mentality
towards
making
things
easier
for
people
yeah
anyway.
B
My
my
thoughts
are,
I
mean
first,
I
think
the
two
big
steps
we've
taken
in
this
direction
already,
that
I've
been
involved
in
are
one
the
adding
the
the
editor
role
and
two
adding
the
dashboard.
Both
of
those
things
could
be
improved
upon.
I
I
like
your
whole
point,
though,
about
actually
having
a
different
menu.
One
of
the
things
that
occurs
to
me
why
the
editor
role
might
not
be
so
effective.
B
So
that's
where
they're
going
to
use
it
if
you're
building
your
own
site-
and
you
start
out
as
admin,
it's
highly
unlikely
that
you're
going
to
demo
yourself
to
an
editor
and
what
I'm
getting
at
is.
Maybe
there
could
be
a
simple
way
to
sort
of
as
an
admin
to
just
switch
to
being
an
edit.
Like
the
editor
view.
B
B
D
D
But
then
they
would
need
to
tweak,
and
that
was
that
was
a
thing
that
the
person
doing
the
presentations
were
saying.
All
the
time
build
this
for
your
your
customer,
tweak
it
for
your
customer.
So
the
premise
that
I'm
making
is
that
we
give
the
tools
to
site
builders
to
easily
with
very
few
steps,
without
possibly
having
to
do
to
install
a
lot
of
contrib
modules
to
get
to
a
point
where
they
deliver
a
site
to
the
site
owners
where
they
have
an
amazing
experience,
but
only
with
things
that
they
absolutely
need
right.
D
Now,
this
task
of
getting
from
being
having
a
lot
of
permissions
being
either
user,
one
or
the
site
builder
or
whatever.
You
want
to
call
it
right
and
then
getting
to
a
point
where
you
can
figure
a
role
for
the
customer,
for
the
site
owner
or
for
the
various
roles,
if
it's
a
slightly
slightly
bigger
organization
where
they
have
a
separate
team
for
quantitative,
separate
teams.
D
Still
it's
it's
some
effort,
so
if
we
can
make
it
easier,
that's
what
I
was
thinking,
how
we
make
it
easier,
whether
it's
core
worthy
or
some
of
the
things
are
core
worthy
or
not.
Yeah.
B
So
if
it's
helpful,
I'll,
just
quickly
show
a
site
yeah,
some
things
that
we've
done-
this
is
a
backdrop
site
for
twin
cities,
opera
guild,
the
this
is
the
site
that
inspired
the
opera
theme
that
I'm
working
on-
and
this
is
the
editor
me
logged
in
as
the
editor.
This
is
what
I
turned
over
to
the
site
manager
and
you
know
the
person
who's
administering
content.
Now
I
think
your
point
greg
is
that,
on
the
one
hand,
we've
really
simplified
this
right.
They
can
only
they
it
this.
B
I
think
this
was
might
be
done
before
we
added
the
editor
role
either
that
or
I
even
I
think,
further
reduced
it,
but
there's
very
few
options
here
now
this
site
has
civi
crm
and
if
you
click
on
that,
you
suddenly
get
the
entire
cvcrm
menu,
which
is
but
that's
unusual
anyways.
So
on
the
one
hand,
I
have
this
yeah,
so
this
kind
of
defeats
the
whole
purpose,
is
now
now
you've
got
like
two-thirds
of
this.
I
don't
even
understand,
but
let's
close
that
close
the
civic
crm
menu
oops.
B
How
do
I
remind.
B
B
I
also
have
a
there's
a
dashboard
plus
module,
which
I,
like
the
manage
content
block
better
that
I
created
for
that
than
the
default
one
where
you
can
just
create
or
manage.
I
like,
I
really
like
this
create
button
which
we
don't
have
in
our
dashboard
right
from
the
dashboard.
I
don't
think
we
do.
We
have
that
and
the
other
thing
that
I
did
on
this,
which
is
not
a
core
thing,
but
just
to
mention
it
to
people
is.
B
I
use
the
book
module
to
kind
of
create
that
editor-only
documentation
for
the
site,
so
so
the
site
manager
has
has
a
little
book
that
kind
of
walks
them
through
the
major
features
and
and
gives
them
some
text
anyways,
but
yeah.
The
main
thing
I
wanted
to
show
was
just,
but
I
think,
greg
what
you're
suggesting.
Is
that
sure
it's
one
thing
to
reduce
this
menu,
but
another
thing
would
be
to
restructure
it
a
bit
to
make
it
more.
D
Yeah
so
so
you'll
see
that
this.
This
is
great.
This
is
a
great
step
like
very
thoughtful
of
you,
as
an
agency
as
a
developer
as
a
site
builder
when
you
deliver
the
site
to
the
the
customer
right,
the
site
owner,
but
still,
if
you
hover
over
content,
for
example,
or
the
dashboard
you
will
see
and
and
structure
right,
you
hide
the
taxonomy,
which
is
the
end
target
under
a
menu.
D
So
there's
levels
of
of
things
that
are
unnecessary
there
right
and
then
one
thing
that
is
missing
here
is
menu
access,
because
if
you
give
them
menu
access,
you
give
them
access
to
even
this
menu
right.
So
that's
what
I'm
saying
that
that
if
you
have,
if
we
had
an
easy
way
in
backdrop
core
to
specify
pair
role
access
to
specific
menus,
then
it
would
make
things
easier
for
you,
as
a
site
builder,
to
give
access
only
to
specific
menus.
D
And
ideally
there
should
be
an
item
there,
not
under
structure
but
a
top
level
item
that
says
menu
and
it
would
give
them
access
say
to
the
footer
menu
and
the
navigation
menu
right
right.
So
so
these
are
the
things
that
have
been
mentioned
in
in
the
presentation
and
it
just
it
makes
absolute
sense.
D
If
I
was
building
sites
for
customers,
that's
what
I
would
do,
but
it
takes
a
small
collection
of
modules
and
some
work.
Of
course,
the
first
link
to
the
first
video
is
back
in
2014.
As
I
said,
there
was
no
concept
of
using
core
yet
and
people
in
drupal
7
had
to
use
the
what
was
it
called
admin
use
to
to
convert
like
even
the
managed
page
into
a
view
that
can
be
tweaked
according
to
customer
requirements,
or
you
know
you
would
have
to
separately.
D
D
B
D
Yeah-
and
you
know
there
are
certain
things
that,
though,
that
makes
sense
as
it
is
like
and
I'll
repeat.
One
of
those
things
is
pair
role
assignment
right
per
menu.
We
do
a
similar
thing.
We
have
similar
ux
when
we
specify
which
roles
have
access
to
which
text
formats,
for
example
right
it
wouldn't
be
a
paradigm,
that's
totally
different
right
and
it
would
be
it
would
be.
It
would
allow
more
fine
grade
control.
D
So
one
thing
that
site
builders
do
not
want
to
give
access
to
people
is
the
the
admin
menu
you
want
them
to
be
able
to
to
tweak
their
navigation
menu,
their
site
menu
right,
but
not
their
the
admin
menu,
because
they
might
break
the
site
in
ways
that
it
would
make
navigation
even
more
difficult
for
them.
That's
where
I
was
getting
it
so
there's
there's
still
small
things
that
obviously
make
sense
and
I'll
add
them
as
separate
suggestions
for
core
but
yeah.
D
Certain
other
things
do
seem,
like
you
know,
a
contrib
or,
as
I
said,
a
documentation
or
a
blog
article
thing
of
hey
use
this
set
of
contrib
modules
and
do
this
this
and
that
but
yeah
yeah.
B
So,
with
the
biggest
thing
I
mean
just
like
my
gut
reaction
right
now
is
that
if
I
were
to
start
today,
I'm
trying
to
to
do
this
that
I
would
start
with
just
rebuilding
a
menu
from
scratch
for
targeted
sort
of
editors
and
saying,
if,
if
I,
if
I
had
the
freedom
to
start
from
scratch
and
rebuild
the
menu
for
site
editors,
what
would
that
look
like?
And
that's
where
I
would.
D
Start
well,
no,
it
would
become
a
problem,
because
your
the
the
the
menu
structure
as
it
is,
is
very
useful
and
we've
we've
poured
a
lot
of
thought
into
it
for
site
builders.
If
we
change
it
now,
we
are
we're
sort
of
like
ditching
that
work
and
we
would
be
messing
it
for
another
user
profile.
So,
ideally,
as
I
said,
first
of
all,
just
let's
make
clear
that
you
can
do
this
now
right
as
a
side
builder,
you
create
another
menu,
but
it's
a
lot
of
manual
effort.
D
We
already
have
operations
so
instead
of
having
the
the
site
builder
have
to
replicate
all
the
menu
items
have
them
cloned
and
then
another
thing
is
that
some
some
items
in
the
current
admin
menu
are
special
items
like
when
you
create
a
new
content
type
that
becomes
an
option
at
their
content
ad
content
right.
So
you
need
to
make
sure
that
the
duplicated
menu
that
is
dedicated
for
content
editors
has
this
functionality
as
well,
because
you
don't
want
to
be
adding
content
types
and
then
having
again
to
do
manual
things
right.
D
So
yeah
there's
a
few
bits
and
pieces
that
can
go
as
small
functionality
in
core
and
then
you
can
piece
those
those
items
together
in
an
installation
profile,
but
what
they
need
to
leave
somewhere.
E
And
you
you
as
well
you
what
you
might
have
and
you
might
need
to
also
hook
into
whether
the
person
has
permission
to
edit
that
content
type,
because
there
will
be
some
content
types
that
that
aren't
going
to
be
applicable
to
the
content.
Editors,
who
were
adding
articles
and
updating
pages
and
events
there'll,
be
other
content
types
that
are
more
related
to
functional
aspects.
D
Content
type
permissions
in
the
content
type
right
screen
and
if
you
disallow
a
content
type
for
a
specific
role
when
they
view
the
structure,
not
sorry,
not
the
structure,
but
the
add
content
menu,
the
types
that
they
don't
have
access
to,
that
are
not
there.
So
we're
doing
a
really
good
job
with
that
right,
but
yeah
you're,
good.
D
You
you're
right
that
that
should
be
so
like
something
that
that
works
out
of
the
box
yeah
or
the
other
thing
see,
because
I
mentioned
that
certain
roles
or
if
it's
a
smaller
business,
that
the
site
owner
should
have
the
ability
to
also
manage
roles
right,
maybe
not
permissions
necessarily,
but
something
that
that
is
being
achieved
by
modules
like
role
delegates.
D
So
there's
these
restrictions
that
yeah
anyway.
So
my
point
is
that
make
it
easier
for
site
builders
too
easily,
so
that
they
don't
get
lazy,
and
this
is
what
we
see
in
gaf
cms
land
right.
We
see
that
govern.
Government
agencies
are
complaining
that
hey.
We
cannot
do
this.
We
cannot
do
that
and
then
the
the
digital
agencies
that
are
looking
after
them,
no
matter
how
expert
they
are
and
because
the
customer
will
complain.
D
If
you
spend
too
much
time
tweaking
things,
they
just
give
them
too
many
too
many
permissions
right
and
they
end
up
working
their
sites
eventually
at
some
point,
because
they
accidentally
do
something
so
yeah.
So
so
I'm
I'm
not
suggesting
a
specific
solution.
I'm
just
saying
that
I
saw
that
and
I
liked
many
bits
of
it
and
how
do
we
make
it
easier
for
site
builders
to
do
a
better
job
faster,
which
is
what
we
already
are
doing
like
by
putting
the
whole
the
whole?
D
What
you
call
mentality
of
of
us
building
backdrop
was
to
make
things
faster
compared
to
drupal
7,
like
you,
don't
have
to
install
views,
you
don't
have
to
install
and
configure
cd
editor.
You
get
these
things
out
of
the
box,
so
this
is
where
I
want
us
to
to
eventually
get
yeah.
B
I'm
gonna
go
back
and
just
defend
the
last
point
I
was
making,
which
is,
I
would
start
and
again
I'm
just
saying
start
hear
me
out
by
redesigning
what
I
I
think,
a
good
menu
would
look
like
one,
because
then
it
would
give
us
an
idea
of
what
the
tools
we
are
that
we
need
to
build
so
that
somebody
could
get
there.
B
It
doesn't
necessarily
mean
that
we
would
implement
that,
but
I
would
like
I
want
to
start
with
what
I
think
that
should
look
like,
so
I
can
figure
out
the
best
way
to
get
there,
but
also
I'm
not
sure
it
is
enough
to
just
give
site
builders
the
tools
to
create
this,
because
I
think
the
work
the
hardest
thing
about
doing.
This
is
all
the
decisions
you
have
to
make
and
what
I
think
I
really
want
is
somebody
to
give
me
a
template
right.
B
I
don't
want
for
you
to
just
give
me
the
tools
to
like
make
all
these
decisions
and
implement
it
myself.
I
want
like
some
real
hints
or
a
template.
This
is
a
starting
place
for
site
editors,
and
now
you
can
modify
that
which
we
to
some
extent
have
already
that's.
I
mean
our
our
editor
role
is
in
some
ways
a
template
of
what
we
think
are
a
a
default
instead
of.
D
So
my
my
sort
of
like
recommendation
would
come
similarly
to
how
we
added
the
content,
editor
role
and
how
we
ship
backdrop
with
an
administration
menu.
They
would
be
a
stripped-down
version
of
administration
manual
would
be
that
would
be
called
content.
Author
menu,
not
administration,
and
it
would
have
different
structure
altogether.
D
Some
of
the
items
not
some
of
the
items
all
of
the
items
would
be
coming
from
the
admin
menu,
but
they
would
be
brought
to
the
top
level.
If
there's
not
any
necessity,
you
know
to
go
through
less
decisions,
less
less
clicks.
I
should
say
so
so
yeah
similar
to
the
way
that
we
went
through
the
process
of
deciding
what
permissions
the
content
admin.
Sorry,
the
content
editor
role
should
have
out
of
the
box.
D
There
should
be
made
similar
decisions
for
that
menu
right,
so
we
would
have
to
go
through
that
process
if
it
is
to
be
done
via
core
right.
There
would
be
some
feedback
about
what
tasks.
When
the
editors
do
most
of
the
time
which
things
they
they
shouldn't
access,
and
things
like
that
and
according
to
that,
we
will
build
it,
but
yeah
yeah
cool
thanks.
B
D
Meta
issue
you
talked
about,
yes,
I
think
I
think
I'm
going
to
start
it
there
and
it's
going
to
have
bullet
points,
and
I
know
that
we,
we
have
a
tag
that
says
contrib
candidate
and
usually
we
use
that
for
specific
things.
Now
there
may
be
multiple
things
that
are
contrib
candidates
and
some
that
are,
you,
know,
core
candidates.
D
But
let's
start
with
with
the
meta
issue,
so
that
we
can
get
a
discussion
going
to
see
if
it's
a
good
idea
or
not,
which
things
belong
in
core.
What's
not
things
like
that?
So
go
ahead
and
do
that
in
the
near
future,
hoping
very
soon
because
it's
a
good
idea
and
then
next
steps
would
be
I'll,
keep
bringing
it
up,
and
I
already
my
I'm
gathering
that
there's
interest
from
the
look
in
your
eyes,
so
anyone
that
wants
to
help.
B
There
you
go
well,
there's
interest,
I
don't
know
if
there's
bandwidth
in
my
part
but
we'll
see
certainly
to
give
feedback
and
to
talk
about
my
answer
to
every
problem
for
the
next
four
weeks
is
going
to
be
to
plan
a
backdrop
live
session.
E
E
B
E
B
B
What
so
do
we
have
any
other
ux
issues
who's?
I
haven't
been
watching
the
issue
queues
mostly.
Do
we
have
any
well,
I'm
gonna
mention,
but
I
don't
think
there's
any
reason
to
talk
about
the
the
big
one
that
we
have
been
talking
about.
Is
this
whole
ageless
nodes
thing
which
I'll
just
report
hasn't
had
any
I'm
saying
this
out
loud,
partly
to
put
pressure
on
myself
no
progress
in
the
last
two
weeks.
B
We
really
know
what
the
next
steps
are.
We
just
need
to
take
them.
We
want
to
do
that
soon,
because
we
don't
want
this
to
drag
out
until
the
end.
We
want
to
get
this
into
into
the
next
version
of
backdrop
soon
enough
that
we
can
test
it
and
we're
not
crushing
it
at
the
last
minute,
but
that's
the
status
on
that.
Are
there
any
other
issues
like
ux,
clearly,
ux
issues
like
that
that
maybe
are
stuck
or
we
could
benefit
from
talking
about.
B
I
just
opened
the
the
list
of
of
of
issues
that
are
marked
as
ux
issues
and
I'm
looking
at
the
most
recently
updated.
One
was
eight
days
ago,
project
installer
enable
modules.
What
is
that
one
greg?
Is
there
sorry
which
one
pro
it's
issue?
5489
looks
like
something
that
you've
worked
on.
I
only
pulled
this
out
randomly
because
it
was
most
recently
updated
by
bug
folder
by
chance.
Maybe
this.
D
B
Which
number
again
50
54.89-
and
this
may
not
be
a
good
one
to
talk
about.
I
don't
know
it's
just
the
most
recently
updated
one.
That's
all
54.89
right,
yeah!
You
just
created
this
eight
days
ago,
54.89
backdrop
issues
yep,
oh
yeah,.
D
Yeah,
so
that's
a
very
simple
thing,
so
if
you
properly
create
the
check
boxes
when
they're
on
the
table,
so
you
have
a
column
with
check
boxes
and
then
you
have
a
column
with
the
labels
of
the
items
like
the
in
this
case
it
would
be
module
names
right.
So
if
you
go
into
the
modules
I
actually
I
can,
I
can
share
my
screen.
I
have
a.
D
All
right
can
everybody
see
my
screen
sure
so
this
works
fine
see.
So
I'm
not
just
clicking
here.
I'm
clicking
the
label.
This
is
a
separate
column.
So
it's
a
separate
item
and
there's
a
trick
where
you
can
make
this
work
right.
Okay,
but
if
I
go
to
install
a
your
module,
yeah
web
form
store
it
right.
D
D
D
B
So
there
are,
there
are
two
ux
issues
that
that
have
I've
noticed
lately
that
interest
me,
although
both
of
them,
I
think,
have
gotten
some
attention
lately.
So
I
don't
know
that
they're
stuck
this.
It
sounds
like
at
the
dev
meeting.
Last
week
you
talked
about
the
making
collapsible
sidebars
in
the
harris
layout.
B
B
It
looks
like
the
discussion
last
week
was
to
put
to
do
something
with
flexible
layouts
and
make
that
possible
with
flexible
layouts.
Is
this
anybody
here
have
opinions
of
or
know
what.
A
B
Sure,
there's
a
yes
there's
a
contrib
module,
that's
in
the
original
description.
It
says
currently
there's
a
contrib
module
that
does
this.
So
I
think
I
think
the
debate
is
what
needs
to
go
into
core.
Like
you
know,
when
do
we
need
something
like
this
in
core
and
then
two?
B
If
we
do,
does
it
need
to
be
like
a
template
or
could
it
just
be
the
flex
of
the
layout
capability
like
as
far
as
I
know,
right
now
you
can't
create
a
flexible
layout
that
does
this,
and
so
I
think,
sounds
like
that's
what
quick
sketch
nate
was
recommending
personally
just.
B
B
I
don't
think
that
works
today,
but
rather
than
adding
a
template
like
this
to
core
or
trying
to
modify
in
a
backward
compatible
way
an
existing
template
that
we
would
just
make
it
possible
to
build
one
with
flexible
layouts.
B
It
seems
to
me
that
there
ought
to
be
some
way
in
core
to
have
a
layout
that,
with
a
flexible
cut,
you
know
with
a
collapsible
column
yeah,
and
it
also
seems
to
me-
and
some
of
you
who've
listened
to
me
like
martin
just
an
hour
ago
to
me,
I
I
I
feel
like
our
current
layouts,
I
mean
our
current
layouts
in
core
lack
some
things.
B
For
me,
the
big
thing
has
been
the
ability
to
do
the
stretch
blocks
all
the
way
across
the
page.
Again
I
rant
about
this
all
the
time
and
I
found
solutions.
I'm
working
on
a
theme
which
gets
around
that,
but
the
opportunity
to
like
add
a
layout
to
core
that
that
is
more
flexible
in
that
regard
to
me
would
be
a
good
thing.
On
the
other
hand,
I
I
buy
the
argument
that
maybe
we
should
be
moving
not
towards
adding
layouts
at
all
and
encouraging
people
or
making
the
flexible
layouts
a
more
powerful
school.
B
E
I
think
it's
still
good
to
have
templates
in
there.
E
E
I
looked
in
the
the
list
of
backdrop,
videos
and
I
couldn't
see
a
helpful
tim
video
about
using
the
flexil
flexible
modules,
flexible
layouts
templates,
so
I
think
it
it.
It
probably
is
powerful,
but
it
I
I
certainly
wouldn't
want
to
be
throwing
new
users
onto
that.
Okay,.
E
And
unless
it
was
made
a
lot,
a
lot
more
straightforward
and
and
and
clear
as
to
what
what
the
user
journey
is
to
build
you
to
build
your
layout
using
that
template.
B
For
greg's
context,
and
because
he
probably
has
opinions
on
this,
I
just
brought
up
the
collapsible
columns,
layout,
columns,
issue
and
and
the
sort
of
general
question
of,
should
we
be
working
towards
making
our
current
selection
of
layouts
better
or
should
we
be
putting
our
effort
into
making
flexible
layouts
that
the
choice?
You
know
a
better
choice
for
people
yeah
because
well
it
wasn't
not.
B
D
We
could,
but
so
so
it
wasn't
my
my
baby
issue.
It
was
irina
who,
who
mentioned
it
for
the
arena
yeah.
So,
as
you
all
know,
I
my
day
job
doesn't
involve
backdrop.
It's
just
it.
It
makes
sense
to
me
when
there's
no
content
in
a
region
to
expand,
but
then
there's
these
different
opinions
like
there's
the
other
camp
zen
camp
which-
and
she
has
a
point
right.
D
If
there's
no
quantity
in
the
sidebar
and
you
have
the
main
content,
the
main
the
main
content
area
expand,
then
you
get
into
other
problems.
It
depends
on
how
long
it
expands,
because
then
the
the
text
becomes
too
lengthy
and
that's
a
known
user
experience
issue
like
reading
long
lines
right
so
yeah.
I
guess
I
guess
it's
to
eat
its
own.
Is
the
expression
right
and
a
matter
of
preference
and
use
case.
I
guess
if
we
could
accommodate
beth
both
in
some
easy
way,
then
that
would
be
ideal.
I.
B
Think
greg.
The
question
I
was
asking:
if
you
had
an
opinion
on,
was
forget
about
the
specifics
of
this
request,
but
the
idea
that
they're,
you
know
we
could
be
making
improvements
in
our
layouts
and
is
it
better?
Should
we
be
thinking
more
about
making
our
existing
layouts
better,
or
should
we
be
thinking
more
about
how
to
make
flexible,
layouts
a
better
tool
so
that
we
really
don't
need
the
structured
layouts?
B
Now
martin
is
just
as
you
came
in
martin
was
saying
that
he
finds
flexible
layouts
to
be
a
bit
challenging
for
a
beginner,
and
so
maybe
we
need
some
work
there
and
two
that
doesn't
mean
that
we
couldn't
provide
some
default
flexible,
layouts,
it's
like
great.
You
have
promoted
that
any
layout
should
we
should
be
able
to
attend.
I
was
about
to
mention
that
being
right,
you
should
be
able
to
convert
them
to
being
flexible.
Well.
That
wouldn't
really
be
helpful
right
now.
D
Well,
if
you
make
any
layout,
if
you
give
easy
like
two
or
three
clicks
steps
to
people
to
to
convert
and
replace
the
existing
layout,
which,
in
order
so
let's
take
this
a
step
back,
a
site
builder
is
not
happy
with
the
current
layout.
D
The
and
there's
not
another
layout
existing
ready-made
that
fits
their
need
and
the
one
that
is
being
used.
There
fits
their
needs,
eighty
ninety-eight
percent.
So
it's
the
two
percent
that
I'm
using
I'm
just
arbitrary
numbers
now,
so
they
have
two
options:
either
they
they
copy
they
the
code
of
the
that
layout,
because
we
don't
have
any
option
to
clone
the
layout
template.
I
should
I
should
mention
right
and
they
actually
get
into
coding
which
we're
trying.
D
This
is
one
of
the
problems
that
we're
trying
to
solve
right,
no
need
to
not
necessarily
any
needs
to
code,
and
this
is
where
I
think
that
that
proposal
would
would
make
sense
if
there
was
an
easy
button
or
a
few
entry
points
that
would
allow
you
to
convert
any
existing
hard
coded.
I
don't
know
what
you're
going
to
call
it
layout
template
into
something
that
people
can
easily
manipulate
via
the
user
interface.
B
And
then
I
have
another
one.
The
problem
right.
The
problem
with
what
you're
suggesting
for
me
is
that
I
have
no
idea
if
that's
realistic
to
be
able
to
and
it
might,
it
might
turn
out
to
be
not
a
big
some
things
that
feel
to
me
like
that
could
be
almost
impossible
turn
out
to
be
really
easy
and
other
things
that
seem
like
they
should
be
really
easy
turn
out
to
be
really
hard.
B
D
Like
that
would
be
manageable,
I
see
I
hear
what
you're
saying
and
I'll
I'll
I'll
tell
you
this.
If
we
were
discussing
this
like
seven
years
ago,
I
would
tell
you
that
I'm
all
ideas
and
I
can't
put
code
where
my
mouth
is,
but
I
have
a
vault,
so
I
still
have
more
ideas
than
I
have
time
to
code.
So
I'm
hoping
that
my
ideas
will
inspire
other
people
and
get
to
implement
some
of
these
things,
but
yeah.