The context
I was asked a few weeks ago to build a new page on a existing Wordpress site, in order to build a "shop area":

I am not very efficient to work on Wordpress template system (not my cup of tea!), and I have now a solid background around React frontend. I want to see how it can be possible to integrate, on an existing Wordpress installation, one React application to produce this particular need.
This article will explore the Wordpress/React options, then I will show you,Ā step by stepĀ how I have implemented a React application inside Wordpress. Finally I list you a few issues of the actual solution.
React with Wordpress?
ReactĀ is a popular javascript library that is generally used to build frontend application inside the browser. There is also a huge ecosystem of solutions around React (CreateReactApp,Ā NextJs,Ā Gatsby...) that help to use the library in a reliable frontend application.
WordpressĀ is a very famous CMS (Content Management System) that is still used by a lot of website. It's very easy to use for content editor, and it comes with lots of plugins.
There is multiple ways to mix Wordpress and React, but I will show you two examples here.
Build a javascript frontend using Wordpress REST API

Wordpress comes with a niceĀ REST API, and so it's possible to build a classic Single Page Application (using CreateReactApp for example) that consume this API. Wordpress is still used to write articles, but the website generated is driven by a different frontend application. It's theĀ Headless CMSĀ concept. This article is a great guide to achieve this:
Gatsby, a static site builder using React, have also a dedicated solution here:
This solution is a radical one for an already existing website, as you need to work on all existing content and transfert it to your new frontend solution. It's nice but it's too big for my own project.
Integrate a React application inside Wordpress
React isĀ onlyĀ a simple javascript library. It's not needed to build an entire site, you can just load the library on a part of your existing page. From theĀ documentation of ReactJs:
React has been designed from the start for gradual adoption, and you can use as little or as much React as you need. Perhaps you only want to add some āsprinkles of interactivityā to an existing page. React components are a great way to do that.
I have a few article disussing how to add a React application in a Wordpress site. This one show that, but for the administration panel:
I choose to go on this way because it's easier than rebuild the entire site, and it give me enough power to work like I want.
Integrate a React application in Wordpress
I want to build a page, visible by end-users, that is loading a React application showing some articles of a particular category from the Wordpress website in a grid layout. This section will guide you in the creation of this page.
The big picture
I will create a new wordpressĀ plugin. The plugin will show the React application if I use a specificĀ short-codeĀ in a page or an article. The React application will consume theĀ REST APIĀ of Wordpress to show the articles.
Build a dedicated plugin
To isolate the development I choose to work in a dedicated plugin. It is also possible to work in the themeĀ
functions.php
Ā but I think it's cleaner to have a specific folder for this project.In theĀ
plugins
Ā folder of your wordpress application, make a new folder namedĀ my-react-app
. Create inside the folder a php fileĀ my-react-app.php
.InsideĀ
my-react-app
Ā let's bootstrap a new Create React App project:npx create-react-app frontend
It will create inside the folderĀ
frontend
Ā a new React application using the classĀ Create React App.In the php file you can put:
<?php
/**
* Plugin Name: my-react-app
* Plugin URI: a url
* Description: A react application
* Version: 0.1
* Text Domain: my-react-app
* Author: Julien Bras
* Author URI: https://sidoine.org
*/
// First register resources with init
function my_react_app_init() {
$path = "/frontend/static";
if(getenv('WP_ENV')=="development") {
$path = "/frontend/build/static";
}
wp_register_script("my_react_app_js", plugins_url($path."/js/main.js", __FILE__), array(), "1.0", false);
wp_register_style("my_react_app_css", plugins_url($path."/css/main.css", __FILE__), array(), "1.0", "all");
}
add_action( 'init', 'my_react_app_init' );
// Function for the short code that call React app
function my_react_app() {
wp_enqueue_script("my_react_app_js", '1.0', true);
wp_enqueue_style("my_react_app_css");
return "<div id=\"my_react_app\"></div>";
}
add_shortcode('my_react_app', 'my_react_app');
You will end with this structure:
plugins
āāā my-react-app
āāā frontend
ā āāā README.md
ā āāā node_modules
ā āāā package.json
ā āāā .gitignore
ā āāā public
ā āāā src
āāā my-react-app.php
Good ! The basic setup is now working ! Let's test it!
Develop your React app
Go into theĀ
frontend
Ā folder. Start the development server by running:yarn && yarn start
ReplaceĀ
yarn
Ā byĀ npm
Ā if needed ! It will start a browser and show you this:
You can start by editing any of the file underĀ
frontend/src
Ā and actually develop your application.Build your React app
In order to use your application in Wordpress you need toĀ buildĀ it. I haven't found yet a solution to develop the application directly inside Wordpress. To build the output for Wordpress, I recommend to rely onĀ craco, a tool that can help to generate a single js file with predictable name.
First installĀ
craco
:yarn add @craco/craco
Then create aĀ
craco.config.js
Ā inĀ frontend
Ā folder:// craco.config.js
module.exports = {
webpack: {
configure: {
output: {
filename: "static/js/[name].js",
},
optimization: {
runtimeChunk: false,
splitChunks: {
chunks(chunk) {
return false;
},
},
},
},
},
plugins: [
{
plugin: {
overrideWebpackConfig: ({ webpackConfig }) => {
webpackConfig.plugins[5].options.filename = "static/css/[name].css";
return webpackConfig;
},
},
options: {},
},
],
};
Then edit theĀ
package.json
Ā file for theĀ build
Ā command:"scripts": {
...
"build": "craco build",
...
},
Comment theĀ
reportWebVitals();
Ā inĀ frontend/src/index.js
: (it prevent from having a single js file, dont forget to remove the import too !)// If you want to start measuring performance in your app, pass a function
// to log results (for example: reportWebVitals(console.log))
// or send to an analytics endpoint. Learn more: https://bit.ly/CRA-vitals
// reportWebVitals();
Modify the div id used inĀ
frontend/src/index.js
:ReactDOM.render(
<React.StrictMode>
<App />
</React.StrictMode>,
document.getElementById('my_react_app')
);
Modify the div id used inĀ
frontend/public/index.html
:<body>
<noscript>You need to enable JavaScript to run this app.</noscript>
<div id="my_react_app"></div>
<!--
This HTML file is a template.
If you open it directly in the browser, you will see an empty page.
You can add webfonts, meta tags, or analytics to this file.
The build step will place the bundled scripts into the <body> tag.
To begin the development, run `npm start` or `yarn start`.
To create a production bundle, use `npm run build` or `yarn build`.
-->
</body>
It's important to modify the id because by default theĀ
root
Ā is too generic for something we will include on a Wordpress page.Add also aĀ
homepage
Ā value in theĀ package.json
Ā (this will help for images):"version": "0.1.0",
"private": true,
"homepage": "/app/plugins/my-react-app/frontend/build/",
"dependencies": ...
Then test the build !
yarn build
It will generate aĀ
build
Ā folder insideĀ frontend
Ā (with a singleĀ script.js
Ā file):yarn run v1.22.4
$ craco build
Creating an optimized production build...
Compiled successfully.
File sizes after gzip:
41.86 KB build/static/js/main.js
518 B build/static/css/main.css
The project was built assuming it is hosted at /app/plugins/my-react-app/frontend/build/.
You can control this with the homepage field in your package.json.
The build folder is ready to be deployed.
Find out more about deployment here:
https://cra.link/deployment
⨠Done in 6.46s.
Test on Wordpress
Login on your Wordpress installation and activate theĀ
my-react-app
Ā plugin. Then in any page or article, use the short-codeĀ [my_react_app]
like this:
If you publish the page you will see:

