Developing a Document Editor
summary
PandaDoc built a browser-based document editor from scratch using React. The talk covers architectural decisions that simplified development, problems and pitfalls encountered, generating PDFs on Node.js with Puppeteer, and some aspects of collaborative editing.
AI-written summary · about
chapters (25)
- 0:00New editor intro
- 1:11Why build a new editor
- 2:15Tech stack and architecture
- 3:21Event sourcing for docs
- 4:06Real-time CRDT collaboration
- 5:11Command and event flow
- 6:14Offline mode and queuing
- 6:55Optimistic UI changes
- 7:59Production error handling
- 8:42Conflict resolution strategies
- 11:53Key requirements and plugins
- 13:19Plugin architecture
- 14:25Error handling and UX
- 15:10Error tracking with Sentry
- 16:37Handling uncaught errors
- 17:43Gradual rollouts and flags
- 19:28Canary deployments
- 20:52Migration case study
- 21:13A/B testing complexities
- 21:55PDF generation challenges
- 23:21Headless Chrome for PDFs
- 25:28PDF rendering pipeline
- 26:53PDF library challenges
- 27:59Electronic signatures in PDFs
- 28:41Q&A
related talks
32mIn the Lab: Crafting the No-Code Editor POC
46mAmbitious Editorial Experiences with Headless Drupal
42mBuilding a reactive multi user document editor in ScalaJS
41mCreating collaborative editing UIs in React
44m"Creating an enterprise level editorial experience for D8 using React"
50mRich text editing with Draft.js
25mRich Text Editing with React
44mThe document’s journey from file to editing: processing 1,000 pages and not dying
