WooGraphQL is a technical publication run by AxisTaylor, LLC. We cover headless WordPress, WooCommerce, GraphQL, and the engineering trade-offs of shipping commerce-grade frontends on Next.js. This page describes how we source, write, verify, correct, and disclose the work that lands on the WooGraphQL blog.

Editorial mission

Help engineering teams ship headless WooCommerce storefronts faster and with fewer surprises. Every post should be useful to someone building, debugging, or planning a real headless WordPress + WooCommerce + GraphQL system. We prefer specific advice with working code over high-level survey pieces.

Sources and attribution

Code samples and demos are first-party — built by the WooGraphQL team against the live woographqldemo.wpengine.com backend or a fresh local install. Third-party plugins, libraries, and packages are linked to their official source (GitHub, WordPress.org, npm) the first time they appear in a post.

External claims — benchmarks, market share figures, plugin capabilities, framework behavior — are linked to the original source: vendor documentation, primary research, or a verifiable measurement we ran ourselves. We do not republish third-party reporting without attribution.

Accuracy and corrections policy

Every post is reviewed against the current state of the demo repo and the linked plugins/packages at the time of publication. We update published posts when:

• An API or plugin behavior the post describes has changed, and the change breaks the working example.
• A reader reports an inaccuracy and we confirm it.
• A new release supersedes the recommended approach in a way that would harm readers who follow the original.

Substantive corrections are noted at the bottom of the post with the date and a short description of what changed. Typos and small clarifications are corrected silently.

To report an error, email support@axistaylor.com or use the form at /support#contact.

AI disclosure

We use AI-assisted authoring tools — primarily Anthropic Claude — as part of our editorial workflow. The role of these tools is drafting, restructuring, and copy review under human direction. Every published post is reviewed, fact-checked, and approved by a human editor before publication. Posts authored or co-authored by an AI assistant carry a byline that identifies the assistant directly (for example, “Kaz the AI Assistant”). Posts without such a byline were written by a human editor.

No published post is the unedited output of an AI tool. We do not use AI to fabricate quotations, statistics, source URLs, screenshots, or code that has not been independently verified to run.

Conflicts of interest

WooGraphQL the publication shares a name with the WooGraphQL plugin and the WooGraphQL Pro subscription, both of which are products of AxisTaylor, LLC. Posts on this site frequently reference, recommend, or demonstrate those products. We disclose that relationship in any post that pitches a paid offering, and we keep the open-source path documented fully so readers can use the free toolchain instead of the paid one whenever it fits.

Editorial team

• Geoff Taylor — editor-in-chief. Founder of AxisTaylor, LLC; maintainer of WPGraphQL for WooCommerce, NextPress, and the @woographql/* JavaScript packages.
• Kaz the AI Assistant — AI-assisted drafting and code-review tool used under editorial direction. Posts bylined to Kaz are AI-drafted and human-reviewed; see the “AI disclosure” section above for the workflow.

Ownership and contact

WooGraphQL is published by AxisTaylor, LLC. For editorial inquiries, corrections, or press contact, write support@axistaylor.com or use the form at /support#contact.