4 ms·

VitePress has a great development experience but we ended up running into several issues with our large (500+ pages) docs site with several broken pages with br

by mythz 3y ago

VitePress has a great development experience but we ended up running into several issues with our large (500+ pages) docs site with several broken pages with broken rendering, duplicate & missing content, etc. that took too long to identity and resolve that we ended up porting it to a .NET Razor SSG website [1] adopting a simpler "pure" .html static SSG pages with progressively enhanced Vue components for any markdown pages requiring interactivity. VitePress is a great choice if you just need a pure docs site, but if you prefer not to have your entire Website built with it, we're maintaining a "Vite Press Plugin" that can be used to add Blogs and other markdown powered features to Vue and React Vite Apps. It includes GitHub Actions to publish to a repo's GitHub Pages branch so the resulting static website can be hosted Free on GitHub Pages CDN as done for the Vite Press Plugin's introductory Blog Post [2]. [1] https://servicestack.net/posts/new-razor-ssg-docs https://servicestack.net/posts/new-razor-ssg-docs [2] https://press-vue.servicestack.net/posts/vite-press-plugin https://press-vue.servicestack.net/posts/vite-press-plugin

Kinrany 3y ago
Wouldn't it be faster to do the same but keep vitepress?
- mythz 3y ago
  Wouldn't what be faster?
  - Kinrany 3y ago
    Instead of porting to static .NET pages + progressively enhanced Vue, keep vitepress for static pages and replace dynamic parts with progressively enhanced Vue?
    - mythz 3y ago
      The issues with VitePress is what caused us to port our docs elsewhere. We had several broken pages with repeated and missing content which we spent a long time trying to workaround their SSR/SPA hydration issues by running custom js to try manually detect and resolve issues, but that started to become unwieldy having to maintain these hacks for several pages that we made the switch to abandon it and move to a cleaner C# Razor SSG .html pages that's progressively enhanced with Vue Components. We no longer have any rendering issues and now have full control over the entire SSG output that we're able to resolve any issues that we do run into.

by mythz 3y ago

Kinrany 3y ago

Wouldn't it be faster to do the same but keep vitepress?

mythz 3y ago
Wouldn't what be faster?
- Kinrany 3y ago
  Instead of porting to static .NET pages + progressively enhanced Vue, keep vitepress for static pages and replace dynamic parts with progressively enhanced Vue?
  - mythz 3y ago
    The issues with VitePress is what caused us to port our docs elsewhere. We had several broken pages with repeated and missing content which we spent a long time trying to workaround their SSR/SPA hydration issues by running custom js to try manually detect and resolve issues, but that started to become unwieldy having to maintain these hacks for several pages that we made the switch to abandon it and move to a cleaner C# Razor SSG .html pages that's progressively enhanced with Vue Components. We no longer have any rendering issues and now have full control over the entire SSG output that we're able to resolve any issues that we do run into.