Commons Feature SDK

The Commons Feature SDK is an open-source developer framework for creating modular, high-performance WordPress plugins that load only the features needed in each context.
It enables developers to structure plugin functionality into discrete modules, activate those modules globally or on a per-page basis, and apply intelligent inheritance across hierarchical page structures.
This leads to cleaner architecture, faster sites, and a more predictable, trustworthy WordPress experience.

---

Purpose

The purpose of the Commons Feature SDK is to provide a modern, ethical, and transparent foundation for WordPress plugin development.
It exists to solve long-standing problems in the WordPress ecosystem:

• Plugins loading features everywhere, even when unnecessary
• Slow frontend performance due to global scripts and logic
• Fragmented architectural approaches across developers
• Telemetry, license enforcement, and hidden call-home behavior
• Difficult-to-maintain codebases with tightly coupled features

This SDK delivers a structured alternative that is:

• Fully open-source
• Privacy-first
• Developer-friendly
• Performance-oriented
• Governed by the AgriCommons Foundation as a public-good project

---

Key Goals

1. Enable Modular Plugin Architecture

Developers can create plugins composed of independently loadable modules.
Each module becomes a first-class citizen with its own logic, assets, and activation rules.

2. Load Features Only When Needed

The SDK provides context-aware loading based on:

• Global enable/disable settings
• Per-page activation choices
• Page hierarchy inheritance
• Frontend vs admin vs REST contexts

This ensures minimal overhead and optimal performance.

3. Provide a Consistent Development Pattern

By offering:

• A Module Interface
• A Registry system
• A Resolver for activation logic
• Standardized configuration
• Automatic module discovery

…developers gain a predictable, reusable structure that simplifies both development and maintenance.

4. Support Developers Without Telemetry or Licensing

The SDK contains:

• No license checks
• No call-home functionality
• No telemetry or analytics
• No obfuscation

Developers and users retain full control and transparency.

5. Reduce Plugin Bloat and Improve Site Performance

WordPress sites benefit from:

• Faster load times
• More reliable plugin behavior
• Lower memory usage
• Better Core Web Vitals
• Clear understanding of feature impact

The SDK directly contributes to healthier, more maintainable WordPress ecosystems.

---

Target Audience

Plugin Developers

Those building WordPress plugins who want:

• Modular architecture
• Cleaner code
• Predictable patterns
• Easier maintenance
• Performance improvements
• Zero telemetry infrastructure

Agencies and Professional Developers

Teams maintaining multiple sites benefit from:

• Reliable, consistent plugin structures
• Predictable feature loading
• Easier debugging and support
• Strong performance outcomes

Open-Source Projects

Ideal for projects that require:

• Transparent governance
• Ethical coding practices
• Public-good digital infrastructure

---

Core Components (Planned)

Module Interface

Defines how all modules declare their identity and behavior.

Module Registry

Collects available modules and exposes them to the SDK.

Module Resolver

Determines whether each module is active based on global settings, per-page overrides, and context.

Context Engine

Detects frontend, admin, REST API, or other runtime environments.

Settings UI

Includes:

• Global module activation UI
• Per-page override UI

Automatic Module Discovery

Modules include manifests, enabling discovery without hardcoded lists.

---

Why “Commons”?

The SDK is stewarded by the AgriCommons Foundation, whose mission is to develop open-source tools that serve the public good.
“Commons” reflects:

• Neutral governance
• Non-commercial stewardship
• Ethical and transparent software practices
• The belief that foundational digital tools should remain free and community-owned

---

Philosophy

The Commons Feature SDK is guided by four principles:

1. Clarity

Developers should always understand when and why code executes.

2. Modularity

Features should be optional, isolated, and independently maintainable.

3. Performance

Plugins should load only what they need, when they need it.

4. Trust

No telemetry.
No licensing enforcement.
No behind-the-scenes communication.
No surprises.

This SDK aims to restore trust and sanity to plugin development through transparency and dependable engineering.

---

Roadmap (High-Level)

Phase 1: Core Architecture

• SDK bootstrap
• Registry, resolver, and context objects
• Basic module loading
• Manual module registration

Phase 2: Automatic Module Discovery

• Module manifests
• Naming conventions
• Autowiring

Phase 3: Settings UI

• Global module activation UI
• Per-page override UI

Phase 4: Inheritance & Context Logic

• Parent → child rules
• Conflict resolution
• Priority rules

Phase 5: Developer Documentation

• Example plugin
• Tutorials
• API references

Phase 6: Optimization Layer

• Asset loading helpers
• Conditional script/style enqueue
• Early runtime caching

---

License

The Commons Feature SDK is licensed under the GPL-2.0-or-later, in keeping with WordPress standards and the AgriCommons Foundation’s commitment to open-source ecosystems.

---

Contributing

Contributions are welcomed and encouraged.
Module ideas, bug reports, optimizations, documentation updates, and architectural discussions are all valuable to the project.

As an early-stage project, issues and pull requests may significantly shape the SDK’s direction.

More contribution guidelines will be added as the project progresses.

---

Vision

The Commons Feature SDK seeks to become a standard architectural foundation for WordPress plugin development.
By offering a stable, ethical, and high-performance framework, it aims to lift the entire WordPress ecosystem toward cleaner engineering and more trustworthy user experiences.

This project represents not just a toolkit, but a statement:

Features should load when they are needed, not simply because a plugin is activated.
Developers deserve clarity and control.
Users deserve trust and transparency.
The WordPress ecosystem deserves a better foundation.

The Commons Feature SDK exists to help build it.