In this four-part series, we’re going to cover how to go about making a PHP app benefit from the use of ReactJS components both server and client-side. The case for this is, for example, if we have a Wordpress or Drupal CMS we want to keep around for it’s content management functions, but want to extend with new and modern functionality.
- SEO: Search engines should be able to crawl and index our content. No need to implement/pay for a pre-rendering service to achieve this.
- Performance: A pre-rendered page can be cached server-side and provide a snappy user experience. React hooks itself up once the page is served and takes over the rendering of it’s components based on user interactions.
- Usability: A user is be able to bookmark the current state of the page and is able to return to it or share it.
- Maintainability: Sharing code between the server and the browser allows for a smaller code base, which is easier to keep healthy.
For these reasons, just adding React components to the existing user interface of our CMS would prevent us from reaping the full benefits, even though it would still provide our application with the reduced development times, maintainability and faster response time that React brings to the table.
This post assumes some basic familiarity with the following:
The goal of our brave little sample app is to connect to Github’s API and fetch a list of developers and display their username and avatar. We’ll also provide a link to their Github profile page and show a simple back and forth pager at the bottom.
The series will be spread as follows:
- Part 1: React components
- Part 2: Router configuration
- Part 3: Server-side rendering
- Part 4: Rendering from PHP with dnode
I’ve created a repository with the finished app so you can download, analyze and tinker with it as you read along. Please be gentle, it’s my first attempt at a coding post+repo! You can find it at this repo.