Change examples to presets
See original GitHub issueI’ve been tracking the project and so far i’m loving it. I’ve seen that you have Storybook in mind already and i’m really hoping that it becomes first class and with that i would love to take it out for a spin and expand the tutorial to include this aswell. But i was checking the readme and the tutorial and it would be a nice feature to include in a future release the inclusion of options to the user. And by options i mean the examples you have mentioned. Probably move them into their own repos and allow the initialization process to use them.
Basically if the user issues yarn create redwood-app ./redwoodblog
it wil default to the de facto setup. But if the user issues yarn create redwood-app todo ./todos
it would initialize a new project based on that and the same for other existing examples and hopefully giving the option to the community to expand this and allow them to create their own templates.
With that i believe that it could mean more adoption and also allow the user/community to learn the building blocks of the framework.
Feel free to provide feedback
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top GitHub Comments
Linking issue https://github.com/redwoodjs/redwood/issues/2218 and PR https://github.com/redwoodjs/redwood/pull/2324; they’re somewhat similar to the conversation here, but have more of a contributing angle.
This came up recently on the Discord. I believe it was @mattmurph9 who asked? Copy pasting here:
The use case was multiple web apps, so maybe this could be solved via multiple sides instead, and just sharing components:
But at least two other users joined the discussion, so it seems like there’s still some real interest here.