Documentation as an application: enabling interactive content tailored to the user
summary
Stripe reworks docs into an app: a React front end, a custom markdown superset called markdoc, and a ruby proxy that supplies primitive context variables. Examples include code samples that show a logged‑in user’s API test key, a checklist that persists state and auto‑checks based on account settings, and an integration builder checks backend that validates API calls. markdoc emits an AST serialized to JSON for static analysis and custom renderers, supports server or client variable resolution, and is mid‑migration with open‑source considered.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:18Legacy Architecture
- 10:46Why Not Markdown?
- 14:15Markdoc Syntax
- 14:43Machine Readability
- 22:42React Integration
- 25:11Why React?
- 26:54Handling Ruby Logic
related talks
42mTwo years of Markdoc: what we’ve learned about balancing developer and author experience
46mDocumentation That Runs: Bridging Code, Prose, and Interactivity
19mStreamlining API Documentation: Proven DocOps Strategies
46mSave a Dev, Write Documentation!
47mDocumentation Is Fine, Don't Worry
48mUseful and Beautiful Developer Docs and How to Create Them
51mWriting the Darn Docs
14mDeveloper Experience: Your documentation deserves more love!