►
From YouTube: Backdrop Design July 5th
Description
Today’s design agenda: https://tinyurl.com/ycmk843e
A
A
Very
excited
about
anything
else.
Okay.
So,
let's
see
this
is
a
meeting
to
check
in
on
active
design,
immune
stability
tasks
for
backrub
CMS.
According
to
the
agenda,
we
are
supposed
to
remind
everybody
that
we
are
working
on
these
our
experience
for
selecting,
magis
themes
and
layouts
on
backdrop,
CMS
org,
we
have
an
issue,
that's
been
marked
as
a
high
priority
in
terms
of
improving
the
modules
consume
layout
pages,
the
search
ability
and
also
a
better
way
of
just
letting
people
know
if
they
don't
actually
mean
a
module
theme
for
Hume.
A
For
backdrop
with
the
UC
beautiful
we
haven't
made
any
progress
on
that
recently.
We
could
use
some
help
there
there's
a
couple
of
separate
tasks
involved.
Some
of
them
are
just
implementation
of
designs
that
we
have
for
the
mantras
instantly
of
pages.
Some
of
them
are
more
complicated,
like
figuring
out
how
we
want
to
solve
the
search
problem
for
searching
for
module
sinks
and
layouts.
We
need
to
make
those
search
results,
return,
not
only
projects
with
actual
releases,
but
also
there's
a
content.
A
Type
thing
called
a
placeholder
project,
which
is
for
something
that
has
been
moved
into
core
or
is
no
longer
necessary.
The
backup
Cena,
so
something
like
took
in
module,
is
something
that
people
might
be
looking
for
if
they're
coming
from
Google
and
letting
them
know
that
that
module
isn't
necessary.
A
The
backdrop
that
history
house
took
in
support
is
gonna
be
valuable,
so
we
need
to
figure
out
how
to
fix
our
search
issues,
also
making
sure
that
the
right
results
returned
at
the
top
of
the
list,
so
making
sure
that
the
title
of
the
module
is
more
important
than
some
content
in
its
body
fields
or
description,
which
in
our
case
is
the
contents
of
the
readme
file,
would
be
valuable
so
trying
to
figure
out
how
to
change
those
rankings
would
be
good.
There
are
a
couple
of
contributes.
The
stump
is
for
Drupal.
A
We
could
also
look
at
switching
from
using
the
built-in
core
search
to
something
like
Apache
Solr,
which
is
a
little
bit
more
work,
but
would
be
good
or
right
now
we're
not
musing.
He
used
to
generate
those
pages.
We
could
look
at
if
there
are
easy
ways
to
change
that
we
use
handles
it's
combined
fields,
filter
or
we
could
write
better
search
filters
that
might
be
more
suited
to
this
particular
use
case
I'm.
A
Just
thinking
of
what
might
be
best
for
our
target
users,
I
think
switching
to
solar
might
not
be,
it
might
be
what's
best
for
backup
CMS
work,
but
it
might
not
be
what's
best
for
everybody
else
running
backdrop.
So
just
kind
of
we've
got
some
bigger
questions
to
answer
there
about
how
to
solve
those
problems.
So
if
anyone
wants
to
help
weigh
in
the
parent
nation
for
working
on
that
is
number
442
on
the
backdrop
semester
org
on
the
forum
site,
we
have
a
code
block
widget
that
was
part
of
CK
editor.
A
A
I
think
if
we
can,
we
can
get
a
CSS
hack
in
on
our
forums
like
that's
great,
but
West
did
also
mention
that
it
might
be
good
to
fix
the
problem
upstream
list
you
can
deter.
The
issue
is
that
their
box
doesn't
take
into
account
the
width
of
the
content
within
it.
A
So
very
at
least
I
think
open
an
issue
for
them
and
say:
hey,
there's
a
problem
with
the
but
width
of
your
box,
and
then
we
can
post
our
CSS
hack,
for
anyone
else
has
that
problem,
but
I
think
it
would
be
good
to
make
that
a
more
robust
fix
upstream,
which
hopefully,
at
some
point
in
the
future.
We
can
incorporate
into
a
pony,
update
Sikandar.
A
So
I
looked
at
most
of
us
this
morning,
but
maybe
not
all
of
them.
The
first
one
is
the
Installer
design.
This
is
issue
number
28,
73
and
the
backdrop
issue
is
Q,
and
this
is
something
that
Opie
brought
to
our
attention
a
while
ago
that
on
mobile
devices,
installing
backdrop
doesn't
look
beautiful
and
I
think
we
have
a
consensus
there
about
reworking
that
table
instead
of
being
two
columns,
it
could
be
a
single
column
and
then
we
would
be
able
to
more
easily
stack
and
unstack
the
label
and
the
content.
A
B
A
A
Yeah
so
dudes
will
tread
carefully
back
uh-oh
I
added
a
label
to
that
issue.
A
marker,
that's
good.
First
issue.
The
people
I
thought
if
it
was
just
making
two
table
cells
and
turning
into
one.
That
might
be
something
that
would
be
we're.
Always
people
easy
to
do,
but
I
haven't
looked
at
the
code
and
sometimes
I'm
overly
optimistic
about
what
a
good
person
is.
So
that
might
not
mean.
Thank
you
all
right.
That's
it
for
to
sign
issues
was
deciding
on
the
design
for
the
Installer.
We
have
a
ton
of
usability
issues.
A
The
first
one
is
our
oldest
one
issue.
Number
37
was
the
modules
page
update,
I
unmet
from
being
myself
a
couple
weeks
ago
and
jock
Lamont
grabbed.
It
almost
immediately
was
just
fantastic.
He
did
a
rear
all,
but
he
did
a
reroll
of
the
original
pull
request,
not
of
the
consensus,
and
so
now
it's
actually
not
even
it's.
It
was
a
rewrote,
his
original
request,
which
is
the
one
that
removed
all
of
the
my
package
groupings
as
well
as
adding
the
select
list
and
the
filters.
A
A
But
if
we
remove
the
package
there,
thanks
without
adding
anything
that
provides
that
usability
feature,
we're
gonna
have
to
usability
regressions
with
this
change,
and
so
I
say,
item
ISOs
in
the
issue
and
I
think
that
if
we
had
decided
to
add
some
of
other
new
features
that
are
in
his
current
pull
requests
like
the
Select
list,
we
would
have
a
replacement
we'd,
be
replacing
the
groupings
with
a
filter,
but
because
we
don't
have
the
filter.
We
just
be
removing
the
feature
that
is
there
now
and
so.
A
E
From
the
people,
because
we
still
don't
have
enough
from
statistics
enough
metrics
to
decide
if
people
are
actually
using
it
or
not,
and
because
there's
no
alternative
at
this
point,
even
if
we
had
stats
implies
what
will
be
the
alternative.
How
could
we
tell
if
people
are
hated
or
love
it
or
what
needed
yeah.
A
So
yeah
I
don't
know
what
the
best
path
forward
is
anymore
for
that,
if
it
will
be
worth
trying
to
get
him
to
rework
his
complete
poll,
requester
blue
should
go
back
to
my
incomplete
one
and
pull
stuff
out
of
it.
That
packages
versus
no
packages
is
the
biggest
change
in
that
pull
request,
so
I
feel
like.
Maybe
we
should
leave
his
and
just
link
it
up
to
one
of
the
other
issues.
One
of
the
issues
we
decided
to
defer
on
and
be
like,
hey
guys.
A
This
is
an
example
of
what
it
would
look
like,
for
example,
with
a
filtering
in
without
packages
and
have
that
be
a
discussion
there
and
then
create
a
new
poll
request
for
the
shoe.
That's
just
adding
the
tags
which
is
sort
of
what
we
decided
on
last
time.
I
didn't
it
types
and
adding
the
types
so
the
search
box,
searches
on
tags.
E
Then,
in
case
in
case
that
I
get
some
time
to
work
on
specifically
what
I'm
about
to
say,
do
you
agree
with
the
adding
the
link
at
the
top
right
like
the
sweets,
the
toggle
between
alphabetical
packages
like
having
the
default
meals,
are
very
cool.
The
way
that
the
doctor
would
believes
it
should
be,
and
then
this
would
offer
people
a
toggle
back
to
the
old
way.
I.
A
Am
conflicted
about
that
because
I
feel
like,
rather
than
giving
people
to
user
interfaces,
we
should
actually
figure
out
which
one's
better
and
give
them
the
better
one.
I
don't
know
if
we
can
figure
that
out
without
like
information,
statistics
and
studies
like
we
should
do
a
study
on
both
versions
and
see
what
is
more,
successful
and
I
think
that
we
can
find
the
two
groups
of
people
are
pretty
easy.
There's
like
people
with
triple
experience
or
backdrop
experience.
A
We
have
a
group
of
them
and
people
who
have
never
seen
the
software
at
all
and
so
I
think
like
setting
up
a
quick
study
with
like
ten
people
in
each
group
at
like
a
triple
camp,
might
be
a
good
way
to
do
it,
and
we
could
probably
do
that
pretty
easily.
Just
by
chatting
people
and
saying
hey
use
this
thing
and
we
I
don't
even
open
you
to
report
it
I
just
have
somebody
there
watching
them
and
noting
what
they
do.
You
can
write
a
little
quick
script.
E
That's
a
really
good
idea,
like
maybe
we
could
have
another
time
in
the
github
cues
that
says
user
studies
required
or
something
like
that.
So
it's
time
that
there's
a
big
session,
a
big
black,
hold
a
backdrop
session.
People
can
just
go
through
these
tickets
and
make
these
new
comers
there.
They
can
ask
them
to
just
that
was
your
opinion.
Yeah.
A
A
Also
sort
of
a
bike
shed,
it
sounds
like
the
consensus
was
reached
that
we
should
start
by
just
changing
the
submit
button
label
and
get
that
in
right
away,
and
then
we
should
talk
more
about
what
we
want
the
radio
buttons
to
do
where
they
should
be
or
if
it
exists,
all
and
make
sure
that
as
long
as
people
are
kidding,
that's
mitt
button,
it
tells
them
what
they're
doing
when
they
hit
the
submit
button.
That's
gonna
be
good,
first
step,
so
that
one
needs
implementation.
A
Next,
one
is
the
update,
dependency
message,
which
I
think
just
needs
review.
So
this
is
what
happens
when
you
are
trying
to
run
updates,
for
example,
from
simple
the
backdrop
and
you'd
have
an
updated
one.
If
your
Drupal
modules
in
the
latest
version
that's
available,
it
throw
a
math
and
error
message
and
say:
there's
a
problem,
but
all
of
their
messaging.
That
currently
does
is
a
little
bit
confusing.
So
we've
written
some
clear
error
messaging
and
that
horrifies
means
for
you.
A
A
One
of
them
is
to
make
it
clear
when
dependencies
aren't
met.
So
if
you're,
installing
a
sub
module
and
you're
missing
parent
module,
the
sub
module
can't
be
install,
or
it
can't
be
enabled
just
trying
to
indicate
to
people
that
they
can
enable
the
other
modules,
but
they
can't
enable
the
one
they're
trying
to
enable
it
has
dependency
and
then.
E
There's
other
small
issues,
they're
small
bugs
like
if
there's
multiple
dependencies,
the
installer
doesn't
install
the
dependencies
other
than
it
doesn't
match
them.
It's
just
as
many
dependencies
there
are.
They
ask
the
user
to
just
click
the
next
button
as
many
times,
so
it
does
it
installs
only
one
module
at
a
time,
one
dependency
at
a
time.
No
yeah
I
can't
I,
don't
have
the
the
ticket
for
that
right
now,
but
it's
not
a.
This
is
not
a
design
issue.
More
of
a
backup,
yeah,
there's
multiple.
There
are
small.
A
Well,
I
think
we'll
be
good.
It's
good
that
you're,
noting
these
and
it'll
be
good
for
us
to
iron
them
all
out.
This
is
you
know
it
was
a
control
module
for
Drupal
7
that
didn't
get
a
lot
of
action
and
they
put
it
into
backdrop
and
there's
gonna
be
a
bunch
of
little
hiccups
as
we
go
through.
So
as
long
as
we
can
identify
them,
it
should
be
pretty
easy
to
fix.
So
that's
very:
do
we
have
a
meta
project,
installer
issue,
a
single.
A
That
agree
and
then
the
next
issue
is
to
add
an
info
type
for
our
Status
Messages,
and
this
is
an
alignment
with
bootstrap
as
well,
and
it
would
be
good
to
update
a
bunch
of
messages
we
have
around
core
and
even
can
trim
your
messages
that
aren't
necessarily
success
messages,
their
comm
using
the
success,
coloring
and
label.
Just
because
that's
all
we
have
and
so
I
think,
there's
some
great
examples
in
here
things
that
we
can
switch
over
once
we
have
it
and
the
current
pull
request
to
add.
It
looks
like
it's
needs
review.
A
E
So
I,
don't
know
how
you
guys
feel
about
that,
but
it
solves
many
other
problems,
like
their
insistence,
is
that
we
have
so
when
we
have
when
we
make
changes
in
views.
There's
this
message
that
says
it
hasn't
been
saved.
You
need
to
click,
Save
or
cancel,
and
these
buttons
are
way
outside
the
users.
E
B
We'll
have
to
do
some
testing.
The
biggest
problem
with
sticky
stuff
is
historically,
it's
been
crap
on
mobile,
so
I,
don't
know
if
that's
gotten
better
or
if
we
like
I
I
kind
of
like
I've
I've
done
that
sticky
stuff
on
sites
that
I
manage
but
like
rolling
it
out
for
all
users
of
a
CMS
is
something
that
I'm
like.
You
should
probably
do
some
more
testing,
because
I
do
kind
of
I.
Do
like
the
idea
and
I
know
exactly
what
problem
you're
trying
to
solve.
Yeah.
F
E
B
We
should
we
should
do
some
implementation
and
then
and
then
kind
of
edit
some
stuff
on
a
phone
and
and
like
you
know,
if
you
pinch
and
zoom,
that's
usually
when
position:fixed
breaks
on
a
phone,
it
behaves
in
a
way
that
isn't
that
intuitive
at
least
last.
This
was
last
time.
I
checked.
This
was
a
couple
years
ago,
at
least
three
years
ago
me
so
it
might
have
gotten
better
so
I
we
just
have
to
make
sure
it
doesn't
make
the
phone
hard
to
use
so
yeah.
C
A
You
can
have
like
a
setting
in
the
theme
that
was
like
sticky,
Save
button
setting
or
something
and
then
in
core
for
new
installs.
We
turned
it
on
the
basis
and
seven
earn
all
themes
or
whatever
and
then
for
existing
things.
It
wouldn't
turn
on
unless
somebody
manually
turned
it
on
and
then
they
would
have
the
option
of
fixing
their
theme
to
account
for
it.
If
they
wanted.
You
yeah.
E
A
Could
find
a
way
to
I
mean
if
it's
just
as
CSS
change,
like
those
buttons
have
to
be
on
the
page
anyway,
even
if
they're,
not
where
you
can
see
them
so
it'll,
just
be
not
as
good.
If
they
don't
even
look
good
checkbox,
that's
the
I,
don't
think
it'll
we
didn't
put
anything
that
would
be
broken
without
them.
Yeah.
E
Below
a
way
forward
that
I'm
saying
is,
although
this
has
been
mentioned
in
Dido,
talk
over
the
years,
what
happened
for
it
to
be
brought
into
service
in
backdrop?
Was
that
lion
implemented,
that
for
the
save
draft
module
and
then
we
said
yeah
well,
it
looks
nice.
Why
not
solve
all
the
problems
using
that?
But
we
don't
have
a
dedicated
issue
for
that.
So
I
might
just
open
that
and
add
the
voices
note
about
the
problem
with
pinching
zoom
things
so
that
we
can
test
it
because
the.
B
Other
problem
I
forgot
about
that
I've
seen
is,
let's
say
we
think
the
best
place
for
the
Save
button
is
the
bottom
of
the
screen.
So
it's
sticky
at
the
bottom
of
screen,
but
they
update
basis,
let's
say
and
add
a
newsletter
signup
to
the
bottom
of
the
screen,
and
then
you
might
have
an
issue
where
you
can't
see
it,
because
the
z-index
is
aren't
and
there's
no
way.
B
E
Was
I
was
actually
thinking
about
that
when
I
saw
your
implementation?
Sorry
was
it
the
intimidation,
not
wasn't
you
with
the
color
yeah,
it
was
yeah,
so
yeah
I
saw
the
iframe
there
and
immediately
I
thought
about
the
not
preview
thing,
because
this
way
we
separate
the
ribbon
from
the
actual
beam
we
solve
that
problem.
So
it
seemed
like
a
nice
idea.
E
The
other
good
thing
is
the
other
thing
when
it,
when
it
comes
to
previews
I
just
did
run
a
quick
demo
WordPress
and
what
they
do
with
the
theming
I'm,
not
sure.
If
you
guys
saw
that
video
yeah
I'll
find
out
find
that
ticket
remember
anyway,
so
that
what
they
use
is
they
use.
They
put
the
settings
in
a
sidebar
and
remember
how
we
had
that
drawer
menu
for
backdrops
Ionesco
told
ya,
so
they
have
a
button
at
the
bottom
which
just
slides
the
controls,
no
matter
how
many
levels
of
control
there.
E
E
F
C
E
C
C
C
So
there's
control
that
fixes
this,
but
I
marked
it
needs
work
because
the
implementation
right
now
just
does
it
blank
it
across
the
forward
like
for
all
files
that
are
uploaded
if
the
rotation
is
wrong.
According
to
the
exif
data,
then
rotated
immediately
on
upload
and
the
concern
I
had
there
was
that
if
we
do
that,
then
that
makes
it
so
that
all
images
that
get
rotated
lose
their
exif
data
kind
of.
Ironically,
whether
we
use
the
exif
data
to
determine
the
orientation.
C
E
C
C
B
A
C
E
C
Any
image
manipulation
that
we
do
in
core
yeah,
including
resize,
or
anything
like
that,
and
so
an
image
style
doesn't
really
make
a
difference
because
it
works
copy
right.
But
if
you
modify
the
original
file,
then,
when
PHP
writes
that
file
back
to
disk
it
just
like
you
know,
it's
just
worried
about
the
image
itself.
It's
not
worried
about
the
metadata,
that's
also
contained
in
the
image
so
that
we're
fixing.
C
It's
possible:
that's
the
exif
module
and
drupal
kind
of
deal
dealt
with
this
kind
of
shenanigans
because
you
basically
have
to
save
the
EXIF
data
at
the
beginning
when
the
file
is
originally
uploaded
and
then
after
it's
been
modified,
then
write
the
EXIF
data
back
into
it.
Yeah
and
writing.
Exif
data
is
possible
with
the
PHP
exif
extension,
but
it's
it's
like
you
know.
It's
kind
of
it.
A
E
It's
we
ignore
the
data.
I
think
that's
what's
happening,
so
we
ignore
the
data
when
we
write
the
new
file.
That's
what's
happening
now
right,
it's
not
that
we
have
exif
sort
of
like
code
in
place
that
just
strips
things
out
they
just
we
ignore
it.
We
just
write
the
image
contents
and
we
ignore
so
this
is
like
bad
a
loss,
but.
A
If
we're,
if
we're
gonna,
read
the
exome
data
in
order
to
rotate
the
image
we
have
the
tool,
we
need
to
save
the
exit
data,
so
it
might
be
worth
opening
another
issue
to
say.
Well,
it's
personal
racks
of
data
on
images
I
feel
like
it's
less
of
a
priority.
Then
don't
upload
people's
images
in
the
wrong
direction,
but
it
could
be
something
that
someone's,
like.
Oh
my
god,
I've
been
running
my
site
for
two
years
and
I
didn't
realize.
A
E
C
Yeah-
and
it's
also
like
I-
mean
whether
or
not
it's
appropriate
in
core,
but
that
I
think
that
discussion
has
already
happened.
It
seems
like
people
have
agreed
that
it's
good
to
have.
People
are
just
worried
about
bloat
that
the
court
get
too
heavy,
but
I'm
not
sure
that
this
is
going
to
be
that
you
know
straw
that
breaks
the
camel's
back.
E
Certain
things
like
be
considered
blocks
for
core,
but
small
things
like
allowing
I
think
these
got
into
core
really
a
Leon,
allowing
the
image
fields
to
capture
images
from
phones.
So
when
one
was
using,
so
this
could
be
considered
a
block
for
someone,
but
now
that
everybody's
using
their
mobile-
it's
not
so
you
know
far-fetched
or
annoyed
case
and
people
appreciate
it.
Nobody
says
that
yeah.