Improved, clear documentation needed about create-vue HOT 6 CLOSED

@sodatea Some people feel entitled to our immediate attention when in fact they are not. Let's apprechiate they ejected
themselves and we can work on this on our terms.

from create-vue.

Yeah... thought so. Hmm... Might be time for me to jump ship (not to Vite, but another framework altogether).

from create-vue.

Just for the record:

• I didn't close this issue because I agree that the documentation needs to be improved; I do appreciate your enthusiasm.
• I didn't reply earlier because I was too damn busy to think about this problem for the past few days. It's been too stressful.

from create-vue.

@LinusBorg No, I don't feel entitled to anything, but I do feel that the community has been fragmented quite badly since everything in the ecosystem at the moment is either in beta, RC, staging, unreleased, renamed, or not yet documented. It has been like this for quite some time now. I'm not blaming anyone, but that's the situation, which I hope will be improved soon...

You're welcome to appreciate it, but I haven't "ejected" myself from anything Vue-related. I only said I just might... speaking rhetorically.
It's interesting that people react (pun intended) only if someone gets a little bit angry. Otherwise, we don't seem to be getting much feedback from the esteemed developers/maintainers for many days or even weeks. I'm sorry, but just a couple of years ago the situation was much more engaging, as far as I remember.

@sodatea Thanks for the heads up, I really appreciate it!

from create-vue.

It's interesting that people react (pun intended) only if someone gets a little bit angry.

That's absolutely toxic mentality.
What can you get from doing this aside from making me feel guilty and become even more burnt out during my holidays??!

Otherwise, we don't seem to be getting much feedback from the esteemed developers/maintainers for many days or even weeks. I'm sorry, but just a couple of years ago the situation was much more engaging, as far as I remember.

It is an unrealistic expectation, especially in the OSS community.

In case you don't know, guaranteed response time is a paid service in the real world. It costs real money.

from create-vue.

As for my personal priority queue, here's the background:

• Unlike create-react-app or @vue/cli, this project is merely a scaffolding tool. All the actual bundling, type checking… are done by other tools such as Vite or vue-tsc, etc. So I don't think there's much to document here; Vite has its own documentation.
• The usage of this tool, and many parts of the logic behind the technical decisions are already covered in the new Vue documentation (staging.vuejs.org), which will become the default on Feb. 7th. You don't have to look at this repository to get more info.

So, my focus in the short term would be:

1. Improve the tool itself. It's already very minimal. So I'm gonna improve the prompt, add more descriptions to each question, and maybe i18n;
2. Improve the visibility of this tool: integrate it into create-vite's Vue template so that there won't be too much fragmentation in the ecosystem;
3. Ship Vue CLI 5 stable.

from create-vue.