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.
I'm facing difficulties managing multiple Slidev presentations. Currently, each presentation is a separate project, and I have to manually build and place the output in different folders. This approach becomes cumbersome as I add more slideshows, and it leads to unnecessary duplication of assets (e.g., 30-50MB per slideshow).
Describe the solution you'd like
I would like to implement a system similar to VuePress for Slidev, where multiple slideshows can be managed within a single project. Each slideshow should have its own route and be listed in a central interface. When a new slideshow is added, I should only need to run a build command to automatically update all the slideshows and routes.
Describe alternatives you've considered
Currently, I manage slides manually by building and moving them to a static folder, served by Nginx. However, this is inefficient and doesn't scale well, especially with duplicated assets across presentations.
I understand that this request might conflict with Slidev’s design philosophy. I’m willing to work on implementing this feature myself, but I’m not entirely sure where to start. Could anyone provide some guidance or suggestions on how to approach the design and implementation of this feature?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm facing difficulties managing multiple Slidev presentations. Currently, each presentation is a separate project, and I have to manually build and place the output in different folders. This approach becomes cumbersome as I add more slideshows, and it leads to unnecessary duplication of assets (e.g., 30-50MB per slideshow).
Describe the solution you'd like
I would like to implement a system similar to VuePress for Slidev, where multiple slideshows can be managed within a single project. Each slideshow should have its own route and be listed in a central interface. When a new slideshow is added, I should only need to run a build command to automatically update all the slideshows and routes.
Describe alternatives you've considered
Currently, I manage slides manually by building and moving them to a static folder, served by Nginx. However, this is inefficient and doesn't scale well, especially with duplicated assets across presentations.
I understand that this request might conflict with Slidev’s design philosophy. I’m willing to work on implementing this feature myself, but I’m not entirely sure where to start. Could anyone provide some guidance or suggestions on how to approach the design and implementation of this feature?
The text was updated successfully, but these errors were encountered: