►
From YouTube: Backdrop Design & Usability - Jan 17th
Description
Today’s design agenda: http://bit.ly/2VsUnMT
This meeting ended abruptly as we accidentally ended instead of stopping the screenshare. We were done at the end in any case. Thanks for watching!
A
Hey
greetings
back
jumpers,
it's
January,
1st
January,
17th
2019,
and
this
is
the
weekly
design
and
usability
check-in
meeting
looks
like
today.
Jen
is
doing
some
traveling.
Lots
of
people
are
busy
after
two
releases
of
backdrop
in
the
same
week,
so
I
might
be
just
going
through
all
of
these
things
by
myself
today,
but
that's
alright.
We've
got
lots
of
things.
They've
been
going
on.
Actually,
let's
see
we'll
start
off
with
backdrops
EMS
org,
the
flagship
website
and
some
UX
and
design
issues
there.
A
We
have
one
long-standing
issue
regarding
the
modules
page
or
the
finding
of
modules,
themes
and
layouts.
The
search
pages
for
those
is
issued,
442
and
the
backdrop
CMS
torgus
YouTube,
and
that's
something
where
we
have
some
designs
that
have
long
existed
to
improve
the
finding
of
projects
on
backtalk,
CMS
org
that
could
be
implemented.
There's
no
status
updates
there
recently
again,
just
mostly
depending
on
front-end
work.
To
make
that
happen.
A
By
st.
Paul
Tim
to
possibly
start
working
on
this
as
part
of
a
virtual
sprint,
C
style,
an
issue
494
suggesting
that
we
take
a
10
day
period
of
time
and
do
some
work
on
fixing
up
back
up
CMS
org
and
the
forum
website,
which
is
a
pretty
great
idea,
just
getting
together,
facilitating
people
that
want
to
help
we're
coming
back
to
up
CMS
story
and
so
he's
suggesting
that
we
do
that
February
first
attempt
which
hasn't
been
any
responses.
Yet
he
just
filed
this
recently.
So
potentially
we
might
see
some
traction
on
improvement,
backdrops.
A
You
must
start
work
and
in
particular
this
this
particular
issue.
At
that
time.
Let's
see
we're
also
moving
forward
on
getting
sandbox
demos
set
up
a
little
bit
further.
We
have
a
little
bit
of
work
on
that.
I'll
actually
show
you
guys
kind
of
what
the
standard
says
that
is.
Let
me
put
the
issue
as
well.
A
It
is
to
422
is
adding
demo
functionality
to
backdrop,
CMS
org
on
the
from
the
home
page
instead
of
spin
up
on
Pantheon
button
instead
having
a
demo
that
looks
like
not
tied
to
any
particular
vendor
and
doesn't
require
a
permanent
sign
up
for
an
account
or
anything
like
that.
So
I'll
show
you
guys
that
real
quick,
so
here's
our
agenda
for
today
and
issue
422
is
creating
a
backdrop
demo
site.
There's
a
little
screen
cast
here,
showing
the
demo
as
it
exists
right
now,
but
I'll
actually
do
this.
A
We
could
potentially
also
put
a
video
that
plays
like
when
you
hit
create
demo,
as
well
as
collecting
things
like
email
address.
We
could
use
this
as
an
opportunity
to
like
sign
somebody
up
for
the
mail
chimp
sign
up
newsletter,
which
is
actually
down
here
at
the
same
time
as
they
created
demo,
but
the
basic
functionality
right
now
is
just
great
demo,
so
you
click
and
then
the
Ajax
it
processes
the
form.
A
Kind
of
special
things,
or
no
special
profile,
or
example,
content
or
anything.
It's
literally
just
an
install
a
backdrop
out-of-the-box
yeah.
Maybe
we
could
improve
on
these
things,
so
this
is
powered
by
a
separate
repository,
so
we
could
potentially
create
a
custom
profile
that
has
different
content
in
it
or
sets
default
title
or
any
other
kind
of
thing.
So
that's
an
area
in
which
we
could
iterate
on
potentially,
but
if
we
have
any
more,
you
know
feedback
as
to
how
this
whole
thing
works.
You
can
go
over
here
to
fact
web
CMS
org.
A
A
A
Admin
bar
icons
got
added
just
under
the
wire
and
actually
in
this
new
sandbox
that
I
I
just
spun
up,
which
is
the
the
latest
version
of
backdrop
from
the
one
dot
X
branch.
You
can
see
up
here
at
the
top
that
we
now
have
these
little
icons,
underneath
the
admin
bar,
which
is
just
a
great
little
improvement
that
happened.
Kind
of
at
the
last
minute,
also
looks
and
works
great
on
the
mobile
version
of
the
site
as
well,
except
I'm.
A
A
A
Sorry
took
my
second
to
find
out
where
the
sandbox
actually
was
it'll
go
here.
Well,
I'm,
not
sure
you
signed
into
this
sandbox
dashboard
actually
hasn't
been
updated
to
deal
with
the
icons.
Yet
so
you
can
see,
dashboard
is
added
up
here
to
the
admin
menu,
but
it
is
not
does
not
have
an
icon
quite
yet,
and
so
this
is
the
dashboard
as
it
stands
right
now,
yeah
definitely
an
area
in
which
it
could
use.
A
I,
don't
know
a
little
bit
of
additional
thought,
it's
kind
of
like
a
fire
hose
of
information
right
now
with
no
real
design
aspect
to
it,
but
this
is
just
a
normal
layout
that
just
has
some
blocks
positioned
on
it
so
dashboard.
When
you
install
it
out
of
the
box,
it
just
uses
one
of
the
existing
layouts
for
the
50/50
split
and
then
places
a
bunch
of
blocks
that
it
ships
with
to
provide
some
basic
dashboard
like
functionality,
I
think
it's
a
great
idea.
A
The
blocks
that
comes
with
are
also
really
pretty
useful,
but
I'm
feeling
like
this.
This
could
definitely
use
some
design
to
it.
I'm
not
sure
if
that
needs
to
be
a
block
or
not,
but
this
is
the
current
status
of
it.
Definitely
just
like
you
know,
bare-bones
information
kind
of
presented
right
in
front
of
you.
It's
mostly
almost
entirely,
actually
a
port
of
the
total
control
module
from
Drupal
7.
So
still
it's
coming
along,
there's
a
good
chance
that
this
would
be
in
1.13,
so
that
issue
definitely
could
use
some
additional
feedback.
A
Let's
see,
save
and
save
draft
in
core
is
issue
3157.
This
is
a
really
simple
proposition.
Actually,
it's
not
actually
about
like
saving
temporary
entity
objects
or
anything
like
that.
It's
really
just
a
simple
Justin
that
we
change
the
buttons
change
the
submit
button
on
the
form
as
you
change
the
action
like.
A
If
you
click
schedule
for
later,
it
should
change
the
submit
button
to
schedule,
publication
or
scheduled
for
later,
and
if
you
have
it
checked
as
unpublished,
it
should
have
the
button
label
be
save
as
draft
so
really
simple
in
concepts,
maybe
not
so
simple
to
implement
that,
just
as
you
make
changes
to
the
form,
the
submit
button
just
updates
its
label
to
reflect
the
action
that
you're
going
to
take
so
no
code
behind
that
one,
yet
at
least
not
in
a
port
list
state.
This
is
just
the
save
draft
module.
A
Let's
see
promoted
modules
from
the
Installer.
This
is
just
an
idea
that
we
would
make
it
so
that,
as
you
use
the
Installer
module
to
browse
and
find
projects,
we
might
like
call
out
a
little
highlight
on
a
particular
project,
saying
that
they
are.
You
know
like
supported
by
a
security
team
or
possibly
going
to
be
moved
into
core
things
of
that
nature
that
could
potentially
flag
them
as
being
special
in
some
way.
This
is
all
just
conceptual,
there's,
add
any
any
code
behind
it.
A
A
So
our
hope
is
that
we
could
somehow
get
rid
of
this
new
password
field
and
show
it
only
conditionally
if
it
were
actually
required
to
enter
your
current
password.
And
so
there
have
been
some
suggestions
here,
like,
as
you
start,
changing
your
email
address
or,
as
you
start,
changing
or
typing
in
a
new
password
that
the
current
password
field
appears.
A
A
A
Let's
see
design
related
issues
for
this
are
for
backdrop
itself.
We've
got
issue
3209,
adding
predefined
color
schemes
to
basis
it's
it's
pretty
much
good
to
go.
We
could
use
some
more
review
on
that,
but
it's
kind
of
been
languishing
without
any
feedback,
even
though
it
has
a
pull
request
and
it
has
predefined
color
schemes.
We
basically
just
want
to
feel
confident
that
the
choices
that
we've
made
are
good
ones,
but
really
this
is
pretty
much
good
to
go.
A
There's
two
ways
we
can
go
about
this.
We
could
put
it
into
basis
exclusively,
in
which
case
it
would
only
affect
the
out
of
box
theme
or
we
could
actually
restructure
the
menu
to
make
it
so
that
the
reset
password
becomes
a
menu
callback
instead
of
a
default
or
instead
of
the
local
task,
which
turns
it
into
a
tab
like
this.
A
The
latter
approach
has
pretty
far-reaching
consequences,
though
it
could
well,
it
will
affect
pretty
much
every
sites
login
form
if
we
change
the
menu
types
which
there's
some
argument
to
me
to
be
made
for
that.
That
would
be
a
good
thing,
but
there's
also
you
know,
the
potential
for
breaking
sites
is
pretty
high
there.
So
there's
discussion
going
back
and
forth
about
how
to
implement
that
and
also
like
if
it
is
something
that
should
be
implemented
or
if
there's
any
ways
that
that
could
be
improved.
A
Issue
2873:
there
aren't
any
updates
on
this
issue
regarding
the
installer
appearance
when
you're
on
mobile,
so
backdrop
when
you
install
it
on
mobile,
actually
does
work
well
up
until
the
point.
If
there's
any
errors,
then
it
prints
this
large
table
of
problems
at
you,
even
if
you're
on
a
mobile
device-
and
it
doesn't
look
good
so
there
aren't
any
updates
here
so
I'm
not
going
to
recap
it
and
a
relatively
new
issue
kind
of
similar
to
the
installer
is
the
maintenance
page
that
the
maintenance
page
in
basis
doesn't
look
good.
A
It's
completely
unstyled,
so
here's
a
screenshot
of
how
it
shows
up
right
now,
I
mean
there's
just
no
margins,
no
centering,
nothing,
and
so
there's
nothing
behind
this
yet
and
no
suggestions
as
to
how
we
could
improve
it.
It's
just
like
clear
that,
even
if
we
did
something
really
simple
like
what
Bartok
does,
where
it
just
centers
it
and
puts
a
grey
outline
around
it,
it
would
be
an
improvement
over
the
current
maintenance
page
shown
in
basis
which
doesn't
have
any
any
kind
of
styling
at
all.