Suggestion to move content collection to the transformation stage instead of the build stage

[hcdo7]

This is a possible suggestion.
In the current model, the transform() function is responsible for including a list of ids that is used to find the .md files and generate the necessary data in the generateBundle() step. Would it be possible, instead of id, to already create a list of contents in the transformation step, allowing the flow to have already undergone a certain transformation at the time of compilation in more complex cases?
One case that I think could be simplified with this approach is in dynamic routes, as noted in issue #30 .

I'm not very familiar with vitepress yet, but I'd be happy to contribute a PR related to possible approaches to this workflow change if you think it makes sense.

[okineadev]

Yes, it would be great if you could implement it manually (not 100% using AI, even Claude), I could sponsor you for that!

The problem with vibe-coded PR's is that AI makes unnecessary unsolicited changes, often minor ones that you don't want to waste time fixing, so you need to make PRs with a Minimal-as-Possible-Diff (i.e. before committing changes, review the diff and undo changes that are not needed in order to have a clean commit without unexpected changes or garbage, this is very useful even if you are working on the project yourself) that can be easily reviewed, understood, and merged instantly even without additional corrections.

Then some big projects that need Dynamic Routes support will switch to using this plugin

If you want, you can do it, you can look at this PR for more info - #80

I would be very grateful if you could help implement this functionality!