Clarification using Starter Kit and Vue Cli3, needed please
-
@nothingismagick I agree with @Ben-Hayat in the sense that “Starter Kit” to me usually means something to train with and is preferably not to be used for Production quality coding.
-
How about “Core Kit” or “Base Kit”. It’s not really just about the CLI. It’s about “beginning”, “getting going”, etc… From there, you can do more including building out to other app types (i.e. SSR, PWA, etc.)
Scott
-
@s-molinari said in Clarification using Starter Kit and Vue Cli3, needed please:
How about “Core Kit” or “Base Kit”.
That’s really what CLI does. Starter Kit, Core kit, Base Kit and etc. are all good, but people “immediately” relate to CLI and what it does. So it’s best to stay with the standard terminologies to reduce confusions, mainly for newcomers. This is important, because with many libraries out there, new users spend a few minutes to check each out and as soon as they see something that looks odd, they disqualify it. Quasar is an excellent and well thought out product and deserves the attention it should get. And that’s where my main post was all about.
-
I agree as well. Ut really is Quasar CLI and it can do more that just get you started. In fact, it refers to itself as Quasar CLI in the version call:
Example usage $ quasar <command> <options> Help for a command $ quasar <command> --help $ quasar <command> -h Options --version, -v Print Quasar CLI version Commands init Create a project folder dev Start a dev server for your App build Build your app for production clean Clean all build artifacts new Quickly scaffold page/layout/component/... vue file mode Add/remove Quasar Modes for your App info Display info about your machine and your App serve Create an ad-hoc server on App's distributables help Displays this message -
That’s really what CLI does. Starter Kit, Core kit, Base Kit and etc. are all good, but people “immediately” relate to CLI and what it does. So it’s best to stay with the standard terminologies to reduce confusions, mainly for newcomers.
But, that part of the docs is not just about the CLI. It’s about developing a core application. It’s about config, routing, build commands (yes with the CLI), app plug-ins, theming, etc. etc. 90% of it has nothing to do with the CLI, thus naming that part of the docs “CLI” or something similar makes no sense. I agree that “Starter Kit” could be named something different, something better. But definitely not CLI.
Scott
-
I am more or less thinking of how new perople would perceive it before they read the docs.
-
One other question on the starter kit.
Does the current starter kit work with Vue CLI 3 or the older one?
In the docs it says:make sure you have vue-cli globally installed
$ yarn global add vue-cli
or:
$ npm install -g vue-cliNode.js >= 8.9.0 is required.
$ yarn global add quasar-cli
or:
$ npm install -g quasar-cliDoes the docs need to be updated or does it mean, Quasar requires the older Vue CLI?
Thanks! -
The docs already state “Vue CLI 3 Plugin”
-
@genyded said in Clarification using Starter Kit and Vue Cli3, needed please:
The docs already state “Vue CLI 3 Plugin”
That is if you want to go the route of Vue CLI3 Plugin and NOT the Starter Kit:
Vue CLI 3 plugin
Make sure you have vue-cli 3.x.x:
vue --version
If you don’t have a project created with vue-cli 3.x yet:
vue create my-app
Please take a look here:
https://quasar-framework.org/guide/index.html -
@hawkeye64 Can you tell me more about your feelings regarding the “onboarding” process. This is an aspect of our communication with the devs that we really want to be succinct, but also informative. Any feedback is greatly appreciated!
-
Hi;
Although you asked hawkeye64 to give you some feedback, I’d also like to offer my two cents, to make Quasar a first class framework especially for new users getting started.When I was looking at different libraries, Vuetify was on the top of my list. the main reason was for the their great "style " of documents, samples, being able to test the samples online and copy a working sample to our code. This provides confidence to the new user and not to get intimidated. like https://vuetifyjs.com/en/components/badges
Quasar has a lot more into it, so to start off, it’s more complex and not having seamless docs, people can easily shy away from it. I took the time to read the docs to appreciate the power and richness of Quasar, but that’s only 5% of new users.
Hope this helps.
-
so to start off, it’s more complex
That impression is the one we need to somehow avoid, because it isn’t true.
Scott
-
Hmm…I was just about to suggest another name for that part of the docs and it looks like Razvan changed it already 3 days ago. Now it is “Quasar CLI” and now that I see it there, I can go with it.
I was about to suggest something like “Developing a Core Project” to go with the other “Developings” below it.
Scott
-
Scott, I still see “Starter Kit”
https://quasar-framework.org/guide/index.html
https://quasar-framework.org/guide/app-installation.htmlAm I missing something?
-
Maybe do a Ctrl + F5?
Scott
-
@s-molinari said in Clarification using Starter Kit and Vue Cli3, needed please:
Maybe do a Ctrl + F5?
I had done that before I posted. No need to make fun of.
Docs Still shows the old stuff. -
Not making fun. Just a humble smile.
Are you looking at the version 17 docs?
Scott
-
-
Ahhh…I see what you mean. Thanks for the screen. A picture says a 1000 words.
I was talking about the menu on the left. That now has “Quasar CLI” instead of “Starter Kit”. Maybe there needs to be more thought put into the docs on this too.
Scott
-
Yes, I noticed the menu first, but all the right hand contents are still referring to starter kit.
Also, the need o fix the Vue CLi installation syntax to CLI 3.
