►
From YouTube: Backdrop Design + UX meeting - July 2nd
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
All
right
we're
live
today
is
july,
2nd.
This
is
our
fortnightly,
design
and
user
experience
meeting
before
we
get
started
with
the
agenda.
I'd
like
to
go
around
and
have
everyone
introduce
themselves
if
you
could
say
what
your
name
is
and
where
you're
from
and
if
you
have
anything
you
want
to
share
with
the
group
30
seconds
or
less
that's
not
already
on
the
agenda,
you
can
go
ahead
and
do
that
now
greg.
Let's
have
you
go
first.
B
Hi,
my
name
is
greg.
I'm
joining
from
greece,
I'm
usually
in
australia,
I'm
joining
the
ux
meeting,
because
I've
been
working
on
some
ux
issues.
Some
of
them
were
older,
pull
requests
that
they
needed
to
be
revisited
reward,
some
of
them
new
ones.
So
I
would
like
to
sort
of
like
get
consensus
and
move
them
forward.
C
Sure
can
you
hear
me
yep
yep,
all
right,
I'm
luke
mccormick,
I'm
a
web
product
manager
in
pheromone,
california,
and
I'm
currently
leading
up
the
ready
to
wear
team
initiative
which
has
a
foot
in
in
both
steam
and
in
sort
of
development
worlds.
So
and-
and
I
I
generally
would
like
to
understand,
design
and
theming
and
front-end
presentations
better
than
I
do
so.
That's
largely
why
I'm
around.
A
A
A
All
right,
mute,
luke,
I've,
muted
you
because
there
were
some
static,
but
if
you
want
to
talk,
feel
free
to
unmute
yourself,
okay,
first
on
the
agenda,
we
have
a
section
here
for
the
theme
initiative
update,
maybe
all
yeah,
but
we
usually
talk
about
the
theme
initiative
in
the
developer
meeting
too,
because
now
it's
an
official
initiative.
A
So
one
thing
that
I
was
telling
greg
right
before
the
meeting
started
is
that
I
think
it's
important
if
you
want
to
have
core
developers
involved
in
the
conversation
about
the
issue
to
have
that
in
the
weekly
meeting.
But
if
you
have
things
that
don't
necessarily
aren't
ready
for
that
yet-
and
you
want
to
have
a
conversation
about
that-
I
think
leaving
this
space
in
this
meeting
will
be
really
useful.
So
we
could
like
hash
out
something
here
and
then
take
it
to
the
developer
meeting
and
be
like
hey.
A
This
is
what
we
decided.
Is
this
cool?
Yes,
no,
that
might
be
a
good
way
to
manage
the
time
so
you're
not
saying
the
same
thing
in
both
meetings.
But
you
know,
initiatives
are
new.
We
are
still
figuring.
A
If
you
have
anything
in
particular
that
you
want
to
talk
about
in
this
meeting,
there
is
space
here
for
you
to
do
that.
A
Luke
is
also,
I
think,
driving
right
now,
so
why
don't
we
go
ahead
and
skip
the
theme
initiative
update
for
now
and
if
he
has
something
he
wants
to
add,
we
can
squeeze
him
in
he's
available.
A
Okay
in
terms
of
design
user
experience,
we
have
a
couple
of
outstanding
issues
that
we
would
like
to
get
worked
on.
One
of
them
is,
if
you
use
the
user
interface
to
update
a
module,
a
theme
or
layout
or
even
backdrop
core.
The
user
interface
is
a
little
weird.
I
remember
seeing
an
issue
about
that.
A
At
some
point,
I
don't
have
the
issue
number,
but
I
would
love
to
work
on
that,
especially
while
we're
working
on
making
updates
automatic,
and
while
we
have
a
lot
of
people
updating
from
triple
seven,
I
think
getting
that
process
smoothed
out
would
be
something
that
would
really
highlight
to
people
how
we
are
focused
on
user
experience
right
now.
We
just
inherited
what
was
available
for
drupal
7.
A
Okay,
so
that
sounds
like
we've
got
a
bunch
of
a
bunch
of
different
related
issues
for
update
process,
and
that
was
one
potential
solution,
but
there
were
a
bunch
of
other
things
too.
There
were
like
language
on
one
of
the
forms
was
confusing,
which
button
to
click
was
confusing
they're
like
about
a
bunch
of
little
tiny
things
too,
and
I'm
not
sure
we
have
a
meta
issue
for
that.
A
They
might
just
be
a
whole
bunch
of
separate
ones,
but
issue
2714
if
anyone's
interested
is
a
much
bigger
issue
of
like
let's
not
just
fix
the
thing
we
have,
let's
like
reimagine
in
a
way
that
might
make
more
sense,
and
I
think
that
that's
important
to
move
that
forward
also,
so
I
think
we
might
still
need.
B
Yeah,
so
that
was
another
issue
here:
there's
this
I'll
try
to
find
it
so
the
main
issue,
the
the
the
main
ux
issue-
is
that
currently
those
pages,
at
least
they
don't
filter
by
the
type.
So
if
you
go
to
the
hello
theme,
so
if
you
go
to
the,
if
you
go
to
the
modules
page
and
you
have
things
that
need
to
be
updated
or
core,
they
will
be
listed
there
as
well.
B
So,
and
this
has
been
standing
there
for
a
while.
So
until
we
decide
if
we're
going
to
merge
these
pages
and
redirect
and
then
have
a
central
page
where
we
do
that
in
the
meantime,
maybe
the
the
low
hanging
fruit
would
be
to
just
apply
some
filtering
on
these
pages
to
make
sure
that
they
show
what
they
actually
say.
B
That
they're
gonna
show
like
filter
out
modules
from
the
theme
page,
the
only
caveat
there
is
that
core,
as
an
update
is
mentioned
in
all
of
them,
and
if
we
remove
it
from
there,
then
people
won't
have
a
way
to
update
core,
so
core
will
be
left
in
all
of
them.
A
I
think
that's
probably
better
than
waiting
for
the
re
org
to
happen,
because
I
think
there's
probably
going
to
be
a
lot
of
heated
discussion
around
where
the
page
should
be
how
it
should
work
whatever
and
it'll.
Take
us
a
while
to
land
on
something
we
have
consensus
for
so
I
think
fixing
the
filtering
is
a
good
first
step
for
that.
A
I
also-
and
my
memory
might
not
be
right,
because
human
memories
aren't
good
at
this
sort
of
thing,
but
I
also
had
a
memory
of
going
through
the
update
process
and
realizing
that,
like
there
were
places
where
you
click
on
a
button
where
it
should
say
one
thing:
it
says
another
thing,
and
then
you
get
to
the
the
next
page,
and
it
has
some
like
description
text
that's
wrong,
and
then
you
have
to
click
on
a
link
instead
of
a
button
and
there's
just
kind
of
it
just
felt
kind
of
clue.
A
G,
all
the
way
through
the
process
of
like
downloading,
installing
updating,
whatever
and
maybe
like.
There
was
a
redirect
issue-
and
I
remember
going
through
this
and
being
like
this-
is
so
frustrating.
I'm
gonna
create
all
these
issues
and
then
I
found
a
bunch
of
issues
that
you'd
already
created
about
it,
and
so
that's
kind
of
what
I
had
more
in
mind,
but
I
feel
like
I'm
not
sure
how
much
of
the
like
we
might
have
fixed
some
of
those
already
but
yeah.
A
I
think
there
is
a
bigger
problem
of
just
the
starting
point
that
we
also
need
to
fix.
So
I'm
gonna
leave
this
other
wonky
issue
on
here
until
I
have
a
chance
to
search
the
issue
queue
and
see.
If
I
can
find
what
is
in
my
memory
and
if
I
can't
find
it,
I
will
remove
it
and
get
focused
on
the
other
one.
B
B
A
Next
up
is
issue
number
3193
about
getting
promoted
modules
on
the
installer,
gregor
you're
gonna
love
this
so
last
week
or
maybe
two
weeks
ago,
luke-
and
I
were
talking
about
this
ready
to
wear
theme
initiative
and
one
of
the
things
we
decided
we
should
do
is
use
the
promoted
checkbox
for
these
themes.
So
that
way
we
don't
have
to
worry
about
getting
these
themes
in
core.
We
don't
have
the
same
gateways
and
hurdles
and
roadblocks
and
schedule
as
core
stuff.
A
A
A
Last
week
I
went
through
this
main
meta
issue
about
to
to
promote
contrib
projects,
and
I
created
a
list
of
all
of
the
sub
tasks
that
we
have
to
do,
including
a
link
to
a
new
issue
number
43
in
the
project
module,
which
I
thought
we
had
one
before,
but
I
searched
the
current
queue
and
it
wasn't
there.
A
So
I
figured
I'd
just
create
a
new
one
and
if
we
find
another
one
later,
we
can
remove
it,
but
this
is
to
update
the
feed
that
project
module
spits
out
to
include
that
promoted,
checkbox,
and
so
with
this
here
I
think
it'll
I'm
gonna
start
working
on.
A
Oh,
is
that
okay,
I'm
gonna
start
working
on
this
one
to
get
the
feed
updated
and
once
we
have
the
feed
updated,
then
we
can
return
to
core
and
try
and
feel
it
how
it's
going
to
handle
that
data,
and
there
might
be
a
little
back
and
forth
there
about
like.
We
get
the
pull
request
for
the
feed
ready
and
then
we
do
the
core
thing
and
we
realize
the
thing
needs
to
be
updated,
etc.
But
I
think
like
having
at
least
a
place
in
both
cues
to
work
on.
A
It
will
be
good
and
then
I
added
the
two
steps
about
the
adding
a
class
with
some
kind
of
color
and
highlight
here
in
the
main
issue
about
promoting
contrib
projects.
But
we
might
also
need
some
designer
feedback
on
that
and
we.
B
Don't
have
the
latest
so
which
issue?
Is
it
the
one
that
you
were
working?
Is
it
in
the
backdrop
or
queue
or
batch
of
cms.org.
A
So
there's
another,
I
don't
think
I've
created
that
other
issue
you're
right.
We
need
one
in
the
backdrop
or
queue.
Also
the
main
issue
I'm
working
on
is
in
backdrop
core
q,
3193.
A
And
then
there
is
a
link
from
that
to
an
issue
in
the
project
contributed
module
which
is
for
getting
the
promoted,
checkbox
aborted,
you're
right.
We
need
another
issue
which
is
to
update
backdrop
cms.org
with
that
new
version
of
the
project
module,
but
I
feel
I
mean
I
don't
know
I
feel
like
it
should
be
possible
to
do
the
core
pull
request
before
we
get
vector
of
cms
at
work
updated
because
I
want
I
don't
know,
I
want
to
have
the
ability
to
revise
the
pull
request
against
project
module
if
we
need.
A
I
don't
know
that
it
really.
Matters
like
we
could
just
do
like
four
or
five
pull
requests
be
like.
Oh
here's,
one
oops.
We
got
it
wrong.
Here's
another
one,
here's
another
one,
but
I
wouldn't
want
to
do
releases
of
project
module
until
we
got
it
right.
So
if
we
merge
the
pull
requests,
we
can
have
a
dub
version.
We
can
figure
it
out,
but
I
do
want
to
find
some
way
that
we
can
like
take.
This
has
been
kind
of
stuck
with
the
like
there's
so
many
moving
parts.
A
A
B
I
made,
I
may
not
seem
like
it,
but
I'm
excited
as
well
metallica,
so
this
is
as
excited
as
I
get,
but
I
am
excited
I
might
not
show
it
but
yeah,
one
of
the
long-standing
pet
peeves
another
another
thing
that
we
mentioned
in
a
previous,
I'm
not
sure
if
it
was
the
previous
or
the
one
before
that
the
meeting
was
the
thought
that
with
promoted
modules,
we've
decided
or
that's
the
plan,
at
least
to
have
the
promoted
style
of
design
being
the
project
browser,
but
because
by
default,
when
you
go
to
the
theme
management
page,
you
only
have
like
three
themes:
the
basis,
seven
and
buttock.
B
A
I
think
I
did,
I
think
there.
There
was
an
issue
somewhere
about
like
the
making
disabled
themes,
not
a
thing
and
on
that
I
might
have
that
might
have
also
been
where
I
mentioned,
like
redoing.
The
themes
page
in
particular
to
maybe
include
promoted,
mod,
promoted
themes
on
it.
I
don't
think
there
was
a
dedicated
issue
for
putting
the
promoted
themes
on
the
themes
landing
page,
but
I
did
mention
it
somewhere
in
one
of
those
issues,
so
yeah.
B
So
olaf
mentioned
an
issue
in
zulip
earlier
where
he
wanted
to
solve
a
completely
disabled,
color
support
for
a
sub-theme
of
basis,
and
I
created
an
issue
for
that
and
while
I
was
working
on
it,
I
discovered
I
think
I
reviewed
another
issue
with
which
is
related
to
that
page,
and
I
tried
to
install
multiple
contrib
modules.
We
had
a
project
browser
like
13
of
them
at
the
same
time,
and
then
I
was
trying
to
enable
them
to
see
which
ones
which
one
of
them
just
have
these
have
settings.
B
B
B
Go
ahead
with
with
in
conjunction
with
what
we're
trying
to
do
to
make
things
more
discomfortable
and
allow
people
when
they
set
up
a
a
backdrop,
vanilla
installation
to
try
a
lot
of
them,
so
many
people
might
actually,
because
you
cannot
possibly
unless
you
just
rely
on
the
screenshots,
you
cannot
get
a
feeling
of
what
things
are
from
the
project
browser.
B
So
I
was
sort
of
like
pretending
to
be
this
person
that
is
new
to
drupal
or
backdrop,
and
I
would
just
want
to
get
all
the
things
into
a
state
where
I
would
I
would
be
positive.
It
would
be
possible
for
me
to
start
switching
between
them
right.
A
Yeah,
so
there's
a
big,
so
there's
a
bigger
problem
here
that
you're
trying
to
solve
in
a
very
specific
way
your
solution
is
I'm
going
to
put
all
the
themes
on
this
site
and
try
them
on,
but
I
think
this
is
something
luke
and
I've
been
talking
about
too,
is
like
the
bigger
problem
is
like
how
do
you
see
what
it
looks
like,
and
there
are
a
lot
of
different
ways.
C
B
Yeah
sorry
to
direct
you
there,
but
I
know
that
I
remember
the
discussion
that
we
had
that
we
we
needed
to
serve
like
it
involves
infrastructure
like
setting
up
a
site
where
people
can
do
that.
But
in
my
head
it's
going
to
take
some
time
because
it's
going
to
involve
a
lot
of
people
getting
another
domain,
perhaps
or
whatever,
and
doing
that,
whereas
in
the
meantime
we
have
the
demo
sandboxes
and
that's
the
direct
way
of
getting
people
to
try
things.
B
So
if,
if
I
was
giving
a
talk
about
backtrack-
and
I
said
oh,
you
can
test
things,
you
have
the
project
browser
or
whatever
people
would
say
all
right.
Where
can
I
see
what
the
themes
look
like?
My
immediate
reaction
would
be.
Oh,
we
have
the
free
demo,
so
you
go
there
and
spin
one
and
then
they're
gonna
say
great.
That's
that's
great.
How
do
I
preview
the
things
now
and
the
pathway.
A
From
there
good
just
so,
but
there's
like
a
bigger
question
here
like
rather
than
like,
committing
something
to
core
that
no
one
is
ever
going
to
use
in
reality,
it's
only
like
a
preview
tool.
Why
don't
we
like
just
use
the
demo
sandbox
put
a
button
on
the
theme
page,
it's
like
demo,
this
theme
and
like
fire
up
a
sandbox
to
let
you
see
it
with
already
the
theme
on
it
and
enabled.
B
Unless
that's
another
way
to
solve
things
unless
nate
and
anyone
else
has
the
problem
of
spinning
multiple
sandboxes
like
if
a
person
wants
to
imagine
that
you
go
and
have
a
talk
and
then
you
persuade
10
people
in
a
conference
to
start
doing
that
and
each
person
files
a
separate
sandbox
to
test
a
theme.
A
A
B
A
Aren't
very
big
like
most
of
the
time,
so
that
shouldn't
be
a
problem
unless
we
have
a
like
an
issue
where,
like
core
sandbox
base,
gets
deleted,
that's
when
they
get
really
big,
because
every
sandbox
is
only
a
diff
of
like
backdrop
core
plus,
whatever
is
different
in
that
sandbox.
A
However,
I
do
think
it's
worth
considering.
I
think
there
might
also
be
so.
This
is
like
more
big
picture
theory,
but,
like
you
know
how
you
go
to
a
you,
can
go
to
a
website
or
and
to
buy
something
online
and
you'll
find
like
four
products
you
like
and
you
hit
like,
compare,
compare,
compare,
compare
and
then
you
go
to
a
page
where
it
shows
like
all
four
of
them
you
could.
A
C
B
Would
get
me
to
a
spot
where
I
would?
I
would
test
everything
I
was
trying
to
think
of
it
of
a
say,
a
small
shop,
digital
agency
where
they
go
to
the
customer
and
the
customer
says.
Ideally,
I
know
we
know
it
in
that
state
where
we
should
we
showcase
contrib
things
as
being
ready
to
use,
but
that's
where
we're
trying
to
get
right.
So
if
I
was
to
present
a
customer
with
these
options,
I
would
start
a
sandbox
and
then
I
would
like
to
have
them
sort
of
like
preview.
B
Those-
and
I
expect
the
customer
to
say.
I
would
like
to
see
some
dummy
content
just
to
get
an
idea
of
what,
because,
if
they
preview
it
with
with
content
that
doesn't
make
sense
to
them,
it
might
not
be
enough
for
them
to
sort
of
like
make
a
decision.
B
So
there
you
have
the
the
you
solve
that
problem,
because
if
you
create
a
demo
sandbox
which
is
live
for
24
hours,
you
can
only
once
create
demo
dummy
content
there
and
then
start
previewing
the
themes,
whereas
with
what
you
proposed
having
different
sandboxes,
they
would
have
to
recreate
the
demo
content
parenthesis
there.
If
we
do
something
like
umami,
then
that
will
wouldn't
be
an
issue.
A
Yeah,
so
there's
a
lot
of
issues
here
that
I
think
maybe
we
should
write
down
somewhere
and
it
I
don't
know
if
luke
has
started
this
already,
but
it
might
be
good
to
touch
base
with
him
too.
Where,
like
we
need
some
way
to
do
demo
content,
there's
a
contrib
module
that
does
it.
I
don't
think
it
does
it
very
well,
not
like
umami
does.
We
could
have
like
some
kind
of
a
profile
like
drupal,
but
we
would
need
to
make
one.
A
A
I
think
removing
the
ability
to
have
them
enabled
would
be
a
good
first
step
so
that
you
don't
have
to
click
that
button.
If
it's
not
going
to
do
anything
anyway
and
then
putting
something
like
theme
switcher
on
there
might
also
be
good
too.
I
don't
know
theme
switcher
theme,
key
whatever
something
like
that.
That'll
allow
you
to
switch
it,
but
I
don't
think
that
those
any
of
those
things
necessarily
need
to
be
changes
to
court.
Like
I
mean
some
of
them
do,
but
not
I'm
not
sure.
A
A
What
are
the
tools
we
already
have
available
in
order
to
make
this
happen,
and
if,
if
you
change,
the
core
is
easier
to
do
than
setting
up
sandboxes
for
with
sample
content
and
a
theme
switcher,
maybe
that
might
be
if
we
can
get
core
committers
to
sign
off,
but
that
might
be
the
right
answer,
but
I
don't
want
to
start
there.
I
think
that,
like
we
have.
D
A
A
I
think
we
looked
at
it.
I
think
the
maintainer
of
theme,
themekey,
was,
in
the
backdrop
core
issue
queue
arguing
about
some
tool
that
we
changed
in
backdrop
core,
that
that
can
trip
module
needed
and
we
were
trying
to
talk
through
how
you
would
solve
that
problem
in
backdrop-
and
I
think
that
was
because
he
was
working
on
a
port
of
theme-
key
that
didn't
get
done
so
that
conversation
might
need
to
be
revisited.
A
I
don't
remember
where
it
ended,
maybe
maybe
it
was
finalized,
but
I
did
check
for
theme
key
recently
and
theme
switcher
and
we
don't
have
either
of
them.
B
We
don't
yeah,
we
don't
yeah,
so
you
touched
on
one
of
the
issues
that
I
meant
to
mention
and
that's
4559,
which
is
titled
either
remove
the
notion
of
disabled
teams
or
properly
handle
them.
B
A
I
think
that
I'm
not
really
sure
what
the
enabled
status
gives
us
in
backdrop
like.
I,
don't
I'm
not
sure
what
he
gave
us
replace
on
admin
form.
B
Yeah,
so
it's
it's
the
thing,
the
same
thing
with
layout
templates.
Basically,
what
we
did
is,
if
you
disable
one
of
them.
What
happens
is
they're
not
being
offered
as
an
option
when
you
create
layouts,
because
they
don't
work
like
modules?
They
don't
have
install
functions
that
run
and
do
something.
C
A
So
layouts
don't
usually
have
settings
like
we
have
a
configurable
layout
that
is
entirely
settings,
and
then
we
have
a
normal
layout
which
is
zero
settings.
But
themes
are
this
weird
middle
ground
where,
like
they
do
have
settings,
and
so
you
want
an
install
and
an
uninstall
to
be
able
to
set
those
values,
but
I'm
not
sure
I'm
not
sure
that
has
anything
to
do
with
status
because
like
well.
B
B
A
If
maybe
there's
a
better
way
to
have
have
that
because,
like
if
no
theme
has
an
enabled
or
disabled
status,
we
could
add
something
to
the
theme
settings
page.
Like
maybe
every
theme
has
the
themes.
Page
it'll
be
like
install
default
settings
button
and
then,
when
you're
done
with
it
like
remove
default
settings
button-
and
maybe
that's
enough
like
if
it's
not
automatic,
because
with
modules
you
have
to
go
to
the
uninstaller
and
run
the
uninstaller,
and
we
don't
have
an
uninstaller
for
theme.
So
there
isn't
currently
a
tool
to
do
that.
A
A
Same
like
automatic
we're
going
to
delete
your
data
without
you
knowing
it
kind
of
thing,
I
would
rather
it
be
like
a
manual
process
where
we
can
give
you
a
button
to
clean
up
your
data.
If
you
want
or
what's
the
harm
leaving
it
there
right,
that's
what
we
do
now.
B
Yeah
exactly
and
that's
that's
what
what's
the
difference
between
modules
and
things?
I
guess
not
the
difference,
that's
what
happens
with
modules.
We
leave
the
settings
there
in
case
people
want
to
re-enable
them
and
keep
the
settings,
so
they
don't
have
to
reconfigure
things
yeah.
If
that's
a
valid
case
for
themes
or
not,
I
don't
know.
B
B
Yeah,
so
so
so
I
I
have
a.
I
have
worked
on
that
issue
on
my
local
actually
and
we
have
a
specific,
like
a
three-liner
case,
where,
if
someone
selects
a
disabled
theme
to
be
the
administrative
theme,
we
also
enable
it
without
letting
them
know
anything
about
it.
B
B
There's,
there's
no
prompt
to
say
the
same
thing
that
does
with
modules
that
if
you
try
to
enable
a
module
that
has
a
dependency
or
whatever
it
says,
oh
we're
going
to
enable
these
modules
now.
So
I
thought
I
filed
another
issue
for
that
to
either
introduce
a
a
what
you
call
it
a
prompt,
a
confirmation
page
that
says
this
thing
is
disabled
will
enable
it
for
you.
The
person
says
okay
and
then
we
do
that
without
doing
it.
B
You
know
magically
behind
the
scenes
or
completely
remove
disabled
pins
from
the
list
that
allows
you
to
select
admin
things,
which
is
what
d8
does
d8
was
forced
to
do
that
because
they
don't
have
a
notion
of
disabled
teams
or
modules
there
are
they
enabled,
or
disabled
or
uninstalled.
A
B
A
A
It's
it
might,
I
might
also
have
a
mental
model.
That's
different,
like
coming
from
wordpress.
There's
no
idea
of
admin
theme,
not
admin
theme,
but
coming
from
drupal.
It's
always
like.
Oh
you
know,
if
you
have
themes
enabled
the
idea
is
that
anyone
can
choose
from
these
available
themes,
and
you
would
never
want
a
front
end
to
buy
someone
to
choose
a
backhand
theme
for
their
front
end
of
their
site.
A
So
I'm
always
like
no,
no
disable
all
the
backend
things
internet,
but
I
feel,
like
I
don't
know
it's
very
then,
like
there's
also
this
weird
use
case
of
like
some
sites
that
have
editors
who
are
regular
users
like
a
blog
site
where
you
can
come,
create
an
account
and
create
blogs
like
you
might
use
the
front
end
theme
on
the
back,
so
we
need.
B
So
I
know
so
all
these
things
when
I
come
to
this
page
all
these
things
just
I
find
them
as
what
wtf's
for
newcomers
and
what
I
would
like
us
to
sort
of
like
be
more
intuitive.
Have
the
the
interaction
with
the
user
behave
as
someone
would
expect
and
not
do
magic
things
and
the
other.
E
A
B
B
Or
change
the
what
you
call
it:
the
scope
of
the
existing
issue
to
sort
of
like
reflect
that.
B
A
Yeah
I
mean
I'd
like
to
get
more
feedback
too.
My
opinion
is
has
been
clearly
stated,
I
think,
but
I
don't
know
I
I
feel
like.
E
C
A
Write
the
full
request
and
see
which
files
it
touches
and
if
it
turns
out
that
the
only
thing
that
changes
is
the
admin
ui,
that's
a
really
easy
way
to
change.
But
if
there
is
something,
if
there
are
some
other
things
in
there
that
use
that
status,
we'll
need
to
weigh
those
into
the
decision
to
remove
this,
and
I
don't.
A
Just
thinking
about
it
off
top
of
my
head,
but
I'm
sure
we'll
find
it
when
we
try
and
make
that
change.
So
I
think
maybe
this
is.
It
should
not
be
a
final
decision
yet,
but
I
will
add
my
comment
on
that.
I
read
that
issue
originally
and
had
this
thought,
but
I
don't
think
I
added
a
comment
on
there.
B
Yeah
that
my
thoughts
on
what
you
just
said
is
that
in
your
head,
so
we
have
two
kinds
of
people.
I
guess
that
have
separate
thoughts
on
one
side
is
what
you
just
said
that
you
distinctly
have
the
notion
of
admin,
only
things
and
fronted
things,
and
you
just
feel
that
it's
just
wrong
to
even
think
that
an
admin
thing
can
be
used
as
a
front-end,
and
I
agree
with
that.
But
who
would
do
that
like
from
a
perspective
of
a
side
builder
like
you?
B
A
B
Yes,
exactly
or
yeah,
their
purpose
might
be
defined
like
in
the
information
page
of
the
the
theme
or
the
maintainers
might
have
stated
that
this
is
the
purpose
the
goal
of
that
thing,
but
other
than
that
we
don't
have
anything
technically
stopping
them.
So
my
point
was:
while
you
were
saying
that
you
were
like
what,
if
someone
comes
and
selects
that
as
a
I,
don't
want
them.
So
I
disable
it.
You
disable
it
in
order
to
prevent
who
from
selecting
it
so.
A
A
You'd
be
like
what
theme
do
you
want
me
like?
Oh,
it's
spring
summer
fall
right.
I
don't
want
them
to
have
spring
summer.
Fall
back.
End
theme
because
I
know
spring
summer
and
fall
are
going
to
look
good.
I've
tested
it.
It's
a
bland
theme.
It's
worked
on
the
front
end,
but
I
have
maybe
haven't
tested
at
minimal
as
being
yeah.
D
A
B
So
what
you
described
now
is
very
similar
to
the
situation
that
we
have
with
layout
templates,
where
you
say
I've
installed
all
these,
but
I
don't
want
them
to
show
up
when
I'm
selected
selecting
a
layout.
So
maybe
that
would
be
solved
with
the
settings
page.
That
says
make
only
these
things
available
to
people
that
have
the
switcher
on
their
user
page.
A
A
A
B
A
B
A
A
I
liked
I
like
your
comparison
between
layouts,
though,
and
as
soon
as
you
said,
that
envisioned
a
similar
interface,
where
we
have
thumbnails
for
all
the
themes
and
like
little
check
boxes
that
are
like
show
on
act
thing
and
I
wanted
like
immediately
like
I
want
to
build
it,
but
then
I
was
like
wait:
where
does
it
go
and
because
we
don't
have
anything
that
provides
that
feature?
That's
I
was
like.
Oh
it's,
but.
B
B
A
B
A
D
A
We're
running
out
of
time,
so
I'm
just
gonna
say
if
anyone
is
interested
in
other
user
experience
issues,
we
have
a
tag
on
github,
all
issues
start
with
ux
and
square
brackets,
and
there
are
a
bunch
of
them
that
are
good
first
issues.
If
you
want
to
find
a
good
place
to
contribute,
there
are
a
bunch
of
them
that
require
designer
feedback
and,
if
that's
true,
there's
a
little
label
on
it.
A
And
a
lot
of
those
can
get
in
at
any
point,
they
can
go
into
any
bug
fix
release.
They
can
go
into
minor
releases
like
so
they're
good
things
to
get
in
quickly.
You
want
to
work
on
them.
Some
of
them
are
really
hard,
like
the
one
we're
discussing
now
or
like
re
moving
the
updates
section,
but
they
are
fun
discussions
to
have
either
way.
A
We
also
have
a
handful
of
issues
that
need
design
feedback
or
will
affect
the
design
of
products
using
that
design
label.
If
you're
interested
in
specifically
improving
the
design
backdrop,
I
would
definitely
recommend
checking
that
out.
We
have
one
issue
that
affects
design
for
core
right
now
that
we've
been
working
on
for
a
long
time.
It's
issue
number
4095.
A
It
solves
an
issue
with
a
unwanted
gap
in
the
basis
theme
underneath
the
hero
blog,
but
it
is
currently
stuck
because
we
have
not
yet
figured
out
a
safe
way
to
handle
css
changes
for
core,
and
I
think
that
is
a
much
bigger,
harder
problem
that
we're
going
to
need
to
maybe
do
some
like
proven
concepts
of
and
get
core
committer
sign
off
on,
but
we
would
yeah
if
anyone
has
thoughts
on
that,
we
would
welcome
more
feedback.
There.
A
Yeah,
so
that
it
might
offer
a
solution
to
that
where
we
fixed
a
problem
with
image
alignment
like
floating
images
and
clearing.
C
A
After
them
and
ended
up
having
unwanted
repercussions
that
we
hadn't
tested
for
specifically
and
if
we
had
included
incremental
css
changes
in
court
in
a
way
that
were
safer,
the
sites
that
had
already
wrote
css
to
get
around
the
first
problem
would
not
have
been
affected
by
the
new
introduced
css,
because
it
would
have
been
sort
of
out
of
the
way
but
yeah
we
don't
have
that
solution
yet
so
yeah,
I'm
not.
I
mean
I
think,
it's
theoretically
possible.
It's
going
to
be
messy.
A
So
that's
why
I
want
core
committers
to
look
at
it
and
see
if
the
theoretically
possible,
messy
solution
is
acceptable
or
not,
and
then
yeah,
maybe
so
right
now,
I
think
the
current
thought
is
like
don't
introduce
any
css
changes
that
affect
the
front
end
because
it
could
be
breaking,
but
that
really
limits
our
ability
to
make
improvements.
That.
A
E
Hi
hi,
I
haven't
been
around
for
a
while
sorry,
just
life
got
in
the
way,
but
I
am
coming
to
you
today
from
dearwood
minnesota
again,
where
I'm
now
officially
living
for
at
least
the
summer
anyways
yeah.
So
I'm
just
easing
back
in
today.
I
didn't
come
with
anything
in
particular,
but
I
haven't
been
around
for
a
while,
and
life
seems
to
be
calming
down
a
bit
so.
A
Yes,
you
too,
all
right.
It
is
the
end
of
our
allotted
time,
so
I'm
going
to
recommend
that
we
wrap
up
this
meeting
and
switch
over
to
developer
meeting.
Unless
anyone
has
anything
you
want
to
throw
in
our
open
q,
a
section.
B
Well,
I
said
that
I
was
going
to
leave
five
of
the
issues
of
the
ux
issues
we
just
spent
most
of
the
time
in
one
of
them
just
really
quickly.
I
would
like
input
on
44.61,
which
is
with
regards
to
moving
the
setting
for
selecting
the
option
whether
the
the
admin
team
should
be
the
same
as
the
default
thing
out
of
that
select
button,
because
we're
currently,
we
have
a
top
text
that
explains
what
that
special
option
does
and
it's
not
even
being
denoted
as
a
special
option.
B
So
yeah,
I
have
a
couple
of
ideas,
so
that's
one
that
I
would
like,
and
it's
all
related
to
the
admin
page
where
you
manage
things
and
the
drive
for
all.
That
was
your
full
request
for
the
admin
thing
being
used
in
the
login
page,
which
introduces
another
checkbox
there,
which
would
be
dependent
on
this
option.
B
Is
because
if
you
select,
if
you
select
the
default
thing,
then
the
checkboxes
should
go
away
because
they
don't
make
sense.
There's.
A
Only
every
select,
so
you
don't
need
it
right:
okay,
yep
yeah!
This
is
a
good
issue.
Do
you
have
a
preference?
Oh
yeah?
Ideally,
so
your
preference
is
another
checkbox
that
hides
everything
that
comes
after
it.
B
Yes
and
we
don't
introduce
anything
like
we're,
not
blocking
the
ui,
because
we
are
removing
the
help
text
with
explains,
which
explains
this
special
option
and
we're
replacing
it
with
a
checkbox.
So
if
you
tick
that
checkbox
everything
just
goes
away
and
it's
just
the
field
set
the
checkbox
in
just
the
same,
which
makes
it
very
simple.
B
Okay,
I
have
a
full
request
for
that.
Nice.
Oh
five
tests,
I'll
file,
a
pull
request,
I'll
file,
a
pull
request
for
the
other
one,
which
is
also
one
liner,
which
is
basically
changing
the
the
default
thing,
do
not
have
a
capital
letter
and
have
dashes
before
and
after
so
it
makes
it
seem
like
the
any
option:
yeah
drop
buttons.
So
that's
if
the
core
maintainers
do
not
agree
with
the
bigger
changes
that
the
other
thing
brings.
Maybe
we
can
just
at
least
do
that
to
denote
that
it's
a
special
option.
It's
not
a
theme.
B
Yeah,
I
know
it's
also
results
which
also
solves
a
dx
problem,
because
that
cell
saves
up
value
in
the
config
json
file
as
zero,
which
needs
to
be
treated
specially
because
sometimes
it
gets
saved
as
a
number
and
sometimes
it
gets
saved
as
a
string
and
then
yeah
all
whole
lot
of
mess.
So
it
cleans
up
the
dx
as
well.
B
A
All
right:
well,
then,
let
me
go
ahead
and
wrap
this,
and
if
you
guys
are
around
in
two
minutes,
I
will
start
up
the
next
meeting.