Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request adds a new API examples page and a custom 404 page to the documentation, enhancing the developer experience by providing runtime API usage examples and a branded error page. The main changes are grouped below:
Documentation Enhancements:
api-examples.htmlpage to the documentation, which demonstrates how to use VitePress runtime APIs likeuseData()with live code examples and displays theme, page, and frontmatter data.api-examples.md.DBzYl0HB.jsfor the new API examples page, implementing the logic to render and display runtime data in the documentation.User Experience Improvements:
404.htmlerror page in the documentation, providing a consistent and branded user experience for not found errors.