Behind every Drupal website are the modules and configuration settings that define the website’s content model, authoring experience, presentation, and integrations. This post will explain and explore how the Schema.org Blueprints module handles configuration compared to a Drupal distribution and a Drupal recipe.
A Drupal distribution provides a predefined list of modules and configuration that define an entire website solution. For example, distributions offer a starting point for building a commerce, government, or intranet website. The Drupal community has acknowledged that distributions can be too opinionated and can become challenging to maintain.
There is now a Recipes initiative whose goal is to provide a modernized approach for distributions. A ‘recipe’ is a composable piece of site functionality and features bundled together. For example, a ‘recipe’ would provide an event registration system with an Event content type, a calendar view, and an online registration webform.
After installing a distribution or recipe, developers and site builders must alter and reconfigure what is installed to meet their organization’s unique requirements. The ‘Recipe’ initiative and the Schema.org Blueprint module share the goal of providing a better starting point for building out a website’s features and functionality. The big difference between these two solutions is the Schema.org Blueprints module does not ship with a predefined content model and configuration. Instead,…Read More