vitepress

how are you thinking this will be deployed and how will developers initially integrate this? ie is this a language-level library, or an internal service in a docker container to deploy? one idea, is vitepress (vitepress.dev) has a local search engine, it would be cool to have moss integrated in that project, https://github.com/vuejs/vitepress

There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548 Given that version 1 landed as "VitePress" they probably decided to keep the name. > I initially gave VitePress a different name because I wanted to be able to explore a different architecture without worrying about backwards compat. After shipping the vuejs.org with VitePress, I believe VitePress is flexible enough to be a full replacement of current VuePress while offering better DX and better performance. > ... > I think we should ship VitePress stable as VuePress 3, but I am open to potential questions and concerns. > Pros: Less confusion in the long run. There will be just one officially maintained SSG with better DX, better performance, and customization that fully aligns with standard Vite-based Vue apps. > Cons: Potential confusio

Consider Nuxt instead of Vuepress/Vitepress. If you want the built-in theme in Vitepress, it's great, but if you want to make your own, using Nuxt with the Content plugin is probably better. I found the strong separation between theme and content to be too great, and if I have a docs SSG site using Vitepress and a webapp SSR site using Nuxt, I can't share themes easily anyway. At least that was my conclusion starting with Vitepress, and ending up with Nuxt 3. https://nuxt.com/ https://vitepress.dev/ (they haven't decided if they are going to replace Vuepress or not: https://github.com/vuejs/vitepress/discussions/548)