Is your feature request related to a problem? Please describe.
A VitePress "project" seems to have a single usage/purpose (per project) - e.g. MPA Site, or "online help" or "blog".
However this is not how documentation is mostly managed (well maybe except for demos) : there's one set of documents (e.g. Markdown content files) than will be used to produce several outputs from the same content: e.g.
an online help (SPA or MPA)
"single long page document" (for offline use, but split per language) ,
several PDFs (mostly per language split),
Simple HTML files/fragments for contextual help inside the application (so no header/navigation/anchors ).
To achieve the above with VitePress, one would need several separate Projects that share the same Markdown content.
Describe the solution you'd like
Have a "goal" or "target" section that would allow to configure inside the same project the issues mentioned above (even themes, base url,, etc. since they can different based on the output target).
Describe alternatives you've considered
https://asciidoctor.org/ and other similar systems allow all the above, but with VitePress is not seem possible for now.
Is your feature request related to a problem? Please describe.
A VitePress "project" seems to have a single usage/purpose (per project) - e.g. MPA Site, or "online help" or "blog".
However this is not how documentation is mostly managed (well maybe except for demos) : there's one set of documents (e.g. Markdown content files) than will be used to produce several outputs from the same content: e.g.
To achieve the above with VitePress, one would need several separate Projects that share the same Markdown content.
Describe the solution you'd like
Have a "goal" or "target" section that would allow to configure inside the same project the issues mentioned above (even themes, base url,, etc. since they can different based on the output target).
Describe alternatives you've considered
https://asciidoctor.org/ and other similar systems allow all the above, but with VitePress is not seem possible for now.
Additional context
No response
Validations