►
Description
In this community meeting we give a demo of all the available Config Recipes for Backdrop CMS and talk about the future of recipes in our community.
Here is a blog post to go with this video: https://backdropcms.org/news/configuration-recipes-for-backdrop-cms-an-update
A
A
Today's
topic
is
going
to
be
on
config
recipes,
which
my
colleague,
Saint
Paul
Tim
will
be,
will
be
leading,
let's
start
off
with
a
quick
round
of
introductions
which
participants
can
choose
to
skip
if
they
don't
want
to
be
involved
with
that.
But
I'll
start,
my
name
is
Luke
McCormick
I'm,
a
web
project
manager
in
San,
Ramon,
California
and
I'm
gonna,
pass
it
over
to
Greg
if
you're,
ready
and
willing.
B
C
D
D
Otherwise,
the
other
way
to
get
rid
of
a
config
recipe
is
pretty
much
to
just
just
to
to
manually
delete
the
parts
that
it
had.
One
of
the
things
one
of
the
definitions
of
Kit
config
recipes
is
that
they
primarily
rely
on
config
files
in
background
CMS
to
add
functionality
to
your
site
that
they
don't
really
config
functionality
right.
That
they're
not
adding
any
new
they're,
not
adding
anything
new
through
PHP
to
your
site,
but
what
what
they're
doing
is
like
setting
up
a
content
type
setting
up
some
views?
Maybe
dropping
your
this.
D
This
new
content
view
onto
a
layout
you'll
see
some
of
that
in
a
minute,
but
it's
all
stuff
you
could
build
by
yourself,
but
a
config
recipe.
Just
does
it
for
you
real
quickly
saves
you
the
time
and
also
might
you
know,
do
some
things
that
you
didn't
know
how
to
do.
For
example,
some
config
or
some
views,
config
or
advanced
anyways,
advanced
stuff,
so.
C
D
No
thank
you
for
reminding
me.
What's
your
name,
Greg
Greg,
thank
you
for
reminding
me
Greg,
because
that
is
an
important
point.
I
had
intended
to
make
and
then
I
slipped
past
it
these.
So,
but
it's
it's!
It
also
gives
you
the
freedom
to
do
what
you
want
here
and
not
worry
about
it
right,
because
it's
just
going
to
go
away
after
24
hours.
You
could
manually
install
backup
and
migrate
or
and
Export
your
config
in
your
database.
If
you
wanted
I've,
never
bothered
to
do
that
but
anyway.
D
So
one
of
the
things
we're
going
to
do
here
is
we're
going
to
jump
into
the
the
list
modules
and-
and
if
you
want
to
add
there,
there
are
a
handful
of
config
recipes
and
I
just
go
to
the
install
modules
and
again
not
everybody
may
be
aware
that
you
can
install
modules
any
any
supported.
Module
in
backdropcms.org
should
be
available
through
the
install
modules
interface
and
is
accessible
for
these
demo
sites.
D
I
actually
had
been
using
these
demo
sites
for
a
long
time
before
it
occurred
to
me
that
I
can
actually
add
modules
and
themes
as
well.
So
keep
that
in
mind
anyways,
if
I
search
for
recipes
there's
only
a
handful
of
them
right
now
and
they
and
we're
going
to
just
go
ahead
and
take
a
couple,
look
look
at
them
now.
The
card
recipe
is
redundant
for
this
particular
demo
because
we
already
have
it.
We
already
have
it.
D
The
purpose
of
the
card
recipe
was
to
provide
the
card
content
type
was
at,
which
was
added
in
a
recent
version
of
backdrop
CMS
and
to
add
this
view
for
those
who
might
have
an
existing
site.
This
the
card
recipe
only
gets
added
to
new
sites.
It
does
not
get
added
to
Old
sites
when
they
upgrade.
So
if
you
have
an
old
site-
and
you
want
the
card,
you
know
the
card
content
type,
you
can
use
this
card
recipe
to
very
quickly
spin
that
up
so
we're
not.
D
D
Some
of
these
recipes
do
have
dependencies
on
other
modules
and
that's
an
interesting
discussion
about
like
where
that
fits
into
the
point,
our
long-term
plan
for
recipes,
but
it
allows
us
to
sort
of
again
we're
not
adding
we're
not
creating
any
new
PHP
to
do
something
that
either
backdrop
or
this
other
config
module
can't
do
but
a
recipe.
Well,
in
this
case,
mostly
just
for
display
purposes,
we
found
the
views
bootstrap
module.
Actually,
we
we
don't
need
the
demo.
D
We
just
need
the
FAQ
recipe
and
use
bootstrap
we're
going
to
enable
those
and
they're
done,
and
if
we
go
to
our
front
page,
we're
gonna
see
one
that
there's
a
menu
item.
That's
been
added
to
FAQ.
We
go
here
and
there's
a
view
of
several
FAQs.
This
module
also
puts
some
sample
content
into
the
site.
If
we
go
to
the
content
menu,
we
can
first
of
all
see
that
there's
a
new
content
type
called
FAQ,
where
we
can
add
a
new
question
and
answer
or
we
can.
D
If
we
just
view
the
content,
we
can
see
the
sample
content,
that's
been
added
and
we
could
really
easily
delete
that.
Just
you
know
select
the
four
nodes
you
know
once
you've
seen
how
it
works.
You
don't
want
that
content
anymore.
Just
select
the
nodes,
hit,
delete
content
and
execute
I'm
going
to
leave
it
there,
because
I
want
that
to
hang
around
for
a
little
bit
and
I
I
am
I'm
talking
quickly,
so
we
get
through
the
demo
part
and
to
get
to
the
discussion
soon.
D
D
It
doesn't
look
like
this.
One
does
require
any
other.
You
know,
and
I'm
gonna
go
I'm
going
to
go.
Leave
that
open
I'm
going
to
go
to
this
other
tab
refresh
the
page.
So
actually,
if
I
scroll
down
this
one
again,
the
idea
is
to
add
a
testimonials
with
this
kind
of
a
format
and
this
one
in
addition
to
adding
the
content
type.
D
D
D
A
D
I
think
we
should
talk
more
about
that
in
the
the
like
road
map.
But
and
again
not
everybody
may
be
aware
of
this
feature,
but
in
backdrop
you
can
especially
on
this
install
actually
I
think.
Can
we
do
this
on
the
list
from
the
the
project?
Installer,
you
can
click
on
the
link
to
the
the
that
info
page
in
all
of
my
modules,
I
try
to
create
a
list
of
exactly
what
the
recipe
is
doing
and
I
would
say
that
that's
not
a
requirement,
but
a
best
practice.
D
If
you
create
a
recipe
to
make
sure
that
you
provide
a
really
clear
list
about
what
exactly
that
recipe
is
doing
so
that
because
there
is
no,
as
I
mentioned
before,
there's
no
uninstall
process.
So
if
somebody
adds
this
and
wants
to
get
rid
of
it,
they're
going
to
just
have
to
manually
go
in
and
delete
the
four
nodes.
You
know
the
menu
item,
you
know,
maybe
disable
the
module.
They
don't
need
and
delete
the
content,
type
yeah.
B
So
you
can
I'm
assuming
because
they're
behaving
as
modules,
you
can
add
an
installation
book,
and
the
only
thing
that
it
does
is
just
sets
backdrop
set
message,
and
then
it
has
a
bullet
points.
So,
instead
of
people
needing
to
know
that
they
need
to
go
to
these
things
outside
the
site,
it
would
be
just
right
after
they
enable
the
recipe.
It
will
say.
D
D
D
This
is
another
kind
of
a
use
case
where
we
had
a
core
feature
that
wanted
this
report
and
there's
talk
about
adding
this
to
core,
but
we
discovered
that
in
fact,
it
was
possible
to
build
the
the
report
that
that
somebody
was
asking
for
using
existing
tools
and
Views,
and
so
I
said
well.
Let's
just
for
now
create
a
recipe
we'll
see
if
people
like
it,
if
it's
possible
or
popular
and
then
we
can
decide
if
it
should
go
into
court,
so
I've
enabled
and
installed
this
module
and
what
all
it
does
is.
D
D
You
can
figure
that
out
in
some
of
the
other
reports
like
this,
the
status
report
or
if
you
go
to
your
modules
page,
but
it's
kind
of
hard
to
cut
and
paste
them.
This
is
a
page
with
a
report
that
you
can
like
really
easily
just
sort
of
cut
and
paste
into
an
email.
You
can
also
easily
filter
by
just
show
me
core
modules
or
just
show
me
contrib
modules.
D
D
We
we
were
talking
about
this
at
backdrop,
live
and
I
I,
don't
have
the
exact
answer,
but
I
kind
of
feel
like.
If
you
created
a
custom
module,
it
would
show
up
when
you
did
contract
anyways
I'm
not
going,
we
don't
have
any
control.
Well,
actually
we
do
have
a
trip.
We
do
have
a
contrib
module
because
our
we
have
our
recipes.
So
if
I
hit
contrib
modules,
these
are
the
contrib
modules
that
I've
enabled.
B
Whereas
on
the
the
issue
that
we
have
it's
an
older
issue
to
filter
the
modules
paid,
we
because
I
remember
Jen
and
I
used
to
work
on
the
algorithm
or
the
logic
that
was
filtering.
We
had
three
different
buttons
or
radio
buttons
and
it,
and
it
was
distinguishing
between
between
contrib
and
and
custom,
so
you
could
say
that
the
system
module
as
it
works
now
that
provides
the
views
filters
is
sort
of
like
has
this
as
a
shortcoming
that
we
could
fix.
Okay,.
D
So
the
the
user,
the
welcome
recipe
includes
the
user
guide
recipe.
So
basically
the
welcome
what
the
welcome
recipe
is.
Is
it
just
adds
a
bunch
of
content
to
your
site
to
sort
of
help?
You
learn
about
backdrop
really
is
the
intent
and
I
included
the
user
guide
as
part
of
it,
but
I
thought
some
people
might
just
want
the
user
guide,
so
I
broke
them
out
in
separate
recipes.
D
D
D
D
D
What
you
were
suggesting
yes,
yeah
yeah,
so
now,
if
we
go
to
the
home
page
of
this
site
this
again
this
this
recipe
is
kind
of
intended,
like
for
demos
or
just
giving
people
examples
to
better
see
the
things
you
can
do
in
background.
This
recipe
does
use
some
PHP
install
code
to
do
things
like
it
changes
the
default
image
in
your
to
something,
maybe
a
bit
more
attractive.
It
adds
the
user
guide
up
here.
It
also
adds
some
content
on
the
about
page.
D
It
creates
a
footer
that
contains
a
block
of
recent
content
and
this
footer.
It
uses
many
the
mini
panels,
and
so
it's
kind
of
a
way.
If
you
want
to
learn
about
many
panels
and
and
see
how
to
you
know
one
way
of
kind
of
creating
a
footer,
you
can
do
that.
You
know
you
could
install
this
module
and
play
around
I.
Put
a
note
here
saying
that
this
the
Opera
theme
will
make
this
look
a
little
bit
better.
So
let's
go
ahead
and
do
that.
D
I
think
one
of
the
things
the
Opera
theme
it
was
just.
There
was
some
weird
spacing
down
here
that
that
got
fixed
from
basis
to
Opera
and
I.
You
know,
I
wanted
a
theme
that
would
work
well
with
this,
this
module
or
this
recipe.
But
this
recipe
is
still
a
little
ugly
and
the
point
is
we
don't
know
when
you're
when
you're
importing
content,
you
know
you're
recording
it
into
different
themes
and
it's
going
to
react
differently
in
every
one,
so
it
isn't
necessarily
pretty,
but
it's
there
we
have.
D
You
know
I
wanted
to
demonstrate
sub
menus,
and
so
we
we
actually
created
some
pages.
The
other
thing
I
did
do
is
is
create
like
links
to
to
videos
about
some
of
the
things
you're
seeing.
So
if
you
wanted
to
use
this
sort
of
as
an
instructional
tool,
if
we
go
to
news,
there's
a
bunch
of
Articles
what
our
posts
promoted,
content
and
again
in
a
few
cases,
we
have
links
to
off-site
videos.
Oh
the
other
place
that
I
used
that
the
video.
So
that's!
D
D
The
idea
for
the
user
guide
is,
first
of
all,
that
it
just
sort
of
gives
you
a
template
of
a
guide
to
this
site,
and
it
has
a
couple
of
demonstration,
Pages
goals
and
objectives.
These
are
ideally
pages
that
you
would
fill
in
to
just
sort
of
you
know
what
what
theme
did
we
use
and
why?
What
are
our
custom
modules
that
you
know?
Maybe
you
could
have
this
information
for
yourself
for
future
developers
and
for
the
site
owner
and
they're.
D
Just
sampling
pages
I
also
put
in
this
like
guide
to
backdrop,
user
guide
section
where
I
basically
copied
and
pasted
some
of
the
content
from
the
the
background
user
guide,
but
then
link
to
the
full
content
and
I
included
links
to
some
videos.
I've
made
I
love
feedback
on
whether
or
not
this
is
worth
pursuing.
D
Keeping
it's
not
clear
to
me
that
actually
having
this
content
in
the
site
is
a
good
idea,
because
obviously
this
the
the-
if
you,
if
you
add
this
content
to
your
site,
it
won't
get
updated
when
the
content
does
on
the
site.
So
you
know
it
might
be
better
to
just
have
a
link
to
the
user
type,
but
I
wanted
to
play
around
with
this
idea
of
providing.
You
know
in
Insight
instructions,
and
it
also
includes
a
glossary
which
is
not
by
any
means
comprehensive
again.
D
If
anybody
wants
to
add
to
this
and
create
a
pull
request,
please
do
so,
but
again
an
editor
might
be.
You
know
working
through
the
backdrop
user
interface
and
have
questions
about
what
what
is
taxonomies
or
what
the
difference
between
taxonomies
and
vocabularies
and
here's
just
a
place
right
in
the
site
without
having
to
Google
it
where
they
could
get
that
information.
I,
don't
know,
tell
me
if
it's
useful,
it's
very
useful.
A
D
A
D
Yeah
yeah
I
agree
with
all
those
things.
The
the
primary
use
case
of
the
user
guide
for
me
was
just
this
ability
to
create
your
own
sort
of
user
guide.
The
other
stuff,
I
think
is
kind
of
icing
or
just
extras
and
I'd
be
totally
comfortable,
getting
rid
of
those
things
because
they
Exist
Elsewhere
but
I.
Think
the
the
user
guide
recipe
is
still
valuable
in
that
it's
a
quick
way
that
you
can
create
kind
of
this
Internal
Documentation,
that's
custom
for
your
site.
D
I
have
done
this
on
a
couple
of
my
client
sites,
I
know
of
other
developers
that
do
this
regularly
and
here's
a
recipe
to
just
get
you
started
with
it.
It
gives
you
the
content
type
you
need
turns
on
the
modules
you
need
gives
you
a
view.
Just
gets
it
all
sort
of
configured
for
you
right
out
of
the
box.
I.
A
D
D
I'm
gonna
mention
because
I
did
in
the
other
session,
I'm
gonna
a
quick
promo
for
if
you're,
using
these
recipes
for
sample
content.
You
should
be
aware
of
there's
one
other:
it's
not
a
recipe
or
it.
It
really
functions
like
a
recipe,
but
it's
it
was
created
before
we,
we
thought
of
recipes.
So
there's
a
a
module
called
sample
animal
content
that
I
created,
which
maybe
I
should
change
it
to.
D
You
know,
change
the
title
and
call
it
a
recipe,
and
if
we
have
basically
all
this
does
it
adds
a
content
type
and
a
bunch
of
content
that
you
can
use
if
you're
theming
or
doing
a
demo,
I
I
created
this
module
because
I
was,
you
know,
doing
theming
and
testing
and
wanted
to
really
quickly
install
a
bunch
of
content.
Now
we
discovered
in
our
demo
on
Friday
that
the
images
aren't
loading
properly
and
I
know
they
were
in
the
past.
So
I
don't
know
why
that
is
so.
D
I
will
have
to
take
a
look
at
it,
but
basically
what
this
module
does.
Is
it
just?
It
creates
an
animal
content
type
and
adds
some
sample
content
and
images
so
that,
if
you
wanted
to,
you
know
give
a
demonstration
on
views.
You
could
use
this
sample
animal
content
to
create
your
demo
really
quick
or
if
you
were
theming
and
you
wanted
to.
You
know
just
see
how
a
bunch
of
nodes
would
look
on
the
front
page
using
the
default
setup.
You
could
add
this
content.
D
D
B
Then
can
I
ask
a
question:
yeah
I
recall
a
vaguely
recorded
a
discussion,
and
maybe
an
issue
somewhere
of
whether
recipes
should
be
a
fourth,
because
in
blackshop
we
have
themes
and
modules
like
in
Drupal,
but
we
also
have
layout
templates
as
a
as
a
third
additional
project
type
and
at
some
point
we
were
discussing
whether
recipes
was
was
needed
for
them
to
be
a
separate
pipe
and
we
went
with
modules
so
they're
listed
at
modules.
Can
you
please
and
I
know
that
you
were
involved
in
these
discussions?
Like?
B
D
Well,
so
I
think
this
remains
undecided.
It's
under
discussion
and
it's
part
of
the
future
of
recipes
discussion
right
I.
Can
the
the
key
points
here
are
one
that
functionally
recipes
are
modules
right
now
right
so
putting
them
on
the
module.
Page
was
just
an
easy
thing
to
do.
It
will
require
some
work
to
Define
them
as
a
separate
type
of
project
and
have
them
listed
now.
Work
has
begun
on
that.
D
John
Lampkin
has
started
a
module
that
would
create
sort
of
a
recipes
Tab
and
allow
you
to
to
filter
out
and
just
sort
of
view
the
recipes
and
and
download
them
without
sort
of
having
to
do
that
extra
step.
But
I
I,
don't
know
how
close
that
bonjour
is
to
completion
some
feedback.
I've
gotten
is
that
for
end
users,
sort
of
Site
Builders
that
the
distinction
might
actually
be
counterproductive.
D
And
I
don't
know
if
this
is
true
or
not
I'd
like
more
feedback,
but
you
know
if
I
add
the
I,
don't
know
what's
another
module,
why
can
I
not
think
of
the
name
of
a
module
I'm
trying
to
think
of
something
with
some
sort
of
functionality?
Let's
just
go
to
in
all
new
modules.
We're
going
to
clear
this.
D
If
I
add
the
I
don't
know
well
these
the
Honeypot
module
right
and
I
have
the
FAQ
module
right,
we're
defining
the
FAQ
module
as
a
as
a
recipe?
Does
the
average
user
understand
the
difference
between
the
Honeypot
module
right
right
right?
They
don't
or
do
they
care
right
for
their
purposes?
They
need
something
on
their
site
and
the
Honeypot
module
happens
to
be
more
complicated
and
does
require
new
PHP
code.
The
FAQ
recipe
doesn't
but
does
the
client
care.
D
If
you
want
them
and
he's
made
the
point
that
he
doesn't,
he
thinks
that
there
are
that
he
would
give.
He
would
give
a
site
editor,
the
ability
to
add
a
paragraph
type,
whereas
he
wouldn't
give
them
the
ability
to
add
a
module
type,
because
they
could
do
a
lot
more
damage
by
adding
a
module.
So
what
we
right
now
with
the
way
recipes
work,
is
that
you'd
have
to
have
the
ability
to
download
and
install
any
module
in
order
to
install
a
recipe.
D
If
recipes
were
a
different
project
type,
we
could
provide
that
as
a
permission
to
certain
users,
I
think
in
their
current
state.
That
I
don't
know
that.
There's
a
big
advantage
to
that
because
you,
you
know,
but
I,
could
see
down
the
road
where
it
would
be
helpful
that
you
know
where
we
might
want
to
do
that.
We
don't
want
somebody
adding
back
up
and
migrate
to
to
the
site,
but
we
want
them
to
be
able
to
add
an
FAQ.
You
know
recipe.
A
Yeah
I
I
think
you're
you're
underselling
the
potential
there
I
mean
I
mean
one
of
the
nice
things.
One
of
the
really
nice
things
about
recipes
is
that
it's
it's
a
very
accessible
feature
for
you
know,
sort
of
content
focused
users
and
I
mean
there.
There
are
some
things
like
that
within
modules,
but
there
are
lots
and
lots
and
lots
of
much
more.
A
You
know:
wiring
exposed,
developer
level,
things
in
modules,
so
I
I
think
there's
considerable
value
to
be
had
of
a
section
which
is
approachable
and
friendly,
and
you
know
not
as
intimidating
not
as
dangerous
and
perhaps
later
on
once
it's
established.
We
may
want
to
revisit
the
modules
page
and
and
see
if
we
can't
build
some
of
those
distinctions
usefully
in
the
into
that
list
to
surface
some
of
those
more
accessible
modules
to
people.
F
D
D
D
D
I'm,
just
going
to
copy
the
link
to
this
experimental
module,
which
I
found
in
the
recipe
space
and
I'm
going
to
go
back
to
the
install
new
modules
feature
but
I'm
going
to
hit
the
manual
install
button
and
I'm
going
to
go
down
here,
install
from
a
URL
and
it
installed,
and
this
could
destroy
our
entire
site,
in
which
case
I
think
we're.
Okay,
we're
pretty
much
done
with
it,
but
enable
newly
added
module
yeah.
Let's
do
it.
I'm
sorry
did
I
already
nope
I
didn't
there.
B
So
the
manual
installation,
the
way
you
sort
of
like
missed
the
thing
yeah
you
didn't
miss
it.
It
was
what
you're
wondering
is
that
the
project
installer
once
it
downloads
the
modules
it
offers
the
options
to
enable
it.
But
when
you
do
a
manual
installations,
we
haven't
hooked
that
into
the
installer
step
where
it
says
you
can
start
enabling.
So
that's
that's
a
feature
request.
If
you
like
got
it.
Yes,
okay,.
D
Well,
we
so
this
module
starts
to
work.
However,
some
of
these
features
aren't
complete
I'm,
aware
of
that.
So,
for
example,
Jen
is
envisioning.
The
ability
to
re
revert
a
module
or
a
recipe
that
doesn't.
She
has
not
made
that
option
operational
yet,
but
she
built
it
into
the
UI.
So
if
you
install
this
module
and
then
tried
to
revert
the
FAQ
recipe,
nothing's
gonna
happen,
I,
don't
know
the
well.
This
doesn't.
Oh,
this
isn't
really
an
installer
right
now.
This
is
really
for
managing
right.
D
B
B
But
the
reason
why
I
didn't
get
involved
for
recipe
into
the
recipe
things
was
that
I
lack
creativity,
so
I
didn't
know
what
to
sort
of
like
make
a
recipe
for.
But
one
thing
that
has
always
been
in
my
head
is
the
out
of
the
box
initiative
in
Drupal,
which
is
basically
Umami.
The
Umami
theme
and
content
is
the
product
on
that.
B
So
maybe
it
may
sound
ambitious
to
Port
that
to
backdrop,
but
the
the
content
is
already
there
so
for
Less,
creative
people
like
myself,
basically
we'll
have
to
just
adjust
things
and
then
we'll
have
a
on
top
of
having
an
individual
thing.
That
is
more
Rich
right
than
those
simple
recipes
with
ready-made
content.
Then
we
would
allow
people
to
install
Drupal
with
the
mummy
and
backstroke
with
the
mummy
and
see,
look,
there's
any
difference
and
be
able
to
compare
it.
No,
so
so
here's
an
idea
that,
in
other
words
for
people.
D
B
D
B
B
Obviously,
now
the
the
usefulness
of
recipes
and
I'm
not
sure
Umami
I
see
that
it's
implemented
as
a
theme,
but
at
some
point
I
know
that
there
was
notion
of
having
it
as
a
installation
profile
or
something
but
I
see
now
with
recipes
that
there
was
another
discussion.
Let
me
back
up
a
bit
about
whether
we
should
have.
We
should
make
teams
first
class
citizens
as
in
allow
them
to
do
certain
things.
B
That
modules
do
like
day
Hooks
and
things
that
they
don't
do
anymore,
so
recipes
might
be
a
gateway
to
that.
Instead
of
creating
a
thing
that
requires
to
do
such
things,
maybe
you
can
create
a
recipe
that
actually
has
the
theme
and
whatever
modules
as
dependencies
on
top
of
that
so
I
see
other
use
cases
for
this
as
well,
besides
the
the
obvious
or
the
intended
initial
usage.
So
it's
good
thanks
for
working
on
that.
C
D
Dependencies
on
a
recipe,
if
that
like,
is
that
a
good
idea
or
not
the
the
closest
I've
got
to
that,
was
the
suggestion
that
I
sort
of
have
a
recipe
where
it
says
you
know
right
in
the
content,
that's
provided
on
the
site.
This
theme
might
work
better
with
this,
or
this
recipe
might
work
better
with
this
theme,
but.
D
The
I
I
think,
like
there's
a
whole
spectrum
of
how
complex
recipes
can
get
and
right
now
there's
it's
really
up
to
the
the
person
creating
it
to
decide
how
complex
they
want
it.
The
you
know
down
the
road
we
might
want
to.
If
we
had
a,
we
had
a
recipe,
a
project
type
we
would
probably
need
to.
You
know
then
set
certain
criteria.
What
qualifies
as
a
recipe
yeah.
B
But
another
use
case
sorry
another
use
case.
Before
we
run
out
of
time.
There
was
a
series,
I
kind
of
remember
the
name
of
the
series.
Exactly
there
was
a
series
of
blog
articles.
A
person
was
writing
about
simplifying
things
for
Content
editors
and
it's
like
not
theme
decisions
but
features
that
are
already
there
as
configuration
in
Drupal
or
or
spend
time
to
fine-grain
the
views
or
make
it
easier
or
change
the
menus.
B
The
order
of
the
menu
of
the
administration
menu
so
that
people
are
not
overwhelmed,
and
it
was
a
series
of
three
or
four
or
four
blog
articles.
I'll,
try
to
find
them
and
link
to
them
that
it
was
sort
of
like
what
they
used
to
do
for
every
single
customer
that
they
had,
so
that
it
makes
it
easier
for
the
content
editors
right
and
because
they
were
doing
it
repetitively.
B
The
the
problem
that
they
were
they
were
sort
of
like
pointing
out
was
that
as
an
agency
or
a
freelancer,
when
you
are
ready
to
hand
over
a
site,
you
would
want
your
customer
to
be
happy
and
to
have
a
less
overwhelming
experience
like
taking
things
out
of
the
way
when
they
don't
need
them
with
permissions.
Maybe
all
that,
but
that
takes
time
to
tweak
the
site,
but
they
found
themselves
doing
the
same
things
repetitively,
so
I
think
that
they
ended
up
scripting
it
or
putting
it
in
a
module
or
a
theme.
B
I
can't
remember
so.
Rest
recipes
is
a
good,
a
good
use
case
for
that.
So,
if
you're
an
agency
that
you
find
yourself
doing
the
same
configuration
installing
the
same,
maybe
custom
modules
over
and
over
with
your
customers
or
for
your
customers
before
you
deliver
a
site.
Maybe
a
recipe
in
that
case
could
be
a
solution
for
that,
just
to
automate
common
repetitive
tasks
that
you
you
do
before
you
deliver
the
size
to
the
customer
that
are
the
same
for
each
customer
right.
B
D
D
B
F
Problem
with
the
install
profiles,
I
think
in
the
has
been
that
you
can
include
modules
in
them,
and
so
people
would
like
include
a
custom
version
of
views,
and
if
you
tried
to
update
views
outside
of
your
distribution,
they
would
break,
and
so
that
would
walk
people
into
their
distribution
versions
dependent
on
their
Drupal
versions.
Right
so
I.
Think
if
you,
if
you
didn't,
do
that,
if
you
only
had
your
own
code
in
there,
it
would
have
a
lot
less
problems.
Yes,.
D
Distributions
don't
have
to
lock
you
in
they
lock
you
in
when
they
do
custom
things.
If
they
relied
exclusively
on
existing
contrib
modules
and
existing
contribs,
then
you
wouldn't
be
locked
in
you
could
just
enable
them
and
then
disable
them
and
I
I
have
used
ones
like
that
before
you
do.
You
want
to
make
a
different
point:
Joseph.
F
Our
users
have
them
and
then
have
a
separate
user
interface.
That
I
was
like
a
separate
modules
page,
basically
where
I
could
say:
okay,
these
are
safe
for
our
users
to
install
and
to
say
enable
or
disable,
and
it
won't
break
those
systems
yeah
and
then
hide
like
I.
Don't
want
them
to
be
able
to
enable
and
disable
views.
B
So
right,
Joseph,
what
you
have
you
this,
this
module,
which
is
called
working
modules,
permissions?
What
is
called
it
sounds
like
that.
You
were
trying
to
to
provide
to
customers
that
I
restricted
version
of
the
modules
page
that
doesn't
list
all
the
modules,
but
only
selectively
the
ones
that
you
want
to
have
listed
right.
B
Yeah,
because
we
we
restrict
that
in
SAS
customers
we
restrict
the
the
access
to
the
permissions
in
certain
pages
and
we
restrict
access
to
the
the
functionality
the
extend
page,
so
they
cannot
SAS.
Customers
cannot
enable
and
disable
modules
directly
from
these
pages
right
and
we
are
using
modules.
There's
two
modules
that
we
have
installed.
I,
remember
the
modules,
the
modules
permissions
module.
It
just
sounds
funny
and
custom
permissions,
or
something
like
that,
and
then
there's
there's
one
that
restricts
like
that.
B
Allows
you
to
specify
an
allow
list
of
modules,
and
then
you
say,
customers
can
only
see
in
the
modules
page
only
these
modules
right
and
use
one
or
people
with
higher
permissions
can
see
the
rest,
like
the
entire
list
of
modules.
I'll
try
to
find
that
in
Drupal,
land
and
I'll
provide
a
link
somewhere
and.
A
B
D
We'll
see
you
thanks
for
coming
Grace
yeah
thanks
for
that
Luke,
because,
yes,
we
are
almost
out
of
time.
We
can
run
over
a
couple
of
minutes,
I
think
if
we
need
to,
but
let's
when
I
the
one
thing
I
didn't
cover
that
I
wanted
to
is
to
talk
about
how
to
create
a
recipe.
And
let
me
do
this
really
quick.
So
the
the
points
that
Joseph
and
and
Greg
are.
We
also
want
to
talk
about
the
future
recipes
and
I.
D
The
current
one
of
the
big
blockers
of
recipes
right
now
is
the
it's
a
little
bit
difficult
to
make
them
I
mean
it's
it's
relatively
easy,
but
it's
not
a
push
button,
easy
right
where
the
comparable
feature
in
Drupal
7,
which
was
features
you.
We
had
a
user
interface
that
you
could
use
to
create
a
a
feature
like
module,
which
is
is
very
similar
to
a
recipe
in
a
ways
but
different
than
others.
D
If
we
could
build
that
user
interface
to
create
recipes,
I
think
they
would
be
a
much
more
valuable
thing
and
we'd
see
more
interest
in
them,
but
barring
that
they're
not
too
hard
to
make
and
that
you
don't
need
to
write
any
custom
code
to
create
a
recipe
I'm.
Looking
at
the
the
project
page-
oh
that's
sorry,
I
had
the
project
page
for
a
specific
recipe.
There
we
go
the
testimonial
recipe
and
basically
the
minimal
ingredients.
This
none
of
my
recipes
unfortunately
include
the
minimal.
They
all
have
something
extra.
D
Some
of
them
have
a
little
bit
of
CSS
to
make
them
look
good
out
of
the
box.
That
CSS
is
only
going
to
work
as
long
as
the
recipe
is
enabled,
if
you
disable
that
everything
will
still
work
except
for
the
CSS,
which
maybe
you
have
a
custom
theme,
and
you
don't
care
about
that
images
and
and
text
these.
This
is
my
sample
content,
so
this
would
is
not
required
in
a
recipe
but
because
I
wanted
some
sample
content,
I
put
some
text
files,
and
so
some
some
images
what's
required
is
the
config
files.
D
Okay,
you
need
your
config
files
that
you
use
to
create
the
the
individual
Fields
the
field
instances.
This
one
has
an
image
style.
It
has
a
node
type
and
it
has
a
view.
So
we've
we
just
basically
we
have
those
at
a
very
minimum.
You've
got
those
config
files
and
you
have
a
dot
info
file
in
the
dot
info
file.
Basically,.
D
The
no
we
okay,
the
dot
info
file
in
order
for
your
recipe
to
work,
do
you
need
to
be
running
background
version
1.20
or
greater?
So
you
need
this
statement
in
the
that
info
file.
That's
it
we
do.
We
we
are
I,
have
been
creating
this
packages
equals
recipe.
This
is
sort
of
a
behind
the
scenes
thing
in
case
we
ever
did
create
tools
that
wanted
sort
of
a
project
type
called
recipes,
but
right
now
there
isn't
anything
that
does
anything
with
that
I
hear
Joseph
trying
to
I
think
you.
D
Yes,
I
think
we've
talked
about
that
before
too
yeah.
The
the
last
thing
that
you're
required
to
have
in
your
recipe
is
a
DOT
module
file
that
is
empty.
We
really
don't.
If
that
we
don't
expect
to
see
anything
in
the
dot
module
file.
It's
required
right
now
by
backdrop.
Just
it
doesn't
recognize
a
module
as
a
module
unless
it
has
this
file.
But
we
don't
really
want
any
code
in
here,
because
I
think
in
theory
recipes.
D
You
should
at
least
have
the
option
to
disable
them
and
they
still
work
and
if
you
had
any
code
in
your
dot
module
file
that
would
no
longer
work
once
you
disabled
the
recipe.
So,
ideally
you
don't
have
anything
there,
but
you,
but
but
the
modules.
So
we
need
a
dot
info
file.
We
need
a
at
least
an
empty
dot
module
file
and
we
need
some
can
faint.
That's
the
minimum.
D
The
I've
added
some
other
things,
I've
also
added
a
DOT
install
file
which
has
PHP
in
it,
but
this
is
just
run
an
installation
to
create
the
sample
contented
nodes.
If
you
turn
off
the
module,
it
doesn't
matter
because
this
all
this
code
only
gets
run
on
installation,
and
it's
never
looked
at
again.
D
D
You
know
these
are
things
we
need
help
on
if
anybody's
excited
by
this
idea,
in
or
instance,
to
help
us
build
or
the
Creator
the
how
to
a
UI
tool,
or
you
could
just
sort
of
export
the
recipe
from
an
existing
site
without
having
to
do
what
I
just
said.
That
would
be
really
helpful
and
move
this
project
forward.
Any.
C
A
F
C
D
Absolutely
yeah,
all
all
recipes
are,
are
sort
of
jump
start.
So
quick
starts.
Okay,
they
build
the
content
type
in
pretty
much
the
same
way
you
would
have,
but
they
do
it
quicker.
So,
once
the
recipe
is
installed,
you
have
complete
control
to
modify
it
in
any
way.
You
want
that
you
could
normally
have
done
right.
The
recipe
won't
give
you
any
new
things
that
you
couldn't
have
done
before,
but
it
will
allow
you
to
continue
to
to
modify
it
in
any
way
you
want.
So.
D
D
Anybody
else
have
any
final
questions:
I
think
that
in
terms
of
the
next
upcoming
meeting,
it's
just
the
four
of
us,
so
we
don't
have
to
cancel
or
stop
this,
but
but
we've
been
going
for
an
hour
or
so,
let's
they're
they're
I,
don't
have
links
handy
to
send
you
to,
but
there
is
I
have
written
a
blog
post
or
too.
If,
if
you
Google
backdrop,
CMS
config
recipes,
you'll
find
a
blog
post
or
two.
D
Please,
if
you
are,
if
you
I,
I've,
gotten
very,
very
little
feedback
from
people
that
have
tried
and
used
recipes
and
I'd
love
to
get
more
of
it.
So
if
you've
tried
out
these
recipes
and
either
you
know
any
like
them
and
found
them
useful,
let
me
know
that
motivates
me
to
make
more
if
you've
tried
them
and
found
like
you'd
think
they
could
be
a
little
bit
better
by
all
means.