►
From YouTube: Backdrop weekly 11/20
Description
A check-in on design related tasks for Backdrop CMS: the comprehensive content management system for small to medium sized businesses and organizations.
A
Backdrop
day,
so
we're
excited
working
on
backed
up
today.
Backdrop,
for
those
of
you
don't
know,
is
a
content
management
system
that
specifically
attended
intended
for
small
to
medium
sized
business,
nonprofits
education,
basically
not
the
enterprise.
So
anyone
who
has
a
significant
budget
or
concern
about
ongoing
costs
of
maintenance,
though
their
website
this
should
be
a
more
affordable
alternative
than
Drupal
7
I.
Think
we're.
B
A
A
Should
be
simplified
and
new
features
should
still
be
added
within
those
restrictions
and
those
last
two
things
is
simplifying
existence
and
adding
new
features
can
only
be
done
without
modifying
API
is
too
much
so
we
want.
This
is
going
to
be
as
similar
to
Drupal
7
as
possible,
but
of
course,
we'd
like
to
still
be
able
to
add
new
feature.
So
adding
new
API
is
fine
and
simplifying
things
with
the
least
amount
of
changing
API
as
possible.
A
Our
timeline
we're
hoping
have
backdrop
CMS
released
this
fall,
which
technically
gives
us
until
December,
so
we're
shooting
for
a
release
date
of
December
2014,
which
is
very
soon
it's
a
month
away
about.
So
we
have
a
couple
of
things
we
need
to
get
done
before
then,
but
we're
looking
pretty
good
in
terms
of
meeting
that
release
date
and
we've
got
a
couple
of
what
will
go
through
those
in
a
minute.
A
But
after
we
release
one
point,
0
point
0,
which
will
be
this
fall,
or
this
December
or
in
one
month
will
continue
to
issue
releases
on
a
regular
basis.
So
we'll
probably
have
one
release
every
quarter
and
in
those
future
releases
will
be
able
to
schedule.
You
know
we're
going
to
have
extra
lead
on
X
date.
It's
going
to
contain
y
features
and
then
that
we
will
be
able
to
continue
to
improve
the
software,
even
though
it's
out
it
won't
be
done,
and
that
will
hopefully
give
us
a
chance
to
continually
iterate
and
improve.
B
A
Time,
we're,
of
course,
not
going
to
be
breaking
major
act.
Ap
is
in
those
small
changes
will
be
able
to
do
that
with
major
releases
will
be
able
to
add
things.
So
if
we
don't
have
a
Drupal,
8
comparable
system
at
release,
that's
fine.
We
can
add
modules.
We
can
add
functionality
as
time
goes
on
what
we
do
need
to
get
done
before
we
release
our
a
couple
of
major
projects
that
we've
been
working
on
for
the
last
few
months
here
in
backdrop,
land
the
first
and
most
significant
is
cmi.
A
This
is
a
solution
that
allows
people
to
build
new
features
and
a
different
environment
and
the
deploy
dose
for
the
longest
time.
We've
had
one
module.
That's
allowed
us
to
do
that
and
that's
featured
module
in
in
triple
seven
and
it's
something
that's
been
frustrating
to
work
with
hard
to
maintain
and
very
time
consuming
and
both
Drupal
7
or
sorry.
Both
Drupal
8
and
backdrop
have
solved
this
problem
by
at
using
configuration
management
tools,
putting
them
in
and
we've
gotten
ours.
In
in
backdrop,
we've
got
a
couple
of
systems.
A
B
It's
been
an
exciting
ride
for
the
past
month,
or
so
for
the
CM
islands.
We
converted
all
the
major
systems
or
almost
all
the
major
systems.
In
the
past
couple
of
months
in
the
last
week,
we
got
them
most
daunting,
one
remaining
converted
languages,
so
language
is
like
the
configuration
of
languages
as
well,
as
you
know,
dating
time
formats
that
go
along
with
them.
Some
of
that
was
already
done,
but
now
it's
it's
all
comprehensively
included.
So
if
you
configure
a
new
language
or
configure
the
negotiation
settings,
it's
all
all
starting
config.
B
Now
it's
all
we've
got
oh,
and
it
was
also
a
really
great
week
in
terms
of
getting
all
of
our
remaining
variables
done,
where
we're
almost
one
hundred
percent
variable
free,
but
not
quite
there's,
one
left
in
the
whole
system
and
it's
the
nail
system
variable,
which
is
kind
of
a
little
bit
of
a
gnarly
one.
It's
very
unusual.
It
looks
like
when,
when
Triple
Eight
did
its
conversion-
and
we
saw
it-
that's
why
it's
just
looking
through
they
just
ported
it
over
pretty
directly,
which
is
probably
what
we'll
end
up
doing
as
well.
Config.
B
B
Menus
were
only
going
to
worry
about
storing
the
actual
like
menu
itself,
not
its
structure,
because,
right
now
at
least
new
links
are
still
in
the
database
and
they'll
probably
stay
that
way
during
release
or
during
initial
release.
Text
form
that
should
be
really
straightforward.
Actions
should
be
pretty
easy,
but
a
little
bit
weird,
just
because
actions
are
just
really
bizarre.
The
way
they're
set
up
now
so
that
will
require
a
little
bit
of
reworking.
B
But
it's
looking
really
good,
like
overall
we've
just
got
these
three
things
left
we're
currently
at
the
pace
of
converting
one
or
two
systems
per
week,
so
we
should
be
in
pretty
good
shape
to
get
this
done.
You
know
a
couple
weeks
before
or
intended
release
date,
but
yeah
it's
it's
close
for
sure.
That's.
A
Great
and
other
things
we've
been
working
on
in
backdrop
that
are
super
in
our
block
some
layout
system.
This
is
the
one
thing
that
we
have,
the
drew
blade
doesn't
have
so
we're
particularly
proud
of
it.
We
have
replaced
the
system
in
Drupal
7,
which
had
this
concept
of
one
layout
for
your
entire
site,
and
if
you
want
to
change
the
Lea,
you
have
to
do
something
really
special
with
how
you
place
blocks
on
some
pages,
but
not
on
others,
and
there
were
some
extreme
limitations
to
way
that
worked.
A
We've
solved
that
problem
by
basically
taking
panels,
putting
it
in
backdrop
and
writing
an
entirely
new
user
interface
for
it,
because
the
thing
most
people
hate
about
panels,
this
its
user
interface,
it's
a
very
powerful
tool.
Some
of
us
really
love
it,
but
it
is
fairly
hard
to
use.
So
we
rewrite
the
user
interface
and
put
that
in
pretty
much
straight
across
just
ported
it
to
the
backdrop
and
we're
super
excited
to
have
that
going.
There's
a
video
that
we've
posted
on
our
YouTube
channel.
A
If
anyone
wants
to
see
a
demo
of
that,
we've
also
done
a
couple
of
demos.
Recent
conferences
in
at
bad
camp
last
week,
two
weeks
ago,
we
were
demoing
blocks
and
layouts
and
the
crowd
erupted
spontaneously
into
applause,
which
is
not
something
that
way
to
experience
before.
So
that
was
very
exciting,
but
yeah
we've
got
the
blocks
and
layout
system
in
in
back
Jack.
We've
got
a
couple
of
follow-up
tasks.
As
of
last
week
hitting
we've
confirmed.
These
are
not
release
blocking
fallout
tasks;
they
all
can
be
done
without
API
change.
A
So
I
think
that
will
worry
on
worry
about
getting
those
done
after
we
get
one
point
out,
which
is
great
and
other
things
we've
got
going
on,
we've
moved
the
views
module
into
core.
This
is
something
Drupal.
8
did
also
uses
the
number
one
downloaded
contributed
module
for
Drupal.
It
allows
you
to
basically
build
lists
of
anything.
It's
a
dynamic
query
builder.
We've
got
it
in
backdrop.
A
We've
got
some
things
that
will
be
nice
to
have
as
views
like
the
node
listing,
for
example,
on
your
front
page,
and
we've
got
some
people
working
on
building
those
views
for
us.
I
think
we're
missing
a
couple
of
upgrade
paths
and-
and
that
is
also
something
I
think
could
probably
go
in
after
release.
Oh
those
aren't
release
blockers,
but
yeah
we're
working
and
getting
those
done,
which
is
great
and
then,
of
course,
will
be
after
we
get
it
out
and
get
people
using.
A
A
It's
also
super
important
for
getting
the
release
out
and
that
is
primarily
making
sure
that
all
of
the
security
issues
that
have
been
fixed
in
triple
seven
have
also
been
fixed
in
backdrop,
and
we
have
I
think
three
left
that
have
been
solved
in
Drupal
7
and
not
yet
in
fact
up
there's
a
new
one
that
came
out
this
week
that
Nate
just
added
for
us
to
the
agenda.
So
we
need
to
worry
about
and
then
we've
got
I,
don't
know
what
the
other
one
is.
A
So
we
need
to
come
up
with
something
a
little
more
elegant
for
backdrop,
but
that
issues
been
open
for
a
while,
if
not
a
bunch
of
feedback
on
it,
I'm,
not
sure,
there's
actually
a
decision
about
which
way
you
should
go
on
that
one,
but
we'll
need
to
reverse
it
that
before
release
2
and
get
something
in
so
that
we're
not
at
least
behind
portugal,
seven
is
and
then
we've
got
a
bunch
of
other
stuff.
That's
been
committed
to
Drupal
7.
Recently,
that's
not
security,
but
like
related,
and
these
are
not
release
lockers.
A
But
it
would
be
nice
if
we
could
at
least
make
sure
that
backdrop
is
not
behind
where
a
Drupal
7
stands.
So
if
we
could
get
someone
to
apply
the
Drupal
7
patches
to
backdrop
where
possible
and
get
as
many
of
those
in
as
possible,
that
would
be
great.
But
again
if
we
are
missing
a
couple
of
really
recent
features
to
triple
seven,
it
wouldn't
be
the
end
of
the
world.
A
A
Some
other
stuff
that
we're
working
on
is
back
porting
the
things
we
care
most
about
from
Drupal
8,
and
we
started
off
by
doing
this
by
looking
at
all
the
commits
that
went
to
Drupal
8
in
trying
to
decide
one
at
a
time
if
we
wanted
them
or
not,
but
there
were
thousands
and
thousands
of
commits
and
that
got
to
be
to
consign
time
consuming.
Depending
concerning
how
much
time
we
have
left
to
work
on
it.
So
we've
died
turned
looked
at
all
those
issues
and
kind
of
picked
out
several
categories.
A
One
look
at
like
we
want
to
make
sure
we
have
all
the
correct
html5
elements.
We
want
to
make
sure
that
we
have
cleaner,
JavaScript
code
and
stuff,
like
that.
So
we've
got
these
subsets
of
things,
so
we've
decided
that
we
care
about.
If
we
don't
get
all
of
the
same
html5
elements
that
Drupal
8
has
I,
think
that
will
be
fine.
We've
got
most
of
them
right
now.
A
There
were
a
few
that
went
into
Drupal
8
that
created
some
significant
problems
and
introduce
some
critical
bugs
that
we
have
not
yet
merged,
because
we
want
those
problems
to
be
solved
and
before
we
introduce
them.
In
the
backdrop,
since
our
release
date
is
much
sooner,
we've
gotta
have
solution
to
those
problems
before
you
really
so
might
as
well.
Not
introduce
the
problems
in
the
first
place,
so
I
think
we're
actually
looking
pretty
good
with
that
list.
A
There's
three
left
and
I'll
check
up
on
those
and
see
how
we're
coming,
but
they
might
just
have
to
wait
until
we
can
have
time
to
either
solve
the
problems
or
self
or
help.
You
know
Drupal
8,
along
with
getting
this
problem
solved,
so
we
can
move
forward
and
in
both
products
we've
got
a
bunch
of
minor
things
to
we're.
Also
working
on
that
are
also
not
really
slackers.
One
of
them
is
a
design
related
and
we've
started.
A
Having
a
fortnightly
backdrop,
design
meeting
where
we
have
someone
who's
interested
in
heading
up,
all
of
our
design
efforts
and
he's
been
really
great,
helping
us
create
design
guidelines
and
human
interface
guidelines,
and
you
know
brand
guidelines
and
a
bunch
of
stuff.
That's
really
important
for
us
to
have
so.
A
We've
separated
that
off
into
a
separate
meeting,
but
I
do
want
to
mention
the
most
important
thing
that
we're
working
on
related
to
design
right
now
is
getting
our
style
guide
for
the
back
end
theme
done,
I,
don't
think,
there's
going
to
be
a
lot
in
there.
That's
gonna
require
API
change,
but
it
would
be
great
if
we
could
at
least
know
where
we
were
going
before
released.
A
So
if
there
was
something
that
required
rewriting
theme
functions
in
order
to
get
intended
markup,
we
could
at
least
have
that
you
know
know
the
Sudanese
to
get
done
before
release
or
it's
not
getting
done,
and
so
that
would
be
good.
We
had
a
couple
of
people
volunteer
to
work
on
style
guide,
but
it
hasn't
worked
out
for
any
of
them.
A
A
It
should
look
different
and
you
can
either
do
that
in
words
or
you
can
do
that
in
Photoshop
or
whatever
design
language
you're
use
to
speaking
to
tell
us
what
it
should
look
like
that's
important
and
then
the
other
thing
would
be
if
we
had
someone
who
can
actually
write
HTML
and
CSS
and
work
on
the
github
project
that
contains
our
style
guide
code.
That's
another
place
where
we
could
use
help.
So
if
you
don't
have
HTML
CSS
skills
but
you're
good
in
Photoshop,
we
can
use
you.
A
We
need
direction
on
what
this
thing
should
look
like
and
then,
if
you
do
have
HTML
and
CSS
skills,
maybe
in
addition
to
that
design,
skill
or
maybe
separate,
we
could
use
your
help
there
too,
and
helping
us
make
backdrop
feel
different
than
Drupal.
So
we've
got
some
ideas:
we
just
don't
have
anyone
working
on
that
right
now,
so
not
a
release
blocker,
but
it
would
be
nice
if
we
could
get
that
done
soon.
Other
things
we're
working
on
we've
got
a
giant
issue
for
a
theme
system
clean
up.
A
This
was
on
hold
until
we
got
layouts
done,
which
has
been
done
and
then
I
haven't
working
on
it
recently
we're
running
out
of
time.
So
I
think
probably
the
only
thing
we're
going
to
be
able
to
get
done
in
terms
of
that
is
removing
the
process
layer,
which
will
also
involve
changing
the
way
our
template
files
work
a
little
bit
so
that
we
can
call
PHP
functions
directly
from
template
files
first
before
we
didn't
use
to
do
that.
A
A
That's
kind
of
the
difference
between
the
way
things
go
and
backdrop
and
where
things
go
and
Drupal
we
like
to
make
it
a
little
better
doesn't
have
to
be
perfect
as
long
as
it's
a
better
that's
improvement,
so
we'll
work
on
perfect
it
later,
but
for
now
I'll
just
at
a
time,
and
then
we've
got
a
bunch
of
stuff
that
could
use
a
little
review.
So
if
you
don't
have
time
to
write
any
code
or
you
aren't
interested
in
working
on
github,
but
you
want
to
do
a
review.
A
What
we've
got
you
can
check
out
the
project
and
just
kind
of
look
the
code
for
us
and
tell
us
you
know.
Oh,
you
know
your
CSS
files
in
the
wrong
location
or
you're,
identifying
things
with
IDs
where
it
should
be
classes.
We
could
use
some
help
with
a
thorough
CSS
review
and
a
markup
review
for
the
new
layouts
that
we
put
in
for
right
now.
A
There's
three
layouts
and
four
there's
potential
for
adding
more
in
the
future,
but
we'll
probably
ship
with
only
three
having
those
three
reviewed
to
make
sure
that
we're
not
doing
anything
front
Enders
will
dislike
greatly
would
be
super
helpful.
So
if
you
haven't
want
to
look
at
the
template
files
for
those
layouts
and
point
out
things
that
you
think
might
be
improved,
that
could
be
useful
as
well.
So
that's
what
we're
working
on
for
backdrop!
The
product
there
are
a
ton
of
issues
in
on
github
that
could
use
some
attention.
A
If
you
want
to
take
a
look
at
it,
I
think
you
can
look
for
anything.
That's
tagged
with
one
point,
0
point
0!
Those
are
the
things
that
we
would
like
to
get
done
for
the
first
release.
If
it's
timed
with
bug,
we
definitely
need
help
with
that.
We'd
like
to
get
all
those
bugs
or
as
many
as
those
books
resolved
as
possible,
but
if
you
are
also
worried
about
your
prowess
as
a
developer,
there's
also
a
tag
for
novice.
A
We
have
a
section
in
this
meeting
to
relay
updates
from
the
project
management
committee.
We
haven't
really
had
a
lot
of
escalated
issues
yet
in
our
process,
because
we
haven't
really
had
that
many
people
who
are
complaining
about
things
yet,
which
is
good.
So
we
don't
have
any
updates
this
week,
but
we
are
retaining
this
place
for
future
updates.
That
need
to
be
there's
a
bunch
of
other
stuff
we're
working
on
as
well
as
backdrops
EMS
the
product,
including
backdrop
CMS
org,
the
website.
A
This
is
amit
will
allow
you
to
register
or
module
some
themes,
you've
written
on
github.
As
being
for
backdrop
and
having
that
association,
there
will
allow
the
backdrop
CMS
dot
work
from
a
website
to
aggregate
a
list
of
all
the
modules
and
themes
that
are
available
for
backdrop.
So
that's
also
super
important,
but
you
know
we
need
to
get
a
product
first
and
then
we
can
get
some
contraband.
Then
we
can
how
great
the.
B
A
We
have
a
place
for
change
records
that
just
hasn't
been
fully
populated,
yet
so
I
think
of
the
things
that
we're
working
on
art
the
product,
getting
our
API
site
updated
with
a
current
list
of
change
records
is
going
to
be
the
most
important,
so
we'll
start
working
on
that
as
soon
as
possible.
I
know
we've
gotten
a
couple
of
people
who
volunteered
to
do
it,
but
doesn't
look
like
any
of
them
are
actually
getting
the
time
we
hoped,
hopefully
we'll
be
able
to
focus
on
that
here.
A
Pretty
sense
that
people
can
see
that
and
then
other
things
that
we're
working
on
I
guess
today.
After
this
meeting
will
have
a
little
sprint
here
in
IRC,
if
were
people
who
are
interested
in
working
on
backdrop,
have
questions
and
how
to
do
things.
You
can
paint
nadir
I
directly
in
there.
You
can
also
tweet
at
us
or
send
us
an
email.
A
We
got
a
bunch
of
great
responses
last
week
after
the
meeting
people
who
wanted
to
help
with
various
things,
and
so
anyway,
you
can
think
to
contact
us
we're
here
to
help
at
least
short
term.
We
can
now
help
you
as
much
as
we
can
possibly
manage
and
we
will
have
some
more
in
real
life.
Sprint
dates
upcoming,
probably
starting
next
year,
so
between
now
and
really
spoil
be
just
working
remotely
on
getting
things
done,
but
we'll
try
and
help
people
as
much
as
possible.
A
We
can
do
skype
calls
if
that's
beneficial
to
help
get
people
on
board
after
that
last
week,
or
we
can
just
chat
another
share
on
Twitter.
However,
else
we've
got
some
pretty
good
resources
to
send
you
to
if
you
want
to
get
involved
so
upcoming
events,
we
are
going
to
be
next
week
in
Madrid
at
symphony
live,
which
is
a
big
conference
that
they
have
therapy.
A
I
think
this
is
their
second
annual
one
and
we're
going
to
be
talking
about
large,
open
source
communities,
not
necessarily
backed
up
in
particular,
but
kind
of
what
what
happens
when
your
community
grows
things
that
you
need
to
be
aware
of
things
that
you
need
to
work
hard
to
solve
and
I
think
that
you
know
obviously
part
of
the
reason.
The
backdrop
this
here
is
because
Drupal
grew
in
a
direction
that
we
felt
was
leaving
some
people
behind.
A
Something
will
be
good
to
talk
to
growing,
budding
open
source
community
about
how
that
happened
and
maybe
how
they
need
to
think
about
things
going
forward
or
thinks
they
might.
Maybe
they
don't
care
I,
don't
know,
but
I'll
be
good
to
raise
these
issues
anyway
and
say
this
is
what
happened
to
us
in
and
and
see
what
they
think.
That's
all
I
have
for
this
meeting.
Nate
I
don't
know
if
you
wanted
to
give
any
particular
updates
this
week.
You
know
you've
been
working
like
crazy,
no.
B
I,
don't
think
so
things
just
kind
of
rolling
along
I'm
feeling
really
good
about
about
merkin
fig
is
and
that
we
probably
complete
it.
There's
a
number
of
pull
requests
that
people
had
submitted.
That
gets
started
on
converting
some
views,
which
is
great
but
I,
think
where
those
last
stood
was
that
they
didn't
include
any
kind
of
upgrade
to
like
turn
on
those
views.
If
you
had
previously
placed
a
block,
for
example
of
recent
comments,
we
need
to
make
sure
that
block
is
replaced
with
the
view.
Okay,
I.
B
Don't
think
that
that
works
correctly,
yet
so
I
mean
all
of
those
views,
conversions
that
would
be
really
nice
to
to
have
done,
but
I
mean
we
can
do
them
at
any
time
after
the
release.
Really
because
the
current
system
is
so
limited,
you
can't
really
modify
it
in
any
way.
So
if
we
replace
it
with
a
view,
you
know
who
are
just
adding
more
flexibility,
so
I,
don't
think
that
would
be
a
hold
up
for
for
later
releases.
A
B
A
So
I'll
go
through
there
and
I'll
send
them
to
you.
If
they
look
like
they're
ready
to
be
merge,
and
then
you
can
do
a
more
thorough
review
in
yeah,
hopefully,
that'll
help
get
us
a
little
closer.
I'd,
also
like
to
work
on
some
of
the
drupal
7
it
shoes
like
either
the
latest
security
issue
or
some
of
the
you
know.
We
could
close
out
that
issue
for
up
to
seven
thirty,
one
that
would
be
nice
yeah.
They
say
we
didn't
get
that
done
today.
A
Okay,
sounds
good
right.
Well,
thanks
for
comin
Doug
and
thank
you.
Everyone
else
for
watching
they've
got
like
a
record
number
of
viewers
right
now,
so
it's
kind
of
exciting
but
yeah.
If
you
guys
have
any
questions
about
anything,
feel
free
to
reach
out
to
Nate
and
I
on
Twitter
I'm,
Jen,
Lampton,
natives,
quick
sketch
or
you
can
just
wait-
it
back
drop
CMS
and
we'll
be
able
to
notice
in
respond.
A
That
way,
if
necessary,
our
IRC
channel
is
found
drop
if
you
want
to
actually
chat
with
us
directly
or
emails
a
good
resource
to
so.
Thank
you
all
for
coming
and
watching,
and
thank
you
all
for
watching
in
the
future.
We
won't
know
who
is
not
watching
live
but
yeah.
We
will
I
think
as
of
right
now
I'm
planning
on
doing
this
meeting
next
week,
but
I
don't
know
what
time
it
will
be
in
Europe.