DEV Community

loading...

Version 0.8 of the GraphQL API for WordPress is now available πŸš€

Leonardo Losoviz
Creating GraphQL server for WordPress. Writing for CSS Tricks, Smashing Magazine, the LogRocket blog and Design Bombs. Tweeting @losoviz
・1 min read

Version 0.8 of the GraphQL API for WordPress is now available for download πŸŽ‰

This release focuses on three areas:

  1. Refactoring the codebase to enable extensions
  2. Further satisfying the GraphQL specification
  3. Completing the GraphQL schema

Release notes: https://graphql-api.com/blog/released-graphql-api-v08/

Discussion (3)

Collapse
rangercoder99 profile image
RangerCoder99 • Edited

If you planing to make one headless cms with GraphQL... Why use WP in the first place? There are much better options out there!

Collapse
leoloso profile image
Leonardo Losoviz Author

On the contrary: WordPress is as good a CMS as you can get. Managing content with WP is great. The issue with WP concerns the generation of the webpage, that's slow, and its templating system is not as good as what you can get with Vue/React/etc.

Which is the reason why adding GraphQL to WP is such a good idea. Keep WP as a CMS only, to manage the content: create blog posts, add tags and categories, enable comments, manage users via user roles. And then fetch the data with GraphQL and print the site using Next.js.

GraphQL + WP means you get a great CMS for managing content, and a great development experience for creating the site.

Collapse
rangercoder99 profile image
RangerCoder99 • Edited

No its not its heavy outdated and was never intented to use as headless cms! If you compare Strapi (one opensource headless cms) with WordPress, you’ll see that WordPress is much slower than Strapi to deliver the same thing. The reason is in the technology WordPress and Strapi are built on.

And this performance has an impact on the whole project, from user engagement or content editor comfort to Google ranking.