►
From YouTube: Backdrop Design - Aug 30th
Description
Today’s design agenda: http://bit.ly/2MtVcDw
A
All
right,
happy,
Thursday
everybody.
It
is
August
30th,
and
this
is
a
meaning
to
check
in
on
active
design
and
usability
tests
for
backup
CMS
this
week,
because
we're
closing
in
on
code
freeze,
which
should
be
by
the
end
of
this
long
weekend,
so
I'm
guessing
Monday.
The
official
code
freeze,
I,
wanted
to
run
over
a
few
of
the
issues
in
would
to
usability
that
still
need
work
in
order
to
get
them
in,
but
before
I
get
to
there
really
quickly
and
talk
about
a
couple
of
issues
for
back
up
semester.
Org
main
one.
A
There
is
to
improve
these
our
experience
for
selecting,
launches
themes
and
layouts.
That's
a
shoot
and
work
for
42.
We
would
definitely
love
some
help
with
that
one.
If
anyone
has
any
time
we're
interested
in
working
on
and
letting
theme
changes
or
improving
search
queries
that
sort
of
thing
on
the
site
there.
The
other
issues
for
forum
backdrop
CMS
org.
We
have
an
issue
number
59,
inform
queue
about
improving
experience
at
using
the
code
block.
Widget
I
could
use
some
help
with
the
CSS
on
that
one
Wes
had
provided
a
CSS
sample.
A
That
is
not
working
when
I
implement
it
on
forum
site
and
so
I
added
some
questions
there
about
how
he
found
the
selectors,
the
being
was
using
for
his
implementation.
There's
a
bunch
of
crazy
stuff
with
seek
editor.
It's
doing
to
build
the
drop-down
menus
and
I,
don't
know
how
to
and
I
can't
I
can't
inspect
them
to
figure
out
what
the
right
elements
are
there
to
select.
So
I
can
use
some
help
on
there.
Anyone
knows
how
to
game
the
CK
editor
buttons.
A
That
would
be
great
okay.
So
that's
it
for
backdrop,
websites
moving
on
to
the
product,
I've
ordered
these
thigh
their
likelihood
to
be
included
in
the
next
version
of
backdrop,
so
the
first
one
is
stickies
submit
buttons.
This
is
issue
number
566
in
the
backdrop
to
the
current
status
of
that
is
need
to
review.
So
we
have
a
the
ability
to
stick
the
submit
buttons
to
the
very
bottom
of
the
page
that
have
a
really
long
page.
You
don't
have
to
scroll
for
a
long
time
to
get
to
the
submit
button.
A
It's
something
had
been
implemented
in
can
in
on
sites
in
production,
in
the
themes
by
one
of
our
contributors.
We
then
created
it
for
quest
to
do
the
same
thing
in
core
I
haven't
eaten
any
my
sites
yet
but
I'm
hoping
to,
because
that's
a
feature
that
especially
will
like
on
those
sites
that
hopefully
long
at
it
forms
so
ition
require
five,
four
five,
six
six
needs
to
review
and
for
reviewing
issues.
You
can
just
go
and
click
on
this
and
watch
and
take
them
for
a
little
spin.
A
You
don't
have
to
know
any
code,
it's
just
about
trying
feature
and
seeing
if
it
works
better
than
what
it
does
now
and
providing
us
with
feedback.
It's
up
next
issue
is
issue.
Number
37,
so
has
a
poor
request,
but
it
will
for
us,
is
there
needs
work.
This
is
our
long-standing
issue
about
including
the
modules
page
so
just
making
it
the
step
works,
making
the
issue
the
first.
A
Second,
thirty,
something
is
making
it
so
that
modules
can
have
tags
in
addition
to
the
categories
that
they're
grouped
in
people
may
want
to
find
a
module
based
on
a
different
type
of
library.
It
might
be
M,
so
I
didn't
ability
from
on
just
like
pegs
is
your
number
thirty-seven.
They
have.
A
pull
request
includes
that
it
also
includes
more
than
that,
and
there
was
not
consensus
about
the
rest
of
those
changes
being
positive,
so
you
will
do
it
one
more
time.
A
The
next
issue,
what
I
think
is
really
close
is
issue
number
thirty
one,
fifty
five
and
this
is
to
add
a
fourth
message,
type
to
the
site.
So,
right
now,
when
you
get
messages
on
your
site,
they
pop
up
as
success
messages,
for
example
after
submitting
inform
successfully
warning
messages
or
error
messages,
and
we
thought
it
would
be
nice.
A
There
was
another
type
that
was
an
information
type,
because
not
all
of
the
messages
that
are
coming
up
as
success
messages
are
actually
success,
sometimes
they're,
just
information
that
would
be
good
to
communicate
that
differently
to
users.
So
this
is
modeled
after
the
bootstrap
info
type.
It's
blue.
Instead
of
green
issue,
number
3155
looks
like
it
just
needs
a
little
cleanup.
A
The
next
issue,
28:58
I,
think
this
is
just
a
text
change
about
update
dependencies,
and
that
also
needs
a
little
bit
of
work,
but
it's
also
it's
very
close.
So
when
you're
trying
to
rely
on
update
HP
updating
from
triple
the
backdrop
if
you've
missed
an
update,
this
is
the
text
that
will
appear
in
that
instance.
A
Okay,
so
there's
a
couple
more
issues
that
are
at
higher
priority.
They
don't
yet
have
pull
requests,
and
so
these
are
less
likely
to
get
in
unless
someone
is
very
passionate
about
solving
these
problems,
getting
them
in
the
next
few
days.
We
do
have
time
for
usability
issues
after
the
first,
but
they
need
to
be
minor
enough
that
they
won't
require
additional
testing.
So
not
not.
All
of
these
will
qualify
for
that.
The
first
one
is
number
13
83,
which
is
to
update
the
button
text
on
the
submit
button.
A
So
when
you're
saving
the
note
form
you'll
know
whether
you're
saving
that
piece
of
content
as
a
draft
or
whether
you're
scheduling
it
for
later
or
whether
you're
publishing
immediately
so
that
text
will
just
change
in
the
button
and
then
there's
another
issue,
issue
3122.
That
goes
hand-in-hand
with
that
which
is
more
clearly
just
defining.
What
a
draft
is,
what
publishing
that
will
do
and
what
scheduling
later
will
do
so?
There's
some
description
text
not
form
already,
but
it's
all
grouped
together
in
a
way
that
is
not
very
intuitive
for
people
using
the
form.
A
So
the
recommendation
here
is
to
separate
it
out,
but
there's
some
CSS
problems
that
also
need
to
be
resolved
so
that
it's
clear
which
text
is
with
which
button
and
then
other
issues
on
manage
to
display
pages.
So,
if
you're
managing
display
of
a
teaser,
for
example,
the
title
on
that
page
needs
to
be
set,
that's
issued
3141
the
promoted
modules.
A
This
is
something
that
colones
has
been
angling
for
so
we
know
for
sure
we
haven't
much
and
we
want
to
include
it
for
something
like
reference
module
or
something
like
rabbit
hole
things
that
we
have
on
our
list
for
possible
core
inclusion
in
the
future.
We
would
like
to
promote
as
being
a
recommended
solution
to
people
who
are
installing
back
jobs.
A
So
if
they're
having
a
hard
time,
deciding
between
two
modules
will
sort
of
guide
them
in
the
right
direction
or
if
they're
trying
to
install
a
module
that
was
named,
ventricle
7,
it's
not
needed
in
fact,
kara
I
guess,
there's
a
different
alternative.
We
can
recommend
alternative
via
futures
modules,
so
that's
an
issue.
It
doesn't
yet
have
a
pull
request
and
then
the
last
one
is
to
make
it
clearer
when
there's
a
problem
with
dependencies
when
using
the
installer.
A
A
So
that's
it
for
active
design,
usability
issues.
There
were
a
couple
of
other
things
that
came
up
today,
not
related
to
design
usability.
So
we
will
talk
about
those
at
our
next
meeting,
which
is
the
dev
check-in
in
about
15
minutes,
I
mean.
Is
there
anything
you'd
like
to
add
like
to
design
tasks?
A
No,
not
today.
Thank
you,
alright.
Well,
we
did
want
to
run
through
the
agenda
really
quickly,
just
if
everyone
update
on
where
those
issues
are
and
how
like
you're
there
get
in.
So
if
you're
really
passionate
about
any
even
once,
we've
just
talked
about
now,
it's
time
to
get
involved
all
right.
But
since
that's
it
we'll
go
ahead
and
wrap
this
meeting,
and
we
will
try
again
15
minutes
about
other
tasks
for
dr.
111.