Mitar

Hm, I was thinking that we could merge my work with your existing work somehow? Also the tracker work and so on. We should discuss how should this be done....

Published repository [here](https://github.com/meteor-vue/blaze-integration) and on Atmosphere under `vuejs:blaze-integration`.

I would suggest we just keep iterating on v3 with those changes.

True.

Integration has been finished and now Tracker and Vue reactivity work together. See these repositories for examples and instructions: * https://github.com/meteor-vue/guide * https://github.com/meteor-vue/todomvc (We still have to see how to...

I would suggest we force push things to `gh-pages` branch, each version into its own sub-directory. We always clone existing branch, regenerate for a particular version, commit-amend, and force push.

Can you elaborate?

Yes, this sounds reasonable. Pull request welcome.

But that will probably make the link a non-single-page-link and will force the browser to reload the whole app? It [seems](https://github.com/vuejs/vue-router/blob/dev/src/components/link.js#L66) one would have to do something like: ```js router.push(router.resolve(...))...

I tested it, it reloads the page. I made [this app have a link from Blaze](https://github.com/meteor-vue/guide). I will make a Blaze template to resolve this.