@guledali made a comment in another thread that sparked a response that I actually think warrants its own topic, so I moved it here instead
The question/request from @guledali brought up a topic that I’ve asked abouot earlier, but not sure if we ever came to a conclusive answer.
How should we handle the cookbook? Should anyone from the community be free to add his/her tutorial as a recipe in the book? If not, who decides what goes in and what doesn’t? Another topic, in addition to the pagination I’ve already written about, I’m interested in turning in to a tutorial/recipe is search. Adding search functionality to the basic redwood tutorial blog. Should that also be an official Redwood cookbook recipe? As mentioned in the original post linked above, I’m sure others will want to add these things too, and adding them as cookbook recipes is great for discoverability. But if something’s added to the official cookbook, who’s responsible for keeping it up to date? The core team?
Another option is to add a link to the awesome-redwood repo. Is that easy enough to find?
I think @dthyresson had similar questions when he wrote the RBAC example app (https://github.com/dthyresson/redwoodblog-rbac) that later became a recipe (https://redwoodjs.com/cookbook/role-based-access-control-rbac)