primitiveshaun wrote this!
on Fri May 29 2020
WIP: check back later…
In the beginning
In my first incarnation as a freelancer there were three main frameworks that dominated Management of Content.
WordPress, Joomla and Magento. These respectively regarded as Blogging, CMS and E-commerce frameworks.
However. Somewhere, at some point WordPress fell into toxic goo and mutated into something so much more.
If you subscribe to the ‘Everything’s an Object’ approach to architecture then you start to see why.
The latest thing to give hard-working developers a good REST would be the Headless, or decoupled, method for creating WordPress websites.
Following some brief experiments with Gatsby and Next.js I discovered Frontity. Each of these like little stepping-stones, taking me closer to what I was looking for. A modern alternative to a trusty WordPress theme frameworks like Understrap?
Are they better than the traditional PHP methods? What’s the pros and cons of this paradigm?
☞ Part 1: A Frontity Theme
WordPress is installed to a subdomain (primitive.press) within a subdirectory of my root directory. SSL is forced at server level.
Frontity deployed to Vercel via a second domain(primitivedigital.co.uk).
This is not ideal as you have to transfer your domain to vercel, or point your domain name servers at vercel. I broke my GSuite setup.
SSL seems to be forced by default on Vercel.
No default handling of subdomains or canonical / non-www.
Think I’ve broke mail-forwarding – poss need MX records setting?
301 redirects seem easily done in the now.json, not sure about masked redirects.
Vercel/Github auto-integration blew up a few times CLI update / me adding image assets to the build / having
- WP REST Cache
- REST API Log
- Yoast SEO + REST API Head tags
- ACF + CPT UI + ACF to REST API
- WP REST Filter: Testing – has limitations
Q: Do I really need all of Bootstrap?
☞ Part 2: A WordPress Theme
Open source rocks! The best stuff is built, tried and tested by everyone, everywhere.