How to Get Started With Gregius Data While the Directory Review Completes

The WordPress plugin directory runs on two tracks. One is the volunteer review pipeline, where experienced contributors scrutinize every submission before it reaches millions of sites. The other is the open-source model itself — where code is public, accessible, and ready to explore from the moment it’s committed.

Understanding both tracks matters. The volunteer review team catches edge cases, security gaps, and integration conflicts that automated scanners miss. Their work is the reason the directory remains trustworthy after more than a decade and tens of thousands of plugins. At the same time, the open development model means nothing gates your access to the code.

By the end of this update, you’ll know exactly where Gregius Data sits in the review process, why that volunteer work is essential to every site that installs from the directory, and how to get the full codebase running in your environment right now.

Here’s the submission status, what the review process looks like from the inside, and how to start working with the current Release Candidate today.

Table of Contents

• The Submission — June 15, 2026
• The Review — Community Quality Assurance
• The Performance — Available Now
• The Path Forward

The Submission — June 15, 2026

Gregius Data was formally registered for inclusion in the WordPress plugin directory on June 15, 2026. The documentation is complete and published. Every component, every module within the codebase, every API pathway is documented and staged.

The submission checklist was clean: licensing verified, security review run, readme structured to directory standards, assets prepared. The team pressed submit, and the plugin moved into the volunteer review queue.

This is where every WordPress plugin sits before it reaches the directory. It is the standard pipeline, not a detour.

The Review — Community Quality Assurance

The review team behind the WordPress plugin directory has been through an extraordinary year. By March 2026, weekly new-plugin submissions had quadrupled compared to 2024, crossing 500 per week. By May, that number climbed past 700. For perspective: what arrives in two days now would have been a full week of submissions in 2024.

The team responded. Three new reviewers — Marcel Tannich, Shiva Shanker, and Shameem Reza — completed their training in April and began reviewing alongside the existing volunteers. Their impact was immediate. The review queue, which had climbed to roughly 1,050 plugins by mid-April, was cleared to near zero within weeks. In May alone, the team completed nearly 3,000 initial reviews — about five percent of the entire directory.

This is not automation. While AI-assisted tooling helps reviewers spot patterns faster, every submission still passes through human judgment. Security context, licensing edge cases, conversations with authors, guideline interpretation — these depend on experienced people making careful calls. The tools support the reviewers. They do not replace them.

The team is not done growing. A second round of applications closed on June 26, 2026, and new trainees will begin onboarding in July. Sponsors across the WordPress ecosystem — through Five for the Future and direct contributions — fund the hours volunteers dedicate to this work.

When a reviewer opens Gregius Data, they will walk through the codebase with the same rigor they bring to every submission. If they find a missing escape, an ambiguous license header, or a performance path that needs attention, that is the process doing exactly what it exists to do: catching the details that, left unattended, become production nightmares. We are eager for that scrutiny. It is what makes the directory trustworthy.

The Performance — Available Now

The full codebase for Gregius Data is live on GitHub today. Every module, every feature layer, every component is accessible, forkable, and ready to stage — independent of the review timeline.

The current Release Candidate is tagged and stable. You can clone it, run it on a staging instance, audit the configuration, and explore how Gregius Data fits into your stack — all while the review team does their essential work in parallel. The documentation is published. The issue tracker is open. The pull request pipeline is active.

A directory listing is a stamp of community scrutiny. A working codebase is a product you can evaluate, install, and shape right now. Both are valuable. Both are in motion.

The Path Forward

The directory listing will arrive when a reviewer completes their assessment. That moment will mean the composition has earned its place alongside every other trusted plugin in the directory.

Until then, the code is yours to explore. Visit Gregius Data today. Clone the repository. Stage the Release Candidate. Configure it for your environment. We’ll be in the issue tracker and the pull request queue, building the next milestones of this project alongside you.

Frequently Asked Questions

Photo: Kazuo ota