Improve docs regarding Nuxt.js compatibility

[alvarotrigo]

Regarding the conversation in the issue #6, we need a way to clarify how to use the vue wrapper when using it together with Nuxt.js.

Any help will be appreciated!

[dobromir-hristov]

From what I am understanding, we need a guide in the docs on how to import Fullpage as a nuxt plugin and set it as ssr:false?

[alvarotrigo]

@dobromir-hristov whatever you think it is necessary to avoid people opening issues like this one: #6

[dobromir-hristov]

Will do.

[dobromir-hristov]

I played around with this and here is what I have.

1. If we define the plugin with ssr:false in the plugins definition, it works, but gives out a warning, saying the dom has changed. This is normal as the plugin is bootstrapped after the dom has rendered on the server side.
2. If we define the plugin as normal, it errors out because we import full-page directly, which accesses the window object. I did try to wrap it in a dynamic import so it only gets imported on mount, but I am getting lots of errors there.
3. Using the <no-ssr> component works, but then the whole slot of the full-page component is gone, meaning your SSR website will be empty to crawlers, which defeats the purpose of SSR.

[alvarotrigo]

Thanks for that!
What are your thoughts on it then? Should we go for the 1st option?

[dobromir-hristov]

Think so. Easiest to do. Best case scenario would be to load everything on mounted so it doenst break. Also could use process.browser but I could not make it work like that.

[alvarotrigo]

Sounds good to me!
Please feel free to commit a PR with your proposed solution.

[alvarotrigo]

Merged in 0.1.0!

[vaso2]

Here's Nuxt module for doing exactly the same thing as in docs, but easier - one line in nuxt.config.js. Still, I hope that you'll return to the underlying issue of SSR compatibility someday.