You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, I have three small blogs due to different approaches. I have customized certain things in the theme design when downloading VitePress, for example, to include in these projects native web components that can be loaded as an html tag from a simple Markdown (.md) file, besides include TailwindCSS.
I am not interested in doing a Fork and would like to evaluate if it is possible to change the directory of the Vitepress documents (separating or decoupling the content of the mechanism) in order to have versatility and not having to copy in each project folder the theme and components (I mean, an srcDir different from root).
Describe the solution you'd like
One idea would be to allow the base directory of Vitepress to be different from the root, separating or decoupling the content of the theme or template (although I would understand if it is a matter of design).
What is wanted is to use the modified Vitepress theme on different blogs without having to copy it to each project (thinking in multi-project of content)
Describe alternatives you've considered
I have tried to apply on each of the three Vitepress blogs with the custom theme ( just that it can lead to theme desynchronization).
Another way is to have every blog under root folder and change srcDir in config.mjs according the blog selected.
Using a symbolic link but eventualy some errors occurs cause it resolves another path (e.g. ../../path) and finally doesn't work.
Is your feature request related to a problem? Please describe.
Currently, I have three small blogs due to different approaches. I have customized certain things in the theme design when downloading VitePress, for example, to include in these projects native web components that can be loaded as an html tag from a simple Markdown (.md) file, besides include TailwindCSS.
I am not interested in doing a Fork and would like to evaluate if it is possible to change the directory of the Vitepress documents (separating or decoupling the content of the mechanism) in order to have versatility and not having to copy in each project folder the theme and components (I mean, an
srcDir
different fromroot
).Describe the solution you'd like
One idea would be to allow the base directory of Vitepress to be different from the root, separating or decoupling the content of the theme or template (although I would understand if it is a matter of design).
What is wanted is to use the modified Vitepress theme on different blogs without having to copy it to each project (thinking in multi-project of content)
Describe alternatives you've considered
I have tried to apply on each of the three Vitepress blogs with the custom theme ( just that it can lead to theme desynchronization).
Another way is to have every blog under root folder and change
srcDir
inconfig.mjs
according the blog selected.Using a symbolic link but eventualy some errors occurs cause it resolves another path (e.g.
../../path
) and finally doesn't work.Additional context
The project with native web components that can be use in Markdown (.md) is: https://github.com/kaesar/onmind-cui
Validations
The text was updated successfully, but these errors were encountered: