docs: rewrite Onboarding as 3-action flow, split reference companion#25
Open
abdout wants to merge 2 commits into
Open
docs: rewrite Onboarding as 3-action flow, split reference companion#25abdout wants to merge 2 commits into
abdout wants to merge 2 commits into
Conversation
Replace the v1 "1./2./3." structure with a sharper "Three actions" frame: prereqs (Pro/Max gate elevated), the three numbered steps, the team prompt, a verification checklist, escape hatches, manual fallback, daily entry points, slim Next links. Long-form architecture, scripts contract, and lessons-from-first-run move to a new Onboarding reference companion at content/docs/onboarding-reference.mdx, slotted in the Reference group of meta.json. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Reflects the reality on the ground after PRs #29/#30/#31 land the v2 scripts: onboarding.mdx: - Promotes 'irm https://kun.databayt.org/install | iex' to the recommended path (one paste, one UAC, three OAuth sign-ins) - Demotes Cowork-driven flow to "Alternative" — still works for Pro/Max users who want narration over a bare paste - Manual fallback updated to use databayt/kun raw URL (the codebase one is now tombstoned in databayt/codebase#2) - Adds 'doctor' to Daily entry points and 'maintain -Install' to the manual fallback chain - "What you end up with" mentions the scheduled task onboarding-reference.mdx: - Scripts contract table flipped: bootstrap, doctor, maintain are now Shipping (no longer 'Planned v2'); health.ps1 marked Deprecated; finish.ps1 reduced to 'Planned (alias for bootstrap)' - Source-of-truth URL changed from databayt/codebase to databayt/kun - Migration order section refreshed — 4 of 6 items checked off, fresh-VM test + team comms remaining Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Update — promoted single-paste to the recommended flow, demoted Cowork to alternative. This PR now reflects the reality of the merged-state world rather than the pre-merge world. The doc rewrite makes sense once #29 + #30 + #31 land. Suggested merge order: ``` If this PR merges before the scripts, the recommended single-paste line will redirect to a Doc changes in this update:
|
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.
Summary
content/docs/onboarding.mdxas a "Three actions" flow with elevated Pro/Max gate, post-flight checklist, and escape hatchescontent/docs/onboarding-reference.mdxcarries the long-form architecture, scripts contract, and lessons from the first real runcontent/docs/meta.json(Reference group, right afterclaude-code)Changes
content/docs/onboarding.mdx— rewrite (replaces the v1 "1./2./3." structure; fixes the%USERPROFILE%\projects\databayt\claim that didn't matchsync-repos.ps1's actual layout of~\codebase+~\oss\<name>)content/docs/onboarding-reference.mdx— new companion (187 lines)content/docs/meta.json— one line addedPlain markdown throughout (no custom MDX components introduced) — matches the convention of every other page in
content/docs/.Test plan
pnpm dev→/en/docs/onboardingrenders the 3-action flow/en/docs/onboarding-referencerenders the companiononboarding-referencein the Reference group/docs/<slug>links resolvepnpm buildpasses (Vercel preview will catch this)Out of scope
The v2 scripts (
bootstrap.ps1,finish.ps1,doctor.ps1,maintain.ps1) belong indatabayt/codebaseand are tracked separately. The reference doc's scripts contract table marks them as "Planned (v2)" so readers see what's shipping vs aspirational.Closes #24
🤖 Generated with Claude Code