Repository navigation
feat(site): add illustrated product tour and practical guides - #372
Merged
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.
Srcly now has an illustrated product tour and a practical user guide. Real app captures connect the repository map to source inspection, symbol references, and data-flow evidence.
What you'll see
Proof
The landing page shows the real app and a direct setup action.
The guide gives product discovery and first use separate entry points.
The case study connects a real self-inspection scan to the map, ranked list, and source witness.
Mobile readers can search the guide and open Topics without shifting the article.
Search highlights its match and links to the section that contains it.
Readers can enlarge app images and inspect source details without leaving the guide.
pnpm -C site buildpasses typecheck and creates static HTML for the landing page and eleven guides. All five site browser tests pass. They check static content, local links and images, screenshot zoom and keyboard close, section-linked search, mobile navigation, and copy feedback.The screenshots come from a local Srcly run at revision
653037aa, using public source and checked-in fixtures. The data-flow capture keeps its real Partial result. A separate content review checked commands, source links, report artifacts, and outcome names against code and real CLI output.Limits
Screenshots show a fixed source revision. The website does not run repository analysis. Source changes remain in the stack until review; the built site deploys separately to GitHub Pages.
Stack: Srcly public site, layer 2 of 2
This slice: Illustrated product tour, design decisions, expanded task guides, and documentation interactions.
Why it is its own layer: The first layer establishes the static site and deployment. This layer adds real product evidence and a deeper guide.
Full story: #371