This document discusses the headless approach to WordPress development. It begins with introductions and then outlines the agenda which includes: defining the headless approach, advantages like using any frontend technology, disadvantages like losing some WordPress capabilities, and a step-by-step process including installing WordPress configured for headless and building a PHP frontend app. The document promotes the headless approach as allowing WordPress to act as just a content management system with any technology used on the frontend, communicating via API.

1. How to create a WordPress not understanding
WordPress, so more on the headless approach.

2. Hi!
I’m Chris
Supposedly, I love PHP and WordPress, but can they really be loved?
You want to contact me? Write and perhaps I’ll answer:
/krzysztofozog

3. A few words about me
A Philosopher and a Developer in one… what’s worse is that it is documented by two diplomas
Although, more of a developer:
➔ I create Web Apps for more than a decade now
➔ I’ve created my first PHP app in 2004
➔ I’m addicted to clean code
➔ I am a technical leader at Codesushi
➔ I am a CodeReview aficionado

4. Agenda dzisiejszych warsztatów
1. The idea and essence of the headless approach
2. Advantages of the headless approach
3. Disadvantages of the headless approach
4. The headless approach step by step …
- Installing and configuring WP for the headless approach
- Front app in PHP
5. Summary

5. 1.
The idea and essence of the
headless approach

6. The essence of the headless approach
➔ Wordpress is treated just as an administration panel and a content
management system
➔ It communicates with an app presenting content via the API
➔ The app displaying the content may be created in any technology

7. Pattern
Frontend app Wordpress
REST API

8. 2.
Advantages of the headless approach

9. ➔ The possibility to use any technology on the front
➔ The possibility to include WP in a more advanced project (for example
consisting of a few interacting systems)
➔ The possibility to speed up the work thanks to a parallel approach
➔ The possibility to make it easier to work on “Legacy” projects

10. 3.
Disadvantages of the headless approach

11. ➔ Losing some WP capabilities, for example live edit
➔ Some plugins won’t work
➔ It’s not the “wordpress way”, so one has to consider
the lack of support for such an approach
➔ Sometimes we lose more than we gain

12. 4.
The headless approach step by step

13. Installing and configuring WP for the headless approach
For WP higher than 4.4 just install WordPress, the REST API is included in the suite
For a lower “legacy”, it’s necessary to install the WP REST API (http://v2.wp-api.org/)
During our workshop we will focus on the latest WordPress

14. Front app in PHP
➔ Although we can use any technology or framework, in our example we will use
the Symfony framework, the Guzzle library for polling the API, and Twig as a
template language
➔ Our app aims to
◆ Communicate with WP
◆ Download data
◆ Generate an HTML basing on that data
➔ We can transfer it to the field of other technologies

15. 5.
Summary

16. ➔
➔
➔

17. Thank you for your attention!
Questions?
If needed, this will be the easiest way to reach me:
/krzysztofozog
chris@codesushi.co