Is your feature request related to a problem? Please describe.
Currently the quasarframework repo is just a home page and a way to group other repos.
Describe the solution you'd like
I would like to see the framework page describe the quasar framework, provide some details about the repo organization, such as noting that the main codebase is in the quasar repo, talk about starter kits.
And --- have it's own issues, to allow suggestions about repo organization, structuring that is framework based and not quasar based.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Pinning 6 repos and then just listing all 50+ repos that are part of quasar is unstructured and doesn't help the new user.
When a third part creates an extension or starter kit, it doesn't alwasy have to be moved into the quasarframework repo. The quasarframework/starter-kits/readme could have a list of the ones in the repo and the ones outside the repo, which would enable quasar create to use them all. Similarly for extensions.
This implies multiple levels of trust. The quasar team created it, the quasar team acknowledged that it is worthwhile to publish in the readme and everthing else.
Is your feature request related to a problem? Please describe. Currently the quasarframework repo is just a home page and a way to group other repos.
Describe the solution you'd like I would like to see the framework page describe the quasar framework, provide some details about the repo organization, such as noting that the main codebase is in the quasar repo, talk about starter kits. And --- have it's own issues, to allow suggestions about repo organization, structuring that is framework based and not quasar based.
For example, my view of quasar is
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Pinning 6 repos and then just listing all 50+ repos that are part of quasar is unstructured and doesn't help the new user.
When a third part creates an extension or starter kit, it doesn't alwasy have to be moved into the quasarframework repo. The quasarframework/starter-kits/readme could have a list of the ones in the repo and the ones outside the repo, which would enable quasar create to use them all. Similarly for extensions.
This implies multiple levels of trust. The quasar team created it, the quasar team acknowledged that it is worthwhile to publish in the readme and everthing else.