-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add Additional Resources to ecosystem dropdown #1182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I agree that tooling could probably be more prominent, so I made a slight modification, adding these resources to a new |
LGTM. My only concern is the entire missing of Vue-templates now, with nowhere to be found throughout the docs. Also, with our docs often praised for being very newcomer-friendly, replacing it with only the most complex template might be – I don't know – a bit weird? |
We do, just indirectly. That same information is available in the Vue CLI readme, which we link to on the installation page.
While that template has the most complex build process, it's also (perhaps counter-intuitively) the one you're least likely to have issues with as a relative beginner, since it does so much for you out-of-the-box and is the best-documented. My experience is that absolute beginners will have a hard time with a build process, no matter what. If they've never used a build tool or module system, then probably every item in the Ecosystem dropdown below the For people who are at least a little more advanced, they often become frustrated with Browserify or the Does that make sense? |
Also a note for the future: I'm thinking we'll be able to replace the link to the Webpack template with one to Vue CLI 3, once that's out, since it will offer the same kind of simple dev experience, but hide away the stuff that looks complex unless you actually need it. |
<li><a href="https://vuejs-templates.github.io/webpack" class="nav-link" target="_blank">Webpack Template</a></li> | ||
<li><a href="https://vue-loader.vuejs.org" class="nav-link" target="_blank">Vue Loader</a></li> | ||
</ul> | ||
</li> | ||
<li><h4>Core Plugins</h4></li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also "Core Libraries" here sounds better since vue-server-renderer
isn't a plugin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Updated.
LGTM |
<li><h4>Help</h4></li> | ||
<li><ul> | ||
<li><a href="https://forum.vuejs.org/" class="nav-link" target="_blank">Forum</a></li> | ||
<li><a href="https://chat.vuejs.org/" class="nav-link" target="_blank">Chat</a></li> | ||
<li><a href="https://github.com/vuejs-templates" class="nav-link" target="_blank">Templates</a></li> | ||
</ul></li> | ||
<li><h4>Tooling</h4></li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, Tooling is a better header. Thanks for updating!
* Replace `true` with truthy (vuejs#1196) * Change "Registration" to "Global Registration" (vuejs#1192) * typos (vuejs#1191) * [Website]: Let menu to be above add (vuejs#1188) Signed-off-by: Bruno Lesieur <bruno.lesieur@gmail.com> * Fix: Demystified markdown logic (vuejs#1186) * Fix: Demystified markdown logic I have changes jsfiddle link with a similar jsfiddle. The difference between two jsfiddle is in javascript code, `marked()` has a comment mentioning its source as external library. This is important because it is easy to assume that `marked()` cmes from an external library instead of Vue, especially for a beginner. * make dependencies apparent in markdown example * Correct the heading tags (vuejs#1181) correct the opening and closing `h4` tags * Make the statement less definitive (vuejs#1190) * Make the statement less definitive * Reword the tip * add SG exception where kebab-case everywhere is also acceptable for components in templates * revise single-file components, with new example sandbox * Add Additional Resources to ecosystem dropdown (vuejs#1182) * Add additional resources to dropdown * reorganize ecosystem dropdown, adding Tooling * Move roadmap to News section of ecosystem dropdown * Update "Core Plugins" to "Core Libraries" * rename SG complex expressions rule to simple * rename SG complex computed expressions rule to simple * address SG question about coupled component names, fixes vuejs#1195 * fix SG typos, fixes vuejs#1194 * make it more obvious in SG that details can be expanded, fixes vuejs#1170 * Update custom-directive.md (vuejs#1198) I suggest add this params demo because i can not understand when i saw this part,i think other people will have the same confusion * clarified titles of SG priority D rules * Re-translate the arrow function tip
…) (vuejs#414) * Add Additional Resources to ecosystem dropdown (vuejs#1182) * Add additional resources to dropdown * reorganize ecosystem dropdown, adding Tooling * Move roadmap to News section of ecosystem dropdown * Update "Core Plugins" to "Core Libraries" * WebpackのTemplateをテンプレート、Roadmapをロードマップに
I visited vuejs.org for the purpose of visiting vue-loader documentation and noticed it wasn't listed. I feel it is a crucial aspect of developing vue and would suggest adding it alongside the ecosystem dropdown.
These three links didn't seem to fit the pattern of the other headers so I created another header. However, if others feel they can be nested under an existing header or one named differently (eg. - 'Getting Started'), I would be happy to make that change.
Thank you all for your great work around this project. I'm happy to help however I can.
Dave