►
From YouTube: Backdrop Design & UX - June 18th 2020
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
Right
we're
alive
today
is
Thursday
June
18.
This
is
our
design
and
user
experience
meeting
four-vector
of
CMS.
Before
we
get
to
the
agenda
items.
Let's
go
we're
gonna.
Do
quick
introductions,
you
could
say:
what's
your
name
where
you're
from
and
if
there's
anything
you
want
to
share
with
us
in
30
seconds
or
less
it's
not
on
the
agenda.
A
B
C
B
Design
and
user
experience,
meaning
we
have
an
update
section
in
the
agenda,
but
now
that
the
ready-to-wear
theme
initiative
is
part
of
our
weekly
develoment
meeting
I'm,
not
sure
we
need
to
talk
about
it,
also
in
designing
user
experience,
but
I
thought
if
there
was
anything
in
particular
that
we
might
want
to
dive
into
Luke
in
more
detail
like
if
there's
something
you
need
help
with,
we
have
specific
items
we
want
to
call
attention
to.
It
might
be
worth
mentioning
in
here.
I,
don't
know,
there's
anything
value.
Let's
do
today,
but
I
was
gonna.
B
B
B
C
Right
so
so
here
let
me
let
me
talk
to
that
that
a
little
bit,
because
I
I
think
there
there
might
seeing
facets
to
it
that
are
appropriate
for
actually
each
of
the
three
meetings.
There's
like
design
aspects,
there's
outreach
aspect
and
and
there's
you
know
obviously,
development
and
and
could
project
management
side
to
it
in
terms
of
the
design.
C
So
so,
where
the
design
aspect
comes
in
design
meeting
is
so
so
what
are
those
option?
Well,
what
are
the
things
that
people
choosing
a
web
design?
What
what
drive,
sir?
What
drives
their
decision?
What?
What?
What
do
they
see
and
I'll
give
like
the
obvious
one
that
I'm
aware
of
is
you
know,
there's
dark
and
light
things
where
the
text
is.
You
know
black
on
light
or
a
light
color
on
a
dark
background
like
that.
C
That's
two
options,
but
you
know
so
as
I
know,
that's
a
little
broad
to
sort
of
yeah,
there's
not
a
question.
If
there's
an
obvious
answer
for
okay,
this
is
meeting
great,
but
that's
not
the
kind
of
stuff
that
I'm
wrestling
way
more
more
directly
design
related
I
I
discovered
this
week
that
there
were
a
few
sort
of
good-looking
backdrop
themes
that
is,
that
I'd
never
found
and
and
I
I'm
just
kind
of
curious.
A
lot
of
those
out
there
I
like
sit
there
I
found
Ryan
Drama
starch.
C
A
No
all
of
the
the
fact
that
I,
like
the
initiative
and
where
this
is
going.
Yes,
it's
gonna,
be
a
bit
tricky
to
figure
out
the
details
and
how
to
move
forward,
because
it
is
a
huge
subject
and
there's
a
lot
of
moving
parts
that
we
need
to
figure
out
how
to
sort
of
like
make
it
work
in
a
in
a
way
that
the
user
experiences
as
less
daunting
as
possible.
A
And
then
at
some
point.
Maybe
this
is
to
be
added.
I
think
that
we
have
an
issue
for
it.
It
just
remembered
it
the
other
day,
because
I
was
reading
those
discussions.
It
was
something
that
Wes
saw
as
a
dream
or
as
an
idea
that
you
would
provide
the
it
would
provide
backdrop
with
the
logo
of
your
business
and
then
backed
up
with
exact,
extract,
the
basic
colors
of
your
logo
or
whatever,
and
then
adopt
the
current
thing
to
use
those
colors
or
variations
of
it,
and
there
were
a
few
ready-to-use
libraries
like
native
HP.
A
B
Like
there
is
something
to
a
good
design
that
you
can't
do
by
like
extracting
a
hex
code
from
a
thing
and
I
know
it
like,
based
on
the
color
support
that
we
saw
in
like
Drupal,
6
interval,
7
Lee
and,
like
everybody,
change
the
colors.
If
they're
like
Garland's
website,
you
know
always
looked
like
100
times
worse
than
it
did
originally
so.
I
think
that,
like
we
should
not
provide
utilities
for
making
really.
D
D
B
Say,
oh
I
can
make
it
sort
of
like
this
or
sort
of
like
that
and
it'll
change
all
that
at
once,
and
every
one
of
those
sets
should
be
like
designer
improved
in
that,
like
it
shouldn't
be
like
created
by
a
machine
and
sure
that'll
work,
but
giving
people
the
ability
to
take
that
designer
crypt,
color
and
change.
Like
one
thing,
I
think
is
I
mean
it's
a
slippery
slope
because
they
can
change
whatever
they
want.
But
it's
it's
more
helpful
than
just
being
like.
A
Yeah
I
mean
there's
a
lot
of
things
to
consider
like
the
colors
that
are
going
to
be
chosen,
and
the
foreground
and
background
thing
is
they're
gonna
be
readable,
like
this
is
gonna,
be
accessibility
concerns
as
well.
My
point
was
that
for
those
people
like
myself
that
I
like
have
no
design
or
sense
of
I,
don't
know
what
these
beautiful
or
what
no
and
they
came
out.
A
D
C
E
C
C
So
so
I
would
greatly
support
the
idea
of
themes
coming
with
some
number
of
thinking
approved.
Color
sets
there
that
wouldn't
necessarily
cross
between
themes.
There
might
be
team
specific,
but
just
so
that
again
the
idea
of
okay,
you
know,
choose
the
shirt
off
the
rack,
they're
ready,
they're,
ready
to
wear
kind
of
thing,
and
it's
like
okay
well
pick
one
of
these
colors
color
palettes,
and
that
could
be
another.
Another
thing
that
people
who
aren't
super
super
sophisticated
are
still
able
to
like.
Okay,
there
there's
five
pallets.
B
C
E
D
There
actually
is
a
way
to
restrict
certain
colors
from
being
changed,
so
you
can
say
it
like
this
one
color
code
here,
don't
change
it
ever
yeah
and
it's
just
that.
The
way
to
do
that's
not
really
documented.
Very
well,
and
it's
convoluted,
like
you,
have
to
put
comments
and
then
the
color
module
reads
her
comments.
A
So
I
was
looking.
I
was
trying
to
explore
the
idea
of
making
the
color
palettes
that
we
have
for
basis
be
shareable,
but
the
thing
is
that
the
color
palette
itself
doesn't
do
anything.
It
needs
to
be
tied,
like
its
color
needs
to
be
tied
to
a
specific
element
on
the
page.
So
for
that
idea
to
work,
we
would
have
to
have
one
on
one
sort
of
like
components
or
elements
in
the
things
that
match
between
each
other.
Otherwise,
we're
not
doing
anything
for
you.
B
B
It
could
we've
completely
derailments
on
the
page
and
I,
wouldn't
want
to
try
and
like
even
recommend
predefined,
like
here's,
five
color
palettes,
because
I
think
that's
gonna
end
up
limiting
what
we
had
get
in
the
end
and
everything
should
be
like
I
mean
I,
don't
know
so.
Design
is
all
something
I.
Don't
really
understand,
like
I
can
look
at
something
this
beautiful
and
be
like
wow.
That's
amazing.
B
B
And
I
think
that,
like
you,
could
you
could
like
recommend
stuff
like
that,
but
I
also
think
that
it
would
be
limiting
and
I
would
rather
everything
sort
of
be
wide
open.
I'm,
not
sure
that,
like
I,
feel
like
the
tools
that
we
have
for
this,
they
aren't
perfect.
Like
we
have
color
module,
we
have
the
ability
for
red
pallets.
We
have
the
ability
to
let
you
change,
color
I
feel
like
it.
All
of
that
is
probably
enough,
like
it's
probably
too
much,
but
I
wouldn't
want
to
take
away
anyone's
tools.
B
C
Yeah
yeah,
no
absolutely
I
mean
I.
Might
my
recommendation
here
wouldn't
be
to
add
more
capabilities
or
just
add
preset,
but
like
if
it's
possible
that
pallet
presets
that
you
know
you
can
choose,
then
we're
done?
If
not,
let's
have
that
because
that's
really
what
I
want
is
I
want
pallet
recess
and.
B
C
B
B
You
with
teasers-
or
you
know,
all
of
those
common
elements
that
maybe
don't
exist
on
this
site.
The
theme
was
built
on,
but
are
gonna,
probably
exist
on
every
site.
You're
gonna
put
it
on
later.
We're
not
gonna,
be
able
to
get
everything
because
again,
part
of
what
we
expect
are
powerful
is
that
you
can
do
anything
but
having
some.
B
C
Inspiration
this
morning
and
I,
it
might
not
be
true,
so
let
me
bounce
it
off
you
and
tell
me
this
is
accurate,
but
but
I
was
thinking
about
themes,
because
this
is
on
my
mind,
you
say
and
occurred
to
me
that
all
of
theme
does
is
it.
It
displays
region,
content
right,
so
I
like
the
there
is
the
whole
rest
of
backdrop.
The
whole
risk
the
Internet
everything
that
flows
into
it.
The
theme
doesn't
know
about
that.
C
A
C
A
So
that's
why
we
have
the
layout
templates,
which
are
flexible,
which
means
that
everything
does
not
have
to
implement
this
responsive
thing
like
it's
been
handled
by
the
layout.
So
as
long
as
you
make
sure
that
the
layout
is
responsive,
no
matter
what
what
theme
you
put
on
top
of
it,
it's
still
gonna
be
responsible.
A
A
Is
that
as
a
back-end
user,
like
a
person
exploring
what
what
the
features
of
Batroc
is
as
a
CMS
as
a
tool
to
build
your
website,
it's
just
navigating
the
backend
right
and
these
people
might
be
coming
from
different
other
CMS's
like
they
might
be
coming
from
Drupal,
they
might
be
coming
from
WordPress
I've
noticed
that
a
lot
of
people
prefer
thee
and
minimal
thing
for
their
back-end
and
I
was
wondering
like
what.
What
makes
it
popular
why
people
install
that
a
user?
A
Is
it
the
color
palette
that
it's
using,
because
I
know
that
that
thing
implements
also
like
in
the
Drupal
land?
It
also
implements
things
like
search
fields
in
the
modules
page
or
in
the
permissions
page.
These
things
have
things
that
we
are
either
done
in
that
shop
already
and
they
so
that
everything
would
inherit
it
or
we
have
plans
to
do
it.
So
we
shouldn't
bother
ourselves
with
that
kind
of
personality.
I.
E
C
If
people
don't
realize
that
fun
charli's
there,
it
could
be
a
you
know,
documentation
or
an
interface
issue.
It
could
be
that
the
software
already
does
it,
but
people
aren't
finding
it
and
thus
we're
not
getting
credit
for
her,
so
so
they
and-
and
that
sounds
like
yeah
easy
compared
to
implementing
people.
Yes,.
A
I
was
I
was
going
to
the
appear
in
spades
and
I
was
trying
to
think
it
from
a
perspective
of
a
person
that
is
new
to
backdrop,
not
necessarily
with
drop
acknowledged
either.
So
we
are
happy
that
we
have
the
project,
browser
or
modules
and
themes,
but
if
I'm,
a
person
that
is
evaluating,
match
up
and
I
go
to
the
experience
page.
That
install
new
thing
is
the
project.
Browser,
basically,
is
something
that
we
as
a
community
are
very
excited
and
we
know
how
to
use
the
tool.
We
are
aware
of
its
existence.
A
We
know
that
we
have
to
do
another
three
or
four
or
five
steps
and
then
we'll
get
more
things
right,
but
for
a
person
that
is
like
clicking
through
quickly
evaluating
the
product
as
it
is
it
doesn't,
it
doesn't
become
apparently
obvious,
like
I,
wouldn't
any
constant
like
at
the
moment
that
I
read
install
new
things.
It
is
another
thing
that
I
have
to
do:
it's
not
something
ready
there.
I
don't
want
us
to
go
down
the
path
of
Drupal
where
they
add
experimental
things,
and
then
they
might
remove
it
or
whatever.
A
So
the
idea
with
Jules
was
that
that
we
would
have
promoted
modules
and
those
would
be
at
the
top
of
the
project
browser.
But
I
was
thinking
that,
for
things
specifically,
we
could
have
things
appear
in
the
actual
appearance
space
known
installed,
like
popular
themes
that
we
want
to
promote
or
that
I'm
I
love
popular
see
how,
in
the
themes
page,
we
have
for
each
thing
disable
enable
set
defaults,
set,
enable
and
set
default
or
settings.
A
We
could
show
another
two
or
three
popular
themes
that
make
it
seem
that
backdrop
actually
has
this
variety
of
things
in
that
page
and
have
one
link
say,
install
and
then
the
the
pub
that
says,
install
new
themes
would
be
others
there's
many
more.
We
can
go
here
as
well,
but
these
are
the
popular
ones.
These
are
the
the
ones
that
we've
checked,
that
they
work
with
every
what
you
call
it
they
are,
so
they
are
approved
or
what-have-you
right.
A
B
A
A
So
I
was
thinking
that
what
we
could
do
on
our
end
is
that
we
can
officially
find
a
way
to
decide
which
these
things
will
be
promoted,
and
what
this
would
mean
is
that
there's
a
lot
of
people
from
the
active
members
in
the
community
that
actually
pay
attention
to
any
bugs
and
we
sort
of
like
support
them,
but
not
as
part
of
poor,
but
we
have
more
eyes
on
them.
There's
a.
A
How
can
I
put
it
like
the
rest
of
the
trip
is
best
effort
by
the
people,
the
owners,
the
maintainer
of
these
projects,
but
these
two
or
three
designs
would
also
have
the
attention
in
the
eyes
of
the
14,
so
to
say
so,
yeah.
That
was
an
idea
I'm,
not
sure
how
what
the
process
would
be
amended,
but
that
one
that
was
Michael
all.
C
C
I
ready-to-wear
should
involve
layouts
I
thought
the
ready,
we're
a
theme
since
is
layout
such
a
key
thing
like
scenes
and
layouts
and,
and
who
knows
you
know,
maybe
modules
or
content
or
configuration
or
other
things
like
it
seems
it
seems
like
if,
if
we
factored
it
into
various
places,
to
make
it
more
logically
sensible
for
us,
we
have
to
take
responsibility
for
that
and
yes
and
and
guide
users.
So
okay
and
I
still
give
them
the
ABCD
choices.
Right
like
excuse
and-
and
it
could
be
a
it-
could
be
a
piece
of
men.
E
A
D
C
C
A
My
point
was
that
for
people
that
are
coming
from
other
CMS's
in
there
evaluating
the
product,
people
like
thumbnail,
so
the
appearance,
the
appearance
page,
does
that
we
already
have
thumbnails.
We
already
give
them
an
idea
of
what
I
think
would
look
like,
and
and
if
they
go
to
the
settings
or
customize
the
theme,
then
they
can.
They
have
a
live
preview
that
we've
added,
so
they
can
play
around
with
anything
call
the
support
group
so
we're
there.
It's
just
that.
A
A
Yeah
and
the
other
thing
was
you'll
have
those
people
that
are
for
one
reason
or
the
other,
either
them
as
a
site
builder
as
a
site
administrator
where
their
content
editors
are
used
to
a
theme
that
they
use
in
true
Poland
or
in
WordPress.
So
maybe
we
could
tweak
the
existing
7
theme
to
have
a
wordpress
feel
like
whatever
so,
in
other
words,
a
person
from
WordPress
or
from
Joomla
tries
patro
for
the
first
time,
and
then
they
say
oh
I'm,
annoyed
by
the
fact
that
the
menu
is
at
the
top.
A
A
But
the
reason
why
I
made
the
proposals
or
the
discussion
that
we
just
had
now
is
that
I
know
that
there's
a
lot
of
work
done
in
the
new
Clara
thing
for
Drupal
lying
and
people
might
might
be
saying
you
know
using
that
as
an
excuse
or
a
reason
to
not
choose
back
up
and
say
yeah,
you
know
what
there's
a
lot
of
work.
That's
done
in
Faro
and
I
would
love
to
have
a
thing
like
that.
A
A
D
B
B
That's
true,
I
didn't
specifically
mention
that
they
needed
to
appear
on
the
appearance
page,
but
I
mentioned
that
I
figured
as
a
starting
move
since
we're
working
on
a
like
recommended
modules.
We
could
do
that
same
thing
on
the
Installer
and
that
way
same
sort
of
handling.
It
wouldn't
be
a
special
case.
Anything
but
I
did
also
have
parents
page
or
somebody
thinks
it
would
be
good.
B
I
think
it'd
be
good
too,
and
then
I
added
a
couple
of
lists
of
things
that
we
need
to
figure
out
how
to
do
like
criteria
for
what
makes
a
themed
feature
complete
or
not,
should
be
both
determined
and
publicized
somewhere,
so
that
people
know
like
how
do
I
get.
My
team
up
here
have
a
list
of
things
to
that
they
need
to
do.
B
We
also
might
need
to
have
a
person
or
a
team
of
people
responsible
for
reviewing
the
things
to
make
sure
that
their
future
complete
and
maybe
even
a
process
for
somebody
to
submit
their
review.
So
if
you
had
one
that
didn't
previously
make
it
that
was
reviewed,
but
you
fixed
it
some
way
to
fly
the
people
who
are
in
charge
of
doing
the
review
to
be
like
hey,
I,
fixed
this
thing
I'm
or
you
have
a
new
one-
that's
maybe
not
on
someone's
list.
Yet
that
might
be
good
too,
and
then
this.
A
A
A
What
they
do
is
they
pick
the
admin
email
thing
like
90%
of
them
and
they
tweak
it,
and
you
see
that
content
editors
complain
if,
for
some
reason
that
changes
in
the
back
end
and
they
complaining
the
thing,
look
for
a
Drupal
user.
It's
like
nothing.
The
theme
change
that
can
still
do
my
job,
but
then
is
like
I
can't
work
anymore.
Like
things,
don't
look
the
way
that
it
used
to
so
I
can't
but
I
refused
to
work
with
these,
and
you
cannot.
You
cannot.
A
E
A
Look
it's
the
other
way
around
the
thing.
We
also
have
an
issue
somewhere
to
make
basis,
look,
look
and
work.
They
simply
when
used
as
an
admin
thing.
It
hasn't
been
worked
on,
but
sort
of
like
a
place.
We
spotted
there,
which
means
that
people
are
not
using
it
as
a
Beck.
That's
that's
my
point
yeah,
but
there's
common
things
like,
for
example,
I
would
ahead.
A
Small
things
that
would
make,
as
I
said,
people
comfortable
working
with
the
backend
now
the
other
thing
then,
then
that
you
said
is
we
are
now
making
the
assumption
that
people
are
looking
for
a
theme
that
would
look
beautiful
on
the
side
like
a
front.
End
theme
have
backdrop
already
installed
and
they're
gonna
go
in
the
project
browser
and
seems
weakened
whatever,
so
we
actually
need
like
that
html5
up,
whatever
site
was
offers
previews.
So
we
needed
to
build
something
equivalent
to
the
demo
thing
that
shows
them.
B
So
we
have
the
tool,
we
don't
know
right.
You
just
need
to
figure
out
how
to
do
that.
I
think
I,
don't
know
if
there's
a
core
issue
for
this
already,
but
we
did
talk
about
it
at
some
point
in
the
last
few
weeks
about
how
we
really
great,
if
we
could
give
people
a
preview
option
for
their
site
in
a
new
theme
in
the
same
way
that
we
have
it
in
the
current
theme
in
a
new
color
or
the
way
we
have
like
preview.
B
A
B
I
think
we
need
both
a
place
where
you
can
see
a
demo
like
that.
Somebody
has
assembled
a
theme
that
they've
made
that
can
highlight
like
all
of
the
best
parts
of
it,
but
then
there's
also
like
what
would
it
look
like
on
my
site
and
I?
Don't
know
like
I,
don't
know
how
extensive
that
needs
to
be,
but
just
the
fact
that
we
already
have
the
ability
to
do
like
a
color
change.
B
C
Yeah
make
sense:
well,
maybe
maybe
there
is
no
in-between
stuff.
Maybe
there
has
to
be
your
site
specifically,
but
what
if
it
was
a
site
all
right
like,
essentially
that
we
could
have
a
certain
number
of
templates
there,
like
this
pages
that
are
built
out,
where
you
can
click
and
like
see
that
page
in
other
218,
because
all
you're
doing
is
switching
CSS
right?
Is
that
all
changing
the
theme
thing
yeah
the.
C
A
I
see
I
see
what
Luke
is
saying,
but
the
way
that
I
visualize
it
is
that
we
have
a
separate
demo
sites
like
The
Mummy,
think
that
Drupal
does
with
fixed
content.
We
don't
allow
users
necessarily
to
edit
so
that
it
won't,
they
won't
mess
it
things
up
for
each
other,
and
there
are
existing
tools
like
the
modules
like
the
game,
switcher
and
think
their
user
things.
A
B
B
B
A
What
I
was
thinking
was
a
single
site
that
it's
time
that
there's
a
release
for
a
thing
hold
the
new
version
of
the
theme
and
this
side
would
have
all
the
installed
and
it
would
expose
even
to
anonymous
user.
The
theme
sweeter,
so
they
can
browse
around
without
having
to
wait
for
even
30
seconds
to
generate
something.
A
That's
what
I
was
going
to
answer
so
a
something
that
is
a
separate
domain
like
a
trap,
things
the
port
and
then
each
person
has
their
own
session
ID
browser
session
ID,
and
they
can
switch
things
and
browse
the
thing
with
existing
content
like
dummy
content.
But
every
single
thing
would
be
available,
so
the
vacant
sweets
that
was.
B
It
would
be
good
to
have
it
so
that
works
too
the
one
site
thing,
but
I
don't
think
people
are
gonna
know
how
to
use
theme
switcher
to
switch
themes.
I
think
what
they're
gonna
do
is
go
back
to
where
they
found
the
theme
and
find
another
theme
and
click
a
button,
and
so
we've
got
to
have
it
set
up
so
that
whatever
button
you
click
backdrop
CMS,
don't
work
will
open
the
other
site
with
the
correct
beam
on
it.
So.
A
With
sorry,
the
way
that
these
works
with
other
services
is
that
they
expose
a
and
what
you
call
it
a
constant
ribbon
at
the
top
of
the
site,
which
has
the
controls
to
switch
things.
So
I
was
thinking
that
we
wouldn't
allow
people
to
remove
those
things.
We
wouldn't
allow
them
to
know
the
intent
aside,
but
we
would
make
sure
that
we
have
built
the
site
with
that
ribbon
at
the
top
with
the
theme,
sweets
are
already
exposed
as
a
block
there.
Independently
of
the
rest
of
the
theme.
B
B
F
D
A
Yeah,
it's
like
a
sort
of
like
a
slideshow
with
a
left-right
arrow
thing
browse
through
the
thumbnails
and
then
select
one
and
boom
itself
like
it
gets
the
whole
sites
switches
to
that
thing,
and
then
they
can
browse
around
yeah.
That
would
work
from
a
user
experience
now,
technically
what
technical
challenges
are
there
yeah.
B
A
B
B
Not
sure
that
really
matters
like
I
think
like
will
need
to
have
the
bar
do
this
thing,
but
I
do
think
that
we
need
to
make
sure
that
people
can't
always
get
to
site
with
the
theme
where
are
they
browsed
or
the
site?
One
of
the
sites
didn't
even
have
a
way
to
get
back
to
where
you
were
browsing.
The
other
one
had
something.
B
A
B
B
C
B
We
talked
about
all
this,
maybe
not
in
this
much
detail.
I
don't
want
to
lose.
This.
Is
this
this
so
there's
two
things
we
need
to
do,
one
of
the
most
effective
CMS
org
tasks
to
set
up
a
being
preview
thing
which
we
know
we
need
to
do,
but
I'm
not
sure,
there's
specific
issue
on
it
and
then
the
other
one
is
the
other
thing
updating.
C
C
B
Just
to
review
today's
agenda,
there
were
a
couple
things
for
micropsia
mesto
org
I
just
wanted
to
highlight
that
the
security
update
yesterday
and
a
couple
of
requests
people
I'm
working
on-
have
been
merged,
but
not
yet
deployed.
So
if
there's
anything,
you
really
want
to
have
work
like
done
on
backup,
CMS
torque.
It's
getting
some
attention
right
now,
so
I.
A
B
The
only
thing
that
was
missing
is
that
it
changed
the
size
of
the
search
box
and
the
design
looks
kind
of
funky
and
I
added
a
comment
with
that
recommendation
on
how
and
where
we
could
put
it
back,
but
that
hasn't
been
done
yet
I
figured
I'd,
give
him
a
chance
to
it,
because
now
he
likes
issometimes
finished
his
own
horror
quests,
but
if
he
doesn't
have
a
time
to
do
it
today,
I
might
go
in
there
and
make
a
pull
request
against
his
floor
press
and
see
if
he
wants
to
use
that.
Okay.
B
But
yeah
it's
closed.
We
sort
of
decided
that
we
couldn't
remember
I'm,
not
sure
if
you
saw
it,
we
mentioned
you
on
the
issue
we
were
like.
Does
anyone
remember
why
we
switched
from
a
search
field
to
a
combine
fields,
filter
and
nobody
could
remember.
We
remember
that
we
did
it,
but
exactly
why,
and
now
we
went
back
so
the
current
ProQuest
goes
back
to
the
search
exposed.
Filter.
B
I
did
find
a
core
issue
about
searched,
exposed
filters
and
views
not
working
correctly
and
then
I
found
a
pleura
quest
from
Nate
fixing
it
without
an
actual
explanation
of
exactly
what
the
problem
was
or
what
it
was
fixing.
So
I've
put
all
that
stuff
in
and
I'm
testing
it
I,
don't
I'm,
not
entirely
sure
they're
all
connected,
but
yeah.