docs: migrate to vitepress #2735
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Live Preview ready!
|
|
@LiamEderzeel As I also commented on #2692 (comment), Nuxt I18n is the Nuxt ecosystem. so, Nuxt I18n docs should be created with Nuxt ecosystem. I apologies that I have to close your PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
#2692
❓ Type of change
📚 Description
I changed out Docus for Vitepress, so i18n had the same doc site as some other Nuxt modules for a more unified look. Resolves #2692.
I could use some guidance with implementing the deployment process. It's unclear to me how the current documentation is deployed. Vitepress provides a GitHub workflow example here.
📝 Checklist