Future Perfect Tense
summary
Claim: current WYSIWYG CMS workflows produce a single amorphous content blob that breaks across devices, so the fix is structured, reusable content. Practical steps: break pages into structured chunks, author short/medium/long headlines and SEO variants, preview at multiple viewports, expose content via APIs and markdown-friendly tools like GatherContent or lightweight CMSes (Perch/Drupal patterns). Surprising data: Netflix runs on ~400 devices, 17% of Americans access only by phone, and ~85% of Fortune 500 lack decent mobile support.
AI-written summary · about
chapters (55)
- 0:00Intro
- 1:37Footnotes
- 1:57This is me
- 2:12Future Perfect Tense
- 5:16Winchester Mystery House
- 7:44What would be cool
- 8:21Mobile versions
- 8:48The designers plan
- 9:13Fear of the unknown
- 10:36Spending freeze
- 10:47Internet Fridge
- 12:32Perfect Time Capsule
- 13:06The Future Perfect Tense
- 15:51The Black Hole
- 16:39The Desktop Site
- 18:14The Designer
- 18:53Playmobil
- 19:10Lego
- 19:51Content
- 20:42The Core
- 22:02Structured Content
- 22:19Orbital Content
- 22:57Mobile Myth
- 27:31Separate App or Site
- 28:21Web Content
- 28:46MultiDevice World
- 29:53Tom Coats
- 30:27Karen McGrane
- 30:49Kitchen Technology
- 31:22Hobs
- 32:39Content Everywhere
- 33:45Open Device Labs
- 34:42No one is ever happy
- 35:02Create structure
- 35:55Join them together
- 36:19Netflix example
- 38:22Do the hard work
- 39:07Platform agnostic
- 39:29Tools
- 39:46Perch
- 40:04WYSIWYG
- 42:42Inline Editing
- 43:24Our Tools
- 44:47Interpretive Dance
- 46:25Pixel Control
- 46:59CMS Makers
- 48:04Keys
- 48:38Chunks
- 49:37Support
- 50:26Multidisciplinary teams
- 50:48You are smart people
- 51:21Multiple pervasive user needs
- 52:11Be the advocate
- 52:56We build teams
- 53:14We build tools








