►
From YouTube: Backdrop Design & Usability meeting - Jan 3rd
Description
Today’s design agenda: http://bit.ly/2GvdbHK
A
A
Everyone
we're
gonna,
do
a
quick
rundown
on
in
today's
meeting
of
the
Institute's
that
did
not
make
it
in
on
code
freeze
by
January
1st
and
talked
about
whether
they
are
gonna
be
good
candidates
for
as
tasks
that
we
can
still
get
in
between
now
and
the
15th
or
if
they
are
feature,
a
question
needs
to
be
bumped
to
that
1:13
milestone
which
will
go
in
on
May
15th
instead
of
January
15.
So
before
we
get
to
the
products.
A
One
issue
outstanding
for
backdrop,
CMS
or
user
experience
of
selecting
mancha
stints
and
layouts
I
have
a
sort
of
half-baked
pull
request
on
my
local
computer
and
hoping
to
fix,
search
for,
but
I've
been
distracted
by
dr.
up
core
stuff.
So
maybe
now
that
we've
moved
into
the
code
freeze
period,
I'll
get
some
more
time
to
work
on
that.
However,
anyone
else
wants
to
work
on
it.
Oh
definitely
love
help.
We're
basically
messing
with
search
ranking
ordering
based
on
other
things.
So
you
have
experience
in
that
area.
A
B
Ok,
yeah
yeah!
Ok,
thank
you.
Sorry,
it's
too
far
down,
and
so
the
modules
page
we
finally
added
the
ability
for
tags
to
restart
youth
being
used
on
the
modules
page
so
now,
modules
and
their
info
files
can
also
include
tags
and
tacks
are
kind
of
like
a
multi-value
categories,
basically,
where
you
can
intern
more
than
one
tank
for
a
module
and
then
the
way
that
that's
represented
in
these
are
interface
now
is
that
there
is
under
the
little
more
expansion
arrow,
which
is
also
now
an
arrow.
B
We
added
quote
cute
little
arrows
to
to
the
modules
page
where
it
previously,
it
said
more
and
less.
You
know
like
as
you've
got
more
information
for
the
dependencies.
For
example,
tags
are
also
shown
underneath
that
more
expansion
list,
which
means
every
module,
now
has
a
more
less
tab,
because
every
single
module
has
a
a
tag
associated
with
it,
and
that
means
that
up
at
the
top,
why
there's
the
filter
search?
B
A
A
A
B
And
it's
a
pretty
minor
thing
as
far
as
the
functionality
on
the
modules
page,
but
it
doesn't
able
us
also
to
start
using
tags
on
backdrop.
Cms
org
link
projects
are
submitted
or
new
releases
created,
the
the
project
node
on
backdrop,
CMS
org
will
start
collecting,
taxonomy
x'
tags
as
new
releases
are
created,
so
that
modules
and
games
and
layouts
will
be
able
to
categorize
them
and
then,
in
the
project
browser
when
you're
looking
to
install
new.
B
B
B
Yeah,
this
is
a
fairly
minor
update
as
well,
but
the
way
in
which
this
views
page
is
arranged
is
now
slightly
different.
In
particular,
the
thing
that
I
like
the
most
is
that
it
shows
you
a
list
of
all
displays
and
then
all
of
the
paths
associated
with
all
those
displays.
So
previously
it
only
pulled
up
the
first
one
yeah
that
taxonomy
term
one.
Is
it
a
good
example
how
it's
got
yeah?
Okay?
Actually,
that's
a
good
one
too
your
feed!
Oh!
B
A
We
have
issue
number
three,
three,
eight
nine,
which
is
showing
the
old
password
field
on
the
user,
account
page
conditionally,
so
it'll
only
show
up
if
you're
required
to
enter
the
old
password.
So
there's
a
minor
usability
improvement
where
that
field
is
always
there
and
makes
that
forum
feel
a
little
cluttery.
It's
not
always
needed,
it's
not
always
required
and
it's
a
little
confusing
to
people
when
they
need
to
fill
it
out.
So
this
issue,
3389,
was
one
that
was
created
to
make
the
process
of
entering
that
new
password
a
little
better.
A
So
I
think
it
just
requires
adding
like
some
Ajax
to
determine
maybe
just
JavaScript,
determine
when
to
show
and
hide
that
field,
and
then
I
think
there
might
be
some
Ajax
or
special
validation
to
try
and
figure
out
when
it's
required
or
not
because
I
know
states.
Doesn't
you
know
that
part
so
I,
don't
know
how
much
code
change
is
involved
in
that,
but
it's
currently
labeled
as
a
task
and
so
I
thought
that
might
still
be
able
to
make
it
into
1:12.
B
So
I'm
looking
for
the
meet
yeah,
so
our
somewhat
subjective
policy
on
completing
things
is
that
UX
enhancements,
string,
changes
and
bug
fixes
are
still
allowed
within
the
feature
freeze
window,
and
so
this
should
be
allowed
as
long
as
it
doesn't
get
too
complicated
like
if
things
start
looking
like
they're
changing
a
lot
of
things
or
they
have
the
potential
for
regressions
that
we
don't
allow
them.
But
if
it
looks
minimal
and
simple
like
if
it's
just
a
matter
of
states
for
example,
then
that's
acceptable
from
1:12.
A
Great
then,
there
are
a
couple
of
things
that
I,
don't
think
are
gonna
make
it
into
one
awfully
good
to
just
confirm
issue
number
495,
which
was
one
of
my
favorites,
which
was
to
add
a
useful
dashboard
to
core.
We
didn't
quite
that
get
that
done
under
the
wire.
It
looks
like
it
needs
a
little
tiny
bit
more
revision,
improvement
and
probably
handful
more
testers
and
then
that
one
can
go
into
1.3.
So
I
think
that's
something
that
is
excited
enough,
that
we
should
add
it
to
the
roadmap
so
that
people
know
that
it's
coming.
A
A
The
next
one
is
saved
wrapped
in
core.
This
is
issue
3157.
We
had
a
handful
of
issues
about
how
to
handle
the
radio
buttons
versus
submit
button
is
just
to
try
and
make
it
clear,
and
all
the
issues
are
rather
confusing
around
which
parts
would
save
Jaclyn
running,
which
weren't
and
it
looks
like,
there's
a
consensus
from
all
of
those
issues.
That
would
just
be
easier
easiest.
We
just
took
what
this
noob
jacked
module
does,
which
is
the
slight
change
to
the.
A
I
think
it
might
be
our
we
lost
you
from
long
lines
or
it
was
in
end
of
the
leg.
So
quality
significance
trying
to
watch
this
now
or
watch
the
video
later
we
have
been
having
spinner
issues.
We
have
new
internet
service
coming
soon,
so
hopefully
I'll
be
like
this
fella,
so
save
Jackson
core
there's
a
great
contributor
called
save
draft,
and
it's
a
super
drupal
exists
for
backdrop.
A
We
want
to
take
that
same
functionality,
but
it
or
it'll
just
clean
up
the
content
creation
plumb
and
make
it
clear
about
whether
you're
creating
a
draft
or
schedule
post
or
something
that
will
get
published
right
next
issue
is
sticky
submit
buttons.
This
is
something
we've
been
talking
about
for
a
while
aware.
If
you
have
really
long
formed,
we
would
take
the
submit
button,
swear
the
flowing
stick
them
to
the
bottom
of
the
browser
window.
A
There
has
been
zero
feedback
on
that
issue,
since
it
didn't
make
it
into
the
last
core
milestone,
111,
and
so
it
seems
to
me
like
that,
is
not
a
high
priority
for
the
backdrop
community
and
so
I
have
removed
the
milestone
for
any
upcoming
quarter.
Release
and
I
think
that
the
only
way
that
would
make
it
into
a
parties
in
the
futures,
if
there
is
all
of
a
sudden,
a
bunch
of
activity
around
people
being
really
passionate
on
that
feature.
A
It
is
something
people
are
currently
doing
in
theme,
so
it's
not
in
any
way
impossible
to
do
it
in
control.
It's
just.
We
thought
that
might
be
a
good
feature
for
everyone,
and
then
your
lesson,
lot
of
consensus
on
it,
so
I
think
we're
moving.
The
milestone
is
right.
The
right
thing
to
do
there,
issue
number
31
93
about
taking
the
modules
that
are
promoted
and
indicating
that
they
are
promoted
in
the
Installer.
A
So
this
would
be
a
slight
CSS
changed
to
the
Installer
module
listing,
there's
two
things
that
are
required
to
do
that.
I
think
the
CSS
change
is
something
we
could
probably
suck
it
in
for
112,
but
changing
the
way
project
browser
sends
that
data
to
the
system
to
include
promoted
modules
is
much
trickier
and
no
one's
been
working
on
that.
Yet
no
one
being
like
myself
me,
you
know
working
on
it
and
so
I
think
that's
probably
not
likely
to
get
into
112.
Do
you
have
any
thoughts
on
that
knee.
A
So
I
think
like
we
aren't
really
sure
how
much
work
is
involved,
but
because
we
haven't
seen
anything
I'm,
not
confident
in
saying
that
that's
possible.
If
somebody
really
wanted
to
make
that
happen
into
the
code
for
question,
it
was
just
the
CSS
change
its
maybe
possible,
but
I
think
it
would
be
better
to
put
our
focus
on
stuff
that
we
know
they
can
get
in
yeah.
B
Start
starting
new
things-
that's
you
know,
are
kind
of
on
the
wish
list
that
we
don't
have
any
code
behind
at
this
point
is
not
it's
not
a
very
good
use
of
our
time.
I,
don't
think
it's
likely
just
to
cause
frustration
that
people's
trying
to
complete
something
within
this
last
two
week
window
that
hasn't
even
been
started
yet
then
the
likelihood
of
it
even
being
acceptable.
It's
pretty
low,
okay,.
A
So
the
milestone
that
was
on
that
one
currently
was
1x
future
I've,
officially
assigned
113
and
hopefully
that'll,
get
a
little
more
attention
on
that
issue
between
town
and
then
okay
for
112.
It
looks
like
two
sentences
for
design
issues.
It
looks
like
the
Installer
design.
This
is
issue.
2873
was
just
some
CSS
changes
that
needed
to
get
done,
I'm,
not
entirely
sure
about
that.
There
might
also
be
a
change
to
the
table
that
outputs
the
information
for
the
installer
page.
A
So
it's
currently
my
marked
as
a
bug
fix
because
the
installer
doesn't
work
on
mobile,
so
I
would
say
we
would
need
to
see
the
code
for
that
in
order
to
determine
whether
to
go
in
if
it
is
simple,
because
it's
a
bug
fix,
it
can
probably
get
into
112.
However,
if
the
code
change
is
complicated
and
it's
going
to
break
any
other
page
or
has
any
possible
regression
that
bug
fix
might
have
to
wait
for
113.
B
A
A
So
some
of
us
see
that,
as
rather
than
an
in
freshmen
improvement,
because
we
don't
like
those
tests
and
they
shouldn't
be
there,
and
so
if
they're
gone
everybody
claims,
but
other
people
might
see
the
removal
for
those
tops
as
feature
loss,
because
maybe
they're
using
some
control
that
required
that
tab
be
there
in
order
for
it
to
work
properly.
So
we
just
need
to
make
sure
that
the
code-
that's
there,
it's
supposed
to
take
links
and
like
print
them
out
on
the
bottom
of
the
form.
A
It
would
need
to
account
for
any
link
added
by
a
control
without
that
control
box
or
requiring
an
API
change.
So
if
it's
just
a
normal
menu
items,
we
need
to
find
a
way
to
get
that.
Okay,
where
it
is
so
I,
don't
know
if
that's
possible,
but
this
is
a.
It
is
a
sort
of
a
heavy-handed
change
and
so
I
think
having
working,
look
at
that
and
say:
don't
do
this,
it's
gonna
break
my
stuff
or
account
for
this
use
case.
If
you're
going
to
do
it,
it's
gonna
be
important.
A
B
I,
don't
know
this
one
looks
like
it,
it
could
have
far-reaching
implications,
I
think
yeah,
so
I
I
would
say
I,
don't
think,
that's
feasible
and
learning.
We
know
how
we
would
go
about
implementing
it
at
this
point,
I
mean,
and
we
could
probably
do
the
really
simple
things
and
you
know,
use
the
description
on
the
field
or
something
like
that
to
then
covered
it
forgot
password'.
You
know,
but
then
there's
a
lot
of
implications
for
existing
sites.
B
A
I
think
the
current
proposal
was
just
to
take
a
list
that
right
now
there's
two
slate
as
many
local
tests
and
render
them
as
like
a
bullet
list
bottom
of
the
page.
That
was
the
only
thing
we
thought
we
could
do
safely,
where
all
of
the
things
that
were
local
thoughts
are
no
longer
displayed
that
way,
but
it
still
seems,
like
kind
of
a
so
let's
say,
needs
more
discussion
bump
to
113
and
we
can
revisit
in
a
few
months.
A
Okay
last
is
designed
and
themed
the
maintenance
page.
So
right
now
the
maintenance
page
for
basis
is
just
a
white
screen.
It's
in
the
top
left
hand
corner
some
text,
accessories
I
said
no
meaning.
So
whatever
your
main,
it's
message
is
in
theory.
This
could
be
some
CSS
that,
like
centers,
that
information
in
a
box
on
the
little
page
and
it
could
get
into
112,
it
could
also
be
a
lot
more
elaborate.
A
It
could
involve
a
template
file
could
involve
some
other
stuff
that
we
might
want
to
test,
for
that
maybe
wouldn't
make
it
so
I
would
say
it
depends
on
how
drastic
the
code
is
for
this
change,
but
a
simple
change
that
in
person
stage
can
probably
still
get
into
112.
It's
the
usability,
improvement
user
experience
and
usability
and
I
think
that
it's
important.
But
again
we
can't
go
too
far
with
it,
because
we
want
to
make
any
break.
A
Ok,
issues
that
we
know
aren't
going
to
make
it
into
113
and
I'm,
not
entirely
sure
about
this
one.
But
let's
confirm
with
me
issue
number
30
209
had
predefined
color
schemes,
two
phases.
This
is
currently
marked
as
a
feature
request
and
so
I
think.
That
means
it
needs
to
have
tests
that
make
sure
that
the
colors
change
to
the
colors
were
telling
it
to
change
and
because
those
colors
have
yep
and
finalize
those
tests
aren't
final
either,
and
my
guess
is:
that's
probably
not
going
to
make
it
into
112.
I
know
it's
pretty
close.
B
And
I
don't
think
it
needs
tests
actually
because
I
think
that
the
setting
of
colors
is
already
tested,
and
this
is
just
adding
the
predefined
ones.
So
it's
not.
Actually,
we
don't
need
to
test
that
each
color
scheme
results
in
be
the
output
colors,
because
all
the
predefined
ones
do
is
they
just
pre
populate
the
fields?
Okay,
with
that
deep
values
does.
B
B
C
A
If
you
want
to
know
what
tags
are
currently
used
in
core,
there
is
a
page
on
backup,
so
you
must've
org
that
lists
all
the
core
tags,
but
you're
also
welcome
to
add
things
that
don't
exist
in,
for,
like
commerce,
for
example,
is
a
really
common
one.
So
I
would
say
there
are
a
bunch
of
categories
on
drupal.org
that
I
pulled
a
lot
of
these
base.
Suggestion
times
from
I
would
say.
Look
at
those
four
examples:
there's
probably
a
lot
more
there
than
we
actually
need.
A
But
if
you
have
a
module
it
doesn't
fit
into
any
of
the
types
that
were
using.
It's
totally
fine
that
you're
on
that's
what
they're
there
for
and
as
we
find
tags
becoming
standardized
on,
will
go
ahead
and
add
those
to
the
list
on
backdrop,
CMS
network,
so
people
will
say:
oh,
is
it
commerce
or
e-commerce
rates
they
can
figure
out
what
the
official
name
for
that
type
is.
Okay,.
C
And
one
other
quick
question:
what
was
my
quick
question,
these
categories,
for
what
can
get
into
a
like
after
code
freeze?
Is
that
documented
anywhere?
Is
that
just
sort
of
understood,
because
I.
A
We
have
a
page
in
the
handbook.
It's
about
semantic
versioning
I
can
look
forward,
I
think
there's
a
paragraph
on
there
that
we
added
when
we
put
in
code
freeze.
So
it's
probably
in
there
if
it's
anywhere,
if
it's
not,
we
should
add
it
somewhere.
If
you
think,
there's
a
better
place,
we
should
put
it
we're,
also
open
to
feedback
on
where
this
information
should
live.
Okay,.
C
Outreach
meeting
last
time,
I
can
ask
this
now
or
we
could
finish.
The
call
and
I
can
ask
you
then,
but
the
birthday
party
thing
is
in
two
weeks
and
we've
just
got
the
I
think
two
official
announcements
yet
and
I'm
just
wondering
like
if
we
want
to
make
a
last-minute
splurged
or
you
know,
push
to
try
and
get
more
people
to
do
it
or
or
not.
A
What
are
you
doing
on
the
15?
We're
gonna?
Do
this
thing?
Do
you
want
to
do
it?
Yes,
no.
You
know
you
know
nobody
wants
to
take
on
responsibility.
That's
also
fine,
and
it
is
a
little
extra
work,
but
yeah
I
think
it's
probably
best
that
the
parties
that
we
have
scheduled
are
successful
rather
than
that,
they're
being
in
a
huge
number
through.
C
That
makes
sense,
so
the
last
thing
that
we
might
as
well
do
now
I
guess
in
terms
of
outreach,
I,
don't
think
I
heard
back
from
either
of
you.
I
did
that
sort
of
summary
of
the
meetings
last
week
without
making
any
commitment
to
do
that
every
week.
Is
that
a
good
thing
to
do,
or
or
not,
where?
Is
it
I
created
a
blog
post,
I
sort
of
summarized
what
happened
in
the
meeting
last
week?
It
starts
in
the
blog.
C
A
C
A
This
is
great
when
Wes
high
more
time
was
participating
in
our
meetings.
He
used
to
do
little
summaries
on
the
meeting
agendas
or
like
these
are
the
things
where
we
need
help
and
I
thought
that
was
really
useful,
but
the
only
people
that
ever
saw
that,
where
people
who
are
in
the
meetings
in
the
first
place,
so
they
can
see
more
better
to
take
that
information
and
put
it
in
a
public
place
where
other
people
who
are
maybe
more
debates
will
see
it.
C
A
And
I
think
that
it'll
also
be
good
this
week
because
we
have
feature
you
know,
code
feature
freeze
happen,
but
now
we
have
like
that
this
little
window,
where
there's
a
couple
like
she
didn't,
we
get
in
that's
another
good
place
to
kind
of
rally
some
support,
and
even
if
these
summary
issues
from
beings
only
happened
in
the
two
meetings,
like
you
know,
around
code
freeze
and
future
briefs,
I'm
still
think
that's
a
huge
improvement,
so
don't
feel
obligated
you
have
to
do
all
the
time.
Yes,
thank
you
for
doing
it,
especially
right
now.
A
Anything
else
from
unique
around
design,
usability
or
anything
else
we
haven't
yet
talked
about
today.
No,
okay,
let's
go
ahead
and
wrap.
We've
got
twenty
minutes
until
the
next
meeting.
We
will
rejoined
in
20
minutes
to
talk
about
all
of
the
other
features
that
did
or
did
not
make
it
into
backdrop.
Cms
version
one
point
twelve
and
what
else
we'll
be
working
on
for
the
next
week
or
so
so,
thanks
for
joining
thanks
for
watching
now
and
thanks
everybody
who
watches
later.