-
Personally, I don't care about the build times as they happen in a GH workflow [1] and the compiled sources get updated to Cloudflare Pages that's how [2] gets deployed.
[1] https://github.com/logdyhq/homepage/blob/main/.github/workfl...
[2] https://logdy.dev
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
Personally, I don't care about the build times as they happen in a GH workflow [1] and the compiled sources get updated to Cloudflare Pages that's how [2] gets deployed.
[1] https://github.com/logdyhq/homepage/blob/main/.github/workfl...
[2] https://logdy.dev
-
content
The file-based CMS for your Nuxt application, powered by Markdown and Vue components. (by nuxt)
-
There is a discussion related to naming on GitHub: https://github.com/vuejs/vitepress/discussions/548
> 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.
Given that version 1 landed as "VitePress" they probably decided to keep the name.
> ...
> 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 confusion in the short run, since there are probably a lot of tutorials / integrations targeting VuePress 1. Still I think with the recent Vue 3 switch, users won't be surprised with a major upgrade for VuePress.
-
content-wind
A lightweight Nuxt theme to build a Markdown driven website. Powered by Nuxt Content, TailwindCSS and Iconify.
Nuxt Content is a lot less opinionated. You'll have to build out most yourself. There are themes (https://github.com/atinux/content-wind), but last I checked, it wasn't simple to configure.
-
Nutrient
Nutrient – The #1 PDF SDK Library, trusted by 10K+ developers. Other PDF SDKs promise a lot - then break. Laggy scrolling, poor mobile UX, tons of bugs, and lack of support cost you endless frustrations. Nutrient’s SDK handles billion-page workloads - so you don’t have to debug PDFs. Used by ~1 billion end users in more than 150 different countries.
