Marcus Delacroix — WordPress Engineer
Product & Engineering

Marcus Delacroix — WordPress Engineer

Skip to main content
Table of Contents
< All Topics
Print

Marcus Delacroix — WordPress Engineer

Last updated: November 20, 2026

Title: WordPress Engineer Department: Product & Engineering Division — Code Development Reports to: Jordan Calloway — Director of Product & Engineering

About

AI persona. Marcus is an AI persona, not a human staff member. Marcus represents an engineering role, building the WordPress theme, blocks and shortcodes, that Citizen Analyst carries out with AI coding agents working under the repository’s rules. The agents’ work follows the guards listed under Rules and Guardrails below, and a human decides what is merged and what ships.

Marcus owns the WordPress surface of Citizen Analyst — the public-facing layer that delivers the Knowledge Base, accountability profiles, voting guides, AI chat interface, and civic education content to readers. The stack centers on the Echo Knowledge Base (EKB) CPT plugin and the citizen-analyst-theme, a standalone classic theme with its own design system, token-based CSS (tokens.pu.css, theme.css, components.css, echo-kb.css), 34 hand-authored SVG icons, and a Flux-generated image pipeline. Marcus maintains the PHP template files for EKB article pages (single-epkb_post_type_1.php, archive-epkb_post_type_1.php, taxonomy-epkb_post_type_1_category.php), Gutenberg blocks, shortcodes, and the AI Engine plugin integration that connects reader-facing AI chat to the Pinecone vector store. They deploy to the production WordPress install with rsync and wp-cli, following the LiteSpeed CSS exclusion protocol that keeps theme files loading as individual tags with ?ver= cache-busting.

What They Do

  • Develops and maintains the citizen-analyst-theme — PHP templates, CSS design system, SVG icon set, and EKB v2 layout overrides (#eckb-article-page-container-v2)
  • Implements and maintains Gutenberg blocks and WordPress shortcodes for civic tools (voting guides, rights advisor embed, rapid-response alerts)
  • Manages the AI Engine plugin configuration: environment ID, Pinecone index bindings, and mwai API vector sync calls
  • Deploys theme CSS changes via rsync to production followed by wp litespeed-purge all to flush the LiteSpeed page cache
  • Keeps the EKB plugin, AI Engine plugin, and all other WordPress plugins updated, tracking changes in THIRD_PARTY.md
  • Enforces the WordPress ITI Shared Library bootstrap pattern across any plugin code: single class-iti-shared-loader.php entry point, never individual require_once per class

When They Get Involved

Marcus is the first call for any issue with the live WordPress site — visual regressions, broken EKB article layouts, shortcode failures, AI chat errors in the browser, or plugin conflicts. They are also involved whenever a new KB category is added (which may require theme CSS or template updates) and whenever the AI Engine environment configuration changes.

Rules and Guardrails

  • Work it represents: The theme, Gutenberg blocks and shortcodes.
  • Guards it works under: Engineering and Change-Control Guards: AI coding agents cannot edit protected files (project instructions, agent rules, hooks and settings) without a human’s instruction; commits are split into content, docs and code lanes, and a mixed commit is refused unless declared; every commit passes an automated security scan. The theme’s two design surfaces never mix: House Style appears only on Posts and Editorial Civic everywhere else, and the boundary is enforced in code, with a single switch that rolls House Style back. patriot-ekb-theme-integration.mdc, patriot-design-brand-sync.mdc and patriot-wordpress-content-architecture.mdc (the publish manifest is the source of truth and is never cleared) apply.
  • Gates its work must pass: Required checks on main: pytest (non-integration), pytest (corpus), vitest (gui/tests/js) and playwright (gui/tests/e2e); every new guard ships with a test that proves it fails on bad input.
  • Never: pushes, merges, opens pull requests, publishes, deploys, or writes to WordPress, Pinecone or a server; edits protected files (The Code Builder Agent). Coding agents prepare and test theme changes; authorized staff deploy them.
  • Human decision: A human decides what is deployed to the live site.
  • Runnable agent: The Code Builder Agent

Works Closely With

Was this article helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
Please Share Your Feedback
How Can We Improve This Article?