Add WordPress Integration: Zyra Workflow Blocks with Scheduling, Narratives, and Optional Human Review

[Hackshaven]

We propose adding support for WordPress integration to extend Zyra workflows into a publishing environment. The goal is to make data + narratives from Zyra available in WordPress as live, reproducible, and optionally human-reviewed content.

---

🔄 Workflow Summary

1. Workflow YAML in WordPress Block (inline editing, external reference).
2. Execution on Zyra Runner Server (datasets + processing live there).
3. Results Returned → Visuals, Narratives, Metadata.
4. Embedding in Gutenberg Block (with provenance).
5. Updates via WP-Cron / triggers.
6. Optional human-in-the-loop review (auto, review-required, hybrid).

---

🧩 Feature Matrix

Editors

• Live Preview in Gutenberg.
• Parameter overrides (UI sliders/dropdowns for workflow params).
• Scheduling panel (auto/review/hybrid).
• Diff viewer (visual + text).
• Accessibility helpers (auto alt-text from narrate stage).

Readers

• Toggle static vs. interactive embed.
• Provenance panel with workflow version & dataset info.
• Explorable parameters (optional lightweight interactivity).
• Bundled narrative + visual outputs.

Admins

• Configure Zyra Runner server endpoint.
• Define default update policy (auto, review).
• Role-based permissions for workflow editing.
• Storage & caching control (media vs. external CDN).
• Logs & analytics (refresh history, execution errors).

---

🛠️ Needed Zyra Changes

• New exporter target (wordpress) for artifact + metadata exchange.
• Runner API to accept workflow YAML + return structured results.
• Support for output “review modes” (auto, pending review, hybrid).

---

🚀 Benefits

• Enables reproducible, updatable, and transparent data stories in WordPress.
• Fits naturally into WordPress editorial workflow (drafts, revisions, review).
• Balances automation (auto-updating dashboards) with accountability (human-reviewed narratives).

[Hackshaven]

Clarification

This feature should be scoped as a WordPress plugin that provides Zyra blocks, rather than a standalone block.

• Plugin responsibilities

  • Register one or more Zyra Gutenberg Blocks.
  • Provide server-side code to communicate with the Zyra Runner API.
  • Handle caching of outputs (media library or external).
  • Expose site-wide settings (Runner endpoint, review defaults, storage policies).
  • Integrate with WP-Cron, webhooks, and the WordPress Revisions API.

• Block responsibilities

  • UI for workflow editing (YAML, parameter overrides, scheduling options).
  • Preview panel for visual + narrative outputs.
  • Provenance + accessibility helpers.

The block is the editor interface, while the plugin is the engine that enables scheduling, review workflows, and runner communication.

[Hackshaven]

Additional Note

Zyra integration could also work in the opposite direction: using WordPress content as the input dataset.

• The plugin could export posts/pages to Zyra Runner for analysis.
• Zyra workflows could check for:
  • Plain language compliance (readability, jargon detection).
  • Accessibility checks (alt-text coverage, color contrast in embeds).
  • SEO and metadata completeness.
  • Legal/compliance requirements.
• Results would be returned to WordPress as admin reports, e.g.:
  • Dashboard summaries (average readability score, % posts missing alt-text).
  • Per-post annotations in the editor sidebar.

This would allow Zyra to serve as both a generator (visuals/narratives into posts) and a compliance auditor (analyzing existing content).