Hi, we’re WPKernel 👋

WPKernel is a config-first meta-framework for serious WordPress plugins.

You describe your product once in wpk.config.ts: routes, storage, schemas, capabilities, UI and the CLI deterministically generates the rest:

• PHP REST controllers & shims
• Capability maps & permission callbacks
• Schema-driven REST args
• Admin DataViews & interactivity wiring
• JS/TS clients & typed hooks
• Block manifests, SSR stubs & apply plans

No more “fix PHP, break JS” or copy-pasted boilerplate that drifts over time. What you declare in config is what you get in code.

Why your sponsorship matters

WPKernel isn’t a one-off plugin; it’s infrastructure for the next decade of WordPress work.

Your support helps to fund:

• Core framework development
  Keeping the pipeline, generators, and runtime sharp, tested, and battle-ready for real production plugins.

• First-class documentation & examples
  Guides, reference docs, and showcase plugins that demonstrate entire products built from a single config file.

• DX & tooling
  Readiness checks, better errors, CI examples, and “three-minute path” workflows so teams can adopt WPKernel without wrestling the stack.

• Community patterns
  Shared recipes for common problems: schemas, resource layouts, block setups, and extension blueprints that others can reuse.

Who’s behind WPKernel?

I’m @pipewrk, long-time full-stack architect, WordPress survivor, and creator of WPKernel.

For years I’ve been rebuilding “proper software engineering” practices on top of WordPress: deterministic pipelines, IRs, AST-driven code-gen, and transactional apply steps. WPKernel is that work distilled into a framework the community can actually use.

If WPKernel saves you time, reduces bugs, or lets you ship cleaner plugins to your clients, sponsoring is a way of saying:

“Keep going. Make this the standard.”

Thank you for even considering it. 🙏