Docs

[yyx990803]

• 1.x -> 2.0 full change log
• 1.x -> 2.0 upgrade guide
• Update vuejs.org to reflect 2.0 changes
• High-level guide on using render in 2.0
• Documentation for the vue-server-renderer package
• High-level guide on using SSR in 2.0
• Documentation for the vue-template-compiler package
• vue-router 2.0 docs
• vuex 2.0 docs

[MeiYuanChen]

1.vue-server-renderer can solve 'seo' question?
2.Why not ’Guidelines Vue docs‘ inside vue-server-renderer?

[stylehuan]

I also need to server-renderer

[tong-zeng]

I wonder when we can have some documentations on vue server side rendering, thank you.

[rajibahmed]

@yyx990803 and @LinusBorg I would love to help you guys somehow ( docs or anything) ...

[chrisvfritz]

@stylehuan @sharp-c As it's listed, rest assured we will be documenting server side rendering. 😉 In the meantime, you might enjoy browsing these tests.

@rajibahmed If you'd like to help, we'd love feedback on the updated guide. Note that the transition system page is out of date, but everything else should be current with the latest beta.

[amirrustam]

@MeiYuanChen Regarding your SEO worries, I'm under the impression that Google search crawlers have been able to understand Javascript. They announced this change back in 2014: https://webmasters.googleblog.com/2014/05/understanding-web-pages-better.html

Google is the dominate search engine in the Americas, Europe, Middle East and rest of Asia. The only exceptions are Russia and China. More than half of search traffic in China flows through Baidu, which does not interpret Javascript with their crawlers. Yandex, is the dominate engine in Russia, and they started crawling Javascript in pages since last year: https://yandex.ru/blog/webmaster/21369

So server-side rendering for sake SEO somewhat depends on your site's audience, and hopefully the info I provided helps. With that said, any server-side rendering that returns pre-rendered plain HTML or text content can be crawled by searchbots. vue-server-renderer will help with this, and actually @yyx990803 mentioned SEO as motivation for Vue on server-side when the issue was brought up: #114 (comment)

[blocka]

Server side rendering is also needed for metatags (think facebook, etc.)

[amirrustam]

@blocka Yes. Also I came back to add that Google's crawlers are not full-proof JS renderers. They can't be fully be trusted yet to process your JS like you would think. Relevant: http://searchengineland.com/can-now-trust-google-crawl-ajax-sites-235267

So the new vue-server-renderer is greatly appreciated.

[elithrar]

As part of a migration to 2.0, I ported some 2-way filters on v-model to custom components with v-bind:value + emitting an input event - referring to http://rc.vuejs.org/guide/components.html#Form-Input-Components-using-Custom-Events

Two parts:

• I'd love to submit a simple "2 way filter to custom component" example, especially after having read the filter issue
• What isn't clear in the 2.0 changelog is why this approach doesn't work on 1.0 (which should also be documented, unless I've missed it, which is entirely possible)

[LinusBorg]

What isn't clear in the 2.0 changelog is why this approach doesn't work on 1.0

...because in 1.0 you have.sync, there was not need for this.

The "v-model on component" feature was developed for 2.0 to provide a mechanism that works a bit like ".sync", but only in cases where it makes sense (components emulating inputs with v-model behavior)

[elithrar]

@LinusBorg Oh, derp. Of course. Is there an upgrade guide WIP - not seeing anything in https://github.com/vuejs/vuejs.org/tree/2.0/src/guide - I'd definitely want to contribute/cover that.

[chrisvfritz]

@elithrar The closest thing we have to upgrade guide currently is in the 2.0 changes issue (see Other Breaking Changes and Upgrade Tips), but we will be building a real one prior to final release. 😃 It would actually be a great help if you could compile a list of things you'd like to see covered beyond what's already in that issue.

[LinusBorg]

It would actually be a great help if you could compile a list of things you'd like to see covered beyond what's already in that issue.

Indeed. We may be blind to some spots as we are too familiar with both versions ...

[elithrar]

OK, so here seems as good as any place to cover some additional migration guide requests:

• How to migrate from Vue 1.0's 2-way filters to a a custom component - this thread provides evidence of a need.
• A more comprehensive Lifecycle Hook guide (ready -> mounted caveats, given how common ready usage is)
• Replacing debounce with your own implementation - partially covered here but definitely needs to be clearly featured in the docs.

[dragonautdev]

@yyx990803 I'd love to contribute with Vue by generating a Spanish translation of the guides. Would this be something you would be interested in having?

Cheers!

[chrisvfritz]

@srodriki Definitely! See vuejs/v2.vuejs.org#308.

[zigomir]

vue-router 2.0 docs & vuex 2.0 docs are done, right? 🎉

[LinusBorg]

Yep.

[chrisvfritz]

@elithrar I'm currently developing those two-way filters to components examples you talked about. You mentioned you might have some good examples to share?

[elithrar]

@chrisvfritz - here's a quick example of how I'm using it - https://gist.github.com/elithrar/659f531e574c46bb3bb8114045b437dc - custom v-model component w/ debounce inside.

[LinusBorg]

your gist link gives me 404

[elithrar]

@LinusBorg fixed.

[chrisvfritz]

Thanks @elithrar! I just added a section on two-way filters specifically to the migration guide. Would love to hear your thoughts.

[elithrar]

@chrisvfritz Great write-up - breaking it down into Vue 1 -> Vue 2 steps does a great job of illustrating the changes required (and the benefits of the custom component approach).