API Maybe: Bootstrapping a Web Application circa 2024 with Carlton Gibson
summary
Bootstrapped a working, interactive web app called pars using almost old‑school Django plus HTMX, Alpine.js, and Neapolitan crud view, hitting 12 weeks to a proof‑of‑concept and another 12 to an MVP inside a year and a half. The claim is that you can avoid JSON‑heavy APIs — 90% CRUD fits in single Django classes and template partials — and deliver a GVP, while admitting integrations, edge/offline needs, or richer client behavior may force an API later.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:24API-first versus server-side rendering
- 3:14Bootstrapping on a tight budget
- 3:57Locality of behavior
- 9:53Neapolitan CRUD views
- 12:21Django templates and components
- 13:45HTMX and template partials
- 16:30Alpine JS for interactivity
- 17:35Forms with Alpine and HTMX
- 19:00Roadmap: Async editing, performance, integrations
- 22:32Django’s evolution and future
- 23:37Q&A
related talks
21mBuilding maintainable Django projects: the difficult teenage years
26mDjango at
38mEmbrace the frontend revolution
21mHow not to end up your app to a hot mess of spaghetti Carbonara
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
39mAdventures in APIs
23mPros Do Vanilla - A Loosely Coupled Front-End
38mThe Front-End Future