🏗 Website: Tech Stack & Information Architecture

[ovlb]

There are some open questions we need to decide on:

• Do you we use something like Nuxt or an SSG like Eleventy with drop-in examples?
• How do we manage to build dynamic examples (looking at Reach, of course)?
• Shall the website include more sections than component documentation (think resources, integrating the blog …)?

And probably more that I miss right now.

[ovlb]

cc @marcus-herrmann

[marcus-herrmann]

@ovlb Nuxt can generate a mix between client-side and server-side, so I guess it's the way to go. But you're much more familiar with 11ty, so you could judge whether it is just as capable in that regard. If so, it's a matter of style, of how close to the Vue ecosystem the website itself should be build. If close, then Nuxt. But considering both 11ty's and Vue's flexibility, I assume it is not a must.

[ovlb]

@marcus-herrmann Nuxt will probably be easier to integrate with live examples and stuff. (After all, all the things are Vue components already). So it might be the safest bet to get something up and running without getting lost in a toolchain. :)

[marcus-herrmann]

👍