Hey all, I have been building with headless WP since around 2016.
I’ve built lots of stuff I’m very proud of with it. But I always felt like I was forcing it into submission. The thing is – lots of the other headless CMS out there still lack support for must-have ACF features.
* Conditional logic (this one is huge)
* A decent block-based layout editor like Flexible Content
* Repeater field where you can see / edit your “array” data directly on the page, rather than loading in additional related “documents” as rows
* Lots of powerful field types
* A straightforward relationship field (note, not over-engineered)
* Self-hosted
This is why WP + ACF always won us over vs. things like Contentful.
But I’ve spent the last 4 years of my life working on something to finally let me ditch WP + ACF, and it’s called Payload. I just [filmed a video]) about finally being able to ditch headless WP, but I’d love to know what this community thinks. Could be a good alternative for many of you still building headless WP, and I want to do my best to make it as powerful as it can be.
So I’m here looking for your thoughts!
[ad_2]
> Are you still using headless WP?
For some reason I’ve never ever had the reason to go headless with WP. Like, why would you even do it? Seems like very high effort for very low benefit.
I would love to pick your brains. I’m trying to do a headless gatsby theme atm. I am getting there very slowly as I’m new to React but I am a little out of my depth with what’s the correct way to use graphql with flexible content blocks.
Really I need to map a large query for all the columns and all the acf flexible blocks data that have been added to the page and then only call the component if they exist.
Easier said than done for a newb.