@@ -26,8 +26,8 @@ Drupal CMS doesn't pin any of its dependencies, so people using Drupal CMS will.
You don't. Drupal CMS is a starting point for creating new sites. Once you're set up, you just have Drupal, plus some sample content and preconfigured features. You can update installed modules and themes exactly the same way you would on any other Drupal site. But Drupal CMS _itself_ is not something you update.
This gives us a lot of freedom to iterate and improve rapidly, because we don't have to care all that much about stability. And it gives _you_ a lot freedom too, because no matter what changes we make to our recipes, we're not going to break your site.
This gives us a lot of freedom to iterate and improve rapidly, because we don't have to care all that much about stability. It gives _you_ a lot of freedom too, because no matter what changes we make to our recipes, we're not going to break your site.
If Drupal CMS adds some new hotness and you want it on your site, you can either set it up manually -- perhaps using the updated recipe(s) as a guide -- or you can try reapplying the necessary recipe(s). The latter may not necessarily work exactly as you expect, precisely because recipes are opinionated and there's no guarantee that the recipe's opinions won't clash with the ones your site has.
At the end of the day, recipes are opinionated bundles of configuration, and opinionated configuration updates are an as-yet unsolved problem in the Drupal. Recipes are not going to be the thing that solves it.
\ No newline at end of file
At the end of the day, recipes are opinionated bundles of configuration, and opinionated configuration updates are an as-yet unsolved problem in the Drupal universe. Recipes are not going to be the thing that solves it.
