Is it (layer) cake: Thinking in content levels
summary
Argues that docs need three concrete layers — orientation decision implementation — and shows a working stack: high-level landing pages, a new middle decision layer for no-code users that maps use cases to integration pieces, and low-level quickstarts and API references. Implements embedded UI in guides and uses page CSAT with thumbs up thumbs down plus follow-up prompts and interviews. Reports clearer user flows, fewer frustrated comments, and faster problem resolution after adding the middle layer.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:47Thinking about users matters
- 3:14User frustration with docs
- 10:04Malls as docs metaphor
- 14:16Docs as user maps
- 15:21High-level content
- 18:30Low-level content
- 20:57Missing middle in docs
- 23:45Middle-level docs for no-code
- 27:15Three content levels
- 28:17Building the framework
- 29:24Q&A
related talks
39mBake a Little Documentation Love into Your Product
45mKnowledge Experience for a PLG Strategy
22mAudience, Market, Product
51mContent is King: How Contentful and CaaS are Changing
23mWriting for Developers: Take your Project Docs to the Next Level
27mContent Planning - How To Beat Writers Block For Now And Forever
21m[Eng Sub]if (extensible design) return "work life balance"
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing