GraphQL kinda sucks for Craft CMS

If you come across a Medium paywall, you can read the blog for free here. Just click the link and access the content without any restrictions.

Every time I have to use GraphQL to get data from a Craft CMS backend to the frontend, it feels like I’m signing up for a headache. It’s like trying to untangle a bunch of cables -annoying, time-consuming, and I’m never really sure what went wrong.

But who am I to question such a highly regarded concept? Let’s back up a bit. I’m primarily a Frontend Developer, and I build and maintain marketing websites for clients ranging from small businesses to big corporations. As the GraphQL headache continued to grow, I thought, “There’s got to be a better way.” And that’s how the Craft Query API came to life — a Query Builder similar to what we use in Twig, but made for JavaScript frameworks. Less pain, more gain (and animations)!

What’s wrong with GraphQL

Soooo much boilerplate

You often end up writing a lot of boilerplate code. For each query, you need to define different schemas, create fragments to reuse parts of the queries, and handle the complexities…