In the Frontity Architecture, WordPress is used as a headless CMS and we use Frontity to generate the final HTML that is displayed in the browser. This means that WordPress is used just for managing the content.
Frontity uses the WordPress REST-API to retrieve content and it then generates the final HTML
Frontity is also able to generate AMP pages with the same React code and CSS
This solution requires a PHP Server for WordPress and a Node.js Server for Frontity, as well as a new domain for your WordPress site as the main one will be used by Frontity, although you can use a sub-domain on your existing domain.
Some advantages of this approach:
Perfect fit for users with free wordpress.com blogs (e.g. myblog.wordpress.com)
Fastest server-side rendering (no useless WordPress request needed)
Some things to take into account:
Users need to change their WordPress domain
A Node.js server to run Frontity is needed (besides the WP one)
The server-side rendering is still slow if the WordPress site is slow, so it may need a cache layer on top
You will need to have one or two servers. At the very least, you will need a PHP server to run your WordPress and, in most of the cases, you will also need a Node.js server to run Frontity.
Node.js Server: In case you need this one, we would recommend to choose a serverless solution as it will make it cheap, easy and infinitely scalable.
You can check out our documentation how to deploy Frontity using
You will need to have two different domains, or a separate sub-domain on your existing domain:
One for the WordPress dashboard
And the other one to show the content retrieved from the API.
Point your main domain www.mydomain.com to Frontity, as it will be the domain your users will visit
Create a new subdomain for your admin dashboard, where you will access the UI to edit your content.
Using a subdomain will prevent you from buying a new one.
You could use, for example, wp.mydomain.com
If your hosting service doesn't provide cache, you may want to look for an additional solution (it could be a CDN), as it is key to improving your web performance.
Furthermore, according to our experience working with media publishers, we suggest that you to look for a service offering stale-while-revalidate, which is the best cache technique for this type of architecture.
If you use Vercel Now, the serverless option we recommend, you won't have to worry about these as it offers both things: a CDN and the stale-while-revalidate technique (or Serverless Pre-Rendering as they call it). This way, you won't have to add anything else.
Although there are some other ways to have a have a Frontity site running in production and the final solution may be different depending on the website, for the majority of sites we recommend:
Having the WordPress dashboard in a PHP server and Frontity in a Node.js Server
Keep the actual PHP server you are using for WordPress for your backend (or select a new one), and deploy Frontity using
now (Vercel), a serverless, cheap, infinitely scalable and easy to set up solution
Point your main domain www.myblog.com to Frontity and use a subdomain (wp.myblog.com) for WordPress
If you have selected Now as your Node.js server solution, you won't need to worry about this, as it offers a CDN and the stale-while-revalidate technique (or Serverless Pre-Rendering as they name it).