Task
Add a no-code naming guide at `industries/nocode.md`. Depends on #180.
Why no-code naming is distinct
- Accessibility signaling — the name must say "you can do this without being a developer" without being condescending
- "Easy" trap — names that signal simplicity can feel toy-like. Enterprise buyers need to justify "no-code" purchases
- Builder/creator metaphors dominate — Bubble, Webflow, Airtable, Notion, Zapier. The "builder" territory is crowded
- Power vs simplicity tension — the name must say "powerful" and "accessible" simultaneously
- Visual/creative vocabulary — no-code tools are often visual builders. Design-adjacent naming works
Sections to cover
- Case studies: Bubble, Webflow, Zapier, Airtable, Retool, Glide
- Anti-patterns: "Easy[X]", "Simple[X]", "No-Code [Category]" — signals toy, not tool
- Territory map: Canvas/studio, flow/stream, building blocks/lego, assembly/compose
Before submitting
Read CONTRIBUTING.md and run `markdownlint-cli2 '**/*.md'` before pushing.
Task
Add a no-code naming guide at `industries/nocode.md`. Depends on #180.
Why no-code naming is distinct
Sections to cover
Before submitting
Read CONTRIBUTING.md and run `markdownlint-cli2 '**/*.md'` before pushing.