►
From YouTube: Backdrop CMS Design call 9/24
Description
Design task review for Backdrop CMS
A
B
So
so
we
like
to
get
together
every
two
weeks
and
talk
about
design
everything
design
related
in
the
project
and
around
the
project
and
the
first
area.
We're
going
to
talk
about
this
week
is
backdrop
the
product
and
some
areas
in
which
we're
making
some
headway
or
would
like
to
make
some
headway.
As
most
people
probably
know,
1.2
came
out
actually,
since
our
last
design
meeting
so
1.2
is
now
out
on
1.3
is
our
next
release,
which
is
where
most
of
our
design
work
probably
will
be
focused.
B
1.3
actually
is
intended
to
be
just
a
like
a
UX
release,
we're
just
working
on
polishing
this
release,
rather
than
adding
nature
new
modules
or
major
new
features,
which
often
means
redesigning
some
of
our
you
eyes
or
just
expanding
the
knots
at
their
friendly
air
and
possibly
redesigning
some
things
that
haven't
been
fully
converted.
Yet
things
like
that,
so
we've
got
three
major
systems
and
all
three
of
them
kind
of
need.
B
A
UI
overhaul,
maybe
not
an
overhaul,
but
some
improvements,
layouts
views
and
fields
and
of
those
you
eyes
filled
dy
is
probably
the
worst
off,
because
it's
the
oldest
UI
and
it
kind
of
was
rushed
to
get
put
into
Drupal
7
and
has
really
ever
seen
any
love
or
changes
ever
since.
So,
if
you,
otherwise
the
most
important
one
and
Wes
was
drawing
disk
this
week
has
done
some
work
on
that
which
looks
really
pretty
exciting
and
west.
You
want
to
give
a
rundown
and
from
your
thought
process
here.
C
B
Me
see
I
do
I'll,
be
I'll
pay
system
to
hang
out.
Yet
it's
also
in
the
oh.
It's
also
an
agenda.
I'm.
C
Alright,
so
shared
my
screen
here
so
a
while
back.
We
had
some
good
thoughts
from
quick
box
and
he
had
ideas
around
like
you
know,
iconography
and,
like
you
know,
moving
things
around
and
I
liked
kind
of
what
we're
his
mind
was
that
and
I
also
steal
a
lot
from
I
mean
borrow
from
if
this
than
that,
whenever
I
think
of
a
complicated
form.
C
If
this,
that
is
by
far
one
of
the
most
complicated
forms,
I've
ever
seen,
but
I
don't
dislike
using
it,
so
I
think
they've
done
something
rather
good,
so
I
kind
of
went
through,
and
if
this,
then
that
flow
just
to
remind
myself
and
so
then
tried
to
break
down
from
a
user's
perspective.
Okay
I
have
this
and
I'm
trying
to
do
this.
So
I
started
with
the
ad
field
screen,
so
first
I,
think
of
okay.
What
kind
of
cut
data
content
do?
C
So
that's
the
first
step,
and
then
I
just
added
a
little
like
green
line
there
to
show
you
kind
of
way
you're
at
and
the
next
screen.
It's
like
okay,
I've
chosen
text
and
it's
and
then
like
I
kind
of
worked
with
the
wording.
A
bit
and
I
landed
on
editor
interface,
so
like
when
you're
filling
out
making
a
new
node
I,
think
that's
how
people
might
think
of
it
and
then
I
wanted
to
just
show
what
that
looks
like.
So
it's
like
it's
kind
of
the
Denny's
menu.
C
B
A
C
C
All
there
are
idiot
in
the
Dom
you
just
kind
of
show
the
one
that's
active,
and
that
way
people
kind
of
people
from
the
old
system
might
have
a
better
idea
of
like
how
this
is
flowing,
and
then
people
who
maybe
aren't
as
sure
what
kind
of
data
they
have
once
they
see
like
on
the
right.
What
what
it
looks
at
the
dennys
menu
that
they'll
be
more
confident
in
their
choice
and
the
other
idea
I
had
is
like
at
no
point
when
you
select
any
of
these
options.
C
None
of
this
submits,
none
of
it
starts
like
the
multi-step
form.
Right
now
is
kind
of,
like
you
take
a
step,
and
you
kind
of
can't
take
some
steps
back,
like
you've
already
gone
far
enough,
that
something's
written
in
hard
clay,
yeah
yeah.
So
my
idea
is,
it
doesn't
actually
until
you
do
create
feel
at
the
bottom,
nothing's
actually
written
to
config
or
anything,
it's
just
all
here.
So
then,
in
order
that
we
don't
lose
any
progress
as
thinking
we
could
probably
do
like
right.
The
forum
state
to
their
session
until
it's
submitted
know.
C
Happens
it's
saved
so
then
we
select
a
radio
button.
So
then
I
was
all
right.
Then
there's
kind
of
the
options
of
okay
I
want
to
do
a
human
named
machine
name
I
might
want
to
change
the
order
and
I
was
thinking.
You
know
these
are
kind
of
like
the
ridges
on
a
physical
device
that
you
might
drag
around.
It's
a
something
they
use
in
iOS,
I
kind
of
like
it
and
that
the
hand
cursor
we
could
do
like
a
grabby
hand.
Yeah
have.
C
B
There
actually
is
a
port
but
I'm
gonna,
link
to
dribble
it
or
because
I
screenshot
cool
options,
comments,
yeah.
C
I
always
want
this,
but
they
don't
realize
the
repercussions
of
it
sometimes,
like
you
can't
save
a
draft
if
you
have
something
required
and
that
user
isn't
have
yet
so
then
editor
interface
again.
So
this
is
the
stuff
that
editor
will
end
up,
seeing
so
label
help
text
etc,
and
then
I
also
wanted
to
have
this
default
value.
Section
be
populated
dynamically,
as
you
type
stuff
in
here
mm-hmm,
which
is
possible
cool,
just
DX
requests,
yeah
I
thought.
C
B
We
might
need
to
come
up
with
something
kind
of
clever
like
a
witch.
I
don't
like
I'm,
not
like
clever
what,
because
right
now
backdrop
needs
the
field
definition
to
already
exist
before
it
can
like
show
you
a
widget
form
or
something
like
that,
so
actually
telling
it
having
it
render
the
back
end
version
of
a
widget,
invalidate
back
in
version
of
a
field
before
that
field
actually
exists.
B
Is
it's
going
to
take
a
little
bit
of
work
because,
right
now
those
fields
actually
need
to
really
have
already
been
created
because
of
like
you
say
that
as
soon
as
you
create
a
new
field,
then
immediately
it
starts
to
exist,
and
it's
just
powder
a
bunch
of
defaults,
and
then
it
just
kind
of
takes
you
through
the
rest
of
the
steps
to
configure
it
as
you
like
right,
but
as
soon
as
you
select
the
field
and
save
its
field
settings,
then
it's
like
it's
now.
It
now
exists,
even
though
it's
not
really
configured
sure.
C
I
was
thinking
more
of
like
when,
whenever
I
see
a
angular
demo
or
whatever
it
just
like
pumps
bunch
in
HTML
in
and
then
it
like
it
does
the
two-way
binding
thing.
So,
as
you
type
it
just
things
and
I,
don't
think
we
needed
to
have
it
like,
as
I
type
character
it
shows
up
down
here,
like
as
they
Eggman,
whatever
they
exit
the
field.
It
updates
down
here,
yeah.
B
C
Or
whatever
it's
called
so
that
was
my
thought,
and
it
wouldn't
necessarily
have
to
be
something
that
came
out
of
like
the
form,
API
or
I,
don't
know,
but
you're
right,
it
is
clever
and
if
they
don't
have
javascript,
this
would
end
up
being
a
multi-step
form,
in
which
case
this
would
be
a
lot
more
straightforward.
Yeah.
B
A
B
Something
like
that,
then
we
just
bind
a
plural
ER,
and
then
we
click
the
button
automatically
in
the
Ajax
loads.
Instead,
none
so
yeah.
All
of
that
sounds
sounds
we
good.
What
do
you
think
about
this?
This
field
selection
type,
it
looks
like
this-
is
pretty
literal,
like
maybe
you'd,
even
let
the
browser
vendor
or
radio
button
and
a
checkbox
in
the
select
list
is
that
what
you're
thinking
are
you
thinking
more
like
an
image
representation
of
these
things?
Whatever.
C
Works
better
I
mean
there
might
be
cases
like
the
user
needs
to
be
able
to
click
anywhere
on
here.
Oops
horsham,
zooming
out
needs
to
be
able
to
click
anywhere
on
here,
and
then
it
selects
that
you
want
a
select
list.
So
if
the
select
list
widget
makes
that
a
pain,
maybe
it
should
be
a
select
this,
but
you
know
ideally
yeah
I
would
want
to
look
like
whatever
their
browser
and
operating
system
would
render
that
as
well.
A
B
C
B
B
A
Like
in
the
in
the
in
the
code,
and
so
what
we
could
do
is
say
like,
if
there's
only
one
and
it's
the
default
skip,
this
step
show
them
what
they're
getting
but
like
don't
make
it
a
question.
Just
move
on
to
the
next
yeah.
B
C
Yeah
I
know
if
it
wasn't
clear
enough
fingers
kind
of
abstracts
like
if
you're
doing,
text
versus
a
number.
Both
of
those
could
be.
You
know
list
which,
in
the
current
UI
is
elana.
Maybe
it's
not
a
great
example
but
they're
like
I'm
I,
I'm
abstracting,
the
like
the
first
two
steps
here
are
abstract
incorrectly
mapped
to
the
data.
How
we
store
it
then-
and
this
is
I'm
trying
to
map
it
more
to
how
a
user
might
understand
it.
Yeah.
A
C
A
And
I
think
we
are
gonna
need
to
rework
that,
like
philosophically
a
little
bit
like
to
change
these
your
interface
map
and
then
match
the
mental
model
and
not
the
data
model,
I
think
that's
totally
fine
I
think
like
this
will
force
us
to
do
it
like.
If
we
think
about
like
okay,
what
goes
here
then
it's
like
okay.
Well,
what
data
type
is
this?
Oh,
it's
not
a
list
data
type,
it's
a
number
data
type
and
then
we'll
have
to
rework
that
code
to
match
that
which
I
think
is
fine.
Okay,.
C
Yeah
I
was
thinking
if
the
code
was
that
way
for
some
really
good
reason,
because
databases
are
black,
then,
like
we
really
just
have
to
understand.
If
a
select
this
this
and
this,
then
this
is
how
we
store
that,
and
this
is
what
that
ends
up.
Looking
like
in
the
data
side
and
like
there
might
be
cases
like,
let's
say,
entity
reference
on
the
widget
side,
it
would
say
you
know
you
want
autocomplete
or
you
want
a
select
list
or
whatever,
but
that
but
then,
like
I,
think
you
ought.
A
A
I'm
also
not
entirely
sure
this
is
a
non.
You
know,
I'm
going
into
a
rabbit,
a
lawyer
I'm
not
entirely
sure.
We
want
entity
reference
for
backdrop,
I
spent
a
bunch
of
time
working
on
porting
it
and
then
reporting
references
module
which
had
already
been
ported,
which
was
a
little
sad
but
anyway,
the
last
week
and
I
just
I
kept
getting
stuck
in
the
way
the
entity
reference
worked,
even
though
I
like
the
end
result
like
I,
like
the
user,
the
user
interface
of
the
way
ND
reference
works.
C
A
C
C
A
C
A
B
C
B
B
C
C
Not
yeah,
I'm
not
sure
that
wouldn't
would
because
it
seems
like
it
seems
like
putting
the
cart
before
the
horse,
like
it
does
sound
nice
from
a
user
perspective,
but
then,
like
I,
think
you
would
make
it
easier
to
make
mistakes
like
you're,
saying,
like
I
you're
talking
about
you're
trying
to
store
before
you
decide
the
container
you
know
like,
if
you
think
of
it
littles
and
say
if
its
water
I'm
gonna
get
a
bucket.
If
it's
like
a
bunch
of
action
figures,
I'm
gonna
maybe
still
use
a
bucket
I,
don't
know
almost.
A
A
Exactly
that
yeah,
but
that
also
makes
it
really
complicated,
because
you
need
not
only
the
data
but
also
the
data
type
in
order
to
actually
render
it
and
the
editor
is
like.
You
can
swap
that
at
any
time.
But
yeah
I've
got
some.
A
A
B
C
A
Them
either,
if
you're,
a
graphic
or
under
item
or
whatever.
That
makes
a
lot
more
sense.
I'm
a
little
bit
concerned
about
Nate,
you
mentioned,
providing
the
same
amount
of
space
for
each
item,
but
I,
don't
think
that'll
mapped
anyone's
mental
model
because
the
a
text
field
and
a
body
field
are
not
the
same
amount
of
space
on
the
page
and
I
think
that
might
be
really
disk
enduring
to
people.
If
you
have
a
text
with
its
huge
or
a
paragraph
field,
it's
tiny
they're
not
going
to.
A
B
There
I
mean
yeah
well
since
I
have
a
survey
website.
Oh
yeah,
there's
that
something
like
it
needed:
okay,
there's
an
example
on
web
forum
com:
you
can
just
go
web
forum
com,
/,
demo,
I,
think
I
show
you
smell.
B
Yeah
sure,
actually,
that
long
yeah
this
stuff-
ok
so
my
giant
face
so
so
this
is
form
builder.
This
is
what
I'm
saying
where
it's
like
icon
and
maybe
the
icon
can
be
a
lot
larger
than
these
guys
are.
But
you
know
you
have
these
representations
of
yeah,
sorry
that
count
blows
out
there
a
little
bit
yeah.
C
C
B
So
anyway,
the
you
know,
like
things
like
a
hidden
field,
you
know
it's
just
like
a
braid
out
box
or
something
like
that,
and
these
might
be
I.
Don't
know
that
mean
there's
there's
a
you
know:
icon
representation
then
kind
of
really
simple,
and
maybe
he's
like
how
to
be
a
lot
bigger,
because
the
space
that
we
have
in
this
new
interface
is
a
lot
larger,
and
this
was
all
kind
of
designed,
for
you
know
a
desktop
interface
for
the
cursor
and
I
think
that
these
days
you'd
end
up
with
something
much
larger.
A
B
Well,
maybe
that's
what
we
could
do,
then
in
wes's
mock-up
is
yeah
make
it.
So
the
first
thing
you
see
when
you
select
something
is
the
default
value
form.
You
know
something
that
renders
a
preview
so
that
way
as
you're
clicking
in
between
the
different
icons,
then
you
get
representations
of
those
things
right
away.
Yeah.
A
B
A
One
thing
this
is
a
crazy
idea
to
just
to
make
it
twice
as
hard.
One
thing
we
could
do
too
is
if
we
had
a
visual
representation
of
the
form
element,
but
also
a
visual
representation
of
the
rendered
data.
So
when
you
dragged
in
like
a
body
filled,
you
would
get
a
text
area
on
the
left
and
then
I'd
paragraph
text
on
the
right.
So
you
would
get
feedback
from
both
of
those
things.
Mm-Hmm.
C
B
C
C
B
You
can
yeah
I,
look
a
good
option
to
hide
yeah
and
then,
and
then,
if
you
want
yeah,
usually
leave
it
that
you
know
most
people
don't
care
what
the
internal
representation
is
them.
But
then
this
Maps
back
to
the
way
it
works
right
now
and
actually
like
default
value,
is
even
like
you
know
you
can
actually
even
type
that
out
so.
C
A
It's
definitely
valuable,
considering
our
primary
target
audience
or
people
coming
from
Drupal
they're
gonna
have
like
I'm
building
a
new
site,
that's
in
Drupal
6
right
now,
I
often
just
edit
the
field
and
coffee
that
giant
massive
glob
and
then
drop
it
in
the
new
site
and
the
cult
done
and
I
think
there's.
There's
definitely
value
in
that.
But
I
would
love
to
like
not
have
to
expose
people
who
don't
know
Drupal
or
backdrop
to
that.
Weird
like
enter
a
key
and
then
a
vertical
pipe
and
then
a
value.
It's
just.
C
That
what
what
if
we,
what
if
we
made
it
so
you
could
toggle
like
a
view
of
the
config.
You
know
what
I
mean
like
we're:
gonna
connect
JSON
in
the
end
right
so
like
we
could
have
a
way.
So
then,
like
you,
have
not
only
the
options,
you
have
everything
you
and
like
the
people
who
know
that
well
can
do
it
and
everyone
else
will
just
ignore
it.
B
C
Like
I
was
thinking,
as
you
were,
explaining
like
heaven
having
a
view
of
what
it
will
actually
look
like
like
what,
if
this
was
a
two
column
design
and
the
left
column
was
the
setting
and
when
you,
when
you
selected
one,
it
would
move
the
the
left
column
would
move
and
get
you
to
the
next
one.
You
could
go
back
up
and
the
right
column
is
a
preview
at,
but
then
maybe
there's
a
tab.
It's
like
the
preview
or
the
config
code,
and
you
could
flip
fluff
I
like.
A
That
I
feel
like
maybe
maybe
the
config
code
that
might
be,
like
a
devout,
add
on
yeah.
It's
a
little
bit
more
sophisticated,
but
I
really
like
that.
You
know
the
ability
for
people
who
know
Jason
to
be
able
to
like
work
with
that.
I'm,
not
sure
I
want
to
encourage
new
users
to
like.
Oh
just
change.
The
code.
I
think
that
might
be
a
bad
about
a
habit
to
create
in
people
sure.
A
B
B
C
B
C
Other
thing
that
came
up
that
I
was
interesting
was
there
was
a
quest
to
be
able
to
add
multiple
fields
at
once,
and
the
comment
that
this
might
push
us
farther
from
that
and
I'm
not
sure
I
completely
understand
the
use
case,
but
it
seemed
it
made
me
think
like
okay,
if
it's
what
I'm
thinking
of
then
maybe
its
power
user
II,
and
maybe
that's
like
it's
not
invalid,
but
maybe
it's
a
contributor
like
you're
talking
about
putting
that
into
Bell.
Well,.
A
We
don't
need
all
the
confirmation
all
the
way
through
if
we
actually
set
intelligent
defaults-
and
we
don't
need
like
we
could
find
some
way
to
like
do
that,
all
at
once
and
I
think
that
if
we
can
do
the
intelligent
configuration
options
that
could
still
be
valid.
Even
with
this
model,
where
you
could
like
dragon
text
field,
one
dragon
text
field,
two
dragon
tricks
field,
three
save
we
just
need
to
figure
out
like
where
the
drag
is
or
where
the
cliq
happens.
That
lets
you
skip
all
the
next
set
of
steps.
A
B
C
B
Okay,
although
I'm,
not
yeah
I'm,
not
totally
sure,
like
you
know,
web
forum
com
is
like
widget,
driven
where
it's
like.
You
choose
the
radio
buttons
over
checkboxes
and
that's
only
possible
because
to
web
form
doesn't
really
have
any
data
types
that
just
saves
it
all
this
text,
so
so
I
did
I
am
yeah
I'm,
not
sure
that
we
could
do
that,
like
I.
B
Think
that
you're
on
the
right
path
here
that
that
you
choose
the
data
type
first
and
as
long
as
we
can
get
through
the
process
of
choosing
a
data
type
choosing
a
widget
and
seeing
a
preview
like
as
quickly
as
possible,
then
then
I
think
that
this
is
going
to
be
fine.
We.
A
Also,
things
like
there
is
some
some
like
it
is
a
little
backwards
to
make
people
start
with
data
type.
So
if
we
can
find
a
way
to
do
that,
that
makes
sense
is
it
would
be
good.
The
widget
is
weird
right
now
in
Drupal
and
backdrop,
because
sometimes
you
can't
change
the
widget
after
the
fact,
but
I
don't
really
know.
Why,
like
it
seems
it
shouldn't
matter,
you.
B
C
There
are
some
cases
where
you
choose:
you
choose
something
that
Drupal
considers
a
data
type,
but
as
a
user
might
not
feel
like
a
data
type,
and
then
the
widget
becomes
locked
in
stone
like
I.
Think,
like
maybe
a
boolean,
is
a
single
checkbox
and
like
why
can't
I
have
other
checkboxes
if
this
ended
up
not
being
boolean
like
oh
yeah,.
B
A
And
I
think
that
if,
if
there's,
if
we
can
try
and
figure
out
like
what
that
problem
is
and
I
mean-
maybe
that's
a
much
bigger
issue
of
just
like
including
some
kind
of
migration
path
and
letting
people
change
their
data,
but
understand
that
if
you
change
it,
you
have
to
like
run
the
script.
That'll
fix
everything
for
you,
which
might
not
be
for
a
problem
that
could
be
a
contributing
people
start
with
it
with
a
widget
is
fine,
because
then,
if
they
make
the
wrong
choice
and
they
get
done,
they
can
change.
Widget.
C
A
C
Sure
it's
in
that
same
thread
that
I
posted
those
mock-ups
and
I
will
share
my
screen
here
and
try
to
talk
through
what
I
think
he
use
doing,
but
he
typed
up
a
pretty
good
document,
so
it
was
basically
he's
borrowing,
similar
syntax
and
and
metaphors
from
the
page
layout.
You
I
as
like
the
the
kind
of
node
entity
you
I,
so
this
would
work
I!
C
Think
it's
more
we're
talking
about
managed,
display,
yeah,
so
yeah
you
would
have
a
blocks
which
could
hold
fields,
and
so
it's
kind
of
like
a
field
group
and
modern
or
in
current
parlance
and
then
from
what
I
understand
you
might
have.
You
know
a
bunch
of
different
blocks
with
fields
in
them
so
like
you
could
have
yeah
or.
C
A
C
You
want
like
the
list
of
articles
at
the
bottom
and
then
the
comments
or
something
I,
don't
know
I'm,
just
like
kind
of
spitballing
I'd
like
a
weird
idea,
but
but
being
able
to
kind
of
put
things
that
aren't
just
from
the
node
in
the
nodes
display
seems
to
be
useful,
sometimes
but
I
know.
That's
weird
well,.
A
That's
only
weird
because
we
come
from
Drupal
right,
but
yeah
I
have
I
have
a
use
case
right
now
at
this
site,
where
we
like
in
bed
all
sorts
of
kinds
of
stuff
inside
the
body,
but
that
that's
naughty.
It
has
also
justice
with
like
performance
and
rendering
and
whatever
filtering
and
everything
else,
but
it
is
like
the
use
case.
There
is
valid
where
it's
like.
A
Sometimes
you
know
you
want
to
put
an
ad
in
the
middle
of
your
content
or
you've
got
a
promotion
for
another
part
of
your
website,
or
you
want
to
show
a
list
of
related
articles
and
if
you
could
do
that
using
a
mini
layout
right
where
it's
like
what
my
full
node
looks
like
it
has
content
on
the
left
and
on
the
right-
or
this
is
what
my
teacher
looks
like
and
it
has.
You
know
image
on
the
Left
text
on
the
right
or,
however,
you
want
to
do
it.
A
There
is
a
use
case
for
that
and
I
think
that,
now
that
we
have
layouts
that
control
the
page
level,
we
could
definitely
reuse
that
user
interface
for
node
view
modes
or
any
entity
view
mode
I
suppose
to
do
that,
it
gets
hard
I
think
in
the
way
that
we
are
doing
pages
and
layouts
and
make
correct
me
that
I'm
wrong.
We
render
like
each
block
individually
and
then
still
concatenate
strings,
but
the
way
that
we
render
nodes.
We
actually
have,
like
a
renderable
item
like
an
array
that
we.
B
A
B
A
The
the
two
kind
of
models
that
are
a
little
bit
different
and
I'm
not
sure
that
we
want
to
concatenate
strings
in
nodes.
I
mean
there
was
a
huge.
You
know:
movement
to
move
away
from
concatenated
strings
in
in
Drupal
to
try
and
make
everything
renderable,
and
we
were
kind
of
trying
to
say
well.
B
Yeah
I
think
are
kind
of
getting
off
from
Marcus.
First,
you
have
the
rise
concern
I'm.
This
is
a
kind
of
interesting
idea,
the
West
that
that
you'd
be
able
to
put
other
stuff
in
in
content
that,
as
if
it
were
a
field,
basically
so
be
able
to
place
blocks
or
something
like
that
within
a
node,
or
you
know.
C
B
B
A
mini
layout
yeah,
exactly
if
so
many
layout
template
actually
would
be
different
than
a
page
layout
template
because
right
now,
that's
all
that
we
have
in
and
that
would
be
kind
of
interesting.
But
then,
then
you
get
into
a
whole
nother
mess
of
complexity
like
from
a
user
like
mentality.
You
know
like
that
this
panel
is
inside
over
this
layout
is
inside
of
this
other
layout
could
do
a
real
brain
bender
and
then
what
happens?
B
A
A
question
so
we
were
come
to
this
place
where-
and
this
happens
all
the
time
interval
where
there's
like
five
models
that
match
what
it
is
that
we're
trying
to
do
like
we
have,
you
can
put
blocks
in
a
node,
you
can
put
new
views
in
a
note
or
you
can
use
mini
layouts
inside
a
layout.
I
was
thinking
about
this
yesterday
and
trying
to
figure
out
if
there
was
a
way
that
we
could
simplify
our
concepts
admit
this
is
might
not
be
something
we
can
do
and
back
to
everyone.
A
Maybe
it's
something
we
need
to
do
a
backdrop
to,
but
something
like
making
their
one
way
to
create
a
page,
and
that's
only
a
layouts
like
getting
rid
of
the
views,
page
display
and
then
trying
to
say.
There's
only
one
way
you
can
create
a
block
and
that's
either
like
a
contour
I,
don't
know
like
whatever
it
is
like
either
a
you
type
content
into
it
and
that's
kind
of
like
a
content
block
or
you
build
it
with
views
and
I.
A
B
A
It
is
but
node
content
consists
of
four
fields
in
a
view
mm-hmm
or
something
that
might
be
enough
of
a
like.
If
you
want
to
put
a
thing
and
the
other
thing
you
use
view
is
always
the
answer
might
be
the
way
to
do
it,
and
then
now
you
have
a
block
that
represents
node
content.
You
have
a
block
that
represents
fields
or
you
have
blocks
or
represent
views,
but
that's
kind
of
it.
A
I
mean
I,
mean
sure
we
need
a
block
that
represents
fields,
it
could
be
a
default
view
something,
but
you
know
it's
just
like
trying
to
remove
the
possible
ways
to
do
number
of
possible
ways
to
do
things
and
in
enforcing
it
like
either
by
setting
defaults
for
something
like
this
is
the
way
we
do.
This
in
backdrop,
would
kind
of
help
create
I
mean.
Maybe
we
can
even
do
this
to
documentation.
A
I
don't
know
but
help
Korea
could
have
like
a
guided
path
like
this
is
the
path
most
followed
the
and
then
people
want
to
do
crazy
things
they
can,
but
at
least
it's
like
your
instructions
are
consistent,
always
ease
of
you
always
use
a
block
put
it
in
the
page
level,
and
you
know
maybe
field
you
I.
The
display
tab
goes
away
entirely,
and
it
just
says
do
that
in
layout,
yeah.
C
C
Too
much
and
it's
like,
if
you
tuck,
then
you
know,
I
come
to
Lola
bot,
right
and
and
I
talked
to
like
a
couple
femurs,
and
then
they
make
me
realize
how
simple
things
can
be
done.
It's
just
like
I
wish.
I
knew
this
for
years
ago,
like
I
thought
I
was,
you
know,
really
proficient
Drupal
now
I'm
like
wow
I
I
can
do
this
a
lot
better
than
I.
You.
C
B
Well
guys
we're
running
out
of
time
we're
going
out
like
10
minutes
left.
Maybe
we
should
wrap
up
field
UI
and
ok.
The
remaining
rent.
A
Meanie
this
is
a
hard
problem.
I
love
Wes
the
work
that
you've
done
and
on
already
and
like
all
the
thought
that's
going
into
it
I
definitely
think
you're
going
the
right
direction,
but
yeah,
let's,
let's
skip
stuff.
Ok,
so,
let's
see
there's
other
stuff,
we
need
to
work
on
for
backdrop.
The
product
most
of
it
I'm
super
excited
about
the
next
release.
A
Being
a
user
experience,
release
so
I
put
a
link
in
the
agenda
for
all
issues
that
are
scheduled
for
one
point
three
point:
oh
and
those
will
probably
continue
to
get
paired
down
as
we
get
closer
to
that
mark,
but
I
think
just
getting
a
whole
bunch
of
stuff
in
that
improves.
That
will
be
huge
and
so
I'll
just
leave
the
backdrop,
the
product
section
at
that
anyone
who's
curious
about
what
we're
working
on
go
check
that
tag
and
backdrop.
The
website
is
kind
of
in
stasis.
A
Right
now,
I
spend
a
bunch
of
time
trying
to
actually
use
it
last
week
and
realized
that
we
do
really
need
to
get
those
development
tasks
done
for
getting
like
links
to
get
hub
exposed
to
where
we
can
actually
print
them
on
the
page
and
so
I'll.
Try
and
prioritize
that,
but
otherwise,
I
think
we're
kind
of
on
hold
in
terms
of
design
there.
A
Is
that
my
computer?
That's
right:
okay,
sorry,
everyone
I
hate,
google,
plus.
Why
does
it
ring
your
phone
when
you're
on
your
phone
anyway?
Okay?
So
we
have
a
tentative
tea
sugar
twin
own
designs
yet,
but
we
have
an
idea
where
we're
going
to
try
and
do
this-
have
their
white
colored
shirt,
which
is
like
a
little
dappled
color,
which
is
really
pretty
I.
Wear
another
shirt
today,
I
thought
was
the
same
color,
but
it
was
way
too
big.
A
So
I
changed
it,
but
our
plan
is
to
put
a
smallish
dragon
kind
of
right
in
the
middle
so
that
his
head
will
be
popping
out
of
your
hoodie.
If
you're
wearing
a
hoodie
and
its
opener
half
six,
we
turn
that
over
to
Darius.
A
We
should
be
getting
designs
soon
and
then
the
most
exciting
thing
is
the
hoodie
which
we
just
kind
of
I
came
up
with
the
idea
when
I
saw
this
dragon
and
our
first
round
of
revisions
I'm
like
oh,
my
god
that
jagan
needs
to
be
giants
and
on
the
back
of
a
hoodie.
So
we're
going
to
try
and
get
those
done
too
and
we're
gonna
put
him
on
the
back
and
then
on
the
front,
we're
going
to
try
and
either
have
it's
a
backdrop
which
would
be
our
word
mark
or
backdrop
CMS.
A
So
I'm
really
excited
about
both
of
those
I
think
we
should
try
and
figure
out
like
a
price
to
to
try
and
take
donations
in
exchange
for
turning
them
out.
I
was
thinking
it
might
be
good
of
us
to
do
a
similar
price
too
bad
camp
since
we're
going
to
be
selling
them
at
fat
camp,
but
we
don't
want
to
be
trying
to
like
undercut
them
on
cost.
A
But
since
we
don't
have
a
middle
level,
I
figured,
we
could
probably
use
that
fifty
dollar
price
point
for
our
hoodies,
so
I
I'm,
hoping
that
will
work
for
people
for
the
t-shirts
we
wanted
to
give
those
away
for
free
too.
So
that's
anyone
who
has
participated
in
any
backtalk
issue
or
donated
design
services
or
been
involved
with
backdrop
in
any
way
so
far.
I
think
that
can
also
include
at
the
backdrop
summit.
A
If
we
can
get
new
contributors
there,
they
should
earn
their
t-shirts
and
that's
totally
fine
and
the
hoodies
are
cost
us
significantly
more,
which
is
why
I
was
wondering
how
we
should
handle
contributors
with
hoodies,
but
I
thought.
Maybe
we
could
offer
some
kind
of
discount.
So
if
you're
a
contributor,
you
get
a
free
t-shirt
and
a
cheaper
hoodie,
or
do
you
think
we
should
make
everybody
by
the
ladies
and.
A
A
A
B
Most
and
most
of
the
time
most
of
our
contributors
are
kind
of
like
oh
good
I.
You
know
they're
look
kind
of
looking
for
an
excuse
to
give
us
money,
rather
than
you
know,
rather
than
feeling
like
they
deserve
a
free
hoodie.
You
know:
ok,.
A
I
think
that's
totally
fair
and
that
way
will
not
lose
money.
Even
after
giving
away
all
of
our
free
desserts,
oh
yeah,.
A
Ok,
and
so
that
was
I,
think
the
only
thing
that
was
super
time-sensitive
is
that
we
need
to
get
these
designs
done
by
october
first,
which
is
next
week
and
then
we'll
start
the
printing.
So
I
think
if
you
definitely
are,
if
you
watch
this
video
and
you
really
want
a
t-shirt
or
hoodie,
you
can
pre-order
them
through
our
website
I'll
make
sure
we
have
a
hoodie
option
if
there
as
well
and
then
we'll
adjust
our
order
accordingly.
A
If
we
get
for
yours
so
exciting,
alright,
nothing
else,
new
I,
don't
think,
since
our
last
design
call
no.