►
From YouTube: Backdrop CMS weekly 8/6
Description
Weekly check-in on development and infrastructure tasks for Backdrop CMS.
A
A
Development
impressed
for
backdrops
general
announcements.
We
still
have
free
phpstorm
licenses
for
backdrop
contribs.
So
if
you
have
a
module
femur
layout,
you
are
working
on
or
supporting.
That's.
In
the
backdrop,
controller
posit
or
you
can
come
out
to
info
@
backdrop,
CMS
org
and
we
can
send
you
a
license
key.
A
B
Sure
so
community
growth
we're
kind
of
stuck
here
at
a
total
number
of
conservators,
although
I
have
heard
from
at
least
one
more
developer,
that's
looking
at,
according
some
Drupal
modules
over
to
backdrop.
So
currently
we
have
38
total,
contributed
module
authors,
and
if
you
are
interested
in
joining
the
contributors
group,
then
we
have
a
group
on
github
for
managing
the
operations
of
a
bunch
of
thanks
called
backdrop.
And
if
you
go
to
github.com
/
backdrop,
ops,
/
trib,
then
that
is
the
location
where
we
do
a
project
reviews.
B
If
you're,
if
you
were
to
module
the
backdrop
in
what
to
get
it
into
the
backdrop,
contribute,
then
you
can
apply
there.
We
currently
have
137
total
projects
for
backdrop,
CMS
that
are
available
on
github
no
new
projects
since
last
week,
but
I
have
been
saying
to
maintenance
on
existing
projects,
which
is
fantastic,
because
it's
just
as
important
that
we
get
these
modules
maintained
in
support
of
our
long
period
of
time
as
it
is
that
we
poured
over
all
bunch
of
new
modules.
B
B
Let's
see
next
item
on
the
agenda,
we
like
to
talk
about
infrastructure
things
around
the
backdrop
project
that
sustain
the
development
tasks
and
otherwise
things
that
we're
doing,
and
so
we
talk
about.
Let's
see,
update,
checking
for
backdrop
CMS.
This
has
been
in
place
for
months
now,
still
working
just
fine,
but
one
item
on
here
that
we
talked
about
that
I
still
haven't
gotten
to
every
week.
B
It's
a
project
browser
so
we're
hoping
to
make
it
so
that,
instead
of
making
people
navigate
to
github
or
backdrop
CMS
org
to
find
modules,
themes
and
layouts
that
they
would
be
able
to
install
those
things
directly
from
the
user
interface
of
their
own
backdrop
website
and
in
fact
they
can
already
installed
it.
But
they
need
to
copy
and
paste
a
URL
from
somewhere,
probably
github
to
to
start
the
installation
process.
And
what
we
want
to
do
is
make
it
so
that
we
have
a
browsing
interface
inside
of
the
CMS.
B
So
they
can
get
those
URLs
and
then
leverage
the
existing
system
for
installing
modules
and
themes
through
a
user
interface
that
kind
of
populates
those
that
information
for
them.
So
that's
currently
held
up
on
issue
870,
which
is
right
now
an
infrastructure
task
that
that
I
need
to
set
up
a
sub
domain
for
backdrop,
CMS
org
to
be
used
explicitly
for
updates
information,
so
yeah
I'm
stuck
on
that
one
I'm
having
to
do
it
in
the.
B
Let's
see
next
item
dress
for
backdrop:
drush
a
dress
is
kind
of
stuck
here.
We
have
the
capability
of
making
drush
for
backdrop,
are
making
drush
work
with
backdrop,
because
josh
is
already
flexible
enough.
That
could
be
made
to
work
with
backdrop,
but
we
need
to
write
an
implementation
class
to
make
it
so
that
rush
knows
how
to
do
all
the
things
that
normally
does
with
Drupal
it
ships
with
the
Drupal
class.
B
That
makes
it
so
that
it
knows
how
to
do
things
like
bootstrap
and
clear,
cashiers
and
things
like
that,
and
we
can
do
that
same
thing
for
backdrop,
but
we
need
to
include
that
in
backdrop
or
as
a
contender,
ushe
will
pick
it
up
and
use
it.
So
the
functionality
is
in
drush
it's
on
our
plate
to
write
some
implementation
there
and
that's
been
stalled
out
for
a
little
while
anybody
that
gets
a
chance
to
take
a
look
at
issue
47.
B
A
So
the
last
few
weeks
we've
been
finalizing
designs
for
the
modules
themes
and
layouts
pages,
which
will
help
people
find
modules,
teams
and
layouts
more
easily
than
they
currently
can
on
github
and
last
week,
I
think
of
our
meeting.
I
went
in
and
created
the
actual
views
that
very
macho
Steve's
and
layouts.
So
if
you
want
to
sneak
peek
they're,
not
styled
yet,
but
the
listings
are
there.
A
So
if
you
go
to
/
modules,
you
can
see
all
the
modules
that
have
been
aggregating
on
our
website,
which
is
great,
if
you
click
through
to
the
module
page,
also
not
styled.
Yet
that's
like
the
default
no
display.
You
can't
see
some
useful
information
like
the
readme
file,
that's
being
pulled
in
from
github
and
the
download
link
that's
on
there,
so
I
think
we're
ready
to
go
whenever
Wes
has
time
he
can
and
start
working
on
those
which
sounds
great.
A
There
are
a
bunch
of
things
in
and
the
way
it
might
be
might
be
accessed
restricted
on
there
I'll.
We
can
undo
that.
So
you
guys
can
take
a
look
at
that
after
after
this
call,
but
there
are
a
couple
of
things
that
we
don't
have
generation
yet
for
like
getting
direct
access
to
get
information
like
the
project,
repository,
New,
York
and
other
I
think
that's.
A
There
is
a
solid
enough
to
launch
with
and
I
think
that
any
time
we
add
use
integration,
we
can
add
a
field
and
we'll
get
something
else
added
to
the
view
and
we
can
style
it,
but
I
think
having
a
listing.
There
is
good
enough
to
you
know:
let's
get
it
done
first
and
then
we'll
fix
it
later
add
more
later,
so
I'll
go
ahead
and
turn
off
the
admin
listings.
Now
that
those
are
working
enough,
that
it's
not
embarrassing,
do
you
guys
can
take
a
look
later
today
and
I?
A
Think
Wes,
you
have
a
login
to
the
society
and
you
have
the
designs.
So
we
should
be
able
to
hit
the
ground
running
on
that
and
there's
just
a
couple
of
follow-up
tests
to
getting
those
last
few
pieces
of
information
that
really
make
it
super
usable
all
of
the
opposed
to
just
sort
it
out
in
the
next
few
weeks
too.
A
So
that's
super
exciting
and
then
coming
soon,
we'll
also
start
setting
up
a
showcase,
so
that
people
who
have
build
sites
with
backdrop
can
show
them
off
we'll
set
up
a
service
listing
I,
know,
there's
a
whole
bunch
of
companies
that
have
added
their
logos
and
names
links
to
their
site
as
supporters.
We
want
them
to
be
able
to
actually
list
what
services
they
might
provide.
C
A
Your
butt
up
in
a
really
cute,
so
if
you
have
a
job
you're
looking
to
hire
someone
or
your
developer,
you're
looking
to
find
a
job
and
backdrop
and
knowing
that
there's
a
place,
you
can
go
to
find
those
listings
as
good.
We
could
also
use
that's
Janet,
a
little
revenue
which
might
offset
the
costs
of
posting
the
site,
so
hopefully
there's
a
way
that
can
all
work
out
beneficial
for
everyone.
A
That
are
backdrop
friendly,
as
we
start
having
backed
up
specific
events
as
opposed
to
drupal
events
that
back
job
talks
might
be
at
we're,
probably
going
to
need
a
place
to
go
to
find
those
backdrop,
events,
and
it
would
be
great
if,
when
that
happened,
we
had
a
website
that
they
could
plug
their
own
events
into
or
go
to
to
search
to
find
events
in
their
area,
and
so
I
think
just
setting
up
some
calendar
that
they
could
search
by
location
or
something
on
there
might
be
a
great
way
to
solve.
That
problem
is
blow.
A
The
building
a
future
right,
I'm
just
excited.
We
finally
got
the
magis
things
and
layouts
kind
of
up
one
step
at
a
time
so
back
to
back,
drop
the
product
itself.
Those
are
the
kind
of
infrastructure
tasks
that
we're
working
on
right
now.
The
product
itself
is
coming
along
really
well
backdrop.
One
point
one
point:
three:
is
our
next
bug-fix
release
that
we're
getting
ready
to
work
on?
We
don't
have
any
serious
enough
bugs
that
have
recently
been
fixed,
that
we
need
to
release
something.
A
There
haven't
been
any
security
issues
or
anything
like
that
recently
on
Drupal
that
we
need
to
squish
in
on,
but
we
will
get
that
release
out
as
soon
as
we
find
something
important
enough
that
we
feel
like
we
need
to
cut
it,
but
other
things
we're
working
on
that
are
more
expensive,
more
expensive,
more
exciting,
also
more
expensive
are
the
features
that
we're
planning
on
putting
in
1.2.
So
in
1.2,
a
most
exciting
thing
we've
been
working
on
is
the
rich
text
editor
and
Nate.
B
This
is
really
exciting.
Anybody,
that's
been
fine,
the
queue
be
pretty.
You
know
we
merge
day,
so
we
have
WYSIWYG
in
Cornell.
Ckeditor
was
merged
in
this
week,
which
is
really
exciting.
That's
issue
101.
If
you'd
like
to
see
where
everything
is
currently
at
there
or
you
can
just
pull
down
the
latest
one
dot.
X
branch
and
check
that
out
the
city.
Editor
module
is
not
turned
on.
If
you
do
enough
date
right
now,
it's
just
it's
just
there.
B
So
if
you're
upgrading
an
existing
site-
and
this
will
happen-
I
think
for
the
1.1
to
1.2
release.
If
you
upgrade,
everything
will
stay
exactly
the
way
it
is,
unless
you
explicitly
turn
on
the
news
together
to
module,
but
of
course,
we're
going
to
ship
it
out
of
the
box
turned
on
this
follow-up
issue
to
to
work
on
that.
B
1087
1087
has
a
number
of
WYSIWYG
tasks
that
we
need
to
do
to
follow
up,
including
enabling
out-of-the-box
doing
image
uploading
through
the
image
dialog
some
work
on
the
third
pages
and
the
way
filter
tips
work.
But
then
we
will
be
in
a
very,
very
good
place.
Actually,
this
week,
I've
been
working
on
the
image
uploading
and
the
image
uploading
is
coming
along.
B
Just
fantastic
I
already
have
it
on
parity
with
with
Drupal
8
according
over
the
existing
patch
was
a
piece
of
cake
which
makes
it
so
that
you
can
upload
an
image
through
a
dialogue.
But
there
are
some
deficiencies
in
the
approach
and
I'm
trying
to
to
fix
them
out
make
something
a
little
bit
more
flexible
right.
Now,
it's
either
one
or
the
other.
B
Either
you
can
use
a
URL
or
you
can
upload
a
file,
and
if
you
turn
on
one,
then
it
disables
the
other
ability
which
is
kind
of
obnoxious,
because
I
think
that
people
want
to
use
local
files
that
want
to
use
remote
files
like
it's
a
common
or
files
that
are
in
like
the
themes
directory,
there's
all
kinds
of
use
cases
you'd
need
for
for
supporting
both.
So
that's
coming
along
great
and
I'm
feeling
really
really
great
out
getting
that
really
well
done
for
the
release
next
month.
B
That's
all
I've
got
a
date
fields.
That's
the
next
item.
So,
besides
WYSIWYG
or
CJ
editor
and
we're
trying
to
do
some
expansion
of
the
fields
that
we
ship
out
of
the
box,
including
date
link
and
email
and
date,
module,
looks
like
it's
coming
along,
really
well
Graham
72s,
taking
the
lead
on
that
and
he's
doing
a
great
job
working
on
making
a
core
ready
version
of
date,
module
and
I
think
that
that's
actually
come
along
really
pretty
well
I
think
he
mostly
need
to
review
right
now.
B
Functionality
wise
as
far
as
I've,
been
able
to
find
that
he's
really
been
pushing
that
forward
so
solo.
If
anybody
has
chance
to
take
a
look
at
issue,
478
issue
478
is
that
ad
date
core
give
the
current
code
review
and
try
to
help
gram
understand
what
needs
to
be
done
left
there.
Then
that
would
be
the
most
useful
thing
we
can
do
to
push
that
one
forward.
B
C
B
Well,
yeah
I
think
I.
Think
that
looks
great.
The
function
on
yeah
just
touch
it
on
and
it
all
worked.
Fantastic,
there's
yeah
some
stuff
that
needs
to
be
removed.
Some
cruft
that
doesn't
apply
to
us
stuff
like
devel
and
my
great
integration
should
be
moved
to
their
respective
modules
instead
of
being
in
in
court.
B
And
the
only
thing
I'd
like
to
see-
and
this
doesn't
have
to
be
before-
release
is
cleaning
up
the
user
interface
for
configuring.
The
link,
because
it's
a
little
overwhelming
like
there's
just
so
many
options
and
they,
but
we
discussed
in
the
issue
that
we
don't
plan
on
removing
any
functionality,
because
that
would
make
compatibility
really
hard
to
maintain.
B
Okay,
let's
see,
and
the
last
one
is
the
last
module
we'd
like
to
include
in
the
next
release-
is
email
and
email
field.
This
issue
has
not
been
really
given
any
attention.
There's
already
a
contribute
of
email,
module
and
and
email
is
actually
a
really
simple
module
by
comparison
with
with
all
the
other
ones,
and
so,
if
anybody's
interested
in
taking
that
on,
all
we've
actually
been
having
a
hard
time
filling
up
your
time.
If
you
get
a
chance,
maybe
that
would
be
a
good,
a
nice
hefty
task.
B
Contribut
trimming
down
a
little
bit
and
then
filing
a
pull
request
to
just
put
it
in
core.
That's
pretty
much
yeah,
that's
pretty
much
the
way
it
goes.
It's
not
actually
very
difficult.
You
can
take
a
look
at
the
link
and
eight
modules,
both
of
which
are
at
pull
request
status
right
now.
It's
basically
take
the
module,
put
it
in
the
core
and
then
file
for
request.
That's
that's
the
starting
point
of
it.
B
Okay
and
that's!
That's
all.
We've
got
there's
a
bunch
of
other
stuff,
we'd,
really
that
are
nice
to
haves
in
the
1.2
release,
but
none
of
them
are
critical,
but
things
like
layouts
there's
a
huge
number
of
follow-ups
for
layouts
to
make
layouts
more
powerful
out
of
the
box
and
some
things
around
making
our
are
you
eyes,
more
responsive
Darius
filed
a
great
issue
about
making
the
menus,
responsive
or
having
some
options
to
like
come
with
a
hamburger
menu
or
something
like
that
and
I
think
that
that
would
be.
B
You
know
another
great
thing
for
us
to
have,
but
all
of
all
of
those
things
we've
got
priorities
and
then
all
of
those
things
if
they
happen,
then
that
would
be
great,
but
nothing
even
the
priority
issues
will
hold
up
the
release
that
will
happen
next
month.
So
anything
that's
ready,
we'll
be
in
and
anything
that's
not
we'll.
Just
have
to
wait
until
the
next
release.
B
A
Do
you
want
to
take
it
back
over
sure,
and
so
in
terms
of
backdrop,
the
product
I
think
we're
looking
really
good.
There's
a
couple
of
other
little
things.
We
work
on
all
the
time
like
user
experience,
issues
and
developer
experience
issues
and
those
are
tagged
with
special
square
bracket
indicators
on
github
and
I.
Think
it's
really
important.
A
Then
we
keep
working
on
those
because
if
we
want
to
appeal
to
a
wordpress
market
and
it's
gotta
be
easier
to
use
and
easier
to
write
code
for
special,
especially
for
an
end
code
that
they've
got
a
huge
front,
end
developer
community
and
we've
gotta
make
it
easy
for
people
to
get
into
writing
themes
for
a
backdrop
as
well,
so
I'm
looking
forward
to
making
that
process
easier
and
easier
for
people
going
forward.
So
we'll
just
keep
an
eye
on
those
issues
as
well.
A
Good
week
after
this
meeting,
we
have
a
little
sprint
where
we
get
together
in
IRC,
and
we
all
talk
about
things
and
work
on
things
together.
But
IRC
is
a
very
developer,
focused
environment.
It's
working
really
well
for
us
right
now,
because
we're
all
mostly
developers-
and
we
have
no
issue
communicating
in
that
medium.
A
But
there
happened
a
bunch
of
issues
brought
up
on
reddit
and
on
github
about
trying
to
build
more
community
around
back
job,
maybe
in
ways
that
are
more
on
focused
to
the
new
people
that
we
would
like
to
attract
a
backdrop,
but
not
necessarily
us
old
groaning
developer
types.
So
I,
don't
know
that
this
is
necessarily
worth
talking
about
right
now.
But
I
did
want
to
mention
to
all
of
you
to
put
your
thinking,
caps
on
and
try
and
think
about
things
we
can
do
to
help
foster
community
around
back
job.
A
Now
that
we've
gotten
to
a
point
where
the
code
is
looking
really
good
and
we're
on
track
for
our
next
release
and
I.
Think
the
big
thing
people
are
going
to
be
comparing
when
they're
looking
at
deciding
whether
they
want
to
move
to
Drupal
8
or
backdrop
is
the
community
around
the
software
and
Drupal
has
a
really
strong
community
or
has
historically
had
a
really
strong
community,
and
that's
going
to
look
really
attractive
to
people
and
backdrop.
Is
new
and
I
think
that
that's
something
that
people
are
going
to
be
worried
about
like?
A
Where
does
our
community
meet?
How
do
we
talk?
How
do
we
function
and
I
think
it
would
be
good
to
start
putting
our
little
brains
together
and
trying
to
figure
out
how
to
foster
more
community
I
think
these
meetings
are
really
useful,
I
think
getting
together
a
Drupal
events
and
having
our
own
backdrop,
events
is
gonna,
really
help
that
but
I
think.
A
Remember
online
community
we
have
github,
we
have
a
reddit
I'm,
not
sure,
that's
enough,
so
I
think
just
start
thinking
about
it
and
well
we'll
open
up
some
issues
next
week
and
start
having
some
conversations
around
what
we
might
do
and
how
we
can
measure
success
in
those
areas.
So
that's
kind
of
what
I'm
thinking
about
right
now,
upcoming
events
we've
had
a
whole
bunch
of
really
fantastic
past
events.
Last
weekend
there
were
three
Drupal
friendly
events
in
the
same
weekend,
which
is
great
west
of
his
talk,
went
really
well,
which
is
great.
A
I
talked
to
Alex
earlier
this
week.
He
said
his
talk,
one
really
well
down
in
Costa
Rica,
which
is
really
great,
I,
think
you
know
things
are
rolling
forward
at
extreme
speed,
which
is
fantastic
for
everyone
involved
upcoming.
At
the
end
of
this
month,
we
have
drupalcamp
LA,
which
is
August
twenty-ninth
to
30th.
We
have
nerd
summit
in
September
and
we
have
more
events
after
that
and
the
biggest
event
honor
horizon,
at
least
in
terms
of
backdrop.
A
For
that,
so,
if
you're
not
planning
on
coming
too
bad
camped
on
think
about
coming
to
Van
Camp,
there's
a
scholarship
program,
if
you're
active
contributor
in
any
open
source
project,
that
would
be
a
good
application
submission
criteria
and
we
can
we
can
try
and
help
get
you
out,
and
you
know,
put
you
to
work
in
terms
of
the
afternoon.
I
think
we
should
just
do
workshops
and
I
think
that
that
should
be
driven
by
whoever
comes
to
the
summit.
A
So
if
we
have
a
bunch
of
core
developers,
we
can
do
some
core
development
sprint
stuff.
But
if
we
don't,
if
we
have
a
bunch
of
introductory
people,
we
should
maybe
do
Q
in
any
sessions
or
talk
specifically
about
concerns
or
use
cases
that
those
people
have
about
backdrop
in
their
environment
or
some
particular
module
that
they
need
and
I'm
not
sure.
If
it's
going
to
exist,
maybe
we
can
do
is
fringe
and
pouring
the
module
or
just
stuff
that
I
think
is
relevant
and
I.
Think
it's
going
to
be
an
event.
A
I'm
excited
to
have
her
first
we're
going
to
have
t-shirts
with
dragons
on
them,
so
everybody
get
really
excited
about
the
t-shirts.
Oh
they're
coming
come
be
here
in
October,
so
definitely
hands
that
are
heading
out
to
bag.
Him
I
think
it's
going
to
be
really
exciting
event.
This
year,
okay,
I
think
we
want
to
talk
about
definitely
covered
a
lot
of
new
stuff
this
time,
but
are
there
any
questions
or
thoughts
or
anything?
We
should
talk
about
today?
It's
not
on
the
agenda.
B
A
A
The
glue
that
dedica,
what
is
the
preferred
way
to
do
similar
things
like
responsive
menus
and
modal's,
which
we
did
in
Drupal
7?
How
do
you
do
that
in
backdrop
and
other
issues
that
people
are
going
to
come
up
with
with
a
drupal
solution?
That
has
a
different
solution
and
backdrop,
and
can
we
either
document
that
solution
or
decide
in
some
cases
on
what
that
should
be
and
I
think
that,
as
you
know,
people
start
using
backed
up
for
different
things,
they're
going
to
be
running
into
lots
of
similar
questions
like
this.
A
World
is
aunt
covers
all
of
the
bases
that
are
necessary
and
I.
Think
that
is
a
great
idea.
I
think
we
should
be
doing
that
already.
I
think
we
have
a
limited
number
of
hands
on
deck,
which
is
why
it
hasn't
happened
yet.
I
also
think
that
will
start
to
happen
when
more
and
more
people
start
building
sites
with
that
job.
Right
now
we
have.
A
We
have
a
lot
of
good
stuff
going
on
in
core,
but
we
don't
have
as
many
sites
running
back
drop
by
something
like
drupal
does
and
with
every
site
that
needs
to
solve
a
specific
goal.
They're
going
to
do
so
in
contribute
rebel,
get
stronger.
Our
first
year,
which
has
been
you
know,
some
about
September
September
in
September,
has
been
about
making
core
strong
enough.
That
people
will
look
at
the
software
and
say
I
choose
the
software
because
of
the
features
you're
right
that
this
effort
doesn't
stand
on
its
own.
A
A
Looking
at
me
see
if
we
can
pick
some
easy
wins
so
that
we
don't
start
standing
still
in
terms
of
progress
and
core
fix
some
small
things
that
will
get
us.
You
know
closer
to
being
feature
comparable
with
Drupal
8
and
put
them
in
quickly
and
easily
so
that
we
can
spend
more
of
that
time.
Also
working
on
contribs,
stop
I
know,
I've
got
a
big
client
project
coming
up
in
backdrop,
that
is
in
the
design
phase
right
now
and
I
cannot
wait
to
start
working
on
it.
A
That's
gonna
make
me
spend
a
bunch
more
of
my
time
in
control
and
I
have
a
feeling
similar
things
are
happening
for
a
bunch
of
other
people
to
like,
as
you
start,
working
on
sites
using
backtrack.
You
start
spending
more
of
your
time
in
kinship
because
those
sites
will
have
real
world
needs,
and
this
will
get
better
and
yeah.
We're
also
going
to
need
to
spend
some
time
doing
migrations
right
as
people
are
deciding
to
go
from
seven
to
get
backed
up
or
even
from
six
to
backdrop,
and
that's
going
to
be
some
time.
A
It's
not
there
too.
So
I
like
the
idea
that
we
should
stop
and
evaluate
what's
missing
from
kindred.
I'm
not
sure
we
should
stand
still
in
core
in
order
to
do
that.
I
think
we
could
decrease
the
scope
of
what
we're
doing
in
Coeur
de
Bay
a
smaller
in
terms
of
the
amount
of
changes
that
are
going
in,
but
I
don't
think
we
should
stand
still
entirely
or
postpone
1.4
for
three
months,
but
yeah.
Definitely
good
good
ideas
and
I
think
we
should
figure
out
how
we
can
do
both.
A
A
Multiple
people
are
thinking
about
importing
from
WordPress,
but
what
is
the
best
way
for
back
job
yeah
I?
Don't
know
there
is
a
wordpress
importing
module
from
Drupal
that
we
could
try
import
that
works
for
drupal,
7
and
feeds
is
also
good
if
you're
just
trying
to
get
data
I
we're
definitely
going
to
need
beads
in
backdrop
land,
and
we
also
could
port
migrate.
There's
a
my
great
for
Drupal
7.
There
are
lots
of
opportunities,
different
options,
I
would
say
we'll
just
have
to
try
them.
A
A
lot
of
these
questions
are
unanswered
because
nobody's
done
them
before
we're
starting
to
venture
into
new
territory,
and
I
think
that
having
the
questions
is
good
coming
up
with
answers,
even
if
they're
wrong
answers
is
better
right.
Try
something
in
me.
Like
hey
everybody
know
whatever
the
right.
This
stuff
will
probably
be
new
to
right,
we're
going
to
come
up
with
a
problem
that
has
a
drupal
solution
that
we
don't
like,
and
we're
going
to
do
something
different.