It's a win š !
Use REST API
Inside the React application it's very easy to consume the REST API. I am actually using aĀ
API
Ā constant that point to the correct endpoint:export const API = process.env.REACT_APP_API || `${window.origin}/wp-json`;
So I am able to define the environment variableĀ
REACT_APP_API
Ā in theĀ .env
Ā file if I want to not use the wordpress on the same host (development mode).Then inside a React component, I can use aĀ
useEffect
Ā to populate aĀ items
Ā state:useEffect(() => {
let category = process.env.REACT_APP_CATEGORY;
const params = new URLSearchParams({
categories: category,
_fields: "id,title,meta,content,featured_media,fimg_url,tags",
per_page: 100,
});
fetch(`${API}/wp/v2/posts?${params}`)
.then((res) => res.json())
.then(
(result) => {
setItems(result);
},
(error) => {
setError(error);
}
);
});
Extra mile with Bedrock and Trellis
On this particular application I am relying onĀ Bedrock, a very good solution to develop on a Wordpress application with managed plugin, and onĀ Trellis, an other very food solution to facilitate the server provisioning and solution deployment (thanksĀ RootsĀ !, I hope to testĀ SageĀ some day !)
I have done the following to help me on this project
UsingĀ mu-pluginsĀ folder
Instead of deploying the plugin inĀ
plugins
Ā I am using theĀ mu-plugins
Ā folder so I am sure the plugin is always loaded. Does not need a plugin activation.Enhanced deploy procedure
I want to deploy only the builded version, and never theĀ
src
Ā folder. So each time I am deploying a new version I want to build my application and send only theĀ build
Ā folder.Inside myĀ
trellis/group_vars/SERVER/main.yml
Ā I have added:deploy_build_before:
- '{{ playbook_dir }}/deploy-hooks/build-before-my-react-app.yml'
This will add a script before build time.
Let's now create theĀ
build-before-my-react-app.yml
Ā file inĀ trellis/deploy-hooks
Ā folder:- name: Install npm dependencies
command: yarn
delegate_to: localhost
args:
chdir: "{{ project_local_path }}/web/app/mu-plugins/my-react-app/frontend"
- name: Compile assets for production
command: yarn build
delegate_to: localhost
args:
chdir: "{{ project_local_path }}/web/app/mu-plugins/my-react-app/frontend"
- name: Copy production assets
synchronize:
src: "{{ project_local_path }}/web/app/mu-plugins/my-react-app/frontend/build/"
dest: "{{ deploy_helper.new_release_path }}/web/app/mu-plugins/my-react-app/frontend"
group: no
owner: no
delete: yes
rsync_opts: --chmod=Du=rwx,--chmod=Dg=rx,--chmod=Do=rx,--chmod=Fu=rw,--chmod=Fg=r,--chmod=Fo=r
Thanks for theĀ Sage 9 build-before exampleĀ š
Conclusion and some concerns
As it's a React application I have some concerns:
- SEO: Google will probably not understand well my page...
- managing correctly CSS is tricky because the Wordpress page will inject some css classes (that you will not see in development mode usingĀ
yarn start
)
This project have been realized because the classic plugin we were using for this kind of page (WPBakery) doesn't come out-of-the-box with filtering and ordering capabilities. SomeĀ optionsĀ are available but limited in personalization. And it's fun to put some new tooling in a classic existing web application ! Get a try !