►
From YouTube: Backdrop Design 12/22 (review entity view modes UX)
Description
Today’s design agenda: https://goo.gl/2BPb0j
A
It
is
december
twenty.
Second,
everybody
we're
going
to
do
a
quick
design
review
meeting
I've
shorten
the
agenda
down
to
include
some
of
the
design
test
for
working
on
right
now,
as
well
as
some
issues
for
backdrop,
16
that
we
should
probably
review
and
then
we'll,
hopefully
end
early,
keep
working
on
backdrop
16
before
the
other
meeting
today,
let's
see
so
the
first
item
on
our
list
is
backdrop
CMS
homepage,
design,
I,
don't
know
if
you
have
any
updates
on
that
Wes
I
do.
C
C
A
C
And
I
haven't
even
bother
styling
this
yet
get
the
Pantheon
block
here
and
then
I
just
kind
of
left
this
stuff,
because
I
want
to
get
this
to
a
point
where
I
can
start
I,
don't
like
that,
have
perfect
at
all
or
I
can
start
like
weddings
cut
out.
Maybe
some
other
people
can
help,
but
or
I
can
do
it,
I,
don't
care
and
then
so
yeah
also
of
note
that
the
search
bar
is
here
which
I
didn't
consider
when
I
originally
designed
it.
C
C
C
It'd
be
great,
so
yeah
I
haven't
considered
everything
yet
so
like
that,
for
example,
I
haven't
done
the
smallest
mobile
size
yet,
but
I
think
my
idea
is
that
the
search
bar
will
just
be
here
at
the
bottom
and
maybe
be
there
whole
time
and
I'll
just
shrink
up
this
stuff
or
it
may
be,
can
only
show
up
when
you
have
it
open,
I,
don't
know
I'll
figure
it
out.
So.
C
C
But
man
looks
like
a
thing
and
then
I
also
got
the
the
default
layout
working
now,
so
I
was
going
to
go
through
a
couple
more
layouts
and
switch
them
over,
because
the
pages
that
are
on
old
layouts
look
like
crap
and
then
after
that,
I
was
going
to
push
everything
up
and
then
other
people
could
help.
If
they
have
time
are.
A
C
A
C
Yeah,
so
this
was,
this
is
the
one
that's
just.
These
are
just
headings,
and
these
are
actual
link,
so
these
ones
work
if
I
it's
just
yeah
I
need
to.
We
need
to
get
rid
of
that
module
and
then
figure
out
what
we
want
to
do
with
handbook,
if
anything
at
the
moment,
and
then
I
was
going
to
make
this
real.
So
if
this
is
just
a
Content
issue,
basically
yeah
there's
there's
plenty
of
stuff.
Here,
that's
not
done
so
yeah.
B
B
C
A
C
A
C
A
B
A
B
C
Yeah,
it
struck
me
weird
that
the
on
the
current
side-
it's
flip
flop,
because
to
me
the
header
is
actually
secondary
and
we
actually
want
people
paying
attention
to
the
content
area.
Yeah
you
know
in
the
search
bar
obviously
is
important,
but
yeah
the
really
big
search
browse.
It
looks
great
cool
array.
A
B
A
All
right,
let's
see
so
that's
it
for
home,
page
redesign.
The
only
other
stuff
I
put
on
our
agenda
today
are
issues
related
to
backdrop.
16
I
put
entity
reference
on
here
because
it
looks
like
there
have
been
a
couple
of
new
user
experience,
reviews
their
issues
in
the
queue
about
like
removing
the
word
entity
and
bundle
and
trying
to
figure
out
what
that
looks
like,
but
I
haven't
played
with
that
very
much
from
user
experience
perspective.
A
A
A
That's
kind
of
a
weird
way
to
integrate
user
interface
to
systems
were
already
using,
and
there
are
a
bunch
of
interesting
recommendations
from
the
people
who
are
working
on
it
to
take
the
entity,
view
modes
list
and
replace
the
manage
display
pages
for
each
entity
with
that
list,
and
then
that
way
it
would
lose
that
weird
navigation
pattern.
We
have
and
feel
do
I
where
you
have
to
use
sub
tabs
for
managing
displays
yeah.
Why
don't
we
both
the
same
locks,
yeah.
A
So
here's
the
where
we
are
right
now
and
we're
working
on
the
text
at
the
top
there's
too
much
text
and
it's
two
entities
specific
or
in
this
case
notes
specific.
So
what
we're
going
to
do,
I
think,
is
delete
the
second
paragraph,
and
this
way
I
have
right
now,
there's
some
really
great
recommendations.
A
Some
of
these
view
modes
are
custom
and
if
they're
custom,
you
get
options
to
configure
them,
which
is
really
just
changing
their
name
I
and
delete
them,
and
if
they're
not
custom
view
modes
like
we
look
at
teazer,
then
you
don't
get
the
ability
to
change
the
same
and
you
don't
get
the
ability
to
delete
it.
That's
because
that's
too
provided
in
code.
If
we
have
view
modes
are
not
customized
if
they're
using
the
default
display,
I
initially
put
them
in
this
collapsed
field
set.
A
So
like
full
content
is
down
here
and
people,
wouldn't
my
thought
was
that
beginners
come
in
at
his
page.
Aren't
going
to
know
what
a
view
mode
is
their
use
cases
I
want
to
change
the
way
my
fields
are
for
full
content
and
if
we
show
them
the
full
content
view
mode
they're
going
to
come
here,
customize
it
which
will
override
the
display
and
then
they're
going
to
have
to
just
manage
the
fields
for
every
single
view,
mud
rather
than
doing
the
default,
but
it
sounds
like
overwhelmingly.
A
People
do
not
like
this
pattern
of
putting
a
second
table
inside
a
collapse
field
set
and
so
right
now
the
suggestion
is
to
make
it
work
more.
Like
the
layouts
you
I,
where
there
is
won't,
you
know
the
custom
ones,
customized
ones
will
come
at
the
top
and
then
the
disabled
ones
would
come
at
the
bottom
section.
A
Well,
yeah:
let's
open
that
too,
it's
a
little
bit
like
if
you
see
you
I
I
did
change
the
color,
so
the
disabled
ones.
Are
this
lighter
gray
and
I
got
that
from
the
views
you
I
the
difference
here.
The
things
I
think
that
would
be
confusing
about
these
two
things
is
that
in
the
views
you
why
the
disabled
ones
have
a
very
obvious
like
enable
link
on
the
right.
A
They
are
not
disabled
or
and
there's
like
no
difference
between
the
default
ons
and
the
non
default
ones.
In
terms
of
their
functionality,
so
these
are
just
they're
always
in
use,
and
you
just
change
it
and
it
works
everything
so
I
don't
know
how
does
like
we've
got
three
slightly
different
use
cases
and
three
slightly
different.
You
eyes
that
are
all
fairly
similar
and
it's
a
little
tricky.
But
what
we
could
do
is
if
we
put
the
default
view
mode
at
the
bottom.
A
Originally,
the
entity
view
modes
module
used
an
action
link
which
I
removed
initially
because
it
didn't
it
made
sense
to
treat
it
more
like
to
feel
you
I
and
put
it
in
line.
But
now
that
we
have
a
table
here
view
modes,
all
of
our
other
ones
have
a
new
whatever
at
the
top,
like
all
of
our
other
you
eyes
and
so
I
think
it
makes
sense
to
go
back
to
using
that
action
link.
So
we
could
say
idea
mode
at
the
top
now
get
rid
of
that
funky
row
at
the
bottom.
C
A
B
A
A
B
B
A
C
Also
gets
around
an
issue
were
like
you'll,
create
a
like
I
just
created
a
view
mode
called
gallery,
teaser
I'd
to
make
it
for
stupid
reasons.
I
was
upset
that
I
couldn't
just
use
teaser,
but
anyway,
I
have
made
view
modes
that
are
pretty
specific
to
one
or
two
content
types
and
in
the
context
of
other
content
types
they
just
don't
make
any
sense.
So,
like.
B
B
C
A
B
B
B
Be
super
useful
because
that's
like
a
you
know,
one
out
of
two
websites
wants
it
one
way
and
one
I
have
to
once
it
the
other
way.
All
right.
It
would
be
really
great
to
have
that
as
an
option.
Now
that
we
have
a
legitimate
place
to
put
it
in
Drupal
7,
and
your
blade
like,
where
do
you
put
settings
for
a
breadcrumb,
you
know,
is
that
like
I
guess,
she's
having.
A
A
A
A
A
A
Oh
yeah
here
we
go
my
should
style
overrides.
So
this
is
something
I
noticed
when
I
had
to
make
a
basis
sub-theme.
As
soon
as
you
created
something
for
bases.
All
of
your
message.
Styles
are
broken,
so
you
get
just
text
with
no
color
and
no
image,
and
that's
because
basis
tried
to
override
the
system
theme
CSS
file,
which.
A
So
we
have
this
room
right
now,
we're
anyone
who
creates
it
basis.
Sub-Theme
doesn't
get
message
styling
and
then
it's
really
really
hard
to
put
it
back,
because
you
have
to
then
go
manually
copy
all
of
those
images
from
wherever
they
were
in
core.
You
can't
just
undo
the
styles
that
are
in
basis
because
basis
does
them
all
over
again,
so
you
can
either
copy.
B
A
A
Unless
they
wanted
them
to
be
different
and
we
spent
a
long
time
making
them
really
nice
and
backdrop
whenever
it
was
we
put
in
the
new
admin
theme
fixing
them
in
seven.
It
would
be
great
if
we
could
actually
love
people
to
use
those
and
since
right
now
the
theme
that,
like
comes
out
of
like
the
default
theme,
makes
it
really
hard
to
work
with
I
thought.
It
would
be
good
if
we
could
fix
that
in
core.
A
A
A
B
A
Don't
know
guessing
on
our
intended
target
audience,
I'm
guessing
those
are
not
people
who
gent
generally
remove
style
sheets,
the
way
that
we
did
in
basis.
That's
why
it
was
a
good
teaching
fool,
but
it's
also
like
I'm,
just
gonna
create
a
theme
heard
from
scratch:
you're
not
going
to
know
how
to
do
that.
So
yeah.