Repository navigation
feat(site): add public landing page and user guides - #371
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 a public landing page and eight user guides, modeled on Draftably's public site. The site is live at https://byronwall.github.io/srcly/.
What you'll see
Proof
The landing page explains local analysis and lets visitors try the labeled example.
The landing page fits a 390px screen without page overflow.
The guides have grouped navigation, search, and section links.
pnpm -C site buildgenerated nine pages plus the docs entry point and error page. All four site browser tests passed. They cover static guide content, local links, section anchors, example controls, search, reloads, and mobile navigation.The existing app browser suite passed 20 tests; one optional latency benchmark was skipped. A separate browser review checked desktop and mobile layouts, command copying, file selection, and console errors.
Limits
The treemap and terminal output use labeled example data. The website does not scan files; Srcly analysis runs locally. Deployment publishes
site/disttogh-pages; source changes remain in this PR until review.Stack: Srcly public site
What splits: A static public site and deployment, followed by an illustrated product tour and expanded user guide.
Why it splits: Review the site foundation separately from the product evidence, content, and documentation interactions.
Why this split: The first site can deploy alone. Splitting every guide into a separate layer would fragment one reading experience.