►
From YouTube: Backdrop CMS weekly meeting 5/29
Description
Backdrop weekly meeting starting in roughly 20 minutes. Today's agenda: http://bit.ly/1nw2PmH #BackdropCMS
A
We're
also
working
on
getting
all
of
the
Drupal
7
cross
ports
in
so
that's
every
commit
that
has
been
made
to
Drupal
7,
since
it
has
been
getting
more
commences
as
time
go
on
we're,
including
those
in
fact
drop
as
well.
In
terms
of
new
projects,
we've
been
working
on
adding
blocks
and
layouts
to
backdrop.
So
that
means
a
better
way
of
placing
content.
On
a
page,
we've
been
putting
views
in
core
which
is
getting
listing
management
tool
so
that
you
can.
A
Lists
of
anything
in
config
management,
so
that
you
can
separate
the
save
the
configuration
from
the
content,
so
they
want
both
be
chef
in
database
and
hard
to
separate
for
deployment
and
other
good
maintenance
reasons.
Minor
projects
we've
been
working
on
are
separating
the
identity
of
backdrop
from
Drupal,
and
we've
got
a
bunch
of
big
updates
on
this.
For
starters,
we
are
replacing
the
word
Drupal
everywhere
in
backdrop
with
the
word
backdrop
includes
functions
that
have
the
word.
A
Drupal
in
them
are
now
going
to
be,
starting
with
backdrop
variables
that
have
the
word
ripple
in
them.
We've
dropped
to
the
word
Drupal,
so
it's
just
the
variable
name
and
we've
got
a
whole
bunch
of
other
things
that
are
getting
updated
to
like
documentation
and
other
stuff,
like
that.
So
there's
a
patch
in
the
keel
I'm
about
75%
of
the
way
through
reviewing
it.
It's
a
doozy,
but
it
looks
really
good
so
far
there
haven't
than
anything
where
I
thought
you
know.
Maybe
we
shouldn't
replace
that,
or
you
know
anything
that
we
have
missed.
A
Apparently
he
was
pretty
nervous
about
it,
but
he
showed
it
to
us
and
just
knocked
it
completely
out
of
parking
I,
both
love
it
and
so
right
now
we're
waiting
for
design
files
from
him.
So
we
can
go
ahead
and
put
them
up
and
show
you
guys
what
it
looks
like,
but
it's
not
a
drop
just
to
kind
of
hint.
A
So
it
looks
really
great.
We've
also
got
a
font
face
that
we're
going
to
be
using
for
for
the
website
and
for
all
of
our
graphic
stuff
too,
which
is
open
source
font.
So
we're
really
excited
about
the
way
everything
looks
and
we're
looking
forward
to
getting
some
of
that
I'm
going.
So
we
can
start
having
an
identity
online,
which
I
think
will
be
amazing.
A
We've
got
our
admin
theme
style,
guide
kind
of
on
the
on
the
same
note
there
underway,
and
we
need
to
have
a
check
in
with
Julia
and
see
how
she's
going
on,
but
now
that
we
have
a
logo
and
font
and
a
color
palette
I
think
would
be
really
great
to
kind
of
include
some
of
those
in
our
admin
theme
too.
We
just
have
to
make
sure
that
our
admin
theme
doesn't
look
exactly
like
our
public-facing
web
site
when
we're
done,
because
that
ends
up
being
confusing
to
people.
A
But
we
are
starting
to
have
our
own
identity,
which
I
think
is
super
exciting
and
then
we're
also
yeah
I
mean
we've
got
some
design
tasks
like
not
only
at
the
admin
theme,
but
also
the
installer
and
some
other
things
that
will
start
to
make
things.
Look
more
backdrop:
Ian
Lester,
bully
other
easier
experience
improvement.
Last
week
we
told
you
awake
our
admin
menu
committed,
decor
we've
had
a
couple
of
minor
changes
to
it.
A
Since
then,
it
introduces
and
fixed
a
bug
yesterday,
just
great
there's
a
couple
of
other
little
things
that
need
tweaking
but
I.
Think
overall,
it's
a
huge
improvement.
I
think
it
makes
managing
a
site
much
easier
right
out
of
the
box
without
having
to
go,
install
a
module
to
help
you
manage
just
navigate
around
just
good
I've
got
some
other
stuff
going
in
we've
got
a
terminology
updates.
A
There's
a
issue
where
we're
working
on
that
I
think
having
the
admin
menu
in
core
is
going
to
help
that
a
little
bit,
because
we
don't
need
to,
for
example,
remove
the
word
modules
from
the
menu.
If
we
have
a
category
called
functionality,
then
we
can
have
a
top-level
item
in
there
called
modules,
and
so
we
can
kind
of
train
people
that,
if
you
need
functionality,
you
add
modules
just
by
having
those
words
in
the
menu.
So
I
think
that
there's
a
lot
of
hope
for
making
our
terminology
a
little
better.
A
Just
by
having
an
admin
menu
in
there
gives
us
more
places
to
put
words
to
help
people
figure
out
what
they
need
to
do,
which
I
think
is
great.
We've
also
got
a
rich
text
editors
next
on
the
list
for
user
experience
and
weapons,
which
is
great
and
for
a
last
few
weeks
with
making
a
ton
of
progress
on
Team
system
improvements.
We've
got
everybody
working
on
CSS,
cleanup,
consolidation
of
template
files,
removing
paint
functions
and
don't
make
sense
and
cleaning
up
all
of
our
JavaScript
to
make
this
in
a
text
look
better.
A
So
I
think
that
the
front
end
is
finally
starting
to
get
some
attention,
which
makes
me
really
happy
because
we've
kind
of
been
ignoring
it
for
the
last
six
months.
So
hopefully,
it'll
start
to
look
and
feel
more
like
a
system
that
front
Enders
will
be
looking
forward
to
using
as
well
as
drupal,
developer,
back-end
types.
So
I'm
super
excited
about
that
too,
and
we
have
no
updates
from
the
PMC
this
week
other
than
the
fact
that
we
have
a
logo.
We
love
it
and
we'll
get
so.
A
A
In
and
then
I
was
thinking
about
updating
all
of
our
like
github
profile
pages
and
such
so
that,
rather
than
having
the
drop
that
we're
using
now
are
a
little
open
source
trap.
We
start
to
kind
of
set
our
identity
on
github
and
then
we'll
have
a
slower
process
of
getting
that
brand
on
to
our
own
websites.
We
need
to
actually
design
the
website,
but
we
will
start
getting
some
of
these
elements
in
some
places,
so
people
can
see
what
they
look
like
and
then,
let's
see
other
things,
we're
working
on
an
API
site.
A
I'm
happy
to
announce
that
I
made
some
commits
to
our
API
have
a
positive
re.
This
week
we
don't
actually
have
a
website
up
yet,
but
we
do
have
a
Drupal
and
a
bunch
of
contributed
modules
that
are
ready
to
go,
which
is
good,
and
so
all
we
need
to
do
is
put
that
up
on
a
server
and
then
I
was
going
to
give
Luke
login
and
let
him
kind
of
go
to
town
on
setting
up
some
content
types
for
change.
A
Notices
in
that
sort
of
thing,
so
I
think
we're
getting
closer
on
that
which
is
really
good.
Then
we
have
update
server.
We
still
need
to
figure
out
how
we're
going
to
make
that
work
for
contribute,
an
official
github
service,
which
will
also
make
our
kinship
work
a
little
better
and
backdrop
primary
website.
We
need
a
new
redesign
with
logo
as
well
as
we
need
to
add
our
module
in
theme
section
in
a
showcase
section
as
well
else.
A
What
we
have
there
sprints
it's
Thursday
we're
going
to
be
working
on
backdrop
this
afternoon
and
anyone
else
who
wants
to
work
with
us
is
effin
and
that's
great.
We've
also
been
kind
of
working
on
backdrop,
Monday,
Tuesday
and
Wednesday
few
weeks,
we'll
probably
do
the
same
next
tuesday
as
well.
We've
got
a
groan
working
on
back
jeff
and
then
thursdays.
It
will
probably
see
kind
of
a
ramp
up
between
now
and
launch.
A
Just
we're
trying
to
get
out
of
these
little
improvements
in
to
kind
of
make
a
big
splash
and
then
drupal
corn,
coming
up
in
July
in
Twin
Cities
drupalcamp
in
August
will
also
be
doing
in
person
its
prints.
If
anyone
wants
to
come
to
you,
those
events
they're
both
gonna,
be
a
lot
of
fun.
Our
article
in
drupal
watchdog
is
out
which
is
kind
of
exciting.
Yes,
even
get
one.
A
A
So
I
think
that
it's
not
quite
the
reason
tatian
I
wanted.
I
was
kind
of
expecting.
It
would
be
like
one
major
article
and
replayed
and
then
one
pager
I've
gone
back
Jeff
and
then
everything
else
would
just
be
peripheral
but
apparently
like
there's
a
lot
that
needs
to
be
said
about
dribbling
no
surprise
there
so
that
basically,
the
entire
magazine
is
to
play
so
I
guess:
I'm
glad
we're
in
there
at
all,
which
is
good
but
yeah.
It's
kind
of
like
after
you've
read.
Everything
here
is
to
read
about
Drupal.
A
If
you're
worried
about
it,
here's
an
article
about
an
alternative
which
I
think
is
good.
It's
at
least
in
there
and
and
I
think
that
we
said
a
lot
of
things
need
to
be
said.
So
it's
a
good
article,
read
it
when
you
get
the
magazine
at
robopong,
you're
going
to
Drupal
hon
they're
handing
it
out.
So
that's
exciting.
Let's
see
anything
else,
Nate
I
know
you
did
a
ton
of
work
on
the
renaming
patch
and
you've
been
reviewing
for
requests
like
crazy
this
week.
You
want
to
add
anything
in
particular:
gosh.
C
Jeez
yeah
we've
been
making
a
ton
of
progress
like
there's,
been
all
kinds
of
activity
in
the
queue
thanks
to
thanks
to
our
drop
during
soar
on
this,
this
phone
call
you
guys
I,
say
hi,
Adam,
Matthias
and
Paul
I
know
so
the
past
a
couple
of
weeks
we've
had
these
guys
doing
an
internship
Rocking
through
the
backdrop,
Asian
q,
learning
how
to
github
and
learning
how
to
drupal
learning
had
a
backdrop.
It's
been
great
and
making
all
kinds
of
great
ports
and
movement
forward.
C
Actually
I
guess
on
the
topic
of
thanking
people
find
the
page
has
been
actively
working
on
on
getting
contacts
module
up
to
date,
moving
it
into
cmi.
It
was
one
of
the
original
authors
of
the
contact
module
actually
so
he's
back
in
our
queue,
working
on
moving
contacts,
module
into
a
fully
ported
version
for
for
backdrop,
which
were
really
excited
about
yeah.
C
Let's
see
yeah,
the
renaming
has
probably
been
the
primary
thing
that
I've
been
working
on
this
week
over
the
past
couple
of
weeks,
and
so
a
couple
of
weeks
ago
we
got
like
we
started
identifying
backdrop
separately,
so
it
had
has
its
own
constants
to
identify
its
version
number,
so
it's
1
dot
x
and
now
we've
got
the
update
numbers
reset,
so
they're
1,000,
instead
of
eight
thousand
but
they'll,
still
move
forward
from
a
Drupal
7
site.
So
in
the
Drupal
7
sites
are
in
the
7000
range
and
backdrop
will
be
in
1000
range.
C
It
will
loop
around
and
pick
up
form
where
drupal
7
left
off
and,
let's
see.
Oh,
we
also
something
else.
That's
kind
of
big
this
week
that
we
don't
have
on
the
agenda.
We
moved
settings,
dot,
PHP
and
the
files
directory
into
the
root
of
the
backdrop
installed
by
default
now.
So
that
means
that
when
you
install
a
new
backdrop
website,
the
modules
are
in
the
root.
The
themes
are
in
the
root
setting
stuff
PHP
is
in
the
room,
and
files
are
in
the
root
and
the
site's
directory
is
now
entirely
optional.
C
So
inside
of
the
state's
directory,
now,
there's
just
a
readme
and
the
site
stop
PHP
file,
but
if
you
want
to,
you
can
actually
delete
the
site's
directory
entirely.
Now,
because
that's
like
it,
the
multi
site
functionality
still
exists
and
still
there,
it's
just
that.
It's
kind
of
a
you
know.
It's
an
add-on
feature
that,
instead
of
being
forced
right
up
in
your
face,
it's
just
kind
of
there
if
you
want
to
have
a
multi-site
install,
but
since
most
Drupal
sites
are
not
multi-site.
C
B
C
At
the
top
above
the
fold,
as
you
would
say,
and
you
can
use
a
simplified
database
connection
string
and
if
you
have
the
database
connection
string,
then
you
know
you
can
skip
a
whole
bunch
of
steps
than
they
install
and
you
don't
even
need
to
write
the
setting
stuff,
PHP
and
there's
a
bunch
of
great
things
that
happen.
There's.
C
Let's
see,
and
it
was
one
other
thing:
oh
yeah,
the
the
renaming
issue
where
we're
renaming
Drupal
to
backdrop
throughout
the
code
in
all
in
all
constants
and
all
classes
and
interfaces
and
all
functions
in
all
documentation
and
in
all
strings.
So
it's
really
it's
a
massive
massive
update
that
replaces
it
touched
on
just
about
everything.
C
The
downside
of
that
is
that
it's
going
to
make
porting
are
patches
more
difficult,
because
there's
going
to
be
a
lot
more
things
that
are
different,
the
good
thing
being
that,
like
once
the
separation
happens
like
will
actually
be
able
to
identify
ourselves
as
as
a
project
that
has
a
long-term
future
rather
than
this
kind
of
schizophrenic,
like
just
temporary
thing,
for
holding
over
triple
seven
websites.
So
I
think
it's
a
really
positive
thing
and
I'm
really
glad
that
that
issue
is
all
ready
to
go.
C
Yeah
and
there's
a
backwards
compatibility,
that's
on
by
default,
so
supporting
modules
to
backdrop.
We
still
want
to
make
it
as
easy
as
possible.
I
think.
Behind
the
page,
the
contact
module
bank
noted
that
he
could
convert.
Let's
see,
I
can't
remember
which
module
it
was.
Oh,
he
converted
a
coder
module.
He
can
ready
coder
module
in
a
couple
of
minutes
and
he
was
just
like
wow.
This
is
great,
like
it's
still
so
similar
and
that's
exactly
what
we're
going
for.
The
port
of
job
should
be
like
yeah.
C
It
should
be
a
weekend
job
and
Max
rather
than
like
you
know,
a
nine-month
project
or
a
year-long
project,
which
is
what
we're
seeing
in
some
of
Drupal
8
modules,
so
so
I
think
we're
doing
really
good,
and
even
though
we're
renaming
everything,
the
conversion
process
should
still
be
really
trivial.
It's
like,
if
you
see
the
word,
Drupal,
replace
it
with
backdrop
and
that's
that's
pretty
much
Universal
yeah,
oh.
C
B
C
So
so
the
version
of
jQuery
that
we're
using,
if
I'm
not
mistaken,
is
a
1
dot
11,
which
is
the
newest
version
of
jQuery
on
the
One
X
branch,
which
still
includes
I
eat
the
legacy
support
so
I
six
through
eight,
but
in
terms
of
our
planned
browser
support
currently
we're
still
supporting
at
internet
explorer
eight,
but
not
six
or
seven.
Okay,
so
issue.