►
From YouTube: Backdrop Design - Aug 16th
Description
Today’s design agenda: http://bit.ly/2LXdcCu
A
All
right,
it
is
Thursday
August
16th,
and
this
is
a
meeting
to
check
in
an
eye
on
active
design
and
usability
tests.
The
bathtubs
a
mess
I
mean
I
apologize
in
advance
because
I
have
two
fighting
kittens
in
here
and
by
fighting
in
me,
pointing
if
you
hear
any
weird
noises.
That's
probably
look
at
this
all
right,
so
black
poop
sea
monster
org.
A
We
have
one
major
user
experience
area
we're
hoping
to
work
on
soon,
and
that
is
the
process
for
selecting
module,
students
and
reactants
on
your
site
and
hopefully,
as
we
get
that
process
cleaned
up,
it'll
also
be
easier
for
people
to
determine
the
state
of
any
given
module,
team
or
layout.
So,
for
example,
if
you're
any
people
seven,
so
you
can
search
for
a
model
your
site's
running
and
if
that
site
doesn't
need
to
be
installed
on
a
backed
up
site.
You
should
have
some
information
on
the
module
search
page.
A
A
That
also
include
design
related
changes
to
the
modules,
themes
and
layouts
pages,
as
well
as
the
search
results
and
so
I
think
you
just
need
someone
to
kind
of
look
at
that
and
grab
anything
that
they
think
they
can
handle
and
help
us
kind
of
make
progress
on
that.
So
there's
also
designed
clear
that
people
want
to
work
from.
This
is
something
that
we
already
have
I.
Think
the
biggest
issue
is
just
getting
off
and
leave
all
page.
A
All
right
next
website
forum
got
backed
up
CMS
dot
org.
We
have
one
issue
that
I
actually
was
working
on
right
before
this
meeting
started,
which
is
to
make
the
drop-down
widget
for
code
block
not
cut
off
the
needs
of
the
styles
or
within
it,
and
one
sent
me
some
CSS
that
I
can
put
on
the
websites
that's
and
I'm
working
on
having
right
now.
So
hopefully
that'll
be
done,
maybe
not
before
the
next
meeting.
But
this
afternoon
is.
A
It's
an
issue
anywhere
that
the
name
of
the
code
block
Styles
is
sufficiently
long
because
the
drop-down
which,
if
it's
you
can't
either
provides,
is
too
short.
So
we
also
haven't
mentioned
in
our
issue
that
we
should
file
on
upstream,
taking
it
what's
the
cancer
to
make
the
width
of
that
drop-down
as
long
as
the
content
inside
it.
So.
A
Having
to
fix
on
every
site
based
on
the
configurations
of
that
site,
so
ideally
that
would
be
a
JavaScript
fix.
We
don't
have
the
solution.
We're
putting
on
the
forum
site
is
the
CSS
fix.
We
could
add
a
JavaScript
fix,
that's
distinct
from
so
you
can
be
their
angel
active
core.
That
would
fix
it
on
all
sites
and
that's
also
maybe
a
good
temporary
solution.
Until
we
can
get
that
stream
fixing
to
see
character,
seven
Armando
take
to
him
if
you're
thinking
about
it
it
could
you
file
an
issue
against
dr.
core
and
reference.
A
A
B
A
B
A
A
B
A
A
If
you
wanted
to
see,
if
you
could
tackle
that
it
would
be
to
grab
a
copy
of
the
forum
database,
which
we
should
have
a
sanitized,
automated
backup
being
created
only
to
check
and
see
like
what
directory
to
put
into
and
then
there's
a
you
should
be
able
to
grab
a
copy.
I.
Don't
remember
the
exact
procedure
for
that,
but
we
tried
to
send
up
to
it.
I
mean
we
could
grab
a
copy
of
any
of
the
backup
sites
and
work
on
them.
A
So
I
think
that,
even
if
you
can't
get
a
copy
of
this
site,
you
can
get
a
copy
of
the
site
configuration
from
the
repository
and
you
might
be
able
to
do
like
a
full
site
and
a
big
thing,
sorry
think
I'm
forgetting
and
if
you
can
get
a
config
sink
you'll
get
the
content
types
of
the
view
on
your
local
and
then
you'll
be
able
to
make
changes
to
that
view
just
from
the
codebase.
A
So
you
won't
have
the
content
you
won't
be
able
to
like
determine
if
the
search
is
working
better
than
it
was
before.
But
things
like
adding
expose
filters,
you
might
not
need
the
content
or
you
could
use
you
know
example
content
and
then
once
I
can
get
that
information
for
you
about
how
to
grab
sanitized
stacked
up
with
the
swamp
site,
you
can
plug
any
money.
The
tests
add
weight
to
them,
so
the
general
process
would
be
right.
Now
this
is
assigned
to
me
and
then
on
assignment
to
me.
A
A
C
C
C
C
A
A
A
C
Okay
right
so
we're
using
the
github
SSO
on
our
sites,
because
I
haven't
ported
the
sam'l
module.
Yet
okay,
it
works
fine,
as
as
far
as
our
testing
is
gone,
I
don't
see
any
security
issues
with
it.
It
it's
limited
in
that
it's
only
synchronizing
your
github
username
and
the
relationship
to
get
had
so
it
doesn't
have.
It
doesn't
move
any
of
your
real
name
credentials
or
any
profile
information
from
forget
that
we
start
to
fill
that
out.
C
A
We
were
planning
on
using
I
know
if
we
ever
looked
into
github
single
sign-on.
It
was
on
our
agenda
for
a
while,
and
then
it
got
pushed
to
lower
priority.
So
I'm
not
sure
we
even
thought
that
far,
but
right
now,
all
like
none
of
our
backup
sites
are
tied
together
in
any
way
as
far
as
users
go.
The
only
thing
is
that
we
have
our
packaging
scripts
at
one
side
like
they've,
seen
a
sort
when
types
of
creating
and
we
didn't
have
group.
A
So
that
is
the
only
connection
between
the
two
sites
so
far,
all
of
earth
between
our
site
and
anything
on
github,
so
for
all
of
the
art
bot
stuff
is
just
on
github,
so
it
will
take
like
existing
github
users
and
have
access
to
github
repositories
or
it'll.
Take
yeah,
that's
it
so
it
doesn't
have
any
interaction
with
our
sites
or
properties.
So
I
think
longer
term.
A
We
are
probably
going
to
want
to
see
more
sophisticated
integration
and
we
will
need
to
do
single
sign-on
as
well,
so
that
we
can
confirm
that
people
on
the
backup
site
are
people
on
github,
but
I
think
the
primary
goal
for
singers
single
sign-on
was
just
to
make
it
so
that
people
who
already
have
github
accounts
don't
have
to
create
a
new
account
on
dr.
up
semester.
Org.
It
was
just
sort
of
a
makes
it
easier
to
get
new
registered
users
school.
A
C
B
A
We
don't
need
to
have
this
as
like
an
association
to
get
public
mount
in
order
to
do
that.
There
were
a
couple
of
different
recommendations.
I
saw
in
different
issue
queues
about
adding
on
lines
like
in
Montes
info
file
that
might
contain
a
github
username,
and
we
could
we
could
just
as
easily
try
and
figure
out
the
github
user.
That's
like
pushing
the
project
to
do
that
in
a
week
that
we
need
that
info
file,
because.
A
C
A
Access
I,
don't
I,
don't
think
we
should
take
github
tasks
that
people
who
have
to
have
experience
and
put
it
behind
a
backdrop
website.
Wall
I.
Think
that,
because
we're
gonna
be
losing
like
that'll
break
the
knowledge
that
people
already
have
about
how
to
use
github,
so
I
think
what
we
should
do
and
I
don't
know
whether
it's
worth
going
back
in
fixing
all
the
projects
that
are
there
now.
A
Whatever
permission,
it
is
for
them
to
be
a
contributor
with
the
role
administrator
and
then
that
person
would
not
have
the
ability
to
add
any
additional
company
things
in
the
same
way,
but
they're
doing
on
github
with
github
schools,
and
they
wouldn't
need
to
be
logged
into
vector
of
schema.
So
org,
or
even
have
a
backup,
Simas
or
account
in
order
to
make
that
happen.
A
So
I
think
we
should
definitely
fix
the
permissions
in
in
the
way
where
only
the
contributors
have
access
to
the
repository
and
the
security
team
has
access
to
the
repository,
and
probably
the
bug
squad
in
the
future
will
have
access.
They
commit
access
to
the
repository,
but
not
everybody
in
the
group
will
have
access
every
repository,
but
I
don't
think
we
need
any
integration,
looks
like
I've
seen
this
at
work.
To
make
that
happen.
That's
just
yeah
hooks
API
the
integration.
A
With
fact
our
CMS
org,
where
that
came
from
was
if
you
were
a
maintainer
of
a
project.
We
wanted
to
give
you
the
ability
to
edit
that
note
on
dr.
up
CMS
at
work,
and
we
need
some
way
to
tie
your
github
username
to
your
backdoor,
see
my
Stewart
username.
If
you
have
one
in
order
to
have
that
control
over
the
project,
so
I
think
in
that
case
we
should
use
something
like
github
single
sign-on
and
require
that
everybody
who's
a
maintainer
and
has
an
account
on
that.
A
You've
seen
us
at
work,
syncs
them
together,
and
then
we
can
say:
okay
since
you're,
making
it
for
this
project.
You
have
edit
access
to
this
node
and
that
might
the
easiest
way
to
do
that
might
be
just
to
change
the
note
author
value
and
then
say
edit
edit
permission,
and
we
don't
need
to
have
that.
Like
user
access
thing,
you
know
what
I
do
whatever
projects
but
means
that,
and
that
might
be
a
good
way
to
to
bridge
that
gap.
So
there's
two
pieces
of
the
puzzle.
A
B
A
That
make
sense,
yeah
and
I'm,
not
sure
I,
think
you're
right
that
this
is
not
clearly
stated
in
any
like
documentation
or
issue,
or
what
have
you
and
I
think
you're
right
that
we
need
to
be
clear
about
where
this
issue
key
is
because
every
time
we
talk
about
it,
I
can't
find
it.
And
then
you
go
away.
C
So
so
I
put
some
notes
on
on
some
of
the
issues
for
backdrop
CMS
about
that.
We
still
have
some
work
to
do
on
that
Google
CSE,
but
as
far
as
consolidating
and
explaining
what
the
different
github
projects
and
repos
are
used
for
in
different
issue
queues,
I
think
that
helps
people
find
what
they're
looking
for
as
well.
Since
things
tend
to
get
spread
out.
A
Yeah
I
definitely
think
like
trying
to
figure
out
where
the
bot
issues
are,
though,
is,
and
it
might
even
be
worth
like
creating
a
dedicated
queue
for
that.
If
we
can't,
if
we
keep
not
finding
them
and
I,
don't
know
if
using
this
node
project
is
the
place
for
it,
I
don't
know
how
you
guys
are
handling
your
github
API
integration
stuff,
but
yeah
yeah.
C
C
A
We'll
figure
it
out
so
that
was
an
important
conversation,
but
maybe
not
related
to
fact,
but
him
did
I
answer
your
question
enough
about
like
how
to
get
started.
If
you
want
help
work
on
that
modules
issue
for
now,
I.
B
A
I
think
we
have,
we
shouldn't,
have
that
setup
for
backups
a
mess
at
work,
the
forum
site
and
the
API
site,
but
I
don't
know
where
the
backups
we
live.
There
might
be
like
a
slash,
backups
directory
or
something,
and
they
think
that
directory
is
password
protected.
So
you
would
need
to
get
the
password
from
somewhere
and
I.
Don't
know
where
that
is
either.
So
we
set
up
like
a
clever
process,
but
it
might
not
be
documented.
A
A
A
There
are
a
couple
of
comments
and
recommendations
there
on
how
to
improve
the
installer
for
mobile
devices,
and
they
think
we
just
need
to
have
something
to
say:
yes,
that's
an
improvement
and
then
we'll
be
able
to
move
forward
on
that,
so
that's
open
open
for
commentary,
but
does
not
have
any
code
on
it.
So
if
someone
read
it
over
into
the
oh,
it
looks
like
the
attorney
for
code.
They
could
also
start
moving
on
to
in
terms
of
usability
issues.
We
have
our
long-standing
issue
number
37
about
improving
the
modules
page.
A
We
have
I
think
reached
a
consensus,
but
not
reach
for
quests
that
matches
the
consensus,
so
that
could
use
work
on
it
if
anyone's
work
on
is
between
the
modules
page
and
I
thought.
That
would
be
great.
We
have
an
exciting
new
issue:
adding
save
draft
back
to
core.
That's
Aquilani,
it's
a
sticker
one.
This
is
always
going
to
you
so
now
that
we
have
the
ability
scheduled
post.
We
want
to
be
clear
to
people
when
they
are
saving
the
draft,
but
they
are
saving
a
job.
A
So
there's
two
issues
related
to
that
1383
and
31:22.
Those
could
give
some
feedback.
So
if
someone
wanted
to
just
give
those
a
test
in
the
same
boxes
and
see
what
you
think
is
improvement,
it
doesn't
still
need
work.
We
could
get
ribbon
on
notice
to
issue
number
28
58.
This
is
when
you're
installing
the
module
that
is
dependent
on
another
module.
A
We
need
to
improve
the
messages
or
maybe
update
when
you're
updating
your
site
in
your
update
is
dependent
on
a
specific
version
of
a
module
explaining
to
people
which
version
in
which
module
is
dependent
will
be
useful.
So
there's
an
issue
to
fix
that
I'm
on
the
manage
display
sub
pages.
The
page
title
is
missing.
That
just
needs
a
knocked-up
subtitle
added
into
those
forms,
just
renumber
3141
project
installer.
Here
we
go
we're
speaking
of
earlier.
A
If
there's
a
problem
with
dependencies,
we
need
to
make
the
messaging
clear
and
that's
issue
number
31
43,
and
if
there
is
a
problem
with
dependencies-
and
you
still
want
to
either
enable
the
modules
we
can
enable
or
finish
your
install
without
enabling
we
need
to
make
that
clear.
That's
issue,
31
42
Oh
looks
like
that
one's
all
ready
to
be
committed,
so
fix
any
good
work
on
that.
Everybody
next
issue
is
adding
a
fourth
message,
type
which
was
going
to
be
info,
and
it's
going
to
be
boil.
The
issue
number
is
31
55.
A
A
Here's
an
exciting
one
issue:
1949
is
being
settings
preview.
So
if
you're
changing
themes
in
particular,
for
example,
changing
the
color
of
your
site
it'll,
give
you
a
preview
of
what
is
being
studying.
This
will
do.
There's
other
theme
settings
that
your
site
or
theme
might
also
include,
for
example,
bar
shake.
You
can
change
the
tabs
from
like
round
it
to
square
corners.
A
Having
a
preview
of
those
would
be
great
issue
number
for
that
is
1949
looks
like
we
could
use
some
feedback
if
she
number
566
is
to
make
the
submit
buttons
on
form
sticking
so
that
you
don't
have
to
scroll
a
million
miles
to
hit
submit
on
any
form.
There
is
a
poll
requests
for
that
click,
economy,
needs
review
and
then
issue
number
31
93
would
make
specific
modules
promoted
in
the
module
installer.
A
So,
for
example,
if
you're
looking
for
a
reference
module
solution,
we
have
both
any
V
reference
and
preferences
in
control,
but
we
would
want
to
recommend
the
reference
module
because
that's
the
ideal
solution
for
a
backup.
So
just
the
idea
that
we
could
mark
a
module-
as
you
know,
didn't
show
up
at
the
top
of
them.
Staller
in
the
top
of
the
search
page
I'm,
backed
up
Cena
sort
I
think
will
help
any
people
who
are
looking
for
specific
modules
fundaments
they
need.
A
A
So
hopefully
you
should
be
able
to
find
any
issues
on
design
finneus
for
me,
the
next
milestone
or
any
issues
for
usability
if
you're
particularly
interested
in
solving
those
I,
don't
know
if
there
anything
in
particular
in
that
list
or
otherwise
that
we
should
talk
about
or
something
that's
not
on
the
list.
We
should
talk
about
today.