►
From YouTube: Backdrop Weekly 2/27
Description
Backdrop CMS
A
Or
like
this
being
broadcast,
you
can
turn
off
your
camera.
Okay,
where
you
are
on
air
all
right,
happy,
Thursday,
everybody!
It
is
backdrop
day.
We
are
very
excited
about
backed
up
day
here
in
the
gen
Lampton,
quick
sketch
household.
We
had
a
lot
of
great
stuff
happen
in
the
last
week,
which
I
think
is
stupendous,
and
we
had
a
bunch
of
really
great
meetings
with
a
bunch
of
people
to
talk
about
backdrop.
We
kind
of
figured
out
like
watch
what
we
should
be
focused
on.
A
A
So
for
those
of
you
who
are
not
aware,
yet
we
are
building
backdrop
CMS,
which
is
going
to
be
a
comprehensive
CMS,
specifically
for
nonprofits
education,
xand
small
to
medium-sized
businesses,
we're
going
to
focus
on
making
the
people
who
need
it
the
most
the
best
possible
tool
we
can
give
them,
which
I
think
is
kind
of
to
the
heart
of.
Why
we're
here
and
we're
going
to
build
a
system
that
has
features
that
are
a
lot
like
those
interpolate,
but
we're
going
to
build
them
on
a
architecture.
A
That's
really
similar
to
triple
seven,
and
we
feel
that
there's
a
cost
that
comes
with
change
and
anyone
who's
working
on
Drupal,
7.
Well,
we'll
have
a
choice
when
Jubilee
comes
out.
If
they
want
to
go
the
change
route
or
if
they
want
to
stay
sane,
and
we
want
to
give
them
a
place
to
go
to
stay
to
say
so.
Working
on
and
we've
got
a
bunch
of
things
we
need
to
do
to
our
new
CMS,
including
fixing
all
of
the
books
that
are
currently
in
Drupal
7
and
by
all
of
the
books.
A
We
also
want
to
do
two
other
big
things
that
will
help
our
target
audience,
in
particular
simplification
of
existing
system,
so
where
things
are
already
getting
a
little
bit
too
complicated,
we
want
to
bring
them
back
down
to
reasonable
levels.
One
of
the
places
where
that's
getting
will
have
controls
the
theme
layer
we'll
talk
about
that
a
little
bit
later,
but
there
are
also
other
systems
in
interval
where,
if
it's
possible
to
improve
things
to
simplify
things
without
changing
the
api's
too
much,
we
want
to
focus
on
that
as
well.
A
So
if
you
have
through
pool
seven
modules,
you
need
to
pour
it
wouldn't
be
too
hard
to
get
them
from
Drupal
7
to
backdrop,
if
there's
new
features
there,
what
we
will
take
advantage
of
them,
but
it
won't
require
changing
the
way
you
think
or
the
stuff
that
you
know
already
about
working
in
in
triple
seven
land,
so
yeah
we're
going
to
keep
the
API
is
the
same.
That's
the
idea!
Less
change
is
easier
on
the
community
and
ecosystem
around
the
software.
A
Our
timeline
is
to
get
back
drop
out
this
summer,
we're
thinking
a
June
or
July.
We've
got
a
couple
of
major
things
that
we
want
to
get
done
before,
release
and
a
bunch
of
minor
things
that
we
can
continue
to
improve
a
bruh
even
after
releases
come
out,
we'd
like
to
do
semantic
versioning
and
releases
very
often
so
we'll
have
a
major
release
as
one
point
0
and
then
we'll
do
a
little
tiny
version,
changes
that
can
also
include
new
features.
So
we
don't
have
to
get
all
of
our
new
features
in
web
backdrop
shifts.
A
We
can
add
them
after
the
fact,
which
I
think
will
be
really
important
for
our
long-term
feature,
set
just
keep
you'll
be
able
to
keep
adding
stuff
whenever
we
get
something
ready.
So
in
terms
of
our
progress,
we
have
a
bunch
of
meta
issues
of
all
of
the
things
that
Drupal
8
has
done,
and
we
need
to
kind
of
look
at
those
and
figure
out
like
do
we
want
to
do
these
things
in
backdrop
and
it's
so.
How
do
we
want
to
do
them?
A
So
we've
got
back
ports
of
things
that
have
happened
in
interpolate
that
we
should
consider
for
inclusion,
whether
we
actually
decide
to
do
it
or
not.
It
will
be
up
to
us,
but
we
need
to
at
least
look
at
the
things
and
make
sure
that
there
aren't
things
that
we
need
desperately
need
to
get
in.
We
also
have
a
massive
list
of
things
that
have
changed
in
Drupal
7
we
forked
Drupal
7
from
713
I,
believe
where
we've
worked.
A
So
if
we
don't
have
what
seven
has
we're
actually
stuff
behind,
so
Andy
has
been
doing
a
bunch
of
work
on
going
through
all
these
commits
that
been
made
to
Drupal
7
importing
them
over
to
backdrop
and
we've
had
a
couple
that
have
been
a
little
bit.
Sticky
we've
had
a
couple
that
we
looked
at
and
said
that's
kind
of
crazy.
A
Why
did
they
do
it
that
way,
we're
going
to
do
a
little
differently
in
backdrop,
but
for
the
most
part
those
issues
have
been
coming
along
really
well,
and
we
have
three
giant
meta
issues.
The
first
one
we
have
is
issue
135
and
it
looks
like
we
have
only
a
few
left.
We've
got
213
of
those
patches
committed
out
of
222.
We've
got
a
couple
that
are
failing,
pull
requests,
but
every
single
one
of
them
has
been
applied
and
there
is
a
fork
West
with
patch
in
it.
A
So
I
think
that's
huge
progress,
which
is
great
and
we
just
need
to
figure
out
the
failures
to
get
those
cleaned
out.
The
next
issue
is
the
meta
issue
134,
and
we
have
127
of
those
179
patches
already
in
which
is
great.
Most
of
that
is
due
to
Andy,
with
his
excellent
catch,
applying
experience
which
is
great,
and
so
that
was
only
if
you
left
there
today,
I'd
like
to
spend
some
time
focusing
on
the
sticky
ones.
There
see
again.
If
there
are
things
we
need.
A
Hopefully
there
will
be
a
couple
that
we
can
just
say:
oh
this
was
already
committed
to
our
project,
so
we
don't
need
it.
So
we
don't
worry
about
the
patch
and
then
there
will
be
some
other
ones.
That,
of
course,
needs
a
little
bit
of
work,
but
yeah
that'll
be
good,
and
then
we
have
our
last
issue.
135,
where
we
have.
It
looks
like
11
issues
committed
since
last
week
we
still
got
a
or
sorry
132.
A
A
A
We've
been
holding
off
on,
like
renaming
all
the
functions
that
used
to
start
with
drupal
we're
thinking
right
now
that,
instead
of
renaming
them
to
start
with
backdrop,
we'll
just
remove
the
drupal
prefix
and
we'll
have
like
a
list
for
developers
that
are
like
these
are
the
functions
that
you
should
not
collide
with
and
it
won't
be.
It
won't
be
too
big
list,
but
it
you
know
it's
there's
right
now.
A
Anyone
has
any
infections,
Jeff
an
IRC
and
tell
us
why
be
odd.
There
might
be
some
some
function
that
we
still
come
across
and
we're
looking
at
that
were
like
oh
yeah.
It
would
be
bad
to
remove
that
and
then
we'll
know
why.
But
for
now
it
just
seems
like,
let's
be
consistent,
sounds
like
a
good
idea,
so
I
thought
ok.
A
So
we
also
last
week,
I
mentioned
that
we
had
all
these
meta
issues
for
all
of
the
patches
that
went
into
Drupal,
but
there's
also
a
bunch
of
other
work
that
goes
into
Drupal,
that
isn't
necessarily
in
a
patch,
in
particular,
security
updates
right.
Those
are
things
that
we
don't
necessarily
want
people
to
be
able
to
go
and
find
the
code
and
exploit.
A
So
there
are
public
issues
on
drupal.org
their
private
issues,
but
the
code
still
does
get
committed,
and
so
we
need
to
make
sure
that
in
backdrop,
we
have
all
the
same
solutions.
If
it's
not
exactly
the
same
code,
we've
solved
all
the
bugs
that
were
stopped
by
those
problems
and
so
I
created
in
that
issue.
A
Last
week,
that
pointed
out
to
all
of
the
issues
that
we've
been
notified
about
in
all
the
months
I
could
find
in
in
drupal's
history
that
also
applied
to
backdrop
and
Nate
found
solutions
to
all
of
them,
except
for
one.
So
there
were
seven
security
issues,
six
fixes
are
in
and
the
last
one
is
one
that
we
actually
created
an
issue
about
the
very
beginning.
A
It's
the
security
issue
that
puts
the
query
string
at
the
end
of
image
tags,
which
breaks
a
lot
of
contribs,
and
so
we
were
trying
to
see
if
there
was
a
different
way.
We
could
solve
that
problem
that
wouldn't
involve
breaking,
can
trim
and
we've
come
up
with
a
couple
of
solutions.
None
of
them
are
perfect,
so
we're
still
thinking
on
it.
A
So
we're
working
on
that
one,
but
six
out
of
seven
or
fixed,
which
I
think
is
great,
so
major
things
that
we're
working
on
in
backdrop
include
config
management.
This
is
kind
of
the
thing
that
everybody
who
has
been
working
with
Drupal
7
to
date
has
been
really
wanting.
We've
been
using
features,
we've
been
doing
workarounds
that
don't
involve
using
features,
and
we
want
to
be
able
to
deploy
configuration
changes
and
so
we're
going
to
get
config
management
into
backdrop.
We
already
have
the
core
committed.
A
There
are
a
couple
of
subsystems
that
need
to
be
converted
and
then
there's
just
a
bunch
of
variables
that
need
to
be
moved
over
a
bunch
of
other
stuff.
We
just
have
to
make
sure
is
writing
to
files
instead
of
to
the
database,
and
that
will
be
usable
and
functional
in
in
backdrop,
come
June
July,
which
is
great.
A
If
you're
itching
to
see
how
that
will
go,
it
does
work
significantly
differently
from
Drupal
8,
but
I
think
that
the
way
that
we've
got
it
makes
sense
for
our
project,
so
I'm
really
excited
to
to
be
playing
with
that
and
then
in
the
wild.
We're
also
working
on
views
in
core
so
views,
obviously
the
number
one
most
downloaded
module
and
drupal.org
it's
something
that
sets
drupal
apart
from
all
of
the
other
software.
That's
out
there
in
terms
of
CMS,
is
like
the
WordPress
doesn't
have
anything
like
views.
It's
a
really
powerful
tool
everybody's.
A
A
So
we
have
useful
collaborations
in,
but
we
don't
necessarily
have
full
operations
for
everything
that
we
had
in
core
in
yet
so
as
we
do,
these
conversions
will
need
to
make
sure
that
all
the
pieces
get
added
as
well,
and
so
the
next
thing
is
this
blocks
and
layouts
idea.
We
did
a
bunch
of
usability
testing
a
couple
of
years
ago,
and
one
of
the
things
we
noticed
is
that
people
were
expecting
to
have
something
like
panels
in
court.
A
So
I
went
on
this
like
hey,
we
need
panels
in
corporate
and
then,
as
your
blade
came
under
way,
people
started
thinking
about.
Oh,
we
should
really
revamp
the
block
system.
It
hasn't
got
any
attention
yet
and
there
was
the
whole
blocks
and
layouts
initiative
that
get
started
in
Drupal.
8
I
got
sidetracked
by
all
the
other
complicated
things
that
weren't
necessary
in
order
to
make
it
happen,
and
it
isn't
really
happening
in
Drupal
8.
A
So
we
thought
one
thing
that
might
help
set
us
apart
from
dribbly
was
to
build
a
really
great
blocks
and
layout
system.
Do
something
like
panels
light
in
core
a
way
to
put
things
on
the
page.
That
is
a
little
bit
more
intuitive,
more
flexible
than
what
Drupal
7
does
currently
and
if
we
can
establish
this
as
a
you
know,
this
is
a
killer
feature.
This
is
something
that
will
set
us
apart.
A
I
think
it'll
be
really
important
for
our
brand
it'll
give
people
the
incentive
to
use
backdrop
/
continuing
to
both
sites
in
Drupal,
7
and
I.
Think
that
we
can
do
it
really
well
with
our
expertise
in
panels
and
knowing
how
to
write
user
interfaces
that
make
sense
and
just
a
lot
of
frustration
with
my.
A
It
will
be
really
big
in
terms
of
features
at
all.
It'll
be
really
awesome.
We
talked
to
a
bunch
of
people
over
the
last
week
or
like
yeah.
You
need
a
killer
feature.
This
is
going
to
be
our
killer
feature
yay.
So
we
had
a
bunch
of
ideas.
We
had
a
bunch
of
conversations
with
certain
people,
usability
experts
etc
about
how
to
do
this,
but
we
hadn't
actually
started
writing
any
code
until
this
week
and
so
Nate.
A
C
Well,
that
issue
86
has
some
of
the
ideas
like
from
the
UI
perspective,
how
we're
planning
on
handling
it,
which
is
very
similar
to
an
idea
that
bullion
came
up
with
a
long
time
ago.
So
his
video
is
basically
how
we're
planning
on
I'm
handling
it
from
the
UI
perspective,
but
code
wise
with
what
we
started
working
on
this
week.
We're
basically
trying
to
tackle
this
new
module
layout
module
as
as
a
porting
job
of
panels.
C
So
reusing
all
of
the
same
concepts
of
panels,
things
like
selection
criteria
and
what
they
call
content
types
we'll
have
to
do
some
rejiggering
on
the
terminology
too,
of
course,
because
just
call
box,
yeah
yeah.
Well
it
looks
yeah
what
what
panels
calls
content
types
more
recently,
it
calls
them
panel
pains
in
the
interface
but
we'll
probably
be
calling
them
just
blocks.
Yeah,
because
we'll
be
like
consolidating
the
terminal
here
and
all
pages
within
all
backdrop
will
be
layout
module
driven.
C
There
won't
be
a
block
system
outside
of
layouts,
so
you
could
still
have
blocks
and
in
theory
and
use
them
in
something
else
other
than
then
within
a
layout.
But
as
far
as
everybody
is
concerned
for
the
out
of
box
experience,
regions
will
no
longer
have
or
themes
will
no
longer
have
regions.
All
layouts
will
be
controlled
by
layout
module,
so
layouts
get
shared
between
themes.
C
A
Simplified
user
interface,
so
panels
provides
a
lot
of
crazy
stuff.
Page
manager
provides
a
lot
of
crazy
stuff
we're
going
to
try
and
remove
as
much
as
we
can
we're
not
going
to
include
like
styles,
we're
not
going
to
include
relationships.
There's
a
lot
of
stuff
we're
gonna
say
this
is
freaking
trib.
All
we
want
to
do
is
to
have
a
replacement
for
blocks
right
interval
or
in
back
shop
yep
right
in
court
yeah.
So
we're.
C
But
all
of
the
individual
plugins
that
panels
provides,
fortunately
very
modular,
so
we're
basically
going
to
be
attempting
to
reuse
all
of
the
individual
plugins
for
ya.
For
argument
handling
for
the
pains
for
the
contexts,
selection
criteria
trying
to
reuse
those
pretty
much
wholesale
with
terminology
updates,
which
is
no
small
task,
but
at
least
it
gives
us
a
pretty
clear
way
forward:
architectural
II
that
we're
not
reinventing
something
we're
basically
treating
this
like
as
a
porting
task.
So
porting
panels
to
backdrop
essentially
so
should
be
exciting.
A
Alright,
so
I'm
really
excited
that
we're
getting
some
momentum
on
that
I
think
it'll
it'll
be
really
fun
to
work
on
it
in
a
system.
That's
you
know,
kind
of
cohesive
from
the
beginning.
So
hopefully
we
can
take
what
we
know
about
panels
and
keep
it
the
same
and
simplified
and
we'll
have
an
awesome
tool.
A
We've
got
a
couple
of
other
minor
things
we
want
to
work
on
to
these
are
things
that
are
really
important
for
bath
Japan
darkness,
major
as
something
like
TMI
or
blocks,
and
layouts
minor
projects
include
user
experience.
Improvements
like
adding
a
WYSIWYG
editor
for
replacing
a
dialogue
system,
getting
a
better
tool,
bar
updating
the
node,
add
or
edit
form,
and
adding
a
new
administration
theme
there's
a
bunch
of
other
little
stuff
that
will
come
up.
A
You
know
one
issue
at
a
time
that
we'll
be
able
to
get
in
any
of
those
things
I
think
could
probably
come
after
the
initial
release.
They
aren't
blockers,
but
I
think
it
would
be
great
if
we
could
get
it.
Was
you
again
a
during
poor
before
we
release
that'll
be
kind
of
important,
especially
for
our
target
audience.
A
They're
open
a
long
one
they're,
not
HTML
writers,
natively,
but
yeah,
there's
definitely
stuff
that
you
know
we
can
add
after
the
initial
release,
like
here's
a
new
feature,
three
months
later,
here's
another
new
nature,
here's
another
one,
so
I
think
that
there's
definitely
room
for
all
this
stuff.
But
if
we
have
anyone
wants
to
work
on
it
now
we
definitely
could
do
it
now
also
be
advantageous
to
us
and
then
there's,
of
course,
the
team
system
cleanup,
which
the
reason
I'm
particularly
passionate
about
it,
is
because
I
feel
like
we're.
A
People
first
touch
code
for
any
system
is
usually
in
the
theme
layer,
because
the
theme
layer
generates
HTML
and
CSS,
and
that
is
a
language
of
web
that
is
universal
to
every
platform,
regardless
of
whether
you're
working
in
rails
or
writing.
Java.
At
some
point,
if
you
have
a
web
application,
it's
got:
output,
HTML
and
CSS.
Everybody
understands
how
that
works
and
when
you
start
with
a
new
system,
you
go
to
the
lowest
common
denominator
and
so
I
think
our
theme
layer
needs
to
be
approachable
and
understandable
and
in
interval
7,
it's
really
not.
A
It's
really
complicated
and
so
I
think
that
there's
a
lot
of
work,
we
can
do
in
consolidation
in
cleanup
of
the
way
that
we
approach
template
files
in
just
you
know
deciding
what
logic
is
okay
to
put
where,
for
some
reason,
historically,
Drupal
hasn't
wanted
to
put
loops
in
any
template
file
and
I
think
that's
to
the
detriment
of
front
of
developers.
They
understand
loops,
just
kind
of
setting,
setting
the
rules
and
doing
some
cleanup.
A
A
So
again,
this
is
dependent
on
getting
all
of
our
Drupal
7
cross
ports
in
as
well
as
figuring
out
how
our
new
blocks
and
layout
system
is
going
to
work
I'm,
getting
some
templates
for
basic
layouts
going
and
then
making
sure
that
everything
stays
consistent
throughout,
or
at
least
as
much
as
I
can
maybe
more
consistent
than
it
is
now
will
be
so
there's
also
other
stuff
other
than
backdrop.
The
project
that
we're
working
on
we've
got
a
website.
That's
in
the
works.
A
We
have
update
server
that
we're
going
to
need
so
that
people
who
are
running
back
drop
sites
can
tell
when
their
stuff
needs
to
be
updated.
We
have
an
official
github
service
that
needs
to
be
created
so
that
people
who
create
modules
and
themes
for
backdrop
can
register
them
as
official
modules
and
themes.
Then
they
can
be
aggregated
onto
our
own
website
and
give
people
a
central
place
to
search
for
them
and,
most
importantly
right
now,
I
think,
is
our
api
site.
A
We've
got
some
significant
api
changes
that
need
to
be
documented
and
change
requests,
and
we
also
need
to
give
people
place
to
just
go
and
look
at
our
code,
especially
if
they're
curious,
like
oh
and
wonder.
What's
going
on
in
backdrop,
we
need
to
have
a
place
that
they
can
actually
see
that
via
the
web.
That
doesn't
involve
cloning.
The
repo
people
will
do
that
anyway,
but
I
think
having
a
place
for
people
to
refer
to
is
going
to
be
super
important.
So
we
need
to
get
that
up
as
well.
A
So
I
think
it's
important
that
we
are
able
to
kind
of
state
where
we're
coming
from
what
we're
working
for
what
our
goals
are,
how
our
goals
may
differ
from
what
they
think
our
goal.
Sorry,
I'm
just
kind
of
set
the
record
straight
paint
the
right
picture
and
we're
going
to
be
doing
that
in
conferences
at
tocs.
We're
going
to
be
doing
that
in
you
know,
blog
posts
and
writing.
We've
got
an
article
coming
out
on
drupal
watchdog
this
summer.
A
That
I
think
will
help
kind
of
tell
the
right
story
that
we're
going
to
be
working
on
for
over
the
next
few
weeks
and
yeah.
Anything
anyone
can
recommend
like
if
you
want
us
on
a
podcast
will
come
talk
about
stuff.
We've
done
a
bunch
of
those
already,
but
would
be
eager
to
do
it
again
closer
to
product
launch,
but
yeah.
We
just
kind
of
want
to
make
sure
that
the
right
messages
out
there
we're
not
doing
this
from
a
place
of
anger.
Doing
this
from
a
place
of
love
right.
A
This
is
the
software
we've
given
our
lives
to
for
the
last.
However,
many
years
and
we're
committed
to
continuing
to
do
that
because
we
love
it
so
yeah
we've
got
a
great
road
map.
We've
got
great
people,
it's
yeah,
it's
gonna
make
all
right.
So
is
there
anything
else
that
either
of
you
want
to
ask
or
update
on
I.
D
Don't
miss
I'll
go
seems
like
I
will
be
getting
done
with
the
the
patches
that
are
a
direct
apply
this
weekend,
great
yeah,
the
132
is
but
after
three
four
stone.
I
think-
and
I
know
I
confited
sometime
on
sunday
so
then,
hopefully
then
you're
rock
stars
can
get
work
working
on
the
layout
new
I
and
that
type
of
thing
and
I'll
fight
go
back
to
see
what
it
is.
I
can
rejigger.
Oh.
C
I
don't
think
we're
going
to
have
a
shortage
of
patches
that
apply
even
like.
Well,
maybe
we
will
once
research
to
going
through
drupal
8
patches,
I
mean
it'll,
actually
kind
of
be
a
rarity
that
any
of
those
will
apply
because
of
because
they
started
converting
things
like
crazy
right
after
we
forked,
but
there's
still
lots
of
things
that
that
are
ridiculously
similar.
They
just
all
live
in
different
locations
now
so
I'm
sure
they'll
continue
to
be
a
good
amount
of
porting,
even
after
we
finished
with
these
Drupal
7
ones.
So.
A
Maybe
maybe
Nate
it
would
be
good
sometime
between
this
week
and
next
week,
if
you
or
I
were
to
go
through
those
triple
eight
meta
issues
and
exclude
the
ones
that
we
obviously
don't
want,
like
anything
that
involves
conversion
to
simpy,
symphony
or
converting
to
twig,
or
you
know,
entity
eunji
any
of
that
stuff
that
we
definitely
don't
want.
We
can
just
take
off
the
list
right
away
and
that
will
reduce
the
number
of
patches.
We
even
need
to
try.
Oh
yeah.
A
C
Is
you
know
we're
not
planning
on
porting
all
these
things,
it's
kind
of
going
to
be
well,
we're
focused
already
on
that
delivering
the
features
that
we
know
we
want.
So
that's
like
we're
driving
really
hard
towards
the
sea
MI
and
views
issues,
for
example,
but
yeah
we're
going
to
need
to
take
a
lot
of
these
like
just
the
ones
that
make
sense
for
us.
So
so.
A
What
I
was
thinking
is
I'm.
Those
meta
issues
are
really
big.
Would
you
so
what
we
did
with
the
triple
seven
issues
was
we
went
through
and
we
wrote
like
na
next
to
the
ones
that
we
didn't
want
were
the
ones
that
we
weren't
gonna
implement
this
they
were
already
in,
and
should
we
just
remove
those
from
the
lists
on
the
Drupal
8
1?
Or
do
you
want
to
do
that
same
process
again,
where
we
identify
what
they
are
mark
them
as
na
and
check
them
off
is
done
yeah.
B
A
C
If
it's,
if
it's
something
that
we
would
benefit
of
having
a
record
from
because
it's
not
applicable
for
a
particular
reason,
then
keeping
in
the
list
is
good.
But
if
it's
literally
just
a
convert,
something
the
PSR
0
or
object,
I
ex
system,
then
we
can
just
remove
those
from
the
list
entirely.
Okay,.
A
All
right,
so
I
will
plan
on
looking
at
that
list.
At
least
the
first
issue
this
weekend,
Andy,
so
that
when
you're
done
with
your
current
stuff,
you
can
start
on
the
first
Drupal
8
issue
and
we'll
see
how
that
goes
like
it
might
not
end
up
being
is
a
straightforward,
really
think
or
it
might
be
more
shape
or
only
think,
but
you
should
at
least
have
something
to
start
working
on
alright.