Articulate Suite

Articulate combines a performant headless storefront with practical WordPress diagnostics and a control-plane workflow. The plugin phones home to RAGBAZ, receives a peer account, and continuously reports runtime and web-vitals context.

Download RAGBAZ-Bridge Open /docs Read onboarding API

Storefront Features (OSS vs PRO/FULL)

This matrix separates open-source capabilities from PRO/FULL capabilities. It is the canonical feature split for the Articulate suite and should be updated whenever storefront features change tiers.

Feature matrix updated: 2026-03-27

Shared baseline

WordPress-connected content model: Products, pages, events, and media flow from WordPress as source-of-truth into the storefront worker.
Headless edge delivery: Cloudflare Worker rendering with route hardening and diagnostics context from RAGBAZ.
RAGBAZ bridge onboarding: Signed call-home onboarding and heartbeat updates for site health and runtime visibility.

OSS storefront

Open-source baseline focused on practical deployment, reliability, and day-to-day operator usability.

Core storefront routes: Home, shop, inventory, profile, and tenant draft routing with baseline UX.
Theme and font system: Element themes + font themes with keyboard rotation and persisted preferences.
Docs and control-plane integration: Access to docs, tenant pages, peer diagnostics, and onboarding API from the same control plane.
GraphQL + fallback behavior: WordPress GraphQL-first reads with guarded fallback handling when endpoints are unavailable.

PRO/FULL storefront

Expanded capabilities for deeper automation, richer operations, and production-grade rollout support.

Advanced commerce automation: Richer purchase flows, entitlement automation, and premium checkout/access orchestration.
Expanded admin and operator tooling: Deeper operational controls, guided diagnostics workflows, and enhanced support-facing observability.
Enhanced media/derivation pipeline: Extended operator set, reusable derivation templates, and advanced workflow features for production teams.
Priority support and rollout guardrails: Production-oriented rollout assistance, higher-touch support patterns, and curated migration guidance.

PRO Storefront Admin UI (Detailed)

PRO/FULL includes an expanded operator console designed for teams running production storefronts with active support, content operations, and performance accountability.

Control-room dashboard: Operator-first top navigation with fast access to Sales, Stats, Products/Access, Storage, Support, Chat, Health, Style, and Info.
Operational diagnostics and remediation: Health checks, non-200 visibility, recommendations with impact wording, and direct action paths to resolve issues quickly.
Media and derivation workflow: Typed derivations, preview-quality controls, full-quality save flow, operator matrix editing, and reusable transformation chains.
Access and commerce administration: Product/access rule control, entitlement-oriented configuration, and payment/access visibility for support and operations.
Storage and upload governance: Unified storage guidance for WordPress/R2/S3 paths, upload diagnostics, and operational safety controls for asset pipelines.
Workflow speed and keyboard ergonomics: Built-in navigation hotkeys, compact control patterns, and high-frequency operator flows optimized for daily admin usage.
Role-aware docs and in-context help: Quick-start, non-technical and technical docs linked from UI context to reduce handoff friction between editors, admins, and developers.
Theme and readability controls: Multiple visual themes with contrast-aware admin surfaces so operators can run long sessions with lower visual strain.

PRO Admin UI Modules

Module	Included capabilities	Operator outcome
Control Room	High-frequency tab navigation, status-first layout, and compact operator entry points.	Faster daily decision loops with less navigation overhead.
Diagnostics + Health	Runtime checks, non-200 tracking, recommendation surfaces, and failure-oriented context.	Shorter mean-time-to-understand and faster remediation.
Media + Derivations	Operator chains, bind/unbind parameter handling, preview/full save safety, and reusable transforms.	Repeatable visual output with lower manual rework.
Products + Access	Access rule editing, entitlement-focused product mapping, and commerce-support visibility.	Cleaner support resolution and fewer access-state ambiguities.
Storage + Uploads	Backend-aware upload guidance, diagnostics, and operational safety boundaries.	More predictable file lifecycle behavior across environments.
Docs + In-Context Help	Role-aware links to quick-start, non-technical, and technical docs from admin context.	Reduced handoff friction across editor/admin/developer roles.

PRO Operator Workflows

Daily operator loop: Check status and non-200 signals, pick top remediation actions, validate outcome, and log operational state.
Campaign/content update loop: Adjust media + derivations, verify product/access settings, run storefront sanity checks, then publish confidently.
Incident handling loop: Open diagnostics context, identify fallback path taken, apply targeted fix, and revalidate through tenant/peer views.

OSS vs PRO Admin Boundary (At a Glance)

Area	OSS scope	PRO/FULL scope
Operational visibility	Baseline diagnostics and health context.	Expanded remediation workflow, richer observability, and support-facing incident context.
Media operations	Core media management and basic transformation handling.	Typed derivation orchestration, safer preview/full flows, and reusable transform operations.
Commerce administration	Core storefront product and access behavior.	Deeper entitlement control, support-oriented payment/access tracing, and advanced operator tooling.
Operator throughput	Practical day-to-day control surfaces.	High-frequency keyboard-centric workflows and denser control-room ergonomics for active teams.
Governance and support	Self-directed operations with standard guidance.	Priority rollout guardrails, richer guidance surfaces, and higher-touch production support patterns.

When Teams Usually Adopt PRO Admin UI

Your team runs frequent campaigns and needs repeatable operator workflows under time pressure.
Support volume is growing and you need faster root-cause isolation for non-200 and access incidents.
Media output consistency matters across multiple editors and storefront sections.
Operational accountability requires clearer separation between baseline and advanced admin controls.

Feature Matrix Maintenance

To keep OSS and PRO feature descriptions trustworthy, this matrix is maintained as part of every storefront feature-tier change.

When a storefront feature changes tier (OSS/PRO), update this matrix first.
Bump the matrix date on every feature-tier edit.
Keep feature labels operational (what teams can do), not marketing-only.

Onboarding flow

1) Plugin requests challenge from /api/v1/home. 2) Plugin signs the payload using challenge + canonical payload hash. 3) Home returns account_id and account_passkey.

Continuous reports

The plugin posts updates to /api/v1/home/heartbeat with account credentials. Peer diagnostics pages update with charts, impact analysis, and improvement measures.

Plugin ecosystem

Guidance includes WPGraphQL and related caching/performance plugin recommendations to improve SEO, editing quality, and conversion outcomes.

API Quick Example

# 1) Request challenge
GET https://ragbaz.xyz/api/v1/home?site_url=https://example.com&plugin_version=1.0.0

# 2) Register signed payload
POST https://ragbaz.xyz/api/v1/home
{
  "challenge": { "id": "...", "nonce": "...", "issuedAt": "...", "expiresAt": "...", "signature": "..." },
  "payloadSignature": "sha256_hex(challenge.id + ':' + challenge.nonce + ':' + canonical_json(payload))",
  "payload": { "site": { "url": "https://example.com" }, "runtime": {...}, "performance": {...} }
}

# 3) Report updates
POST https://ragbaz.xyz/api/v1/home/heartbeat
{
  "accountId": "...",
  "passkey": "...",
  "payload": { ...latest measurements... }
}

How RAGBAZ complements WordPress plugins

WPGraphQL provides structured APIs. Smart Cache boosts response reuse. RAGBAZ diagnostics turn these runtime readings into impact + action that teams can execute and track.

SEO and editorial outcomes

Lower TTFB/LCP and smaller transfer sizes improve crawl quality and user conversion while keeping familiar WordPress editorial workflows for content teams.

Stakeholder-oriented reporting

The peer report maps each technical issue to business impact and specific measures, so site owners can prioritize what actually moves performance and usability.