►
From YouTube: Backdrop Design May 24th
Description
Today’s design agenda: https://bit.ly/2ryauLH
A
All
right
we
are
on
air
is
Thursday
May
24,
and
this
is
a
check-in
meeting
on
active
design
and
usability
tasks
for
backup
CMS,
starting
on
our
website,
backed
up
CMS
to
org.
The
biggest
problem
we
have
on
the
site.
Right
now
is
people's
inability
to
be
able
to
tell
which
modules,
themes
and
layouts
are
running
for
a
backdrop
or
necessary
for
backdrop,
and
that's
because
I'm
on
descent
only
adds
pages
search
box
doesn't
work
very
well.
A
For
us,
the
biggest
problem
is
that
the
title
field
does
not
have
a
heavier
weight
than
the
body
field,
and
so,
when
you
search
for
something
specific,
the
order
that
comes
back
is
sort
of
arbitrary,
rather
than
having
like
the
name
of
the
module
you
search
for
is
the
first
item
in
the
list.
So
that
is
one
thing.
I
thought
of
haven't
tried
it
I,
don't
know
if
they'll
work
or
not,
but
we
do
need
to
figure
out
somewhere
to
make
those
features,
return
the
results
in
the
right
order.
A
When
you
do
a
search,
another
idea
would
be
to
replace
the
views.
A
Filters
on
those
pages
with
core
search,
if
we
could
figure
out
a
way
to
make
the
search
boxes
limit
their
results
in
various
different
interfaces.
So
if
we
could
use
the
module
search
to
search
only
modules
and
the
theme
search
to
search,
only
themes
and
all
I
had
to
do
only
layouts
left
to
be
an
option.
I,
don't
think
that's
a
boring
in
core,
but
there
might
be
a
contributor
in
Drupal
7
that
we
could
use
for
that
or
we
could
write
something
specifically
for
backdrop.
A
That
would
give
us
multiple
search
boxes
and
the
search
boxes
could
have
different
functionality
associated
with
them.
So
that's
an
option.
Another
thing
we
talked
about
was
switching
from
using
core
search
to
solar
search,
but
I'm
a
little
hesitant
to
do
that.
Even
though
it's
a
good
that
for
backup
CMS
org,
it's
not
going
to
be
improving
this
problem
for
everybody
else,
who's
trying
to
use,
search
on
their
own
sites
and
various
different
ways.
Neither
would
be
hacking
around
query
with
a
query
alter
function.
A
But
if
you
know
this
goes
on
for
too
much
longer,
it's
gonna
start
hurting
back
up
that
our
website
isn't
working
well.
So
it's
setting
in
solar
and
getting
solar
search
is
gonna,
solve
the
problem
and
make
everything
better
for
backdrop,
except
for
vector
for
search,
that's
probably
better
than
leaving
it
the
way
it
is
now
so
I
don't
know
if
you
guys
have
any
thoughts
on
which
direction
we
should
move
in
terms
of
fixing
our
model
search,
but
I
am
hoping
to
work
on
that
today.
These.
A
A
custom
thing
that
only
applies
to
the
project
browser
we
might
have
the
same
problem
where
I
don't
know
what
fields
it's
searching
on,
and
it
might
mean
those
fields
to
be
weighted
differently,
but
that
at
least
is
a
very
like
concrete
place
to
fix
it.
Whereas
on
our
website
like
how
to
build
a
module
search
page
on
our
website,
some
arbitrary,
like
we
could
choose
to
do
it
any
number
of
different
ways,
and
so
the
solution
that
we
implant
to
fix
it.
B
A
Looked
extensively
I
know
there
are
modules
for
Drupal
7
that
adjust
the
weight
of
the
fields
for
core
search,
but
I
don't
know
if
those
can
be
used
to
create
different
instances
of
core
search
like
we.
We
would
need
one
that
was
specific
to
modules,
115,
Samanta
layouts,
that's
right
now
we're
using
use
for
that
I
don't
know,
but
I
suspect
there
might
be
a
model
for
people
something
that'll
allow
us
to
bleep
those
exposed
heel
rankings
for
views.
That
sounds
like
a
fairly
common
use
case,
although
it
is
fairly
complicated.
A
C
I'm
not
even
sure
which
way
it
would
be
easier,
I
mean
solar,
has
got
its
own,
I
mean
it
would
solve
the
search
problem,
but
it's
bets
on
infrastructure
overhead
and
we
set
it
up
and
I'm,
not
even
sure
if
we
have
a
Search
API
module
equivalents
available
for
backdrop.
Yet,
although
you
know
that's
important
terrible,
we
do
already
have
it
I,
don't.
A
A
Forum,
so
the
forum
site
has
had
a
couple
of
minor
improvements
recently
and
we've
got
the
search
box
added
and
the
search
results
are
looking.
Ok,
that's
easy
for
search,
we
think
searching
the
whole
site
for
everything,
the
email
templates.
We
have
it
some
feedback
that
they
weren't
super
useful.
Perhaps
too
verbose.
One
of
them
didn't
contain
an
unsubscribe
point.
So
Dhokla
nice
done
a
bunch
of
work
on
that
I
pulled
down
his
progress
yesterday.
It
looks
really
good.
I'm
gonna
merge
it
in
people
yet
today
and
then
we'll
get
those
emails
updated
for
everyone.
A
No,
no
I
think
you
might
have
pointed
out
on
back,
don't
see
enough
to
orbit
there's
something
about
our
code
blocks
that
don't
look
great
or
that
looks
consistent
across
our
sites
and
I
think
it
was
Tim
pointed
out
that
in
the
WYSIWYG
editor
the
drop-down
menu
that
tells
you
what
your
styles
are
is
set
to
a
fixed
width,
and
so
you
can't
read
the
text
of
what
style,
you're,
selecting
and
so
I'm,
not
really
sure
how
much
control
we
have
over
that,
because
it's
just
you
can
either
legit
I,
but
we
can
see,
if
maybe
we
can
like
force
it
either
with
CSS
on
aren't
or
JavaScript
on
our
end
to
make
that
field
as
wide
as
is
necessary
for
the
content
within
it.
A
B
Might
be
related,
I,
don't
like
you
so
my
lessons
in
theater,
but
that's
with
the
be
total
site,
the
if
you,
if
you
select
a
format,
something
that's
in
line
like
within
a
sentence
like
a
bit
of
code,
then
that
does
not
yes
fight
on
the
front
end,
but
you
can
see
them
the
while
in
edit
mode
and
ckeditor.
But
when
you
say
it
doesn't
get
by
what.
A
B
Actually
I
saw
it
while
I
was
editing
weeks,
which
post
about
the
dev
and
backdrop
okay,
I'll
file
a
ticket
from
that,
because
it
just
I
just
messaged
you
on
theater
and
might
get
lost
so
I'll
file
a
ticket.
So,
okay,
great
also
before
we
move
on
from
foreign
thing,
I
had
I
didn't
take
a
lot
of
particles.
I
didn't
have
fun,
maybe
the
whole
building
forum.
A
So
we
do
have
a
forum
at
all
and
I
think
that's
also
a
little
confusing,
because
people
try
and
use
the
forum
I,
don't
think
they're
gonna
get
Quebec
word
form,
but
we're
not
using
the
phone
module
on
this.
One
I
think
like
in
terms
of
what
we
have
that
can
be
reused
as
soon
as
we
come
up
with
what
a
recipe
is,
we
can
take
all
of
the
configuration
that
the
farm
site
is
running
and
package
it
together
as
a
good
use
case
for
our
recipe.
A
So
all
of
that
configuration
is
also
already
in
version
control
on
github
and
so
anytime.
Anyone
asks,
at
least
on
the
forum
how
the
forum
was
made
I
plant
them
in
our
repository
and
go.
This
is
where
all
of
our
stuff
is
and
they
can
use
our
configuration.
It's
like
config
sink
import
in
order
to
get
all
the
content
I've
seen
taxonomy
that
were
using
that
so
I
think
it's
not
a
deal.
A
C
Okay-
let's
see
here
so
gosh
I
haven't
actually
looked
it
nice
to
these
hang
on
so
there's
some
design
related
problems
that
we
have
that
could
use
it
designers,
and
that
includes
issue
28
73,
which
is
a
change
to
the
way
the
requirements
list
shows
up
on
the
installers
like
if,
if
there's
a
problem
that
makes
it
so
that
that
drop
cannot
be
installed.
How
we
display
that
both
on
desktop
and
on
mobile
is
a
bit
uncertain
at
the
moment.
We
actually
have
a
direction
there.
C
That
Olaf
suggested
that
I
think
is
pretty
good,
so
it
could
be
that
that
may
not
need
design
I
so
much
as
as
a
capable
front-end
er
to
do
some
table
styling,
which
is
never
a
a
pretty
thing
to
accomplish.
So
that's
issue
2873,
currently
no
code
behind
that,
but
but
we
have
some
concepts
there
issue
23:53
is
a
database
log
design,
oh
yeah,
and
this
is
we
are
kind
of
stuck
in
May.
Nobody
really
agrees
a
position
here.
C
Let's
see
user
experience
issues,
we've
got
issue
37,
which
is
one
of
our
oldest
issues
regarding
what
to
do
on
the
modules
page,
making
it
so
that
modules
can
be
searched
for
or
categorized
by
more
than
a
single
package.
Name
is
what
we
have
right
now
and
we're
suggesting
that
we,
in
addition
to
packages,
also
have
a
concept
of
tags,
so
that
modules
can
be
grouped
together
in
multiple
ways
both
for
the
main
are
both
for
the
modules
page
and
for
when
you're
doing
a
search
in
the
Installer
module.
C
Two
like
pulling
things
from
by
top
CMS
to
work.
Ultimately
tags
would
be
used
in
both
of
those
places.
So
we
were
discussing
this
issue
before
the
broadcast
started
and
Gregory
and
gender
teaming
up
against
me
here
that
I'm
showing
resistance,
adding
more
user
interface
elements
on
the
modules
page
that
could
be
adding
noise
and
part
of
that
is
probably
paranoia
from
the
module
filter
module
from
Drupal
7,
which
totally
went
over
the
top.
C
But
it's
been
suggested
that
what
we
could
do
here
as
a
compromise,
is
not
add
any
new
user
interface
elements
to
the
modules
page
just
continue
to
only
have
the
search
box,
but
have
the
search
box
include
this
capability
to
search
tags
as
well,
and
then
we
get
the
basic
functionality
of
having
modules
that
can
be
categorized
in
either
the
package
or
by
tags.
But
then
the
interface
of
the
page
at
least
the
control
elements
still
stay
the
same
as
they
are
currently,
which
is
basically
just
a
single
search
box.
C
That
also
happens
to
include
the
ability
to
search
tags.
So
I
posted
an
update
to
that
issue.
At
the
beginning
of
this
meeting
before
we
started
the
broadcast,
if
I
I
take
that
approach,
I
don't
think
anybody
would
anybody
believe
me,
whoever
eq
begins.
Did
it
even
though
it's
less
ambitious
than
what
that
that
issue
currently
encompasses?
C
Let's
see
next
up
issue
2681.
There
is
an
issue
just
that
when
we
split
up
the
way
that
display
modes
work
on
content
types,
the
tabs
or
local
tasks
are
missing
from
those
pages.
We
have
a
pull
request
there
to
fix
that
problem,
so
I
think
Jen
might
jar
to
BC,
so
I
think
that
we're
we're
to
go
actually
on
that
one.
C
Let's
see
issue
31
41,
also
having
to
deal
with
manage,
display
or
manage
view
modes
or
display
modes
on
content
types
looks
like
this
is
a
new
issue
and
new
poll
requests.
That's
the
page
title
there
is
just
incomplete
right
now.
It
just
says
the
name
of
the
content
type,
not
the
fact
that
you're
modifying
a
display
mode
for
that
content
type.
C
B
This
is
related
to
another
ticket
that
I
filed
recently,
it's
not
added
in
the
list,
but
I
think
the
use
of
of
these
warnings
makes
sense.
It's
not.
Next.
There
are
messages
that
we
need
to
convey
to
the
people.
It's
not
you
know,
literature
or
help
text.
That
is
always
there.
It
appears
on
certain
occasions.
Not
always
there.
B
Although,
although
the
less
screen
that
I
see
the
last
screen
shot
makes
it
a
bit
confusing
that
you
see
both
a
warning
that
says
that
you
have
pending
updates
and
one
that
says
no
pending
updates,
but
that's
a
thing
we
can
fix
the
the
messaging.
The
success
thing
to
say:
I,
don't
know
something
as
hunting
right
now,
I'll
think
of
something,
but
still
it's
the
right
direction.
I
think
mm-hmm.
C
Yeah
yeah,
okay,
let's
see
next
up
is
issue
23:02,
which
is
gregor.
You
filed
this
one
that
the
search
box
on
the
account
listing
page,
the
manage
accounts,
main
admin
listing
and
the
label
name,
but
name,
doesn't
actually
search
fields
that
you
may
have
also
set
up
on
your
site
for,
like
first
name
and
last
name,
and
so
the
solution
there
for
now,
because
not
all
sites
have
a
first
name
and
last
name
set
upon
user
accounts
and
even
if
they
do,
we
don't
necessarily
know
what
they're
called.
C
It
is
just
to
specify
that
that
field
searches,
user
name,
not
name
which
could
be
more
comprehensive
and
so
simple
solution.
There
is
just
to
rename
that
label
so
that
it
is
using
them,
instead
of
name
to
make
it
clear
what
we're
actually
searching
and
that
one
is
actually
as
of
yesterday.
So
that's
great.
We
can
knock
that
up
for
the
support
for
future
meetings
and,
lastly,
is
issued
2923,
which
is
adding
settings
to
the
search
bloc
form.
A
C
A
A
B
A
C
B
C
B
Yeah
and
then
might
break
the
consistency
of
the
page,
because
I
see
if
it
is
the
most
recent
limitation
is
what
I
see
in
the
screenshot
there.
What
you
will
have
another
set
of
to
check
box
real
check
box
field
amend
out.
That
thing
would
be
the
opposite.
It
would
be
filled
in
a
checkbox
and
people
I.
A
Think
my
preference
would
be
to
have
the
your
interface
behavior,
how
people
would
expect
where
it
would
say,
show
it
and
then
they
would
get
a
field,
but
if
they
don't
say
to
show
it,
we
would
still
printed
on
the
page
but
would
just
use
the
text
search.
So
it's
not
customizable,
but
it's
still
there.
A
That
would
be
clever
because
then,
if
you
did
have
that
weird
use
case
of
like
hitchens,
they
searched
things
to
say
like
find
a
dog
or
whatever
like
it.
Would
you
could
Eve
have
a
weird
work
around
where
you
wouldn't
need
to
write
custom
code,
I
think
I've
I've
done
that
a
lot
of
times
and
then
use
alright
or
you
have
to
like
change
the
fields
and
configure
the
fields,
and
then
you
change
it
back
to
like
the
other
format
where
all
the
fields
disappear,
but
it's
using
the
field
values.
A
B
B
So
so
you
have
people,
you
know
being
able
to
click
the
checkboxes
that
to
select
modules
from
the
top
list,
the
top
table,
where
it's
modules
without
dependencies,
but
there's
no
submit
button
for
that.
Okay,
this
is
so.
This
is
aux
bud
and
the
other
one
which
is
related
to
that
is
maybe
it's
better
if
you
have
a
single
module,
that
has
a
dependency
and
you
reach
that
tight
like
when
I
was
going
through
the
Installer,
because
it
was
in
my
head
and
because
I
have
in
my
head.
B
I
am
a
sequence,
expect
something
to
happen
at
the
end:
I
whit's,
a
page
where
there's
a
lot
of
literature,
there's
just
a
cancel
button
and
I
have
to
read
to
understand.
What's
going
on,
this
is
sort
of
like
more
I
like
a
task,
and
my
thoughts.
I
still
want
some
feedback
on
that,
but
my
thought
was.
Maybe
we
can
change
the
message
about
above
to
be
an
actual
message,
like
the
text
that
we
have.
The
da
I
mean
info
mentions,
like
a
blue
message
that
says
out
anything
see.
B
This
is
a
similar
case
with
the
text
that
we
had
in
the
Installer
in
the
actual
installer,
where
we
converted
the
text
that
we
had
into
a
warning.
This
does
not
need
to
be
a
warning.
It
can
be
a
employ
message
and
then
perhaps
the
the
help
text
that
is
underneath
there
that
says
these
modules
are
meeting
missing
dependencies
or
even
the
the
entire
role
of
the
module
that
has
a
dependency
I.
A
A
So
it
looks
like
these
are
also
related
to
there's
another
issue
that
I
couldn't
earn
meeting
bugs
Nate,
where
backup
thinks
and
is
less
than
nine
so
like.
If
you
have
a
dependency
like
you
can
see
in
the
screenshots
they're
like
1.10
needs
to
be
the
requirement,
so
he
put
in
like
greater
than
1.9,
but
it
thinks
that
9
is
less
than
10.