What do Drupal recipes do?
A recipe applies a set of changes to your site in one action. It can install and enable the modules a feature needs, import the configuration that makes them work together, and add starter content so the feature is usable right away. Once a recipe runs, it steps out of the way. Your site is left with the end result, not a dependency you have to keep installed.
What are the benefits of Drupal recipes?
- Faster setup. Common features are configured in one step instead of being assembled by hand every time.
- Consistency and best practices. Every site built from the same recipe starts with the same proven configuration.
- Composable by design. Recipes can apply other recipes, so you build a site by combining smaller, focused pieces.
- No lock-in. A recipe is unapplied after it runs, so you are free to customize everything it produced.
- Repeatable and shareable. The same recipe gives you the same starting point across projects and teams.
How are recipes different from distributions?
A distribution is a full Drupal install profile that your site is permanently tied to. A recipe is applied to an existing site and then unapplied, leaving only the configuration and content behind. That makes recipes far more flexible. You can mix and match several recipes on one site rather than committing to a single all-in-one package.
How Webhaven uses Drupal recipes
Webhaven is built on recipes from the ground up. Instead of one rigid bundle, Webhaven ships a set of recipes that install its theme, page-building blocks, design elements, and default content, giving you a fully functional website you can launch right away and then shape to your needs.
Can I see Webhaven in action?
Yes, you can see Webhaven in action here.