refactor: move the VSCode and tooling sections up the front page - #224
Merged
Conversation
The front page promised "the best tool support" in the intro but made readers scroll past three compiler-internals sections before showing any of it. Move Visual Studio Code Support and the Tooling Comparison Table, as a block, to just after the Standard Library section. The page now reads: what you get (library, tooling), how it is engineered (compiler architecture, performance, optimization), and who is behind it (community, JVM, funding). Pure move: no content changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The front page promises "the most extensive standard library, the most detailed documentation, and the best tool support" in the intro, but a reader had to scroll past three compiler-internals sections before seeing any of the tool support.
This moves Visual Studio Code Support and the Tooling Comparison Table — as a block, since the table's LSP row is the VSCode section's punchline — to just after the Standard Library section.
New section order:
The page now reads in three movements: what you get (library, tooling), how it is engineered (compiler architecture, performance, optimization), and who is behind it (community, JVM, funding).
Pure move — no content changes (136 insertions, 136 deletions),
<hr>separators kept intact. Verified withnpm run build.🤖 Generated with Claude Code