Teach IPv6 notation and separate language API guides - #33
Merged
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
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.
The documentation previously mixed an address-format reference with installation and API details. Rewrite the entry page as an IPv6 introduction that explains hexadecimal groups, zero compression, prefixes, common addresses, ports, zone IDs, and embedded IPv4 through worked examples and expandable practice questions.
Move API usage into separate C, JavaScript, and TypeScript guides, with a development page for builds, testing, and publishing. Share the documentation stylesheet and navigation, and update the README, demo, and existing guides to link to the new pages.
Validation:
The TypeScript guide documents existing declaration/runtime differences. This change does not modify the parser or its declarations.