‘PWA’ Progressive WordPress Applications
summary
Shows a concrete WordPress PWA built for a real site: adds a dynamic manifest via functions.php, registers a service worker and fixes its service worker scope by altering headers or placing sw at the root, and uses Cache API strategies. Uses workbox + webpack to generate hashed cached assets, implements offline comment queuing and the native Web Share API, requires HTTPS and checks browser support. Lighthouse score starts at 27 and initial load ~6s, then improves after these changes.
AI-written summary · about
chapters (20)
- 0:00Introduction and background
- 2:16What are PWAs and why they matter
- 6:37Auditing with Lighthouse
- 8:01Key PWA requirements
- 9:30Adding to home screen
- 12:29Dynamic manifest in WordPress
- 17:17Creating a real user experience
- 18:19Service workers explained
- 21:12Service worker scope and fixes
- 23:43Caching strategies
- 25:31Caching files with Workbox
- 28:58Handling cache updates
- 31:14Webpack and Workbox setup
- 33:18Caching rules and hashing
- 34:51Native features integration
- 36:14Offline comment handling
- 37:44UI changes for offline state
- 38:50Sharing content natively
- 40:23Beyond service workers
- 41:30Final tips and Q&A
