Is it possible to speed up redeploy in v3?

[gitFoxCode]

Hi, I have a website with ~1,000 markdown files. I use nuxt generate to create a static site and serve it with Nginx. The problem with this approach is that changing a single Markdown file or anything else requires regenerating all the files, which takes a long time. Is there a way for nuxt generate to cache files and only regenerate the ones that have changed? Or, if only the Markdown files have changed, is it possible to update them in a database without having to regenerate everything?

[yudin-s]

With nuxt generate, the output is a static snapshot, so there is no built-in only-regenerate-the-changed-markdown-page mode comparable to ISR on a running server.

The options are mostly architectural:

1. Keep static hosting, but cache build artifacts in CI so unchanged dependencies/content parsing work is reused as much as possible.
2. Split the site into smaller deployable sections if the content tree has natural boundaries.
3. Move from full static generation to SSR/ISR for pages where content changes frequently.
4. Put the content source outside the app build and fetch it at runtime, then cache aggressively at the server/CDN layer.

For an Nginx-served static site, changing one markdown file still means the generated HTML/search/navigation payloads may need to change too. Navigation, search indexes, previous/next links, tag pages, and listing pages can all depend on more than the single file, so a safe incremental generator has to understand that dependency graph.

If redeploy time is the main pain, I would first measure whether the time is spent in content parsing, prerendering routes, image processing, or CI install/build setup. The best fix depends heavily on which phase dominates.