-
Notifications
You must be signed in to change notification settings - Fork 38
docs: Improved Welcome and Quick Start pages for clarity, structure, and onboarding UX#546
docs: Improved Welcome and Quick Start pages for clarity, structure, and onboarding UX #546hashirshoaeb wants to merge 12 commits into
Conversation
...g UX - Remove Welcome from sidebar (root pages conventionally hidden) - Add product description, prerequisites, and nav cards to Welcome page - Add scope statement, prerequisites, and Installation heading to Quick Start - Wrap steps in <Steps> component; use <Tabs> for install method and app type - Add "Install with AI" tab with copy-pasteable LLM prompt - Remove shorebird CLI help output dump; use `shorebird doctor` instead - Add terminal restart instruction before PATH verification step - Fix passive voice, typos, filler sentences, and duplicate welcome messages
hashirshoaeb
commented
May 27, 2026
There is build error. I'll push the fix.
hashirshoaeb
commented
May 27, 2026
Update: code is formatted and build successfully.
hashirshoaeb
commented
May 27, 2026
Hey @tomarra, PR is ready to be reviewed. :)
@nickshorebird
nickshorebird
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Nits otherwise.
@AbhishekDoshi26
AbhishekDoshi26
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rest looks good, just some small changes :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be included. You can add this after the successful installation note.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've considered including the output, but I'm leaning against it for a few reasons:
the help text can change between CLI versions (creating maintenance overhead), and users can always run shorebird --help to see the latest commands. This is also consistent with how most modern CLI tool docs handle it (e.g., Vercel, Flutter).
That said, I'm happy to add a short line like: "Run shorebird --help to see all available commands." this acknowledges what's available without duplicating content. Would that work for you? But If you think it is still worth it, I'll revert and add back.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can include the shorebird --help command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pushed.
... in Quick Start guide
Uh oh!
There was an error while loading. Please reload this page.
Status
READY
Description:
Summary
Rewrites the Welcome (
/) and Quick Start (/getting-started) pages, takinginspiration from Vercel, Next.js, and Flutter docs, and applying Google's
Technical Writing One principles.
Welcome Page (
/)Added
immediately understand what the product does
Code Push, and CI Integration
Fixed
/pages are conventionallyhidden from navigation
expectations (ref)
"Reach us through any of these channels"
(ref)
Quick Start Page (
/getting-started)Added
(ref)
## Installationheading to anchor the steps section in navigationFixed
shorebirdCLI help output — unnecessary;shorebird --helpand
shorebird doctorserve this purpose bettershorebird doctor)— the PATH is not reloaded without it
<Steps>component forclear visual sequencing
<Tabs>for conditional steps:(ref)
descriptionfrontmatter from "The easy way to get started withShorebird" to "Install Shorebird and push your first patch."
Further Improvements (out of scope for this PR)
the docs should focus on Shorebird-specific content
embedded per feature in the relevant doc page