-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate migration to VitePress #174
Comments
I've been taking a look at the repo, it would be necessary to change the routes, the md files are mostly ok besides some alert syntax... just the blog and some other things that needs changes to make components in a way that looks good on Vitepress, the server part apparently isn't used as it only has this healthcheck also, I can help with vp migration. |
Hi @brenoepics 👋 Thanks for doing an initial investigation! I think the main migration of the documentation should be fairly straightforward, as you pointed out! Do you know how easy it would be to migrate the LandingPage of the documentation? The difficulties I still see are:
Feel free to continue the investigation, however for now, we are prioritizing some updates on the modules themselves and would potentially revisit the documentation migration in the summer! |
Describe the feature
As Docus is now abandoned (nuxt-themes/docus#1016), we will not receive any updates or security patches for our documentation software.
Therefore, we want to look into migrating to vitepress. For this, we need to estimate how long it will take and what the benefits would be, to decide if it makes sense!
Additional information
No response
The text was updated successfully, but these errors were encountered: