Developer Standards

Stable

Applies to: Vexal, SmartBlocks, WileyLabs plugin ecosystem

Introduced: Platform engineering baseline

Updated: Documentation v1

Build Vexal as a portable intelligence layer: theme-agnostic behavior, scoped frontend assets, namespaced code, and strict WordPress security practices.

Summary

Standards ensure compatibility across major themes/builders while keeping recommendation and telemetry systems deterministic and auditable.

Use cases

Implement new SmartBlocks features safely
Review plugin PRs for compatibility and security
Onboard contributors with consistent architecture rules

How it works

Contributors follow a common contract: namespaced CSS/JS, conditional asset loading, registry-based recommendations, and ledger-backed mutations.

Inputs

WordPress coding and capability model
Existing registry, telemetry, and ledger APIs
Project compatibility and release policies

Outputs

Theme-safe plugin code
Explainable recommendation behavior
Secure admin and AJAX operations

Admin UI location

This is a documentation reference; implementation appears throughout SmartBlocks and related plugin admin pages.

Telemetry standards cover bounded logging, redaction, and reproducible reporting inputs.

Mutation pathways should log stable event keys and snapshot links in the visibility ledger.

Security

Require nonce + capability checks on admin/AJAX writes; sanitize input, escape output, and avoid logging secrets or sensitive payloads.