Skip to content

chore(copy): drop "scaffold" jargon from user copy - #16

Merged
Codehagen merged 1 commit into
mainfrom
feat/concrete-language
Apr 19, 2026
Merged

Codehagen merged 1 commit into
mainfrom
feat/concrete-language

Conversation

@Codehagen

Copy link
Copy Markdown
Owner

Summary

"Scaffold/scaffolded" is conventional create-* vocabulary but doesn't say what HAPPENED. After ◇ Project scaffolded! the first-time YC-founder persona asks "...okay, what does that mean? did anything actually exist now?" "Project" is also generic where it should be specific — they didn't get a project, they got a help center.

Cold-path before/after

BEFORE                              AFTER
◇ Project scaffolded!         →    ◇ Help center ready!
--internal: Scaffold an...   →    --internal: Use the internal-KB layout...
--deploy: ...after scaffold  →    --deploy: Publish immediately after creation
--no-deploy: scaffold only   →    --no-deploy: Create only, don't publish

Where "scaffold" stays (correct vocab for audience)

  • Internal code comments (auth.ts, ship-it-now.ts, scaffold.ts)
  • Architecture/Contributing README sections (lines 443+)
  • helpbase preview --reset flag (sub-100 dev users, all internal tooling)
  • Test descriptions, error code names (E_CONTEXT_PREVIEW_SCAFFOLD)
  • Function names (scaffoldProject) — internal API

Test plan

  • pnpm --filter helpbase --filter create-helpbase typecheck — clean
  • pnpm --filter helpbase --filter create-helpbase test — 410 + 47 passing
  • Zero behavior change — copy-only

🤖 Generated with Claude Code

"Scaffold/scaffolded" is conventional for `create-*` tools but doesn't
say what HAPPENED. After `Project scaffolded!` a first-time founder asks
"...okay, what does that mean? did anything actually exist now?"
"Project" is also generic where it should be specific — they didn't
get a project, they got a help center.

User-facing string changes:
- Spinner: `Project scaffolded!` → `Help center ready!`
- create-helpbase flag descriptions (--internal, --deploy, --no-deploy)
- Login skip note + AI-generation fallback notes
- Token-budget retry hints (`after scaffold` → `from the new project`)
- README hero, features bullet, quick-start, H2 section heading
- Doctor command's package.json-missing fix message

Internal vocab kept where audience is dev/contributor:
- Code comments (auth.ts, ship-it-now.ts, scaffold.ts internals)
- Architecture/Contributing README sections (lines 443+)
- `helpbase preview --reset` flag (sub-100 dev users)
- Test descriptions, error code names (E_CONTEXT_PREVIEW_SCAFFOLD)
- Function names (scaffoldProject, etc.) — internal API surface

410 helpbase + 47 create-helpbase tests passing. Typecheck clean.
Zero behavior change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
helpbase Ready Ready Preview, Comment Apr 19, 2026 8:55am

Request Review

@Codehagen
Codehagen merged commit 54be00d into main Apr 19, 2026
4 checks passed
@Codehagen
Codehagen deleted the feat/concrete-language branch April 19, 2026 08:58

This branch was successfully deployed

1 active deployment
Preview — 467bdb32 Deployed Apr 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant