@wolfiton said in Honest opinion and what can be improved in the docs:
It doesn’t have a step by step guide but it has this https://typescript.nuxtjs.org/, which made possible this post https://www.codegram.com/blog/nuxt-typescript-apollo-a-bumpy-road/ and also other developers that do real-world applications developed this further until it reached a point where it could be usable.
You can be the first framework that uses Vue for SSR to have a guide on how to integrate this stack for developers(Typescript codegen apollo). This will ensure that quasar may become a standard in the industry if you take out the pain from this process.
Also, Vue 3 is coming with typescript and that will be a game-changer and help Vue to be more testable, easier to read for others that review your code.
Also, my question is:
Did the quasar team ever wonder why there are so many nuxtjs examples on youtube, but very few quasar tutorials?
Thanks, @s-molinari for the follow-up
We can all agree that class-based applications are easier to test with jest than function-based ones.
Nuxt has a lot of modules and very detailed documentation when it comes to auth and middleware. Also when you first open their page you feel some sort of familiarity.
Another big advantage is the possibility to have just some pages static and the rest rendered with ssr.
So if you want to change this opinion then releasing a step by step tutorial created by the team of quasar with tests will certainly help change people’s views about what quasar can offer.
Also showcasing big companies that use quasar could be another good option to make it more popular.
It is good if you can improve that package and also integrating those stacks directly(typescript support codegen apollo unfetch) will certainly make it very useful.
PS: Quasar Team: Please take into account that jwt is old and should the replaced by paseto as state here https://developer.okta.com/blog/2019/10/17/a-thorough-introduction-to-paseto