HTML Hypermedia APIs and Adaptive Web Design
summary
A working Kanban board demonstrates the claim: an HTML hypermedia API (rendered with microformats2) serves as both site and API, supports a rule set (only one-state moves; fixed back-transition rules) and requires no JS to perform core actions. A compact tiny Ruby client (about eight lines) consumes the HTML and continues to work after adding an archive state — one server-side line changes behavior across clients. The demo runs on Heroku and uses conditional lazy loading/aggressive enhancement.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:15Demo
- 5:25Rules
- 6:51Hypermedia APIs
- 8:45Template Engines
- 9:10HTML vs Jason
- 10:15Microformats
- 12:50Mobile first
- 15:05Progressive enhancement
- 19:20Adaptive Web Design
- 23:15Summary
related talks
27mHTML Hypermedia APIs and Adaptive Web Design
33mHypermedia – the solution for future web applications?
44mDesigning Hypermedia APIs
49mBring back the joy in web development with HTMX and Hypermedia-Driven Applications
36mReturn To Simplicity: Architect Hypermedia REST applications using Hanami + HTMX
01h 02mThird Way Web Development
40mHTML Re-imagined for the era of web apps
42mHypermedia - less hype, more media please