What developers get 🚫WRONG🚫 about headless WordPress

Some developers only consider page load speed when deciding between a traditional, monolithic app vs. a headless WordPress app for their next project. Don't do that! There are lots more factors to consider. 👇🏼

The five benefits covered in the video:
1. Component-based architecture
2. Route-based code-spittting
3. Instantaneous route transitions
4. Future-proof backend API
5. Career benefits from learning technologies like React & Vue, building GraphQL and REST APIs, etc.

WATCH NEXT:

JOIN THE COMMUNITY:

[kveldalf]

I’m hooked—pun intended. You are an excellent communicator and teacher!

[pilatec]

Your content is friendly and easy to digest for someone new to Headless WordPress. Just subscribed and now watching all the videos you uploaded on the channel.

[paulsalele]

Thanks, learned some news things and now I want to go the headless route lol

[treckstar]

This really is a fantastic video explaining headless as a whole. I had a similar mindset as seasoned developer but this really changed how I think about things. Plus #nerdjokes 🤓😬

[minecraftwordpress]

CAN WE DEVELOP LARGE WEB APPLICATON USING HEADLESS WORDPRESS LIKE CUSTOM DASHBOARD

[adriandixon]

Hey @Kellen Mace, would you say a blog site that has posts being submitted by the user on the front end via ACF forms every hour and is then published to the front end as well for viewers, is something that you think would be suitable for a headless wp scenario? I would be the developer and all and it’s a project that I’m just testing out.

[alexkey]

I'm about to re-create a relatively big ecommerce site (thousands of products with variations already build with traditional woocommerce). I'm really tempted to use nextjs & react for the FE and use woocommerce for backend. Is this worth it? The things i'd have to re-build: cart functionalities, cart discounts etc, checkout, authentication for users, payment gateway integration during checkout. There are several plugins which tackle those problems but not all of them. Using SSR takes ages for the page to load, using SSG takes long for the whole site to build, for SSG with incremental builds it might cause unnecessary requests to the server. I'm really confused on what's best in this scenario. I love react and nextjs, really despise php and Wordpress way of coding but it's all about the customer, not me. what are your thoughts? :)