Skip to content

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

Merged
merged 4 commits into from
Oct 8, 2017

Conversation

fakefarm
Copy link
Contributor

@fakefarm fakefarm commented Oct 4, 2017

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

@chrisvfritz
Copy link
Contributor

I agree that tooling could probably be more prominent, so I made a slight modification, adding these resources to a new Tooling section. I've also reorganized the dropdown to follow the order that I think people might need these resources in their journey to learn Vue. I just want a couple other team members to sign off on this one first.

@phanan
Copy link
Member

phanan commented Oct 7, 2017

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?

@chrisvfritz
Copy link
Contributor

@phanan

My only concern is the entire missing of Vue-templates now, with nowhere to be found throughout the docs.

We do, just indirectly. That same information is available in the Vue CLI readme, which we link to on the installation page.

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?

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 Devtools will be confusing to them.

For people who are at least a little more advanced, they often become frustrated with Browserify or the webpack-simple template. We simply don't have as robust support for Browserify, so there are more bugs and fewer features. And webpack-simple actually requires knowing more about Webpack, ironically. 😄 If they want to use a CSS preprocessor, for example, they have to do quite a lot of work and know more about the Webpack ecosystem. The webpack template, on the other hand, describes in detail how to work with CSS preprocessors and doesn't require them to change any configuration. They just install the appropriate loaders and peer dependencies, e.g. sass-loader and node-sass.

Does that make sense?

@chrisvfritz
Copy link
Contributor

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>
Copy link
Member

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

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Updated.

@yyx990803
Copy link
Member

LGTM

@chrisvfritz chrisvfritz merged commit 5d934ab into vuejs:master Oct 8, 2017
<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>
Copy link
Contributor Author

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!

phanan added a commit to vuejs-vn/vuejs.org that referenced this pull request Oct 10, 2017
* 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
kazupon pushed a commit to kazupon/vuejs.org that referenced this pull request Nov 24, 2017
…) (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をロードマップに
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants