►
From YouTube: Backdrop CMS - weekly 10-23
Description
Backdrop CMS!
A
Alright,
we
are
on
air,
it's
Thursday,
which
means
it's
factor
update,
so
we're
here
to
have
a
little
meeting
to
update
everyone
on
where
we
are
with
backdrop,
we're
working
on
backdrop
CSS,
but
backdraft
CMS,
so
many
letters
which
is
a
content
management
system
specifically
for
nonprofits
small
to
medium
sized
businesses
and
people
who
are
concerned
about
the
cost
of
moving
a
Drupal
8
system
to
triple
seven
system
into
Tripoli.
So
we're
going
to
try
and
create
an
affordable
alternative.
A
Hopefully,
it'll
have
comparable
features
to
Drupal
8,
so
we're
creating
things
like
cmi
and
putting
these
in
core.
We'll
talk
about
these
a
little
bit
more
later
and
we're
hopefully
trying
to
add
new
features
going
forward.
So
we're
gonna
release
one
point
0
and
then
were
going
to
add
new
features
slowly
into
the
future,
which
will
be
great
so
that
will
be
able
to
create
a
system
that
is
really
comparable
to
triple
eight.
No
one
run
I'm.
A
While
we're
working
on
these
changes
right
now,
we're
also
going
to
be
fixing
bugs
so
anything
that
exists
in
Drupal
7.
Anything
that
exists
interpolate,
anything
else
that
we
find
that
maybe
isn't
particularly
either
one
of
those
if
we
can
squash
it
and
fix
it
along
the
way
that
would
be
great
and
we're
also
going
to
be
trying
to
simplify
existing
systems.
So
when
we
can
find
something
that
doesn't
require,
a
change
in
the
API
is
too
much
and
we
can
remove
it,
reduce
it
or
make
it
make
a
little
bit
more
sense.
A
We'd
like
to
do
that
as
well,
because
real
estate,
Drupal
7,
is
already
expensive,
difficult
platform
for
some
people
to
work
on
and
we'd
like
to
help
improve
the
lives
of
those
people
while
we're
doing
it.
But
the
biggest
thing
for
backup
is
not
to
change
too
much,
and
so
we're
going
to
try
to
keep
ap
is
as
close
to
Drupal
7
as
possible
and
so
achieve
all
the
same
things
that
your
plate
is
chiefing
and
that'll
help
make
it
easy
to
move
from
Drupal
7
to
backdrop.
It's
similar,
our
timeline.
A
A
That
will
include
like
okay,
well,
whatever
we
don't
get
in
to
one
point,
0
point
0
will
put
into
one
point:
one
will
decide
what
that
is,
we'll
work
on
it
and
when
one
point
one
comes
out,
it'll
contain
that
feature.
If
that
feature
doesn't
get
done,
it
push
till
one
point
two,
but
one
point
one
will
still
come
out.
A
So
we've
got
a
bunch
of
stuff
we're
working
on
right
now.
We've
got
a
handful
of
things
that
we're
calling
major
projects
that
are
sort
of
API
blockers
that
are
preventing
us
from
releasing
and
I've
got
a
bunch
of
other
stuff.
That
is
important,
but
maybe
not
a
blocker
I
think
that
we'd
like
to
do,
but
if
we
don't
get
done
in
time,
won't
release
any
way,
and
then
we
have
a
bunch
of
minor
projects
that
are
just
going
to
make
this
software
much
better.
A
So
we'll
start
with
the
major
projects
here
and
the
first
thing
I've
got
big
news
on
this-
is
our
blocks
and
layouts
initiative.
This
is
a
replacement
for
the
block
system
in
Drupal
7
and
our
layouts
that
were
dictated
by
our
themes
that
did
a
one
layout
/
site,
which
of
course
is
not
realistic
for
the
actual
websites
we're
building
these
days
and
people
have
come
up
with
a
gazillion,
different
kinds
of
workarounds
for
how
to
solve
this
problem
in
in
Drupal,
and
so
we've
taken.
A
B
B
So
we
now
have
our
new
layout
system
is
now
officially
in
backdrop
for
which
is
fantastic.
It's
a
really
pretty
sweet
system.
It's
not
that
different
from
the
demo
that
we
gave
a
couple
of
weeks
ago.
If
you
want
your
YouTube
channel,
there's
a
layout
preview
in
there,
and
it's
really
just
about
the
same
as
what
you
see
in
that
video.
The
past
couple
of
weeks,
we've
just
been
fixing
bugs
making
sure
everything
works
correctly
and
making
a
few
the
enhancements
here
and
there,
but
for
the
most
part,
it's
really
the
same
thing.
B
There's
nothing
really
new
as
far
as
the
blocks
that
you're
able
to
place,
but
the
underlying
framework
is
now
just
a
lot
more
powerful,
so
we're
going
to
continue
rolling
along
with
with
blocks
and
layouts
as
much
as
possible.
But
at
this
point
we've
got
it
barring
any
any
major
bugs
in
a
shippable
position,
so
which
is
great.
That
means
it
would
probably
shift
some
of
our
resources
to
other
things
that
are
release
blockers
like
can,
like
finishing
the
cmi
conversions.
B
A
Do
have
in
the
meta
issues,
there's
a
bunch
of
feedback
already
that
can
be
addressed
so
if
you're
reviewing
it
and
you
start
creating
a
list
of
you
know
things
that
you
don't
like
I
thinks
you
want
changed,
make
sure
to
compare
to
that
meta
list
of
issues
for
changes
because
there's
a
lot
of
stuff.
The
weird
you
know
about
that
obviously
needs
to
get
done
that
you
know
we
can
fix
things
later,
so
some
of
those
sex
are
also
novice.
A
So
that's
great,
that's
super
exciting,
with
working
on
it
for
months
and
months
until
getting
it.
Finally,
in
is
huge,
I
think
it's
going
to
be
huge
improvement
over
the
way
that
Drupal
7
handles
things.
It
obviously
needs
a
little
polish,
but
it's
it's
solid,
so
I'm
super
excited
to
start
playing
with
it.
Next
up
other
things
that
are
blocking
a
release.
A
This
is
what
are
we
are
shifting
our
attention
right
now
is
the
configuration
management
a
tool,
so
this
is
something
that
we've
created
an
impact
truck
much
like
they've
done
in
turmoil,
as
you
just
save
your
configuration
in
two
files
rather
than
storing
it
in
the
database,
and
we've
been
working
on
this
for
a
while,
we've
gotten
a
bunch
of
systems
converted,
but
we
don't
have
all
of
the
super
important
ones
covered
it
already,
particularly
content
types
and
fields,
and
so
I
know.
Nate
has
also
been
doing
a
bunch
of
work
on
that
lately.
B
B
Let's
see,
the
new
layout
system,
of
course,
obviously
is
using
config
files
to
store
all
of
its
functionality,
and
a
nice
thing
is,
is
that
the
layouts
branch
actually
fixed
a
whole
bunch
of
things
because
variables
used
to
be
used
for
all
of
the
block
settings.
So
there
was
only
one
time
you
could
place
a
block
on
the
entire
site,
so
things
like
you,
know
the
number
of
recent
users
to
show
or
something
like
that
used
to
be
a
global
setting
stored
in
the
variables
table
and
with
the
new
layout
system.
B
The
most
important
pieces
that
we're
missing
right
now
is
content
types
and
fields,
but
I
started
on
constant
types
a
couple
weeks
ago
in
issue
171,
and
it
looks
really
pretty
good.
I
actually
think
that
it's
ready
to
go
it's
just
that
we
wanted
to
get
my
out
first,
because
there
was
once
your
conflicting
update
hooks.
So
now
that
layouts
are
in
we
can,
you
know,
resolve
all
the
conflicts
that
that
we
had
between
node
types
and
and
blocks
and
then
and
then
get
no
types
in
I.
B
Think
with
most
of
these
things,
like
no
types,
it
only
took
like
a
couple
days
to
get
it
converted.
The
next
big
thing
will
be
fields
and
I'm,
hoping
that
it
will
go
along
quickly
and
quickly
as
quickly
as
well
play
as
well
more
complicated
than
then
just
about
anything
else.
So
ya
know
types
are
going
to
be
done
here
in
the
next
probably
week,
then
we're
going
to
move
on
to
fields
and
then
from
then
on
the
rest
of
the
major
subsystems
listed
in
issue.
1
69,
that's.
A
Great
and
that
one
of
the
other
major
issues
we're
working
on
is
getting
views
in
core.
We
have
the
views
module
in
core
right
now,
but
there's
a
bunch
of
listings
in
core
that
are
generated
by
things
that
are
not
using
views
and
we're
working
on
getting
those
converted
to,
and
we
had
a
lot
of
help
in
the
last
few
weeks
with
people
building
views
for
us
and
helping
get.
Those
ready,
which
is
great.
A
B
We
did
stuff
like
we
just
took
the
entire
config
file
out
of
a
out
of
the
the
default
config
director
module
and
just
threw
it
right
into
the
active
directory,
but
we
realized
that
that
was
going
to
cause
upgrade
problems
in
the
future.
If
we
end
up
changing
the
default,
the
chips
with,
like
let's
say,
default
views
that
ship
with
user
module.
If
we
change
them
later,
then
we'll
also
have
later
update
hooks.
That
expect
the
default
view
from
when
from
when
user
module
was
initially
installed
like
at
one
point.
B
Oh,
so
we
can't
just
copy
the
active
configure
the
default
config
files
into
the
active
config.
We
need
to
essentially
rebuild
the
entire
config
as
a
giant
array
and
then
just
save
it
into
the
active
config
directory
as
part
of
an
update
hook.
So
it's
it's
a
little
tedious,
but
it's
not
actually
that
much.
It's
not
actually
that
difficult
to
do
and
that's
what
we're
missing
on
on
most
of
those
views.
Conversions
already
converted
they
already
work,
but
they
don't
automatically
create
themselves
if
you're,
upgrading
from
a
Drupal
7
site.
B
A
file
right,
yeah
and
and
what
that
really
means
is
that
you
would
say
like
config
and
then
choose
the
name
of
the
file
like
views,
dot,
view
dot,
I,
don't
know
user
admin
or
whatever,
and
that
that
opens
up
a
config
file
for
writing
and
they
say
config
arrow
set
data.
And
then
you
pass
in
the
entire
array.
And
then
you
say:
arrow
save
sound.
So
you
can.
B
B
Yeah
that
there's
a
bunch
of
other
places
where
we're
doing
this,
like
the
new
update,
hook
kind
of
gives
you
a
kind
of
good
idea
of
how
to
do
that.
The
node
type
conversion
is
going
to
do
a
lot
of
that
as
well,
because
it's
the
same
sort
of
thing
and
then
all
of
the
variables
we
have
converted
all
due
to
do
this
as
well.
But
they
all
just
open
up
a
config
file,
write
a
whole
bunch
of
times
and
then
save
okay.
A
So
other
things
we're
working
on
other
than
the
our
release
blockers
are
making
sure
that
we
are
keeping
up
with
what's
going
on
in
Drupal
and
there's
a
couple
of
places
where
that's
really
super
important.
The
first
one
is
security
issues,
so
any
security
fix
that
has
gone
into
triple
seven
may
need
to
make
sure
we
have
a
comparable
fix
for
backdrop.
So
last
week,
everyone's
probably
aware
of
this
horrible
security
problem
that
came
out
in
Drupal
and
everyone
has
been
frantically
updating
all
of
their
Drupal
sites
to
avoid
getting
hacked.
A
We
need
to
get
that
same
solution
into
backdrop
as
well,
and
that's
super
important
for
anyone
who
is,
you
know,
running
a
live
backdrop
site
which
I
think
that's
one
of
me.
Would
anyone
else
should
should
I
keep?
We
need
to
mean
to
make
sure
we
get
those
security
updates
from
Drupal
into
backdrop
as
well.
There's
also
a
couple
of
others
that
haven't
been
fixed
yet
previously
that
we're
slightly
less
serious.
Those
are
really
important
for
us
to
get
in
before
we
release
and
then
the
other
thing
is.
A
A
I
need
to
look
into
I,
think
that
might
have
actually
gotten
done,
so
it's
unblocked
now,
but
I'll
double
check
and
then
there's
two
other
things
that
have
been
introduced
into
drupal
aidan
and
caused
some
serious
problems
either
in
terms
of
accessibility
or
introducing
bugs,
and
so
we're
waiting
to
commit
those
to
see
if
those
problems
can
get
resolved
in
in
tripoli.
First,
so
I
think
what
we're
going
to
end
up
doing
is
when
we
need
to
release
what
we'll
do
is
we'll
mark.
A
This
meta
issue
is
closed
and
create
a
follow
up
with
this
stuff
that
doesn't
actually
get
in.
So
that
way
we
can
still
say.
Oh,
you
know
if
we
need
to
add
in
html5
required
property
later
we
can
do
that,
but
that
way
that
we
don't
have
to
keep
looking
at
this
same
issue,
we
can
create
another
one
where
we're
specifically
focus
sing
on
that
and
try
and
getting
get
it
done,
and
then
we've
got
some
other
things
that
we're
working
on
that
are
important
for
backup,
but
not
release
blockers.
A
The
first
one
is
to
separate
backdrops
identity
from
that
of
Drupal.
When
you
log
into
a
backdrop
website
as
a
user,
it
should
feel
different
than
logging
into
a
Drupal
site
and
that's
hard
to
do
because
it's
almost
the
same
this
triple
seven,
but
what
we
thought
would
make
a
really
big
difference
is
to
update
the
style
guide
for
the
admin
interface.
So
the
7
theme,
what's
currently
called
the
seven
theme
and
still
looks
and
feels
the
same
as
it
does
in
Drupal.
A
They've
done
a
bunch
of
stuff
into
your
blade
to
kind
of
bring
it
a
little
bit
a
little
bit
more
modern
and
we
want
to
do
the
same.
We
want
to
solve
the
same
kind
of
problems
that
they've
solved,
but
we
obviously
don't
want
to
use
their
patches
because
then
backtrack
will
still
to
continue
to
feel
just
like
drupal.
A
So
we've
had
Julia
doing
some
work
on
creating
a
style
guide
for
us
for
the
last
few
weeks
that
I'm
not
entirely
sure
she's
got
the
time
to
really
commit
to
get
that
done
for
us
in
time
for
the
release.
So
I
would
like
to
follow
up
with
her
sometime
this
week
and
see
if
we
can
get
that
handed
often,
maybe
someone
else
who
can
get
us
a
style
guide,
and
this
is
not
something
that
requires
any
skill.
So
if
we
have
anyone
who's
watching
this
video,
it
doesn't
require
any
coding
skill.
A
A
Work
did
I
bone
one
person
who
doesn't
have
very
much
time.
So
we
have
anyone
watching
this
video
who
has
that
design,
aesthetic
which
we
are
lacking,
and
it
would
really
be
great
to
have
someone
come
and
contribute
at
least
that
much
and
then
we
can
take
over
the
code
and
implement
that
stuff
later
or
if
you
have
both
sets
of
skills.
That's
even
better,
but
I
think
the
Julie
is
going
to
need
some
help
there.
So
if
we
could
get
someone
else
on
that,
that
would
be
super
useful
and
then
other
stuff.
A
We're
doing
is
minor
cleanups
to
the
theme
system,
so
making
sure
that
people
who
are
theming
for
a
drupal
7
are
slightly
less
frustrated
when
they
are
theming
for
backdrop.
There
are
some
things
that
we
have
done
in
Drupal
8
to
improve
the
theme
layer
that
don't
have
anything
to
do
with
changing
all
the
fastest
wake.
I've
got
a
list
of
those
changes,
I'd
like
to
make
some
of
those
change
same
changes
to
backdrop.
These
again
are
not
super
critical
to
get
in
before
we
release
it's
more
important
that
it.
C
A
Really
similar
to
Drupal
7,
so
we'll
take
the
ones
that
are
the
most
annoying
change.
Those
thinks
I
might
gives
performance
improvements
and
change.
Those
we're
not
going
to
be
changing
everything
and
then
other
things
are
user
experience.
Improvements
so
for
people
who
are
using
the
software
Drupal
can
sometimes
be
a
frustrating
experience.
A
Apple
products
are
really
amazing
to
use
and
we
don't
believe
in
their
licensing
rules,
but
the
you
can't
deny
that
the
products
are
intuitive
and
they're
friendly
and
they're
fun
and
you
can
use
them
very
easily
and
they
have
a
really
solid
example
of
a
user
interface
guideline
which
helps
people
follow
the
rules
about
how
to
make
something.
That's
intuitive
it
useful
and
so
we're
going
to
try
and
do
is
establish
something
similar
for
backdrop.
A
Don't
think,
that's
something
that
Drupal
has
if
it
is
something
as
triple
has
I
haven't
seen
it,
which
means
it's
either
not
public
or
not
easy
to
find
so.
I
think
that
that's
something
that
really
helped
us
out
to
long
term
and
trying
to
create
a
better,
more
intuitive,
more
simplistic
product,
so
I'm
super
looking
forward
to
that,
which
is
great.
A
Let's
see
so,
we've
got
a
couple
of
changes
that
happen
in
the
last
week,
which
is
really
great,
BW,
panda
added
a
submit,
an
issue
to
add
a
cancel
link
on
a
node
creation
form,
which
is
something
that
I
have
wanted
for
a
very
long
time.
So,
when
you're
creating
a
note,
it
gives
you
two
buttons.
It's
like
preview
and
save,
but
but
what
do
you
want
to
do
if
you
don't
want
to
save?
A
If
you
want
throw
this
thing
out
and
right
now,
the
only
solution
is
that
the
back
button
in
your
browser,
but
it's
kind
of
silly,
like
we've
trained
people,
don't
hit
the
back
button
in
your
browser
because
sometimes
that's
not
what
you
want
to
do.
You
want
to
give
them
a
way
out
of
that
form,
so
we've
added
a
cancel
link.
This
is
the
same
kind
of
experience
that
you
have
when
you're
and
you
get
to
a
confirm
form
and
the
confirm
form
says
you
know,
continue
or
cancel
and
there's
a
cancel
link
there.
A
C
A
My
god,
dr.
boosted,
early
fast
so
yay
for
having
a
nice
small
issue
queue
or
things
can
get
tended
to
quickly
for
now
so
I
think
that
that's
a
huge
improvement
and
thanks
to
be
w
panda
for
that
change.
Also.
So,
let's
see,
we've
also
got
a
bunch
of
stuff
that
we
would
love
to
have
reviewed
before
release
and
since
we're
getting
close
to
release,
it
would
be
great
to
have
somebody
look
at,
for
example,
the
mark-up
that
is
generated
from
layout
module.
A
That's
brand
new
adjustment
in
this
week,
so
if
we
could
have
somebody
I
ball
that
and
make
sure
we're
not
doing
anything
that
front
Enders
are
really
going
to
disagree
with.
That
would
be
great
and
then
also
if
we
could
have
kind
of
a
CSS
review
and
I
really
high
a
high
level
like
are
all
the
CSS
files
in
directories
called
CSS,
and
are
we
using
classes
instead
of
ID's
as
much
as
possible?
Things
like
that
would
be
really
good
jest.
A
A
So
if
anyone
wants
to
work
on
that,
that
would
be
a
good
place
to
jump
into,
especially
if
you
have
front-end
skills
like
HTML
and
CSS,
that
something
new
Drupal
is
notoriously
bad
at
getting
right,
and
so
since
we're
inheriting
that
legacy
we'd
like
to
improve
that
as
possible,
so
we
good
to
have
a
review
there.
Let's
see
a
peripheral
thanks,
we're
working
on
the
API
website
is
up
and
running,
which
is
great.
We've
got
change
records,
I'm
not
sure
if
anyone's
done
any
work
on
that
since
last
week.
C
A
See
yeah,
so
if
you
I'm
not
sure
if
you
can
see
this
agenda,
they
make
an
plus
this
in
here
too,
but
in
the
section
here
for
the
API
website.
There's
a
link
of
change
records
that
are
currently
on
github.
So
these
are
the
ones
that
Nate
and
I
have
changed
something
and
then
tagged
it
as
needs
change,
notice,
usually
nate.
Those
are
the
ones
that
we
need
to
add
and
then
there's
also
a
list
here
of
change
records
from
drupal
org.
A
So
we
just
need
to
take
the
earliest
ones
from
one
drupal,
8,
forked
until
january
29th
2012,
and
make
sure
that
we
didn't
get
those
included
too,
and
so
it
might
be
good
to
start
with
the
drupal.org
ones,
because
those
are
more
similar
to
what
we
actually
are
going
to
want
on
our
API
site.
But
if
we
could
get
a
couple
of
those
moved
over
you'll
probably
start
to
see
how
the
the
architecture
on
the
drupal.org
side
doesn't
exactly
match.
A
C
A
That
so
yeah
I
think,
if
you
can
just
create,
like
five
of
them,
it'll
become
really
obvious,
where
the
deficiencies
are
in
the
architecture
and
then
we
can
switch
over
like
if
you
want
to
create
off
and
would
be
amazing.
But
do
you
want
to
switch
over
and
try
and
create
a
new
one
based
on?
What's
github,
you
can
see
if
there's
any
differences
there
as
well
and
some
of
those
like
we
don't.
A
We
don't
necessarily
have
final
wording,
but
it
would
be
good
to
get
a
placeholder
for
them
on
our
API
say
anyway,
that's
like
we
know
we're
going
to
need
this
change
record.
We
don't
know
what
it's
going
to
say:
here's
a
rough
guess
at
what
it
is,
and
then
that
way
we
can
come
back
and
edit
it
more
easily
as
they.
Oh,
you
know
what
I
meant
to
say
was
this
oil
is
change,
the
title
or
whatever
it
is.
They
need
to
get
an
update
and
at
least
we'd
have
a
starting
place.
It's
easier.
C
B
C
A
That
sounds
about
right
all
right
and
in
the
biggest
thing
is
just
making
sure
like.
If
we
can
get
the
first
ten
done
will
know
that
we
have
the
architecture
done
and
we
can
hand
it
off
to
anyone
to
create
the
rest,
but
because
are
intimately
aware
with
how
that
API
site
is
set
up.
Having
you
do
the
first
ones
and
change
things
when
you
run
into
problems
would
probably
be
the
best
use
of
your
time,
and
so
you
can
go
ahead
and
make
changes
to
the
fields
and
stuff
if
that's
needed.
Okay,.
C
A
Be
great
all
right,
okay
and
then,
if
you're
doing
a
as
your
Borg
one,
you
can
link
to
Drupal
that
or
like
if
there's
any
history
in
there.
That's
like
here's
how
this
has
changed
like.
Obviously
we
don't
have
that
history
and
backdrop,
so
you
can
still
link
those
out
to
dribble
the
org
I
think
that
would
be
valuable
for
people
who
are
coming
to
backdrop
and
need
that
information
and
so
I
wouldn't
be
afraid
of
life
stuff.
The
links
off-site
yeah.
A
All
right
update
server,
so
we
haven't
done
any
progress
on
the
update
server.
We
need
to
build
a
server
that
will
allow
your
backdrop
site
to
talk
to
its
mothership
and
find
out
if
it's
up
to
date
or
not.
We
have
some
great
idea
about
how
we'd
like
to
do
things
a
little
bit
differently
on
backdrops
dates
over
than
we're
doing,
I
Drupal's
and
particularly,
would
like
to
check
information
about
which
modules
and
any
given
back
to
outside
are
being
used
and
some
of
the
subsystems
as
well.
A
So
we
have
some
ideas
about
what
we
want.
We
haven't,
I,
don't
have
anyone
working
on
it.
It
would
be
great
if
we
could
get
someone
to
start.
If
not
it'll
have
to
wait
until
the
backdrop
one
comes
out,
which
is
our
backdrop.
One
point
0
point
0
just
less
than
ideal,
but
you
know
the
code
done.
First
is
more
important
and
then
we
also
need
an
official
github
service.
A
So
this
is
so
that
people
who
create
modules
and
themes
on
github
can
identify
those
modules
and
things
it's
being
specifically
for
backdrop
and
then
backups
website,
the
flagship
site
vector
of
CMS
org
can
gather
all
of
that
information
off.
If
you
have
to
build
a
listing
that
people
can
search
to
find
stuff
again,
we're
gonna
need
modules
and
themes
before
we're
going
to
need
this
service,
but
we
are,
we've
got
a
couple
we
can
use
to
test.
A
If
somebody
wanted
to
start
working
on
it
right
now
in
it
would
be
super
useful
to
have
that
with
the
redesign
of
our
website,
which
well
Cynthia
some
happen.
So
we
haven't
even
work
on
an
update
server.
That
would
be
really
valuable
in
addition
to
our
service
official
github
service
and
so
other
things
you're
working
on
for
our
primary
website.
We
want
to
get
a
redesign
kind
of
around
the
same
time
as
our
launch,
though,
will
show
you
know
we're
not
just
a
software
project
in
development,
but
we're
actually
a
legit
thing.
A
Once
we
become
a
legit
thing,
that
would
be
useful.
We
want
to
use
our
new
logo
and
fonts
in
our
general
branding
guide
once
we
have
that
done,
which
will
be
really
handy.
We
want
to
be
able
to
build
the
service
little
people
to
find
modules
and
themes.
We
also
want
to
have
a
showcase
site.
Much
like
drupal
has,
which
is
super
successful
and
also
a
directory
where
people
who
are
doing
things
with
backdrop
can
be
found.
So
Drupal
also
has
a
way
that
you
can
search
for
service
providers
and
various
different
areas.
A
I
think
backdrop
me
it's
the
same
kind
of
thing
and
then
Drupal
also
recently
launched
a
drop
a
job
site.
So
if
you're
someone
looking
for
a
job
which
we're
looking
to
hire
more
likely,
you
can
post
those
listings
on
the
website,
I.
Think
getting
all
these
things
for
backdrop
is
going
to
be
super
useful
priorities,
though,
like
you
shouldn't
post
any
drops
until
we
have
any
jobs
shouldn't
build
the
job
site
till
we
have
jobs
longer
priority.
Just
thankfully
see
Drupal
doing
and
going
oh
yeah.
That's
a
good
idea.
I
wish
do
that
too.
A
We
throw
in
this
list
and
we
offer
now.
It's
the
redesign
getting
some
branding
up
there.
That
says
we're
doing
the
right
thing.
Some
new
words
are
good,
that
kind
of
stuff,
so
the
dress
have
stuff
to
do.
We
can
use
help
everywhere
along
the
way
people
want
to
jump
in.
Just
let
us
know
we
work
virtually
together
every
Thursday.
So
after
this
meeting
through
the
rest
of
the
afternoon
evening,
we
are
going
to
start
doing
a
fortnightly,
a
design,
specific
meeting
for
backdrop.
A
This
is
not
a
good
time
for
that
meeting,
so
we're
going
to
try
and
do
another
one,
it's
on
a
little
bit
of
a
shifted
schedule
so
that
we
can
get
people
from
all
around
the
world
included
and
so
we're
planning
on
meeting
at
eight-thirty
p.m.
tonight.
But
I
don't
think
they're
available
tonight,
so
we're
going
to
try
and
start
next
week
next
week,
so
we'll
have
meeting
in
the
middle
of
the
day.
This
one
is
kind
of
lunch
time
for
those
of
us
in
California.
A
We're
gonna,
try
and
do
another
one,
just
after
dinnertime
little
work
for
breakfast
for
people
in
India,
so
hopefully
that'll
work
out
and
we
can
kind
of
include
some
people
for
more
in
more
parts
of
the
world
than
just
here
in
the
US.
So
hopefully
that'll
be
the
right
time
we'll
follow
up
on
Twitter,
wherever
we
can
with
an
actual
time
once
that
gets
settled,
but
yay
designers,
we
don't
have
any
of
them.
They
are
amazing.
I'm
super
excited
other
stuff,
we're
going
to
meet
in
real
life
at
bad
camp
on
sunday
november.
A
9Th
we're
gonna
have
an
in-person
sprint,
we're
going
to
steal
a
round
table,
or
maybe
more
than
one,
depending
on
how
many
people
show
up
in
the
mezzanine
level,
which
is
where
all
of
the
sprinting
happens
at
bad
camp.
So
they're
going
to
be
having
a
court
about
four
summit
nearby
we're
going
to
steal
one
of
the
tables
there
in-in
decoder
area
for
backdrops,
printing,
so.
A
We
can
all
work
together
to
make
everything
better
in
the
same
place,
I'll
get
along,
which
will
be
great
and
other
stuff.
That's
coming
up.
We
also
are
going
to
be
giving
a
talk.
Not
only
at
bad
camp
session.
Schedule
was
posted
earlier
this
week,
but
also
at
symphony
con
in
Madrid.
We've
been
asked
to
do
a
keynote
talk
on
open
source
communities
and
so
that'll
be
super
interesting
to
talk
to
a
community.
A
That's
not
Drupal
about
the
Drupal
community
and
backdrop
community
and
hopefully
see
see
what
they're
growing
open
source
community
is
running
into
as
well,
so
I
think
that
will
be
super
fun
and
then
other
stuff
coming
up
next
year.
We
don't
have
anything
for
firm
on
the
calendar,
but
we
are
looking
into
places
where
people
are
interested
in
hearing
about
backdrop.
A
So
if
you
want
us
there,
let
us
know
if
you
don't
want
us
there,
don't
let
us
know-
and
we
probably
won't
show
up
that-
is
it
I
guess,
for
today's
agenda,
but
I
did
want
to
open
up
and
see
if
anyone
had
anything
else
to
add
or
any
questions
or
anything
that
we
should
add
to
this
weekly
Jenna
I
got
nothing
got
nothing
I
feel
like
so
much
amazing
stuff
has
happened.
I
do
want
to
add
just
cuz.
I'm
super
excited
about
it.
A
C
I
actually
do
have
one
thing.
Yes,
the
the
backdrop.
Examples
project
that
I
I
I've
started
is
is
on
github.
I
I
can
put
the
repository
and
if
you
tell
me
where
I
should
broadcast
that
and
not
be
happy
if
anyone
else
want
to
jump
in
and
do
the
same
kind
of
thing,
it's
it's
really.
It's
super
easy.
You
know
most
most
of
the
examples,
just
each
change
you
that
info
file
and
they
work
nice
and
and
then
the
ones,
don't
that
that's
the
interesting
stuff
so
either
way
it's
get
into.
C
B
That's
that's
a
thinking
that
we
should
invite
you
loop
to
to
the
backdrop,
can
trip
right
now.
There's
a
group
on
github,
github.com,
/
backdrop,
hyphen
contribs
and
the
only
module
that's
in
there
is
the
devel
module.
If
you're,
if
you
needed
a
backdrop,
portage
LOL
module,
but
it
would
be
great
but
examples
in
there
as
well
I
mean
long-term.
A
All
right
well,
thank
you
Luke!
That's
amazing!
I
can't
wait
to
see
it
we'll
see
everyone
in
IRC.
You
have
any
questions
you
can
tweet
at
us
we're
at
backdrop.
Cms
enjoys
an
IRC.
You
can
find
us
on
Facebook
you
can
you
can
try
and
find
this
at
Google+,
but
I
wouldn't
recommend
it.
It's
really
possible
find
anything
on
google
plus
so
yeah
Twitter
Facebook,
IRC
email.
However,
you
can
get
a
hold
of
us
to
go
ahead
and
do
it
we're
here
to
answer
questions
all
right.