A Case for Building Web Applications on WordPress
summary
Argues WordPress is a foundation not framework by showing concrete builds: a tiny plugin (Easier Excerpts) and a larger plugin that communicates with a third-party API, parses and discards malformed records, creates custom post types/taxonomies and templates, and uses batch processing with a job scheduler to chunk thousands of records to avoid server timeouts. Describes a working distributed system: an iOS patient app + WordPress backend via the REST API with heartbeat polling, notifications, auth and HIPAA-minded session handling — all implemented successfully.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:05About me
- 1:52Blog and Podcast
- 2:40How I got into WordPress
- 6:51Building web applications with WordPress
- 11:18Web site vs web app
- 12:44What are sites
- 13:49What are web applications
- 15:14What is a website
- 16:38Applications
- 17:34Application Architecture
- 18:46Application Sounds Big
- 19:55Plugin Extensions
- 20:45Easier Excerpts
- 22:43The Four Things
- 24:15API Key
- 26:25Job Scheduler
- 28:00Notification
- 29:17Notification System
- 30:21Taxonomy
- 34:42WordPress API
- 37:21Saving data
- 38:41Physicians web application
- 40:22WordPress is an option
- 41:30WordPress is not a framework
- 43:47Thank you
- 45:10How do you learn
- 46:13Resources
- 47:27Self Learners
- 48:48Developer Resources
- 50:24WP Sessions
- 52:04Is it possible to turn off WordPress
- 53:20Do I recommend doing an upgrade
