►
From YouTube: Backdrop Design June 21st
Description
Today’s design agenda: https://goo.gl/cxFmKm
A
So
the
first
thing
we're
going
to
talk
about
is
backup
CMS
for
the
website,
and
we
don't
have
issued
many
issues
that
we're
tackling
with
backup
CMS
org
right
now,
except
for
this
long-standing
issue,
which
is
issue
442.
In
the
backdrop,
pops
back
up,
CMS
gorgish
your
cue,
which
is
improving
the
search
for
the
modules
themes,
the
layout
search
page
when
we
first
commissioned
the
designs
for
backed
up
CMS
toric
made
these
really
excellent
mock-ups
of
how
how
the
filtering
and
sorting
should
work
on
the
search
page
for
installing
modules,
themes
and
layouts.
A
But
we
never
built
that
out,
and
so
there
are
mock-ups
in
that
issue
that
have
really
great
suggestions
of
how
that
functionality
should
work.
But
it's
not
been
implemented.
So
all
that
we
really
need
there
is
a
volunteer
to
put
in
some
time
to
make
that
mock-up
a
reality
and
where
that
work
would
actually
happen
is
backdrop
CMS
org
has
its
own
project
and
its
own
issue
queue
and
some
git
repository
and
that's
where
all
of
the
activity
is
happening
for
backdrops,
even
a
starboard.
A
A
A
Although
maybe
it's
just
a
matter
of
updating,
you
know,
maybe
that
would
fix
it
in
any
case.
It's
tracked
right
now
and
in
the
forum
site,
because
it
affects
that
site
directly,
probably
figuring
out
how
to
fix
it
on
once.
I
ever
think,
it's
starting
point
and
then
then
see
where
we
can
move
that
upstream.
A
So
these
things
kind
of
happen
when
we
redesigned
the
we
redesigned
the
status
report
page,
but
we
didn't
quite
realize
it
was
also
going
to
infect
the
Installer
and
so
there's
some
suggestions
in
there
about
how
we
could
potentially
improve
these
problems
or
improve
the
display
of
the
information
for
both
desktop
and
mobile.
While
doing
the
installer
I'm,
not
sure
how
many
people
are
doing,
you
know
back
drop
installs
from
their
phone,
but
it'd
still
be
good
to
be
comprehensive
and
are
fixing.
A
Let's
see
the
modules
page
we're
working
on
reworking
the
modules
page
slightly
to
make
it
so
that's
the
filtering
and
searching
works.
A
little
bit
better,
that's
issue
number
37.
We
have
a
compromise
and
that
issue
the
pull
request
needs
to
be
updated
to
adjust
to
the
new
agreement
that
is
reached
in
that
issue.
A
The
short
of
this
is
that
the
only
thing
that
we've
truly
agreed
upon
is
that
when
you
change
the
publishing
state,
let's
say
you're
you're
saving
something
as
a
draft
or
you're
scheduling
it
or
you're.
You
selected
it
to
be
published.
The
button
on
the
node
form
should
reflect
what
action
you
are
about
to
what
actually
you're
about
to
execute.
A
So
right
now
the
note
form
always
just
says
save,
and
we
want
to
make
it
so
that
if
it's
going
to
publish
the
button,
says,
publish
and
if
it's
going
to
be
scheduled,
then
the
button
gets
relabeled
to
schedule
or
save
for
scheduling
or
something
that
matches
the
action
that
you're
about
to
you're
about
to
do.
I
think
that's
best
expressed
an
issue
31:22
and
the
reason
why
this
is
confusing
is
because
a
save
as
draft
is
a
contributor.
Does
this
save
draft
module?
A
It
basically
does
this
exact
same
thing,
and
so
the
concept
of
merge,
save
draft
into
core
and
rename
the
labels
to
match
the
action
that
is
going
to
be
achieved
so
they're
both
two
ways
of
describing
basically
the
same
thing:
there's
some
minor
variation
in
there,
which
I'm
not
actually
sure
what
what
that
variation
is.
But
that's
why
we've
got
two
issues
anyway,
so
we're
all
in
agreement
there
I
think
that
we
really
need
to
just
put
a
pull
request
up
that
reflects
that
goal
and
then
and
then
proceed
from
there.
A
A
A
Let's
see
and
lastly,
the
ones
that
we've
got
slated
for
it
on
the
agenda
is
two
issues
that
relate
to
the
installer
module
that
let
you
install
modules,
the
themes
and
layouts
from
backdrop
issue,
31
42
and
31
43,
which
and
I
have
to
read
read
this
has
to
do
with
dependency
management.
Like
saying
you
know,
if
a
module
is
dependent
upon
another
one,
actually,
Express.
A
I've
wait
a
minute
here,
I
think
I'm
going
to
skip
on
this
one,
actually,
because
I
think
that
we've
solved
this
problem,
that
what
this
these
issues
are
related
to
in
a
way
that
is
different
than
what
is
being
described
here.
There
was
an
actual
bug:
I
think
that
that
was
corrected
with
dependency
checking
and
so
I'm
just
going
to
skip
that.
A
B
There
we
go
so
this
was
done
for
da
cos.
I
thought
that
the
person
maintaining
it
would
be
interested
in
it
seems
like
that
might
not
be
the
case,
but
I,
don't
think
there's
anything
different
in
backdrop.
To
be
honest,
I
think
it's
all
the
same
UI.
So
this
doesn't
take
away
any
functionality
which
makes
it
difficult.
But
you
know
that's
like
a
totally
different
discussion,
but
if,
if
the
functionality
was
changed,
you
could
simplify
this.
B
There
are
some
design
critiques
I've
gotten
so
far,
and
this
is
I
would
say
first
draft
stage
basically
I
was
trying
to
do,
is
group
things
in
a
way
that
makes
sense
for
what
they
do
and
get
rid
of
the
advanced
column,
because
it's
terrible
and
then
feedback
they
got
in
d8
land
on
UX
was
they
wanted
to
see
a
better
preview?
So
I,
don't
know
how
possible
it
is.
B
What's
gonna
show
up
because
I
don't
I,
don't
think
you
necessarily
care
so
much
about
that
fine
details.
So
much
is
like
the
gist
of
what
it's
looking
like
and
there
could
be
other
ways
of
handling
that,
but
that
was
kind
of
a
way.
I
thought
then
I
also
got
the
you
know
URL
parameters
here
and
then
like
a
refresh
and
open
a
new
window
and
again
I,
don't
know
how
plausible
those
are
yeah
and
I.
Also
I
took
some
things
out
of
where
they
were.
B
So,
let's
see
edit
view,
settings
I,
don't
think,
there's
a
really
great
way
to
do
that.
But
I
thought
that
should
be
something
that
was
exposed
somewhere,
but
it's
also
very
tertiary,
so
I
wanted
to
get
that
in
there
and
then
so
display
settings
to
me
is
just
you
know
you,
you
create
a
block
or
a
page,
and
it
has
whatever
options
it
has
and
always
showing
things,
even
if
you
can't
edit
them.
B
So
this
little
question
mark
here
is
just
to
say:
you
can't
edit
the
machine
name
of
this,
but
this
is
what
it
is
and
then
I
felt
like
access
felt
so
Braille.
It
related
to
the
other
things
here
with
path
and
menu
link,
so
I
shoved
that
up
there
and
then
query
just
being
how
stuff
gets
on
the
page,
I
separated
filters
and
exposed
filters,
because
it
creates
an
annoying
multi-step
form.
B
That's
confusing
and
glitchy,
at
least
in
Drupal
7
I
always
have
weird
bugs
with
it,
where
I
have
to
like
go
in
with
CSS
and
like
unhide,
something
or
whatever,
and
it
just
this
way.
You
I
think
you're
you're
telling
the
user
that
you
have
multiple
ways
of
doing
filters
and
maybe
there's
a
way.
We
explain
what
these
are
individually,
but
you
know
this:
is
these
filters
happen
before
without
the
user?
A
B
B
That's
something
that
you
decide
on
the
wizard,
but
is
never
surfaced
again,
and
you
can
never
get
back
to
that
wizard
and
it's
it's
kind
of
good.
Then
it's
good
information
once
you
really
start
to
understand
views
like
you
might
have
set
this
up
a
year
ago
and
forgot
oh,
this
is
maybe
showing
texana
me
terms
to
a
relationship
or
something
weird,
but
it's
actually
working
off
of
node.
B
B
B
I,
don't
like
the
tabs,
I
think
they're,
dumb
and
I
just
having
a
select
drop-down
to
choose
your
display
and
like
tell
people
what
the
hell
of
display
is
because,
like
that's
not
necessarily
intuitive
and
then
the
ability
to
edit
the
display
name
would
just
be
like
it
would
toggle.
It
would
hide
the
select
box
and
make
it
a
text
field
and
then
you'd
be
able
to
save
it
or
something.
I.
Don't
know,
yeah
that
that
is
what.
A
B
Since
I'm
going
to
show
it
client
site
here,
I'm
going
to
pick
a
very
innocuous
view,
all
right,
so
it
would
be
this.
It's
like
content,
:
right
now.
It's
just
part
of
the
thing
and
I
think
it's
kind
of
obnoxious,
because
you
like
it'd,
be
best.
If
these
things
are
on
the
far
left,
just
the
way,
it
would
read
nicer
and
I
wanted
a
way
to
make
this
secondary,
but
still
there.
It's
also
like
the
category
that
this
thing
is
so
it
gives
context
to
this.
It's
kind
of
a
goofy
problem
to
have
yeah.
A
That
content
colin,
is
really
just
that's
just
the
label
of
the
particular
filter,
and
it
just
so
happens
that
it
labels
it
by
default,
content,
colon
and
then
the
name
of
the
filter.
You
can
actually
even
right.
Now
you
can
choose
a
custom
administrative
label,
then
it
will
just
like
remove
the
word
content
and
then
put
something
else
there
who
that
yeah,
it's
kind
of
yeah
it.
You
raised
a
good
point
that
maybe
that
entire
word,
for
the
most
part,
is
superfluous.
A
A
B
A
A
It's
kind
of
interesting
that
array
is
kind
of
a
good
point
that
that
might
be
superfluous,
because
if
it's
like
you
know,
comment
subject,
it's
really
dumb,
then
it's
like
comment,
:
comment
subject,
you
know
right,
but
I
can
see
a
lot
of
places
where
it
could
be
ambiguous.
I
don't
know
maybe,
but
for
the
most
part,
I
don't
encounter
situations
where
it's
likely
to
be
ambiguous
right
right.
B
A
B
Sky,
like
you
know
it,
some
of
these
things
could
just
be
like
little
little
fixes
that
don't
have
to
involve
an
entire
redesign.
I
I
wanted
to
do
a
pie
in
the
sky
to
think
about
what
what
I
would
change
if
I
were
ruler
for
a
day.
Didn't
worry
about
time
or
person,
person,
time
or
code
difficulty,
yeah.
A
Okay,
well,
that's
I'll!
Let
you
go
and
actually
we'll
kind
of
wrap
up
the
whole
meeting,
because
there's
no
there's
no
anything
else
on
you
Jenna.
So
thank
us
and
thank
you.
Everybody
out
there
for
joining
the
meeting
today
or
for
watching
and
we'll
meet
up
again
for
design
tasks
in
two
weeks
and
development
tasks
here
in
30
minutes.
So
thank
you
all
very
much
and
I'll
see
you
guys
soon.