►
From YouTube: Backdrop Design & UX - Dec 6th
Description
Today’s design agenda: http://bit.ly/2zBiqz5
A
All
right
we're
on
air
happy,
Thursday
everybody.
It
is
December
6.
Sorry,
I've
been
away
for
the
past
few
weeks,
but,
as
I
mentioned
earlier,
I'm
really
happy
that
I
am
not
needed.
Anymore
feels
fantastic
that
you
guys
can
carry
on.
Without
me,
this
meeting
is
to
check
in
on
casaya
design
and
usability
tasks,
protective
CMS,
starting
with
our
web
properties
back
from
CMS
at
org.
Our
flagship
website
has
some
problems
with
module
to
module
schemes
in
layout
search
pages.
A
What
you're
looking
at
is
a
new
View
mode
specifically
for
modulus
things
and
layouts,
so
that
the
search
for
it
turns
not
like
the
teaser
but
I
think
it's
called
searchers
modules,
some
project
search
or
something
like
that,
so
that
it
just
for
the
search
result,
each
be
looking
ton
of
note
IDs
that
it
matches
and
then
we'll
be
able
to
order.
Those.
However,
we
need,
and
then
let
us
render
correctly
so
other
than
having
to
list
all
the
fields.
A
It's
making
the
view
kind
of
complicated,
and
so
since
I
wanted
to
return
like
control
the
results
of
the
view
and
way
to
anyway,
so
I'm
doing
some
work
on
it.
It's
kind
of
a
mess.
The
design
part
is
great,
but
I
want
to
get
search.
Part
cleaned
up
too,
before
we
launch
that.
So
that's
what
I'm
working
on
now!
A
Oh
yeah,
also
we're
trying
to
add
filters
so
that
people
can
not
just
use
the
search
box,
which
is
what
they're
doing
now,
but
also
like
control,
sort
order
and
filter
by
you
know
other
things,
and
so
we
have
issue
number
37
which
we'll
talk
about
in
the
next
meeting
that
might
add
to
this
as
well
and
then
right
now.
You
can
also
filter
by
most
installed
and
most
downloaded,
which
are
the
two
counts
that
we
currently
have
I'm
showing
in
the
side
bar
but
will
be
able
to
control
sort.
A
A
It
Wes
gave
me
some
code
that
I
tried
to
throw
into
a
couple
of
different
places,
and
it
didn't
quite
do
the
trick
and
I
don't
know
if
that's
because
the
selectors
have
changed
since
he
wrote
the
code
or
if
this
you
can
deter
JavaScript
is
overriding
anything
we
do
in
CSS.
So
there's
probably
some
other
ways
we
can
fix
that
we
could
probably
fix
it
javascript.
A
We
might
be
able
to
fix
it
by
putting
that
code
into
a
smarter
location,
but
trying
to
figure
out
how
to
add
a
breakpoint
in
your
browser,
inspector
and
figure
out,
exactly
which
piece
of
the
code
needs
to
be
changed
when
it's
a
little
bit
beyond
my
skill
level.
So
if
anyone
wants
to
take
us
out
of
that
and
figure
out
how
to
fix
that
up,
that
would
be
great
again.
That's
issue
number
59.
In
the
backdrop,
see
messed
up
or
QED
all
right.
A
Talking
about
backdrop,
the
product,
the
first
issue
in
the
list
for
user
experience
is
issue
number
37.
This
is
why
I'm
just
meant-
and
this
is
about
adding
tags
to
modules.
So
all
of
this
issue
does
is
add
text
to
the
info
files,
and
that
should
make
it
so
that
we
can
search
by
those
tags
on
the
modules
page
so
using
the
normal
search
box.
It'll
also
provide
all
of
these
tags
to
back
top
semester,
org
to
enable
better
searching
on
the
site
and
to
project
browser
from
evil
better
searching
there.
A
So
the
issue
itself,
37,
is
pretty
minor,
just
add
tags,
but
the
utility
of
those
tags
elsewhere
in
the
vector
ecosystem
is
I.
Think
the
real
win
there
so
I
believe
there
was
an
issue
with
that.
Current
law
request
on
number
37
and
it's
assigned
to
me
to
figure
out
what
I
broke
last
revision.
So
I'll
try
and
take
a
look
at
that
sometime
soon.
A
The
next
issue-
1005,
is
add,
options
element
in
court,
so
this
essentially
takes
the
giant
text
area
where
you
type
in
key
value
pairs
and
turns
it
into
a
nice
interface
with
a
key
column
and
the
value
column,
and
you
can
hide
the
key
column
little
Auto
number
or
you
can
for
a
lot
of
create
values
and
it'll
just
make
a
better
experience
for
entering
key
value
pairs.
So
that
issue
is
currently
at
needs,
review,
I.
Think
right
now
it
works
really
well
with
core
I.
A
Don't
know
if
we're
gonna
need
to
make
any
changes
to
webform
in
order
to
make
it
work
there.
It
was
originally
written
as
our
web
form
and
not
the
poor.
So
there
might
be
a
couple
of
little
topics.
We
have
to
do
in
kinship,
make
sure
that
it
works
with
the
new
core
implementation,
but
so
far
all
testing
is
done
in
the
core
version
is
really
good.
I
put
a
couple
really
nitpicky
little
like
wishlist
items
and
the
mission
cue
and
just
took
them,
took
care
of
them
right
away.
A
So
oh
definitely
encourage
more
people
to
take
a
look
at
that
and
I
I'm.
Looking
forward
to
seeing
it
next
issue,
566
is
about
adding
sticky
submit
buttons,
so
this
would
be
if
you
had
a
really
really
long
form
the
buttons
are
sick.
The
bottom
of
your
page
shows
your
scrolling
button
to
always
be
accessible.
A
I,
think
the
polar
press
is
in
good
shape
and
what
we
need
on
that
is
feedback.
So
if
anyone
wants
to
take
that
poor
request
for
a
little
test
ride
in
the
sandbox,
let
us
know
if
you
think
it's
improvement
or
not.
It's
definitely
one
of
those
things
where
it
really
depends
on
who's
using
it,
whether
they
think
it's
better
than
it
was
before
I
really
like
it,
but
I
would
love
to
get
more
opinions
on
that
before
we
commit
it.
A
Next
issue,
remember
1383.
This
is
just
a
quick
one
to
update
the
button
text
when
you're
saving
a
form.
So
you
know
what's
gonna
happen
when
you
hit
the
Save
button
right
now,
he
just
says
save.
This
is
for
a
note
form
in
particular,
if
you're
gonna
publish
the
content
mean
you
would
save,
it
should
say,
publish
if
you're
gonna
schedule,
it
should
say
schedule.
We've
got
some
I
think
recommendations
in
there
for
what
it
might
what
the
text
might
be.
A
A
The
next
one
is
to
make
the
help
text
more
legible,
for
publishing
status
options
so
also
related
to
other
year,
creating
a
draft
publishing
or
scheduling,
there's
sort
of
a
really
long
paragraph
of
text.
That
explains
what
all
of
those
things
do,
rather
than
having
a
nice
concise
sentence
for
each
one.
So
there's
a
couple
of
recommendations
here
about
how
we
could
separate
that
out
into
something
that
might
make
more
sense
for
each
and
then
there's
also
another
issue
about
styling
sort
of
globally
in
cor.
A
How
we
should
handle
the
description
text
in
particular
or
Radio
options,
and
then
next
up
is
just
a
clarification
on
the
dependency
message.
This
is
number
28
2015.
You
are
making
updates
from,
for
example,
a
triple
sevens
backdrop.
If
you
can't
run
an
update
hook,
it
should
tell
you
why
which
modules
the
problem-
and
we
already
had
all
that
data
as
part
of
the
update,
so
the
latest
version
just
prints
it
to
the
screen.
I
would
love
it.
A
If
that
got
our
view
to
make
sure
people
think
it's
clear
enough,
I
think
there's
some
pretty
good
steps
to
reproduce
in
there,
but
I
really
like
the
last
version
and
the
previous
version.
I've
written
changed
a
lot
of
stuff
and
then
English
didn't
have
to
do
that
because
all
the
information
was
already
in
there.
So
not
just
pins
out.
Let's
change.
A
I
think
we
have
already
set
up
the
main
backdrop
sites
to
promote,
but
we
have
not
yet
included
that
value
in
search
rankings
and
then
once
we
get
the
search
results
correct.
We
also
need
to
do
the
same
thing
for
the
project
modules
output,
and
this
would
be
what
affects
the
in-app
project
installer
and
so
right
now.
The
query
that
determines
the
results
of
the
search
is
hard-coded
in
project
Mondol
and
so.
A
Be
good
if
we
could
figure
out
how
to
make
that
query
match
the
results
of
the
search
on
the
front-end,
a
factor
of
CMS
org,
so
you're
getting
similar
results
that
when
we
search
for
the
same
thing
on
both
places,
but
my
original
intent
was
to
try
and
figure
out
how
to
get
that
search.
I
think
we're
turning
things
in
the
right
order.
First
and
then
we'll
figure
out
what's
necessary
to
update
project
module
once
we
know
the
actual
order.
A
C
A
A
C
A
A
D
I'm
sorry
I
thought
we
were
talking
about
updates,
but
are
we
talking
about
the
project
so
just
like
the
project
browser
that
that's
sorry
yeah?
Secondly,
it's
a
JSON
feed
that
gets
returned;
okay,
but
you're
right
that
the
order
comes
back
from
backdrop,
CMS
org
and
then
the
search
results
just
display.
Whatever
backdrop
see,
my
start:
work
returned
okay,.
A
A
Oh,
that's
it
for
user
experience
issues,
so
we
don't
have
anymore
user
experience
issues,
there's
a
lot
of
user
experience,
issues
and
backdrop.
We
know
that
and
every
time
we
have
a
good
idea
about
how
to
fix
something
or
really
complain
about
something.
We
usually
create
an
issue
with
UX
and
square
brackets
in
the
title.
So
if
you're
particularly
interested
in
user
experience
and
want
to
see
the
issues
that
we're
working
on,
you
can
search
the
issue
queue
for
us.
A
We
also
have
a
special
milestone
for
the
next
major
version,
minor
version
of
backdrop,
which
is
112,
and
you
can
search
that
for
all
the
us
issues.
We
would
love
to
have
done
by
that
version.
The
great
thing
about
user
experience
issues
is
a
lot
of
times.
They
just
require
some
rewording
or
minor
improvements
of
text,
and
those
are
great
issues
for
people
who
haven't
contributed.
You
have
to
get
started
with
so
looking
through.
That
queue
is
also
great
way
to
find
good
versus
use,
work
all
right,
I'm.
Moving
on
to
design.
A
We
have
a
couple
of
issues
related
specifically
to
the
design
of
backdrop.
The
first
one
is
number
3209,
which
is
about
adding
predefined
color
schemes
to
basis
I
think
we
have
a
pretty
good
pull
request
here
that
has
a
bunch
of
colors
in
it.
My
last
feedback
on
that
one
was
that
we
should
run
all
of
those
colors
through
an
accessibility
checker
to
make
sure
that
the
contrast
is
high
enough
that
all
of
our
core
color
sets
are
accessible
out
of
box.
A
So
I
think
that
might
require
some
minor
tweaks
to
some
of
the
colors
just
to
make
sure
that
they
will
show
up
in
all
the
combinations
that
we
provide
by
default.
If
anyone
is
particularly
interested
in
accessibility
in
color,
that
would
be
a
great
one
to
get
wrapped
up.
You
think
I,
don't
remember,
but
I
think
I
threw
a
link
to
an
accessibility,
color
contrast
checker
in
that
issue,
but
if
not
I'll
take
that
later.
B
So
on
that
issue,
yes,
I
was
planning
on
doing
that,
but
I've
just
been
caught
up
with
stuff
and
I
also
wanted
to
there's
another
issue
to
allow
splitting
out
the
color
options
in
a
multiple
field.
Sets
and
I
wanted
to
do
that
as
well,
so
that
we
could
have
more
options
there,
because
we
kept
running
into
issues
where
we
like
didn't,
have
enough
option,
and
so
those
two
things
were
too
close
together,
because
they
were
using
the
same
colors
as
somewhere
else.
B
A
It
might
be
good
to
take
a
look
at
that
run
it
through
the
contrast,
checker
and,
if
they're
like,
for
that
pass,
just
get
those
in
committed
right
away
and
then,
if
they're
like
for
the
don't
push
those
until
we
can
get
all
the
additional
colors
added
in
field
sets
and
do
it
later
and
now
we
will
kind
of
get
something
done
rather
than
waiting
to
get
everything
done
all
at
once.
Current.
A
A
I'm
like
wait,
why
don't
we
just
fix
this
entirely
for
core,
so
I
have
an
issue
for
that,
which
is
what
this
is
three
three,
oh
nine.
It
looks
like
there's
some
concern
in
that
issue
that
just
removing
the
visual
tab
might
cause
a
problem
for
some
people
that
were
maybe
relying
on
it,
and
so
we
need
to
figure
out
a
way
if
we're
going
to
make
that
jessyca
change
in
core
how
we
would
make
that
better
for
everyone
who
might
be
using
them.
So
my
solution
was
like
a
formal
term.
A
That
would
add
a
new
form
element
that
contains
the
link
and
then
just
change
the
menu
call
back
type
for
those
tabs.
Instead
of
being
many
local
tasks,
just
making
to
be
like
many
links,
but
some
people
were
concerned
about
just
altering
people's
forms
to
furling
links
on
them
with
an
update
might
be
a
bit
heavy-handed,
so
there
were
also
some
recommendations
about
trying
to
do
it.
In
the
basis
thing.
My
concern
about
doing
it
and
the
basis
theme
is
that
anyone
who's
not
using
basis
or
something
would
not
get
the
advantage
of
the
change.
A
A
Would
it
be
ugly,
it
is
the
benefit
of
having
like
a
non
style
link
is
the
benefit
of
not
having
tabs
wrists
worth
the
risk
of
having
an
on
styling
on
one,
so
just
kind
of
figuring
out
like
if
that's
worth
pursuing
in
its
current
state
or
if
we
need
to
rethink
how
that's
so
I
love
feedback
on
that
issue.
Sue
people
think
very
onin.
A
Alright,
the
next
one
is
number
28
73.
This
is
to
redesign
the
installer
on
a
mobile.
So
if
you
desperately
need
to
install
backdrop
right
now
on
your
phone,
how
would
that
feel,
and
can
we
improve
that
we've
got
some
great
recommendations
about
how
it
can
be
done.
We
just
need
to
have
some
covert,
so
if
somebody
wants
to
write
some
CSS
and
maybe
a
theme
function
or
something
that
should
be
a
pretty
good
first
session
to
jump
in
on.
A
Next
is
basis
we
didn't
notice.
In
the
basis
theme,
the
maintenance
page
has
not
been
styled,
so
this
is
25:58.
You
can
take
a
look
at
the
maintenance
page
in
seven
and
the
maintenance
page
in
Bartok
and
say
that
they
both
have
sort
of
a
distinct
feel
to
them.
Where's
the
beef,
the
maintenance
page
in
basis,
is
just
a
blank
white
page
with
a
unstyled
message
in
it,
so
it
might
be
good
to
just
kind
of
say
in
a
basis
world.
What
does
our
mean?
A
It's
page
look
like
I
would
love
it
if
we
could
number
one
just
get
something
that
looks
like
it's
not
styled
there,
but
also
number
two.
If
we
could
use
this
as
a
way
to
kind
of
express
a
little
bit
more
of
backdrops
personality
in
branding
I've
seen
a
lot
of
really
cute
things
done
with
like
404
pages
lately
and
I
feel
like
that
gives
a
lot
of.
A
A
A
A
About
how
to
make
our
maintenance
page
four
basis,
cute
and
lovely
and
not
unbranded,
that's
a
good
video,
a
good
place
to
do
25
all
right
and
then
back
on
our
list.
Is
the
news
use
your
interface
redefine
redesign
31
71.
This
again
is
something
that
we
know
the
beauty
of
the
interface
is
over,
but
all
people
that
are
coming
to
us
from
gerbil
know
how
to
use
it,
and
there
is
extreme
value
in
that.
A
But
that
said,
I
do
think
we
need
to
rethink
this
and
I
think
that
in
a
couple
of
years,
when
we
no
longer
have
the
mass
onslaught
people
arriving
in
Vectra
from
Drupal-
and
nobody
has
the
muscle
memory
of
how
to
use
fuse,
we're
gonna
need
to
make
this
thing
a
lot
easier
for
people
to
understand,
and
so
it
would
be
good
to
think
about
that
problem
now
and
if
we
come
up
with
a
result
and
really
like
see
what
of
that
result,
we
can
integrate
now
without
breaking
that
memory.
A
So
it's
a
great
experiment
to
get
it
done
early,
and
then
we
can
see
what
what
we
can
use
now
versus
what
we
should
wait.
So
we
definitely
need
feedback
on
that
issue.
31
71
I
think
there's
a
great
design
there.
That
starts
to
kind
of
grip
things
a
little
more
logically
as
well
differently,
logically,
and
to
see
how
we
can
start
to
make
improvements
on
this,
and
if
you
are
very
interested
in
design
and
want
to
get
involved
with
the
backdrop,
we
have
a
tag
in
the
issue:
queue
audience
design.
A
A
C
An
airy
question
because
this
is
Larry
in
my
head:
it
came
up
in
a
UX
issue.
Do
we
allow
non-bank,
UX
issues
to
be
committed,
the
fixes
during
past
releases
or
what
they
have
to
be?
So
it
was
my
understanding
that
we
do
allow
small
fixes,
I
think.
A
It
depends
on
the
fix
like
if
it
is
a
small
fix,
like
the
terminology
like
changing
edit,
to
configure
or
something
yeah.
That's
that
counts
as
like
a
bug
fix.
But
if
it's
something
huge
like
reviewing
the
views
UI,
then
that
definitely
needs
to
wait.
I.
Think
Nate
was
your
rule
like.
If
it
needs
tests,
it
has
to
wait
for
a
minor
version.
A
A
C
Helped
was
there
so
so
it's
issued
3389,
which
there's
a
WTF
thing
there
going
on
with
resetting
passwords
and
the
reset
the
current
password
field
is
not
marked
as
required.
So
some
people
skip
it.
We
are
in
a
better
in
a
better
situation
than
Drupal,
because
we
have
removed
the
double
password
fields,
the
the
that
requires
the
confirmation,
so
we're
slightly
in
a
slightly
better
situation.
C
But
then
we
alternate,
we
have
a
username,
a
password
field,
email,
another
password
field,
so
either
click
the
two
password
fields
together
or
not
anyways,
but
the
solution
that
I
went
with
was
that
to
hide
the
hide.
The
current
password
field
until
the
moment
that
someone
edits
their
email
or
they
change
the
password.
So
I'm
not
sure
if
this
is
too
much
of
a
change
that
should
wait.
This.
A
C
A
I
can
think
of
a
way
that
we
could
fix
this
like
for
this
particular
issue,
but
we
might
also
want
to
take
a
step
back
and
say.
Maybe
this
is
something
that's
gonna
happen
like
all
over
easing
our
form
states
where
there
could
be
something:
that's
not
required
until
something
else
is
in
a
certain
state,
and
do
we
have
a
process
for
marking
that
not
only
in
validation
but
also
on
the
front
end
and
figuring
out.
If
there's
like
a
found,
States
thing
we
should
implement.
That
would
make
that
happen.
So.
C
There
is
a
Dakotas,
your
core
issue,
we're
against
the
form
API,
so
the
source,
so
the
required
property
does
not
work
with
States.
That's
the
problem
right.
You
cannot
use
States
to
say
when
a
field
is
required.
In
that
case,
we
would
abuse
this
so
the
workaround
or
the
hack
that
I
have
used
for
my
solution.
There
was
so
sorry,
let
me
rephrase
that
what
I
said
before
it
doesn't
practically
work
with
validation
wise,
but
it
does
like
when
you
use
the
states
in
combination
with
requirement
required.
C
The
field
does
get
the
asterisk,
with
the
note
says,
as
required
that
the
validation
doesn't
work,
so
we
still
need
the
validation,
the
custom
validation,
so
I
added
that
just
to
indicate
it
and
then
so
to
make
it
selective
doesn't
seem
as
always
required.
I
keyed
the
field
and
I
make
it
show
up
only
if
someone
adds
something
in
the
email
or
the
password,
so
that
field
is
completely
hidden
away
until
someone
actually
changes
they
mail
or
types
in
your
password
and
in
that
case,
I'll
indicate
it
as
required
is.
A
There
I
mean
it
still
that
still
sounds
sort
of
like
a
custom
solution
for
this
page
I.
Don't
know
that,
maybe
that's
what
we
need
to
pursue
here,
because
that's
gonna
be
much
easier
than
fixing
form
API
seats,
but
is
there
some
way
that
we
can
so
what
what
state
sends
handle
like
JavaScript,
stuff
right
so
making
something
validate
or
not
validate
is
happening
in
PHP,
but
I
wonder
if
there's
some
kind
of
flag
we
get
adding
JavaScript
that
would
enable
or
disable
the
pound
validate.
A
A
Active
anything
I,
don't
tonight,
I
run
into
the
sewer
I'm
trying
to
to
make
like,
as
I
move
modules
from
triple
to
backup,
I'm
sort
of
doing
a
hughster
experience
clean
up,
and
a
lot
of
that
is
adding
count
states
so
that
things
that
aren't
required
until
they're
required
physical
hit,
invisible
sort
of
stuff
and
they're
required.
Something
super
tricky,
so
yeah
I
mean
I.
Think
like
there
is
going
to
be
an
underlying
form,
API
change
somewhere.
A
We're
gonna
have
to
figure
out
how
to
get
the
front
back
talking
to
each
other
in
order
to
make
that
work,
but
I
think
maybe
you're
right
that
we
should
just
figure
out
the
hack
for
the
user
form,
because
we
know
this
is
an
issue
there
and
that's
gonna
happen
on
every
backdrop
site
ever
and
I
like
your
idea
of
adding
the
pound
required
marker,
but
hiding
the
field,
because
that
would
people
won't
see
the
required
marker
until
they
make
the
change
and
then
once
they
make
the
change.
A
C
The
alternative
that
I
thought
yeah
before
I
implemented
the
solution
with
hiding
the
field,
the
alternative
that
I
thought
was
if
there
was
a
way
to
use
States
to
show
and
hide
just
the
indicator,
because
if
you
have
the
required
indicator
all
the
time,
it
doesn't
make
sense
still
because
it's
not
required
until
someone
changes.
Those
two
fields,
yeah
is.
A
Form
API
versus
html5,
like
I,
think
if
you
mark
a
field,
is
required
in
html5,
it'll,
fail
validation
on
the
front
end
too
and
I
think
we
need
to
be
careful,
we're
not
doing
that,
especially
for
hidden
fields,
because
that
would
be
super
confusing.
But
if
all
we're
doing
is
adding
an
asterisk,
that's
really
funny
yeah.
C
The
thing
is:
it's
not
it,
that's
not
the
underlying
problem.
The
underlying
problem
is
basically
that
we
are
having
conditionally
required
fields
and
when
a
person
has
an
overview
of
the
page
and
say
they
type
something,
and
the
only
change
that
happens
is
that
the
asterisk
then
appears
it
might
not
get
noticed
right.
C
C
Yes,
so
you
you
have
a
new
password
field,
which
is
a
single
one.
Now,
because
we
have
the
show/hide
thing
with
the
password
and
once
you
start
typing
in
it,
the
the
required
field,
the
current
password
just
shows
up
okay
right
underneath
it.
So
it's
not
I.
Guess
it's
more
obvious.
The
only
situation
where
it
wouldn't
be
obvious
I
guess,
is
its
small
viewports,
where,
while
you're
editing
the
current,
the
new
password
field
is
right
at
the
bottom
of
the
screen.
So
when
the
parent
password
thing
shows
up,
it's
outside
your
viewports
yeah.
C
C
A
C
A
C
A
Okay,
so
that's
it
for
back
to
team
s
at
work
issues
in
fact
up
C
message
use
product
is
she
said?
Okay
next
up
is
print
design.
We
would
love
to
have
a
banner
like
a
pop-up
in
or
not
a
pop
up
on
your
website
like
an
actual
physical
thing,
we
could
put
next
to
a
table
for
backdrop,
the
bumps
anyone
wants
to
design
one.
We
don't
have
anyone
with
those
skills
working
on
it.
A
A
A
A
C
A
C
There's
one
sorry
I
just
it
just
came
to
me
now,
there's
another
design
issue,
what
we
have
a
specific
issue
and
for
that
but
see
how
we
redesigned
the
listing
for
the
views
and
we
added
the
naming
and
the
sorry
that
the
label
of
the
view
and
the
machine
names
we
added
in
the
same
column.
And
we
said
that
we
should
be
consistent
with
the
rest
of
the
UI.
So
we
have
a
ticket
for
that
specifically.
C
A
I've
added
two
new
items
to
this
agenda
for
the
views
listing
clean
up
an
admin,
interface,
consistency
and
I
will
figure
out
where
those
issues
are
throw
links
in
here.
Yeah
I
read
the
comments
on
that
I
thought
they
were
all
spot
on
and
like.
If
we
have
plenty
of
space
mining
things
in
the
columns
may
not
make
sense
the
long
we
don't
have
space
I,
think
mining
them
does
make
sense,
so
I
think
sort
of
every
interface
we'll
have
to
figure
out
like
whether
it's
worth
pushing.
C
In
and
since
we're
bringing
this
up,
I
was
testing
in
the
same
issue.
The
the
mobile
version
of
the
useless
thing.
It's
completely
different
than
the
rest
of
the
you
I
saw
so
for
the
rest
of
the
UI.
We
use
priority
sorry
priority
classes
for
the
colons
that
show
and
hide
them,
but
if
usually
use
a
vertical
table,
thingy
I,
don't
know
what
to
call
it.
A
Is
sort
of
completely
different
from
the
rest
anyway,
so
I'm
not
too
worried
about
that,
but
I
think
that
it
just
because
there's
a
lot
more
information
there,
but
I
think
that
we
should
maybe
look
at
the
way.
Everything
else
is
done
and
make
sure
that
it's
all
done
consistently
across
everything.
And
then,
if
we
find
a
way
that
we
think
it
should
be
the
same
with
something
weird
that
stick
with
it
should
be
different.
We
should
fix
that
yep.