►
From YouTube: Backdrop Design - Sept 27th
Description
Today’s design agenda: http://bit.ly/2MunFET
A
All
right
we
are
on
air,
it
is
Thursday
September
27th,
and
this
meeting
is
to
check
in
on
active
design
and
usability
tasks
for
backdrop,
CMS
starting
off
with
backdrop
CMS
org
our
website,
our
primary
focus
there
is
to
improve
the
process
of
selecting
modules,
themes
and
layouts
the
issue
for
that
is
issue,
number
442
and
the
backdrop
semester
or
Q.
We
know
there's
a
bunch
of
issues
would
like
to
improve.
We
have
better
designs.
We
want
to
make
the
search
butter.
We
want
to
include
information
about
projects
that
are
not
needed.
A
All
of
those
things
need
to
be
addressed
in
that
issue.
We
could
definitely
use
some
help
if
anyone
has
some
time
on
our
forum,
site
forum,
backdrops,
CMS
org,
we
have
one
sort
of
major
outstanding
issue.
Everything
else
is
rather
minor,
that
is
issue
number
59,
and
that
is
about
cleaning
up
the
way.
The
drop-down
in
the
rich
text
editor
looks
for
adding
styles
to
your
forum
post
text
and
we
have
sort
of
a
rough
idea
of
how
to
fix
it,
but
no
direct
implementation
of
that
solution.
A
Yet
I
think
last
time
Wes
said
I
said
he
wanted
to
work
on
it.
They
didn't
have
any
time
to
look
into
it,
so
he
does
know
how
to
fix
it,
and
hopefully
he'll
get
us
some
code.
We
can
apply.
That's
issue
number
59
in
the
forum
dive
back
Jeff
CMS
to
org
queue
for
back
up
the
product.
We
have
a
number
of
usability
issues
we
wanted
to
draw
attention
to,
and
then
we
have
one
a
design
issue
that
I
believe
the
design
has
been
finalized.
We
just
need
an
implementation
Nina.
A
Do
you
want
to
enter
these
or
do
you
want
me
to
do
them?
Yeah?
If
you
would
please
go
through
them?
Okay,
so
the
first
one
is
sticky,
submit
button
buttons-
and
this
is
issue
number
566.
In
the
backdrop,
issues
queue.
This
is
an
issue
where
it'll
help.
If
you
have
a
really
really
long
content
form
and
the
buttons
are
all
the
way
at
the
very
bottom
of
the
maybe
you're,
just
changing
something
like
the
title.
A
Having
those
buttons
be
sticky
at
the
bottom
of
the
browser
window
means
you
would
not
need
to
do
quite
as
much
scrolling.
So
this
is
something
that
I
have
wanted
on
several
of
my
clients
sites.
It's
something
that
I
believe
Larrin
has
implemented
in
several
of
his
themes
for
his
client
sites
as
well.
A
So
we
just
need
feedback
on
whether
we
think
this
kind
of
change
is
an
overall
improvement
for
backdrops,
something
that
we
feel
should
go
in
core
or
if
we
think
it's
something
that
should
continue
to
be
implemented
on
a
site
by
site
basis,
like
maybe
it's
not
good
enough
improvement
that
it
would
help
you
know
80%
or
more
of
editorial
teams.
Maybe
it's
only
gonna
help
Lehren
and
mine,
so
I
would
love
feedback
on
that.
We
have
I,
believe,
there's
a
poor
quest
and
a
sandbox.
A
A
The
next
issue
is
a
long-standing
is
ability
issue.
We've
had
about
the
modules
page,
that's
issue
number
37.
This
is
something
we've
been
trying
to
get
done
for
both
the
last
two
releases
of
backdrop.
When
we've
run
into
various
sticking
points
on
each
of
them,
I
think
we
now
have
a
working
poor
request
for
that.
We
just
need
more
review
so
again,
someone
to
go
and
try
the
sandbox
login
and
go
to
the
modules
page
and
see
if
you
think
the
new
modules
page,
there
is
more
useful
than
the
previous
one.
A
The
biggest
change
there
is
that
we've
added
tags.
So,
in
addition
to
searching
for
package
or
grouping,
you
can
also
search
for
tags
that
are
things
that
might
help
you
find
a
module
on
that
page.
So
that's
issue
number
37.
In
the
backdrop,
issues
queue
and
we
just
need
more
help
reviewing
it.
The
next
one
is
to
clarify
the
update
dependency
messaging.
So
this
is
what
happens
when
you
go
to
update
your
site
from
Drupal
to
backdrop,
there's
a
newer
version
of
a
Drupal
module.
A
It
should
tell
you
we
can't
update
this
to
backdrop
yet
because
it
needs
to
be
updated
to
the
latest
rupal
version.
First,
and
previously,
it
didn't
tell
you
which
module
was
having
issues
and
that
we've
got
some
new
messaging
there.
It
looks
like
that.
Pull
request
still
needs
work,
I,
don't
know
if
that
needs
to
be
rebased
or
it
needs
tests
or
what,
but
the
issue
is
number
28
58
and
the
backdrops
issues
queue.
A
If
you
want
to
have
a
look
at
that,
the
next
issue
is
to
change
the
text
on
the
submit
buttons
for
the
content
forum.
So
if
you're
creating
content-
and
you
want
to
change
it
from
published,
unpublished,
the
submit
button
should
say
unpublish
and
if
you
want
to
do
the
reverse
and
take
unpublished,
content
and
publish
it,
the
submit
button
should
say,
publish
so
it'll,
be
a
little
clearer
to
people.
What's
gonna
happen
when
they
click
that
button.
That
is
issue
number
13
83
and
it
looks
like
we
need
a
poor
request
for
that
one.
A
There
was
a
lot
of
back-and-forth
in
that
issue
about
what
we
should
do
in
order
to
improve
the
submit
button
text.
I
think
we
have
landed
on
that
decision.
All
we're
gonna
do
in
that
issue
is
change
the
text
label.
If
there's
another
issue,
that
would
talk
about
removing
the
options
for
publishing
on
publishing
and
draft
and
instead
provide
three
different
buttons
for
that
or
publishing
draft
or
scheduled,
which
is
a
little
bit
more
complicated.
So
I
wanted
to
do
that
in
a
follow-up
issue.
A
We
also
have
related
to
our
new
publishing
options,
issue
number
31
22,
which
would
take
this
there's
sort
of
a
big
paragraph
of
help
text
at
the
bottom
of
the
submit
or
at
the
bottom
of
the
publishing
options
that
tries
to
explain
what
all
of
them
does.
My
recommendation
was
to
separate
that
text
into
an
individual
bit
of
text
for
each
option
and
when
I
originally
implemented
that
pull
request,
we
found
some
design
concerns
with
the
way
that
our
description
text
is
displayed.
So
we
need
a
CSS
update
there
as
well.
A
That
would
take
the
description
text
for
individual
radios
or
checkboxes
and
line
them
up
with
the
label
of
those
radios
and
checkboxes
so
that
it
doesn't
look
like
it's
four
separate
element
the
page,
and
we
might
also
need
a
little
bit
of
vertical
space
clean
up
there
too,
so
that
it's
clear
that
those
three
options
are
part
of
the
same
question.
So
you
know
what
do
you
want
your
published?
That
is
to
be,
and
then
having
three
bullets
that
are
answers
to
that
question.
A
So,
there's
just
a
little
usability
cleanup
on
the
visual
display
of
how
that
would
work.
That
needs
a
little
update,
so
that's
issue
number
31
and
22
and
then
the
next
and
last
usability
issue.
We
wanted
to
discuss
this
issue
number
13
193,
and
that
is
the
idea
of
having
promoted
modules
both
on
the
back
trip,
Sonesta
org
website,
in
the
module
section
and
in
the
feet
of
modules
that
gets
pulled
into
the
module
installer
page.
A
So
this
would
be,
if
you're
looking
for
a
solution
to
adding
a
reference
from
one
type
of
content
to
another
on
your
site,
the
promoted
module
section
would
recommend
the
reference
module
as
opposed
to
the
entity,
reference
module
or
the
references
module.
So
it
helps
steer
people
towards
what
we
hope
will
be
the
dominant
or
most
popular
solution.
A
Even
though
right
now,
we
don't
necessarily
have
numbers
that
back
up
the
fact
that
references
module
should
be
the
most
popular
solution,
so
it'll
sort
of
help
guide
people
towards
what
we
expects
to
be
the
most
widely
adopted
and
also
hopefully,
once
it'll
go
into
core.
So
in
the
future,
if
we're
gonna
take
reference
as
much
one
put
it
into
core
it'll
be
easier
for
people
to
handle
that
update
step.
If
that
module
is
recommended
to
them
earlier,
so
that
when
that
goes
into
core
their
their
process
of
getting
part
will
be
easier.
A
So
I
think
that
that
makes
sense.
We
just
need
some
decisions
on
what
a
promoted
module
would
look
like
on
backdrop,
semester,
org
or
on
the
Installer
browser
itself,
and
then
we
need
to
figure
out
technically
how
to
implement
it
on
the
side
of
our
feed,
so
I
believe
on
our
site.
That
fee
is
generated
from
a
view
it
might
not
be.
It
might
just
be
part
of
project
module.
A
Do
you
happen
to
know
I?
Think
it's
just
private
project
module
I,
don't
think
it's
that
of
you?
Okay,
so
that
might
need
a
little
work
than
to
try
and
figure
out
how
to
get
that
promoted
projects
to
appear
at
the
top
of
that
list,
especially
if
we're
doing
a
search
on
the
client
side,
how
we
would
get
the
recommended
ones
to
appear
at
the
top
of
the
search
results
still
in
an
order,
that's
sensible.
So
that
could
be
a
little
tricky.
A
All
right
next
issue
would
be
design.
We
have
one
design
related
issue
which
is
improving
the
design
of
our
backdrop
installer
for
mobile
devices,
and
it
looks
like
we
have
landed
on
a
conclusion
for
what
we
want
that
to
look
like,
but
we
don't
yet
have
a
flaw
request,
that's
implementing
the
design
changes
and
that
issue
is
number
28
73
and
the
backdrop
issues
Q.
We
did
just
come
out
with
the
release
for
a
backdrop
111
we
are
expecting.
There
will
be
a
handful
of
bug,
fix
or
usability
fix
improvements
on
that
release.
A
But
if
you
are
interested
in
what's
coming
in
the
future,
there's
a
tag
on
the
or
a
milestone
in
the
backdrop,
issues
q4
112
and
that's
where
all
of
these
issues
are
currently
slated.
So
anything
here,
you're
trying
to
find
later,
you
forgot
what
issue
number
it
is.
You
can
go,
look
at
the
mount
stone
for
1.12
and
you
can
see
all
of
these
issues
in
there.
Also,
if
you're,
specifically
interested
in
helping
with
usability
issues,
you
can
search
the
issue.
A
Queue
for
square
bracket,
UX
square
bracket
and
you'll
find
all
the
issues
that
are
related
to
usability
or
if
you're,
particularly
in,
are
some
design
issues,
there's
a
tag
there
audience
design
and
those
should
highlight
issues
where
we
specifically
need
designer
feedback
or,
in
some
case
lenient,
actual
designs
created
for
the
problem
space.
So
that's
a
hopefully
good
place
for
designers
to
get
involved.
That's
all
I
have
on
today's
agenda.
A
No
okay,
then,
let's
go
ahead
and
wrap
this
meeting,
and
we
will
have
another
meeting
in
about
45
minutes
to
talk
about
current
development
tasks
that
are
underway.
Perfect
I've
seen
this
so
thanks
for
watching
everyone,
and
hopefully
that's
a
good
rundown
on
what
to
work
on
next,
all
right,
Thank,
You,
Jen,
everyone.