►
From YouTube: Backdrop Design - Aug 1st
Description
Weekly meetings where we discuss current topics for BackdropCMS.
B
All
right
well,
we're
live,
so
let's
go
ahead
and
introduction,
which
is
hello,
everybody,
it's
August
1st.
This
is
the
design
and
usability
weekly
meeting
or
trying
out
new
tools
today,
we're
using
the
zoom
instead
of
Google
Hangouts,
so
expect
some
fighting
to
end
it
discussion
about
tweaking
and
tools.
What's
that
you.
B
D
C
Let's
see
this
week,
we
haven't
had
any
major
updates
to
backdrop
CMS
to
org.
We
have
two
outstanding
tickets
that
we
could
use
help
with.
One
of
them
is
a
design
update
for
the
try
backdrop
page,
so
the
issue
numbers
555,
there's
a
couple
of
recommendations
in
there
for
things
that
we
could
do
to
make
the
page
look
better,
but
if
we've
had
any
one
with
design
skills
who
wanted
to
look
at
that
page
and
make
recommendations
on
how
to
do
it,
how
to
improve
it?
That
would
be
great
so
far.
C
The
next
issue,
number
442,
is
a
long
outstanding
one.
We
want
to
improve
the
process
for
finding
and
selecting
module,
C
and
layouts
on
backdrop,
semester
org.
We
have
some
grand
plans
about
linking
up
like
the
module
search
to
also
documentation
on
how
to
move
from
Drupal
the
back
job.
So
if
you're
looking
for
the
path,
OTO
module,
there's
already
a
page
in
our
site,
that
tells
you
you
don't
need
to
install
the
path
auto
module.
A
C
Gonna
fill
it
out
with
some
instructions
on
what
you
need
to
do
if
you're
currently
using
the
path,
auto
module-
and
you
want
to
move
to
backdrop
like
just
don't
put
the
module
in
your
backdrop
site
and
it
will
good
for
you
automatically.
We
know
that
we
need
to
write
that
down
and
communicate
that
to
other
people.
So
there's
a
note
on
our
site
that
we
want
to
show
up
and
search
results
so
that
when
you're
searching
for
pathauto
you'll
get
all
that
information
and
that
piece
is
not
hooked
up
yet.
C
So
we
have
the
notes
that
they're
not
showing
up
in
the
right
places.
There's
been
no
progress
on
this
issue
since
our
last
meeting,
but
if
anybody
wants
to
help
work
on
it,
it's
number
442,
I,
believe,
there's
a
branch
on
the
backdrop,
semester,
org
repo
called
modules
or
something
like
that
projects.
C
Okay,
the
next
section
here
is
on
backdrop
the
product,
and
we
have
a
couple
of
issues
we
pulled
out
as
design
and
usability
focused
and
these
ability
issues
we
want
to
make
some
progress
on
adding
promoted
modules
into
the
project.
Installers,
that's
installer
module
along
backed
up
itself.
We've
got
a
couple
of
steps
here.
C
We
need
to
figure
out
technically.
This
is
not
a
necessarily
UX
issue.
It's
a
sort
of
a
heavy
dev
issue.
We
have
to
figure
out
in
project
module
the
kinds
of
changes
we
have
to
make
to
the
feed
to
get
the
data
we
need
into
the
feed,
but
once
it
is
there,
then
we
have
sort
of
a
design
and
UX
issue
about
like
do
we
just
but
a
different
colored
background
on
it
and
what
color
is
that
background?
C
And
how
do
we
indicate
visually
in
the
Installer
that
that
module
is
special
and
then
we
have
a
great
issue
number
37:55
for
creating
configurable
layout
templates?
This
is
something
that's
coming
along
really.
Well,
there
is
a
sandbox
if
anybody
wants
to
give
it
a
try.
I
think
at
the
very
end,
were
just
gonna
need
a
little
UX
cleanup
in
terms
of
you
know,
just
the
dragging
and
dropping
intuitive,
but
right
now
it's
still
sort
of
a
work
in
progress,
so
I
would
encourage
from
you
and
his
curious
started
to
be
pretty
Chinese.
C
You
think,
but
I
think
it's
coming
along
really.
Well
already.
We
also
have
an
item.
I
think
this
is
added
during
our
last
design
meetings.
I,
don't
have
the
issue
number
for
it,
but
we're
talking
about
setting
up
a
consistent
way
to
display
both
the
human
name
for
something
and
its
machine
name
all
throughout
court.
So
we
have
a
couple
of
examples
of
places
where
it's
done
differently.
C
I
think
the
place
that
we've
decided
we
want
to
model
after
is
the
list
on
the
content
types
page
where
there's
like
a
normal
sized
font,
mean
that's
human,
readable
and
then
a
smaller
sized
name
in
parentheses.
That's
the
machine
name,
it
says
machine
name,
colon
and
then
the
machine
name
in
there
I
think
that's
the
standard.
If
we
want
to
adopt
all
throughout
core
and
if
we
had
a
specific
function
we
could
use
for
that,
then
we
could
just.
C
It
would
be
really
easy
to
standardize
on
it.
We
wouldn't
have
to
think
about
it
anytime.
We
wrote
it
down
a
lot
of
times.
What
happens?
Is
we
end
up
with
those
things
in
different
columns
and
we
talked
about
how
giving
the
machine
name
a
calling
of
its
own
sort
of
implies
that
this
is
developer
software,
because
we're
giving
people
stuff
they
need
for
code
rather
than
and
use
yourself
a
rule
and
give
them
a
machine
name.
C
We're
always
very
interested
in
moving
those
forward.
So
even
if
they're
not
called
out
in
particular
in
any
given
meeting
that
doesn't
mean
they're,
not
important,
and
if
we
get
a
working
for
requests,
we'll
be
able
to
merge
it
in
whenever
all
right.
So
next
up
design
issues
on
the
design
front.
The
first
thing
we
wanted
to
do
was
fix
the
header
at
some
point.
C
A
hover
color
was
added
onto
the
account
links
and
it
makes
it
very
confusing
as
to
whether
the
main
menu
is
the
main
menu
or
the
account
links
of
the
main
menu
and
so
I
think
the
decision
there
was
just
to
remove
the
background,
color
and
add
an
underline.
There
hasn't
been
any
pushback
on
that.
So
I
think
we
can
go
forward
with
that
decision,
but
if
anyone
has
better
design
instinct
on
how
to
handle
those
we're
open
to
that.
C
C
Color
would
allow
it
to
remain
backwards,
compatible
for
all
the
sites
that
are
already
using
it,
but
it
would
give
the
people
in
the
future
the
ability
to
run
off,
or
we
could
just
turn
off
by
default
and
leave
them
option
to
turn
on
which
could
be
my
preference.
So
I
don't
have
the
issue
number
for
that
one
either
I
think.
C
C
It
would
just
print
the
same
thing
like
different
like
within,
like
elements
attributes
on
the
tag,
rather
than
trying
to
create
a
copy
of
the
image.
So
there's
got
to
be
a
lot
of
kind
of
technical
Kody
stuff
to
figure
out
how
to
like
work
around
the
way
image
module
currently
works.
There's
a
kinship
module
searchable
that
handle
SVG
images,
some
of
them
things
like
a
completely
custom
field,
type,
which
I
think
we
don't
want.
I.
C
Don't
know:
I
forgot
what
it
was,
but
I
don't
think
it
was
exactly
what
we
wanted.
Unthinking
integrated
with
image
launched
all
the
way
we're
looking
for.
So
we
might
have
to
look
at
those
for
inspiration
on
how
to
solve
this
problem,
but
can
try
and
figure
out
how
to
integrate
and
I.
Don't
know
what
that
issue
number
is
either
but
again,
I.
Don't
think.
That's
necessarily
designed
related
sort
of
with
the
new
feature
request,
I
guess,
but
yeah
I
just
need
to
figure
out
how
to
do
it
to
better
support.
C
C
Great,
that's
what
all
we
have
for
backdrop:
the
product
itself.
We
have
a
couple
of
items
for
print
design
that
we
would
love
to
have
pop-up
banners
for
events
and
new
stickers.
Both
of
those
would
need
some
design
direction,
so
someone
would
have
to
go
into
the
issue
and
be
like
in
a
pop-up
banner.
C
This
is
what
we
wanted
to
contain:
the
logo,
the
following
tagline
or
whatever,
and
once
we
have
that
information
documented,
we
have
a
volunteer,
that's
going
to
do
the
art
part
of
it,
but
I
don't
even
have
any
guidance
as
to
like
what
we
want
on
the
banner
and
so
they're
having
a
hard
time
starting
the
minutes.
So
if
anyone
has
any
instincts
about
the
kinds
of
things
with
one
put
on
the
banner
I
think
it
would
be
good
good
to
brainstorm
that
and
figure
that
out.
C
A
C
That
feels
like
a
bug
that
just
feels
like
it
was
designed
with
one
layout
in
mind
and
I
think
it
actually
might
have
gone
in
before
all
our
layouts
went
in.
So
that
could
be
something
we
just
never
tested
before,
to
figure
it
out
and
I
bet
that
there's
a
better
selector
to
put
that
margin
on
than
the
field
itself
or
a
more
specific
one.
It
would
be
like
when
that
field
is
in
its
region
layout,
but
yeah.
That
would
be
something
to
take.
A
look
at
I
definitely
think
as
you're
working
through
these
things.
C
It
would
be
good
one
issue
where
you
write
all
them
down
and
then
that
way
we
could
go
through
me
like
okay.
This
is
a
sub
issue,
and
here's
this
you
know
follow
up
like
a
meta
and
then
like.
Oh
this
one,
maybe
not
you
can,
even
if
that's
like
an
issue
in
your
theme
where
it's
like
this
is
the
stuff
that
might
be
more
even
in
the
readme
or
something.
This
is
the
stuff
that
might
be
missing
just
that
we
have
a
place
that
lists
all
the
things
for
like
that.
C
Depend
we
will
have
to
look
at
what
the
problem
is
and
what
the
fix
is,
because
the
way
CSS
works
is
that
if
somebody
else
is
already
overridden
it
their
override
will
win.
We
just
need
to
make
sure
that
we're
not
going
to
be
like
adding
padding
to
somewhere
that
they
won't
expect
it
to
appear
right.
So
it's
hard
to
say
without
seeing
it.
My
guess
is
something
like
that
we
probably
could
do,
but
it
could
be
that
we
look
at
the
code
and
were
like.
Oh
there
isn't
anything
we
do.
C
A
B
A
A
A
I
mean
we
there's
nothing
to
prevent
us
from
going
ahead,
whether
or
not
you're
there,
but
that
was
part
of
the
motivation
but
I'm
starting
to
pull
together
a
lists.
I'm
gonna,
hopefully
do
a
couple
of
tweets,
but
my
expectations
are
huge,
but
maybe
we
get
two
or
three
people
that
show
up.
Maybe
some
of
them
are
coders
and
I'm.
A
C
C
Yeah,
that's
design
related,
so
the
problem
and
I'm
no
summer
Isis,
but
let
me
know
if
you
don't
think
I
got
it
right
is
on
API
site.
We
have
this
fantastic
page
for
our
form,
API
reference.
That
is,
this
crazy
grid
of
all
of
the
form
elements
and
the
properties
that
are
available
for
each
one
and
though
it
is
nice
and
easy
from
user
experience
perspective
to
navigate
and
find
what
you
want.
C
Do
it
the
same
way
and
even
back
then
I
think
Luke
was
working
on
in
his
like?
Isn't
there
a
better
way
to
do
this,
like
maybe,
but
it's
gonna
be
hard,
so
peter
has
volunteered
to
figure
out
what
the
better
way
might
be
and
help
us
trying
to
try
and
get
this
form
into
a
state
that
we
can
more
easily
maintain.
C
My
friend
that
config
file
it
was
in
Jason
would
be
something
you
could
just
add
a
new
line
to,
and
it
would
end
up
in
then
rendering
in
the
table
in
the
right
place
and
we
would
take
the
design
and
layout
element
was
separated
from
the
data
which
I
think
sounds
good,
but
Nate
I
think
you
did
a
bunch
of
work
on
this
page
and
I.
Don't
know
if
you
want
any
thoughts
on
and
other
ways,
we
could
make
it
easier
to
update
yeah.
B
It
pages
ago,
yeah
I
made
it
so
the
table
was
at
a
diagonal
for
the
headers,
which
helped
a
lot
honestly
made
it
so
that
you
can
actually
kind
of
read
that
see.
If
check
boxes,
I,
don't
think
we
could
need
to
throw
out
the
content,
type
issue
or
content
type
suggestion.
It's
just
a
lot
of
work.
That's
kind
of
all
there's
to
it.
I
think
it
would
be
a
good
thing
to
do,
though,
because
then
you
could
do
stuff
like
you
could
search
for
like
pound
weight
or
something
like
that.
B
C
B
C
B
That
little
section
would
be
its
own
node
out
of
me
and
but
maybe
what
we
would
do
is
we
wouldn't?
Actually
maybe
those
individual
pages
would
be
accessible,
but
maybe
also
you
it
just
linked
to
the
view
and
jumped
down
to
the
section
of
the
page.
You
know
just
like
it
does
right
now,
so
it
would
have
its
own
page,
but
maybe
that
page
would
actually
just
redirect
to
the
overall
listing
and
put
it
in
place
or
there,
maybe
not
I,
don't
know
that
form
API
page
is
really
kind
of
overwhelming.
B
B
B
B
E
There's
also
an
issue
with
PSO
plane
with
display
and
the
content.
This
is
just
what
creating
consistencies
of
a
silver
North
Channel
earlier
and
just
little
tags
or
other
things,
just
not
consistent
anything
else
in
the
page,
so
separating
out
that
here's
the
content
and
then
style
it
separately,
we
may
just
mean
I
know
it's
update,
it's
all
more
consistent
to
it.
B
C
A
C
That
and
then
there's
also
going
to
be
a
lot
of
work
to
actually
make
it
render
the
way
we
want
it
to
because
there
isn't
already
abuse
handled.
It's
like
make
this
table.
That
goes
like
this.
You
know
this
information
in
these
places
and
cross-referenced
in
two
different
ways
than
what
have
you.
So
we
just
need
to
send.
Do
some
massaging
like
take
maybe
four
records
and
see
if
we
can
get
that
output,
the
way
we
want
and
if
we
can
and
we're
like?
Yes,
we
can
do
it.
C
A
D
C
We
could
even
get
you
a
sanitized
database
of
the
API
site
if
you
wanted
to
start
with
that,
but
yeah.
If
you
wanted
to
do
I
mean
figuring
out
like
the
data
structure,
what
the
feelings
should
be
on
the
content
type
that
would
be
entirely
up
to
you.
So
if
you
wanted
to
do
that
somewhere
else,
that
would
be
fine,
but
I
think
it
would
be
do.
C
C
The
config
is
in
there
pylori,
it
should
be
committed
both
in
the
staging
victory
and
in
the
live
Eric
Street,
and
then
there
should
be
a
deaf
directory.
That's
empty!
That's
for
your
local
site
and
there's
a
readme
file
in
the
config
directory.
That
explains
like
the
way
that
we
deploy
config.
So
it
should
there's
just
a
couple
of
like
there's
some
sensitive
data.
C
That's
in
the
Sunnyside
PHP
file,
I
could
get
have
integration
stuff
and
whatever
that
you're
not
going
to
get
when
you
do
well,
but
you
probably
won't
need
that
on
your
local
site
anyway,
so
I
think
the
biggest
thing
is
getting
you
guys.
Sanitized
copies
of
the
database
and
I
know
we
have
folks,
we
know
so
org
where
there
are
sanitized
copies
of
backdrop.
Cms
two
org,
but
I'm,
not
sure
that
API
site
the
forum
site,
it'll,
look
cool
I,
don't
think
any
of
those
are
in
or.
C
D
C
So
if
we
could
do
the
same
thing
for
all
the
sites,
I
think
that
would
make
it
easy
for
anyone
to
work.
On
short
terms,
though,
we
could
manually
create
a
sanitized
database
for
forum,
for
you,
Tim
and
I
can
put
it
in
the
sanitized
location
and
then
at
least
you'd
have
one
from
first
and
then
once
we
get
the
ticket
resolved
later,
we
could
have
a
habit
update
with
daily
ones,
I'm.
A
B
Well,
yeah
yeah
send
a
ping
out
to
Justin
Missy
he'd
be
able
to
do
that.
He
set
up
the
sanitized
scripts
previously
I
doubt
it's
even
very
complicated
what
you
said
up
here,
especially
we
could
just
make
like
multiple
pages
like
one
for
each
site
or
something
like
that,
and
we
could
just
reuse
the
exact
same
thing
done
one
for
each
site.
C
Right,
let's
meet
again
in
20
minutes
almost
so,
let's
go
ahead
and
wrap
this
up,
and
if
anyone
comes
up
with
anything,
they
think
is
designer
who
Billy
really
did
too
that
they
want
to
talk
about
next
week,
closely.
I'll
put
it
in
the
agenda:
I'm
excited
about
zoom,
meaning
the
slowly
worked.
Yeah.