// the find
bstavroulakis/vue-wordpress-pwa
An offline-first SPA using Vue.js, the WordPress REST API and Progressive Web Apps
A Vue 2 + Vuex SPA that uses the WordPress REST API as a headless CMS backend, with service worker offline support. Built as the actual codebase behind fullstackweekly.com, so it's a real-world reference rather than a toy demo. Aimed at developers who want to decouple a WordPress site from its theme layer without abandoning the WP admin.
Ships both a service worker and an AppCache fallback (index-appCache.html), which was the correct belt-and-suspenders approach for offline support in 2017. The Vuex module structure is properly split by domain (category, page, learning-paths) rather than dumped in a single store. Includes SSR entry points (client-entry.js / server-entry.js) and separate webpack configs for client and server bundles — someone thought about SEO, not just SPA convenience. The Azure deploy.cmd and .travis.yml CI setup means the repo is genuinely deployment-ready, not just a local scaffold.
Hard requirement on Node v11, which hit EOL in 2019 — this will not build cleanly on any modern Node without patching. Vue 2, Vuex 3, and vue-resource are all deprecated or superseded; adopting this today means inheriting a full migration debt before you write a single line of your own code. The WordPress plugin list in the README (four separate plugins just to make the REST API usable) signals that the WP side is fragile and undocumented — break any one plugin and the API shape changes silently. No tests of any kind anywhere in the tree, which is a problem for something billing itself as a starter that others will fork and maintain.