►
From YouTube: Backdrop CMS Design meeting 11/19
Description
Design check-in for Backdrop CMS
A
A
One
point
three
point:
oh
is
easier
experience
focused
release
and
we
have
a
bunch
of
a
little
teeny-tiny
issues
if
you
check
in
to
get
a
issue
key
one
with
a
milestone,
1.3
and
we'll
be
working
through
those
getting
for
quests
and
trying
to
get
as
many
of
those
in
as
we
can
on
or
before
three
point.
Oh,
we
have
three
major
areas
that
we're
trying
to
get
serious
design
and
user
interface
improvements
tone.
One
of
those
is
layouts.
A
B
A
You
know
either
we
knew
we
didn't
get
done
the
first
time
around
or
that
people
have
brought
up
recently
that
are
getting
worked
on
views.
Ui
is
something
that
is
always
been
really
painful,
just
because
they're
really
a
powerful
tool
and
trying
to
build
an
interface.
That
is
understandable
for
something
that
can
do
so.
Many
things
is
really
hard.
We
know
that
it's
a
pretty
good
interface
now,
because
everybody
who's
been
working
with
it
for
drupal
7.
The
last
five
years
has
kind
of
learned
the
way
around
it.
It
definitely
has
room
for
improvement.
A
There
are
specific
things
that
we're
having
trouble
with
the
use
UI
and
backdrop
like,
making
it
responsive
and
making
the
font
consistent
and
stuff
like
that.
There's
a
handful
of
follow-ups,
but
there's
also
been
kind
of
a
larger
movement
to
kind
of
rethink
the
views
problem
space
and
see
if
we
can
come
up
with
a
better
solution
for
that
as
well
and
a
little
hesitant
to
try
and
push
that
by
1.3
number
one.
A
Well,
so
that's
there's
an
issue
for
that
as
well.
It's
issue
number
13
14
on
github.
If
you
want
to
start
thinking
about
that
and
then
something
I
would
like
to
see
get
into
1.3,
but
may
not
happen
because
it's
going
to
be
really
hard
as
a
new
redesigned
field
view,
I
and
I
know
that
Wes
you
in
particular
have
been
doing
a
ton
of
great
work
on
that
we're
gonna
need
to
figure
out
which
way
to
do
it
and
start
thinking
about
technical
implementation
pretty
soon.
A
If
we
want
to
get
it
that
into
1.3,
but
I
definitely
think
we
sell
time
to
do
it.
So
if
anyone
wanted
to
start
working
on
that,
that's
totally
filled.
You
is
also
a
separate
module
course,
so
we
could
just
kind
of
swap
out
the
one.
That's
there
with
the
new
11,
we're
ready
on
1.3
time
frame,
so
I
think
that's
kind
of
what
we're
working
on
in
backed
up
the
product
in
terms
of
design
user
experience
stuff.
A
Also,
if
anyone
is
working
on
a
new
front,
end
design,
that
would
be
a
good
base
theme
for
anyone
to
be
able
to
launch
a
site
on
or
build
a
new
theme
off
of.
We
can
put
that
at
any
time.
So,
if
you
have
one
on
a
site
you're
using
now,
you
really
like
you
want
to
make
a
recommendation.
We
can
create
an
issue
to
put
that
in
core.
We
can
evaluate
it.
We
can
rewrite
it
if
necessary
and
make
it
core
ready
that
can
go
in
anytime
in
the
one
point
actually
cycle.
A
So
just
keep
that
in
mind
as
you're
building
backdrop
sites
and
making
things
that
we
are
kind
of
looking
for
something
bootstrap
II
in
the
sense
that
it
looks
good
by
itself,
but
it's
also
easy
to
decorate
to
make
it
more
elaborate,
all
right
so
backdrop,
CMS
org
primary
website.
We
know
we
have
a
bunch
of
follow-up
issues
to
do
for
module
students
and
layouts
I,
always
looking
through
the
issue
queue
today
on
those
and
we've
actually
got
a
bunch
of
good
feedback
from
people
who
have
been
using
the.
A
Website
about
things
that
they
want
a
lot
of
those
things
are
things
that
were
in
our
original
design.
Comps,
we
just
didn't,
have
them
technically
implemented,
so
I
think
maybe
it's
a
good
time
to
focus
on
those
and
if
anyone
wants
to
work
on
the
primary
backdrop,
CMS
or
website,
the
whole
thing
is
in
a
public
repository.
If
you
go
to
github.com
/
backdrop
dash
ops,
you
can
find
it
there.
So
if
you
want
to
make
a
suggestion,
that's
fantastic
there's
an
issue
queue.
Do
you
want
to
deploy
request?
A
A
For
those
kinds
of
things
so
we'll
definitely
keep
improving
module
seeing
some
layouts,
but
our
focus
right
now
is
to
get
the
profile
page
elements
down,
because
we
want
to
do
now
that
your
plate
is
out.
It
came
out
today,
congratulations
triple
8
and
all
the
people
who
did
amazing
work
on
that.
Now
that
that's
out
people
are
going
to
actually
start
trying
to
compare
backdrop
and
Drupal
8,
and
it.
A
If
we
could
give
people
something
to
join
like
when
they
come
to
dribble
or
if
they
can
create
a
triple
account,
I
think
information,
other
Drupal
people.
We
should
have
the
same
kind
of
thing
for
backdrop,
even
though
there
isn't
a
lot
for
people
to
do
on
the
backdrop
website,
yet
we're
hoping
there
will
be
in
the
future.
So
we
should
go
through
and
figure
out
what
kinds
of
things
are
going
to
be
most
important
to
collect.
A
On
backdrop,
users,
backdrop,
people
so
I'm
going
to
start
with
drupal
org,
because
that's
what
I
know
and
I
think
they
actually
have
done
a
really
good
job
over
the
years
of
trying
to
figure
out
what
is
most
important
data
to
collect
on
people.
And
then
we
can
also
take
a
look
at
things
that
aren't
Drupal
related
like
if
wordpress
or
rails
or
any
other
I
website.
/
community
is
doing
something
that
Drupal
hasn't
thought
of.
A
We
should
look
at
that
and
see
you
know,
or
maybe
Drupal
has
thought
of
it
and
decided
they
didn't
need
it.
We
should
think
about
whether
that
is
valuable
for
us
as
well.
I'll
be
really
interested
to
see
like
what
the
jQuery
community
does
or
symphony
like
people
are
based
on
github.
What
do
they
feel
like?
They
need
to
collect?
A
That's
not
part
of
the
github
user
account
process
and
see
if
we
can
build
kind
of
the
same
thing
in
parallel
for
people
who
are
on
get
having
people
who
aren't
on
github
and
that
way
we
can
make
everybody
designer
developer
or
you
know
just
enthusiast
feel,
welcome
all
right
so
I'm,
starting
on
the
drupal,
org
user,
page
and
I
think
we
should
definitely
collect
some
of
the
same
things.
So
under
personal
information.
A
A
A
Document
I.
A
A
Okay,
that's
just
wondering
if
maybe
I
could
get
you
to
take
notes.
Then
it's
not
cuz,
I'm
just
going
to
be
going
like
back
and
forth
between
two
screens
and
that
might
be
a
little
make
people
noxious.
A
A
All
right
so
I'm
just
going
to
go
ahead
and
take
a
look
at
what's
on
here
already.
Maybe
I
should
start
from
the
Edit
side
to
do.
Okay,
so
personal
information,
so
where
it
goes
before,
I
think
we
definitely
should
collect
first
name
last
name
and
country
I.
A
Mean
how
do
you
not
save
a
little
kitchen
I,
don't
know
I'm
going
to
tell
you
what
location
is
I
want
you
to
forget
when
I
hit,
save
I,
don't
know
what
that
means.
Language
might
be
useful
to
like,
especially
if
we're
starting
to.
A
How
many
people
want
transliteration
or
I
don't
know
like
some
translations
about
example,
cuz
we're
putting
that
in
import,
but
I
18
n,
or
something
like
that.
I
might
give
us
good
a
good
idea
of
like
how
many
people
are
not
in
non-english
speaking
languages
or
locations.
I'm,
not
sure
we
need
gender,
but
I.
Think
it's
good
to
collect.
Just
to
you
know,
trying
to
figure
out
like
I.
Think
Drupal
has
a
lot
more
female
members
than
other
open
source
communities
and
I.
Think
they're
really
proud
of
that.
A
Think
that
having
that
information
would
be
useful,
so
maybe
we
should
collect
that
as
well.
A
biography,
I
think,
is
good.
People
can
say
whatever
they
want
about
themselves.
I'm
IRC
is
probably
fine.
I
think
over
time
we
might
not
stick
with
IRC
as
our
chat
client,
we
might
switch
to
something
like
get
her,
in
which
case
your
github
user
name
is
going
to
be
far
more
important
than
your
IRC
name.
A
So
maybe
in
the
short
term,
we
should
collect
IRC
plus
when,
as
soon
as
we
add
a
single
sign-on
with
github
will
be
collecting
github
user
names
as
well.
Any
websites
people
want
to
show
off,
I
think,
is
also
good
same
with
social
links.
I
think
that's
a
letting
people
choose
their
social
media
profiles
to
share
time
zone
is
built
into
backdrop.
A
Language
settings,
that's
interesting,
so
I
guess
we
collect
like
what
languages
you
speak,
which
is
different
from
what
language
you
would
like
to
see.
This
website
in
I
think
that's.
This
is
also
built
into
backdrop,
but
we
could
see
contact
form.
We
don't
have
contact
module
on
in.
A
Backdrop
I'm
just
trying
to
remember
with
the
status
of
contact
module
in
backdrop,
I
think
I
think
we
took
out
only
the
email,
email
field
contact
or
no
check
that
I've
email
much
okay,
so
should
be
the
same.
So
we
can
have
that
on
and
then
we
do
have
a
backdrop
newsletter
mailing
list.
We
could
add
in
there
as
well.
So
I
think
that
would
all
be
good.
We
I
think
aren't
using
google
analytics,
but
if
we
do
we
can
as
well.
A
So
this
is
just
kind
of
like
drupal
stuff,
so
it'll
be
back
drive
stuff
in
betcha,
alright,
so
under
the
drupal
tab
on
drupal.org
there's
a
list
of
things
that
people
contribute
I,
think
that
would
be
good
as
well.
This
gives
people
who
aren't
necessarily
developers
the
chance
to
highlight
the
contributions
they
do
make
that
aren't
necessarily
code
related,
so
I
think
that's
super
useful
to
let
people
say
these
are
the
things
I
do
you
know
even.
A
Not
be
so
visible,
I
also
really
like
the
idea
of
having
mentors
it
lets.
You
know
it
shows
a
little
bit
more
of
the
community
aspect.
So
just
saying
like
these
are
other
people
that
I,
you
know
have
worked
with
or
have
been
inspired
by
or
similar,
so
I
think
we
could
add
that
that
would
be
fantastic
areas
of
expertise.
I
mean
I.
A
To
use
that
I
mean
we
could
say
like
backdrops
I'm
going
to
back
in,
but
I
feel
like
maybe
too
early
okay
work,
I,
definitely
think
it's
great
for
people
to
be
able
to
highlight
where
they
have
and
where
they
could
work,
especially
if
we
end
up
using
these
organizations
as
I.
A
You
know
in
the
services
listing
or
I,
don't
know
people
like
if
you
wanted
to
give
credit
in
the
showcase
part
of
the
website.
It
is
a
little
bit
complicated
on
the
architecture
side
because
we
need
to
then
like
create
an
organization
and
then
try
and
give
people
an
easy
way
to
add
new
organizations,
in
addition
to
referencing
existing
ones,
which
is
kind
of
a
usability
study
and
getting
that
right.
But
we
definitely
could
figure
out
a
way
to
do
it
and
then
I
also
think
Industries
is
interesting
too.
A
It
would
I,
think
it'll
be
great
if
we
could
do
yeah.
This
is
left
over
from
previous
I
think,
but
rather
than
a
text
field,
which
is
how
Drupal
that
were
key
to
do
it,
making
sure
we
have
like
make
it
more
like
tags
or
something
similar.
So
we
could
count
like
how
many
people
are
in
education,
okay.
So
so
far
we
haven't
found
anything
Drupal
does
that
we
don't
want
get
access
newsletters,
we
hope
should
only
have
one
email
addresses
everybody
can
see.
A
A
B
B
B
A
Okay,
I
think
that's
a
pretty
good
list.
I'll,
try
and
I
mean
we
looked
at
the
Edit
for
I'm,
not
necessarily
to
view
forum,
but
I
think
that
we
don't
necessarily
need
to
display
all
the
information
we
collect
things
like
mentors.
We
don't.
Oh,
that's
a
question:
do
we
want
to
use
your
profile
picture
right?
There's,
definitely
like
a
bunch
of
good
ways
to
display
things
that
we
can
say.
A
Oh
you
know,
I
want
to
show
a
list
of
my
mentors,
but
if
we
don't
have
a
profile
picture,
then
we
can't
there
it's
not
going
to
be
visually
as
exciting.
To
put
them
on
the
page,
so
I
would
say
we
should
collect
profile
pictures.
We
can
decide
in
the
future
where
to
display
them
like
if
we
do
end
up
creating
a
backdrop
based
forum
and
having
people's
photos.
There
is
nice,
but
yeah
I,
don't
know.
A
B
B
Or
it
could
be
like
the
project
if
the
project
has
fields
on
backdrop,
CMS
org,
one
of
them
could
be
contributors.
It
selects
users
would
be
easier
mapping
yeah,
but
put
the
responsibility
on
the
maintainer
to
log
in
and
do
it,
though,
looking
at
WordPress
I
have
activity
you're
just
kind
of
interesting,
but
they
also
had
favorites,
which
I
liked
so
like
some
maintainer
liked,
favorited
some
plugins,
okay
kind
of
interesting
I,
don't
know
if
it'd
be
very
useful
for
us,
but
I
mean.
A
I
think
it
could
be
because
that
way,
you
know
you
could
you
could
see
like
which
are
the
most
favorited
projects
like.
What's
the
ever
reason,
most
favorite
theme
like
there
could
be
some
useful
information
there
or
even
though
you're
not
a
contributor.
You
want
to
record
that
yeah.
B
Yeah
badges
would
be
fun,
but
that's
like
a
whole
gamification
thing,
yeah
linkedin
at
me,
I
thought
maybe,
but
now.
A
A
Checking
out
what's
on
sets
do
labs
symphony
as
well
user
profile,
and
it
has
single
sign-on
with
github
twitter,
linkedin
and
facebook
Wow,
which
is
pretty
interesting.
I.
A
For
something
that
Symphony
based
I
but
there's
but
yeah,
then
then
additional
fields
they
have
his
birth
date,
which
is
something
I
don't
think
durable
that
work
collects.
But
that
could
be
interesting.
A
A
Yeah
and
then
it's
just
a
short
bio
field
looks
like
all
the
other
stuff.
They've
got
city,
country,
company,
job
position
name
and
in
symphony
just
has
a
single
field
for
name
which
I
think
it
makes
more
sense
for
a
european
and
community,
or
you
know
there
are
some
places
where
first-name
and
lastname
don't
necessarily
mean
the
same
thing.
A
single
field
also
allows
for
a
middle
name
like.
A
Name
and
first
last
doesn't
do
that,
but
it
it
doesn't,
make
it
hard
to
sort
people.
So
if
you
ever
want
to
have
a
list
of
people
and
sort
them
by
last
name,
you
can't
do
that
with
a
single
field.
B
A
We
should
I
kind
of
would
lean
towards
a
single
name
field
and
say:
let's
just
not
list
everybody
in
the
same
place
like
I'm,
not
sure
what
did
we
have
a
use
case
for
doing
that
now,
I'm,
not
sure
the
cheesecakes
really
not
on
drupal.org,
but
that's
just
you
know
how
they
collected
data
just
make
it
easier
if
you're
like
managing
mailing
lists
and
stuff
to
be
able
to
have
dear
mr.
Lambert,
but.
A
Ok,
just
taking
a
look
at
the
other
case,
the
other
things
we're
planning
on
doing
on
the
website,
a
showcase,
I
think
in
a
showcase.
We
might
want
to
list
the
person
who
posted
it
and
if
we
could
link
to
their
profile
and
have
all
this
fancy
information
that'd
be
fantastic.
Oh,
we
also
want
to
do
a
service
provider
listing
that's
another
use
case
for
having
that
organization,
entity
or
node
type
or
whatever.
It
is
we're
going
to
do
there
that
we
can
reference
and
yeah.
A
So
I
think
all
these
things
are
going
to
tie
together
same
things.
We
want
to
do
like
job
postings.
The
job
postings
would
probably
belong
to
an
organization
and
I
think
that
organization
and
something
that
your
post
on
really
well
as
giving
organizations
credit
for
contributing
two
things
in
one
way
or
another,
so
either
letting
them
contribute
like
directly
on
a
module
page,
which
we
kind
of
can
do
in
the
credit
section
on
readme
files
on
github,
but
also
then
as
a
developer.
A
When
you're
in
working
in
an
issue
queue,
you
can
see
I'm
working
on
this
project
for
this
company
or
I'm
working,
you
know
you
can
specify
which
company
and
it
is
that's
contributing
by
allowing
you
to
to
work
on
drupal
stuff,
I'm,
not
sure
we're
going
to
be
able
to
have
a
similar
way
to
do
that
in
a
github
world.
The
kids.
A
Buy
that
on
github
and
but
having
some
way,
you
know
on
backdrop
CMS
to
org,
for
companies
to
say,
like
I,
contribute
the
following
projects
or
something
or
the
other
way
around
I.
Don't
know
it
might
be,
it
might
be
nice
yep
long
term,
we'll
figure
that
out
architectural
a
difficult
okay.
So
I
think
that's
it
for
backdrop.
The
flagship
website
will
get
that
information
over
to
darius
and
see
if
he
can
work
out
some
kind
of
designs.
Our
timeline
for
that
is
december.
Seventh,
which
is,
I
think,
in
two
weeks.
A
Are
we
gonna
week
and
a
half,
so
hopefully
that'll
still
be
able
to
happen,
and
then
I
would
love
it
if
we
could
get
that
profile,
page
ack
actually
implemented
by
january
first.
I
think
that
would
be
a
great
like
one
year
anniversary
of
backdrop
thing
to
take
care
of
where
it's
like:
hey
we've
been
around
for
a
year,
guess
what
welcome
community?
We
have
all
this
stuff.
You
can
do
on
our
website.
A
A
Experience
about
the
look
and
feel
it's
about
having
a
community
to
join
I
think
it's
spending
the
first
year
on
the
software
was
important
like
we
needed
to
have
a
product
go
bleep
remote,
but
now
it's
the
time
to
be
like
okay,
we're
also
about
community
so
and
that'd
be
great,
alright!
Well,
that's
all
I
had
for
this
meeting.
I
did
want
to
reiterate
that
if
you
love
dragons
and
you
want
a
t-shirt
or
hoodie
with
a
dragon
on
it,
you
can
go
to
backdrop
CMS
or
contribs
backdrop.
A
Cms
network
/
contribute
and
if
you
make
a
donation
of
$95,
we
send
you
a
t-shirt
with
the
dragon
on
it.
If
you
make
a
donation
to
fifty
dollars
to
get
a
hoodie
with
a
dragon
on
it,
they're
very
soft
and
comfortable,
and
we
have
a
lot
of
them
which
we're
hoping
will
last
us
all
year.
But
if
you
want
to
get
your
orders
and
now
mail,
you
one
before
the
next
backdrop,
event
and
you'll
definitely
go
in
for
now.
A
So
that's
good
to
know
and
other
things
they
too,
if
you
are
going
to
an
event,
you
want
to
give
a
talk
on
backdrop.
We
have
slides
in
reveal
jas
on
github
under
the
backdrop,
ops
group,
and
if
anyone
wants
to
spend
some
time
working
on
online
branding
assets,
I
did
create
an
issue.
It's
on
the
backdrop
CMS
torque
you,
but
it's
issue
number
121.
A
If
you
want
help
us
create
like
a
background
image
for
Twitter
Facebook
Google+,
any
of
that
there's
a
little
conversation
London
over
there
about
what
kind
of
imagery
we
should
choose
to
be
consistent
across
all
platforms
and
and
if
you're
really
interested
in
create
helping
us
create
a
consistent
user
experience
across
all
backdrop
core
and
can
trip.
We
are
working
on
human
interface
guidelines.
A
We
haven't
had
anyone,
contribute
any
documentation
there
for
a
while,
but
it
is
something
we
want
to
do
we're
running
into
issues
already
about
when
and
when
not
to
use
things
like
drop
buttons
and
vertical
tabs
and
getting
those
documents
that
we
can
refer
to.
That
I
think
would
be
really
useful
going
forward.
B
Did
you
see
there
was
something
I
was
interested
in
kind
of
doing
I.
Think
there
is
a
I
think
Nate
responded.
It
was
basically
like
what,
if
we
did
something
pattern,
lab
ask
that
accomplished
code
documentation
and
like
ux
guidelines
in
one.
Yes,.