Developing a good editor experience with Microsoft 365 / Google Workspace
summary
Uses Word/Google Docs and Sheets (or SharePoint) as the CMS: documents map directly to URLs, sheets become JSON APIs, and a preview button sends the doc to an hlx.page preview bucket then to a live bucket on publish. Implements flat blocks with options (blocks cannot be nested), a block library plus auto-blocking to detect hero/metadata, metadata sheets for redirects/headers, and fragment embedding; deployed on hlx.live and Adobe Blog and works in production.
AI-written summary · about
chapters (11)
- 0:00Introduction to document-based authoring
- 4:29The content workflow
- 6:55Repository organization
- 9:47Document structure and elements
- 12:30Technical rendering pipeline
- 15:43Managing blocks and auto-blocking
- 24:34Metadata and global settings
- 29:31Themes and templates
- 31:59Working with fragments
- 36:11Summary and collaborative workflow
- 38:34Q&A session
related talks
46mAmbitious Editorial Experiences with Headless Drupal
32mBuild a Google Docs clone with CKEditor 5 & Vue.js Solution LIVE
42mHeadless CMS
46mHow We Built a Web Document Editor
31mUsing WordPress for an editorial team
08mHeadless - The Future of CMS Is Here
42mEngineering Documentation
15mEnhancing user experiences within Google Workspace