The Story of ReScript's Documentation Platform
summary
Consolidates three legacy sites into a single Next.js project, migrates all markdown, and doubles down on design with Tailwind and a public Figma process. Hooks in anonymous analytics and Ahrefs, adds site search and a syntax lookup tool, and proves value with Hacker News traffic spikes and steady growth. CI checks internal links and enforces 100% compilable examples, provides a version toggle plus redirects, and offers an automatic migration command to move old Reason/Bucklescript content to ReScript.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:20Context
- 2:05Elevator Pitch
- 5:22React Component
- 6:11Other Features
- 9:49Target Group
- 12:03Product Context
- 12:24ReScripts History
- 14:27Why ReScript
- 15:05Language Philosophy
- 15:15Lean Development Process
- 18:22Unified Documentation
- 18:55Simplified Documentation
- 20:30Analytics
- 22:07Website Stats
- 23:20CI Testing
- 24:57Redirects
- 26:57Look Up
- 27:41Syntax Lookup
- 30:15Community
- 31:50Contribution Sites
- 32:46Wrap Up
- 33:26QA
related talks
24mHow to prevent a rewrite
13mGateway to React: the react.dev story
40mFrom resistance to adoption: navigating the challenges of docs-like-code
42mEngineering Documentation
25mWhat’s not to love about Reason?
32mSwitching from Sphinx to Markdown
26mWhat you get when you invest Non-Docs time in Docs tools
30mDesigning with React