docs(readme): add workbench plug above the fold#196
Merged
Conversation
The Workbench is the fastest way for a first-time visitor to see what locus actually does, but the only mention was a single word in the nav row pointing at the repo source directory. Surface it as its own CTA right below the nav so it's hard to miss, and switch the nav entry to the public docs page instead of the in-repo workbench/ directory. Signed-off-by: Federico Kamelhar <federico.kamelhar@oracle.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
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.
Summary
Surface the Workbench prominently at the top of the README. Before this PR, the only mention was a single word in the centered nav row, linking to the in-repo
workbench/source dir. After: a dedicated CTA right below the nav, with a one-line pitch and a direct link to the Workbench guide. Also fixed the existing navWorkbenchentry to point at the public docs page instead ofworkbench/.Diff
Test plan