I’ve been following Wes Bos’ Advanced React course, and it’s got me thinking:
Would it be possible (and indeed desirable) to continue getting the benefits of Sage, but using a client-side, WordPress API-fuelled site architecture?
Perhaps using Styled Components, Next.JS, WPGraphQL and something like Prisma?
If the answer to this is “Yes”, would (slowly) moving Sage itself (rather than starting a new WP theme) towards this architecture be the best way to go about this?
My reasoning for this proposal is that WordPress itself (starting with Calypso and now Gutenberg) is clearly shifting from a “back-end first” (jQuery / JS and PHP) philosophy to a “front-end first” one (React w/ API).
The benefits are obvious, in the form of super-fast loading (given that only JSON for each page is being pulled down from the server, and in many cases pages are pre-fetched) and the ability to create complex UIs.
It’s my view that moving Sage in this direction, early and ahead of the curve, would future-proof the theme, for years to come, whilst also retaining the awesome community, who I’ve found (purely anecdotally) to be lightyears ahead of the wider WordPress theme development world, in terms of their outlook and the technologies / approaches taken.
What are others’ thoughts on this suggestion / proposal? Even simply, is this good or bad? Are there downsides beyond the learning curve?
I’d love to hear peoples’ thoughts.