Architecture Overview

Two independent WordPress installations. Not multisite — separate databases, separate themes, separate repos, separate deploy pipelines. They share a Cloudflare R2 bucket for media, but that's it.

System Diagram

The Two Sites

Media and CDN

All media is offloaded to Cloudflare R2 (S3-compatible object storage with free egress). This is not optional infrastructure — it's where the images live. If you don't understand R2, read the Decision Log before touching anything.

• Marketing site media: static.marketofchoice.com
• Reservations site media: static.marketofchoice.com/catering
• PDFs are excluded from R2 offload on the reservations site
• Credentials: S3_UPLOADS_* env vars in wp-config.custom.php, from .env locally and WP Engine's environment in production

Reservations Site — Where the Complexity Lives

MU-Plugin System

All custom business logic lives in src/wp-content/mu-plugins/. The yax-loader.php auto-loads plugins with priority-based dependency resolution. Disable any plugin by renaming it to .disabled.

Core business plugins (moc-*):

Infrastructure plugins (yax-*): yax-loader.php (auto-discovery + dependency resolution), yax-common/ (service container), yax-cleanup/ (admin declutter), yax-disable-comments/, yax-plugin-modifications/, yax-version-sync/.

CDN/Media: s3-r2-support.php (R2 config), uploads-to-cdn.php (URL rewriting), exclude-pdf-from-s3.php (PDFs stay local).

Theme: Moc-Avada

Child theme at src/wp-content/themes/Moc-Avada/ with 24 PHP files in functions/:

Notable Plugins (Regular)

Custom MoC plugins in src/wp-content/plugins/:

Key third-party plugins:

Product Data Model

• SKU (PLU): The canonical product identifier. Always use SKU, never WP post IDs. The client references everything by PLU number. API: wc/v3/products?sku=XXXXX.
• product_availability: ACF meta field (field_6722be5565a68). Array of seasons like ["standard", "easter"]. NULL = standard.
• Weight-based pricing: Identified by weight_based_pricing meta = 1. Two fields must stay in sync: _moc_price_override (per-lb display) and regular_price (per_lb x max_weight_range).
• Allergens: Stored in TWO places — the Allergens product attribute (for filtering) AND the <strong>Allergens:</strong> line in the description HTML. Both must match.
• Category IDs: Bakery=193, Kitchen=197, Appetizer=192.
• Supper Club tags: Supper Club (222), Standard (249), Chef's Favorite (248), Add-ons (229).

Tracking and Analytics

Marketing Site — Simpler but Avada-Heavy

The marketing site is mostly static content managed through Avada's Fusion Builder. The child theme (Avada-Child-Theme) has custom templates and a functions/ directory, but the majority of page content lives in the WordPress database as serialized Fusion Builder shortcodes in post content — not in template files. See Notes for what this means in practice.

Key Plugins

Content Patterns

• Store locations: Avada pages with WPUPG grid shortcodes at marketofchoice.com/locations-{slug}/. Dynamic content (manager, maker, blog) pulled from regular posts.
• Weekly specials: Custom post type. PDF + CSV + Issuu embed. Updated weekly.
• Recipes: Custom post type with ACF fields (Serves, Difficulty, Prep Time, Cook Time).
• Maker profiles: Regular posts. When removing, scrub all mentions — home page, local photos, Amplify pages, specialty pages.

Local Development

npm run setup          # First-time: generates Caddyfile, updates /etc/hosts
npm run start          # Start all containers
npm run stop           # Stop containers
npm run logs           # All container logs
npm run logs:wordpress # PHP-FPM only
npm run shell          # Bash into WordPress container
npm run wp -- <cmd>    # WP-CLI (e.g., npm run wp -- plugin list)
npm run build          # Build dist/ for deployment

docker compose up -d   # Start containers
docker compose down    # Stop containers