Docs at Weaveworks DX from open source to SaaS and beyond
summary
Weaveworks documents move from scattered markdown and WordPress into a Jekyll site backed by Built.io + Jekyll, with open‑source docs pulled from repo and CI-built preview URLs via Netlify. Product docs cover Flux + Scope + Cortex + Weave Net for the new Weave Cloud SaaS. Interactive learning uses Catacoda so users hit value immediately. Result: home loads drop from ~5s to <100ms, but builds are slow, CMS updates can go out of sync, and engineering‑docs coordination still needs a reliable notification flow.
AI-written summary · about
chapters (9)
- 0:00Introduction and thanks
- 1:47Starting point for docs
- 3:32Moving away from WordPress
- 7:30Pivot to Weave Cloud
- 8:53Website architecture
- 14:12Documentation structure
- 16:39Weave Online user group
- 18:21Current challenges
- 19:45Closing and hiring
related talks
42mEngineering Documentation
47mEngineering Documentation
36mIf you build it, they will come: Our journey to unified (and discoverable) docs
44mPushing documentation (so it doesn't hurt anymore)
26mWhat you get when you invest Non-Docs time in Docs tools
35mBuilding Docs like Code: Continuous Integration for Documentation
25mChanging The Game with Developer Experience
48mUseful and Beautiful Developer Docs and How to Create Them
