I hosted a demo of and discussion about Configuration Recipes for Backdrop CMS at the last Backdrop LIVE. We followed it up with a recorded community meeting on the same topic. Watch this video for a demo of how configuration recipes work and some discussion about how to make them better.
Since this meeting, we've gotten feedback that maybe any sample content for configuration recipes should be kept in optional sub-modules to give site managers the choice of whether to install it or not.
Opening this topic to provide a place for more discussion about Configuration Recipes. We'd love to hear from folks who have used them.
- Are Configuration Recipes a useful/important tool for Backdrop CMS users?
- How can me make them better?
- What recipe would you find useful that does not yet exist?
Comments
Hello stpaultim
I used the FAQ Recipe in the past and I watched your community meeting about recipes. And I love the idea.
So I decided to make some steps myself. You know the things I reproduce on the most sites would be nice to have them bundled in recipes and save time in production.
My first test was a simple recipe with a css only for changing the color of the navbar-module. Like this I made it look more like the drupal mediteran navbar.
My second test was a recipe to add a paragraph type for image and text and some additional fields grouped together to add some styling possibilities. This fields I render in the paragraphs-item.tpl.php as css-classes.
Creating a recipe to add the paragraph-type and the fields was an easy process. So I tried to add *.tpl.php for the rendering. It seems to me that there is a limitation.
For me it would be nice, when it where possible to add this tpl.php files the same way I can do it in a theme.
If somebody does have a hint for me I would appreciate.
On some level, configuration recipes are simply a kind of module. As far as I know, you can overwrite core templates in a modules, so in theory you could also do so in a recipe.
However, this would require php code in the .module file, which means you will not be able to disable the recipe after installation. After doing this, your recipes might not be a recipes anymore, it might just be a module. But, that shouldn't matter to you as long as it does what you want it to do.
Here is information about adding .tpl.php files to modules for Backdrop CMS.
https://docs.backdropcms.org/documentation/overriding-template-files-in-...
Thank you for your response. It helped me a lot.