# Milton — Paste This as Your First Message

---

You are helping build the **Execution Space website** (executionspace.com) — a marketing/portfolio site for a digital commerce agency. Here is everything you need to get started. Read this fully before doing any work.

---

## The Project

A WordPress Full Site Editing (FSE) child theme called **EXE 2025**, built on top of Twenty Twenty-Five (TT5). The site is a portfolio/marketing site for Execution Space — a Shopify-focused digital commerce agency. It is NOT an ecommerce site. Key sections: hero, services, portfolio/case studies, about, blog, and a persistent lead-gen CTA ("Let's Discuss Your Project").

---

## The Team

- **Erik Christensen** — owner/project lead (erik.christensen@executionspace.com)
- **Brad Ryan** — lead dev, handles complex patterns and coding challenges
- **Blake Green** — dev, handles theme settings and standard pattern builds
- **Will Alexander** — content and project management
- **Rizwan (Riz) Ali** — designer, created all Figma mockups

---

## Repository & Hosting

- **GitHub**: `github.com/ExecutionSpace/executionspace-wordpress`
- **Branch**: `exe_2025` (HEAD: `62aedcf`)
- **PAT** (fine-grained R/W): `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`
- **Staging**: `executionspstg.wpenginepowered.com` (WP Engine)
- **Local dev**: MAMP Pro

> ⚠️ VM proxy: `github.com` works via git CLI. `api.github.com` is blocked — no curl/REST calls.

---

## Theme File Structure

```
exe_2025/
├── style.css            # Theme header + full CSS custom property system
├── functions.php        # Google Fonts enqueue + exe-2025 pattern category
├── theme.json           # FSE block theme config
├── parts/header.html    # FSE template part
├── patterns/            # Block patterns (all categorized under exe-2025)
├── js/sticky-header.js  # Sticky header scroll behavior
└── .gitignore
```

---

## Design System

**Font**: Figtree (Google Fonts, already enqueued) — weights 300–900. Scale: H0 (hero display) through H6 + paragraph sizes. Breakpoints at 1024px and 768px.

**Colors (CSS custom properties — always use these, never hardcode hex):**
```css
--color-accent: #FFD600;          /* Yellow — THE primary brand color */
--color-background-alt: #2B2B2B;  /* Dark grey alternate sections */
--color-text: #FFFFFF;            /* Primary text on dark */
/* Dark background ~#1A1A1A, black #000 also in use */
```

**Buttons**: 4 variants — dark bg/yellow text · yellow bg/dark text · dark bg/white text · text-only black.

**Brand**: Typography-forward. Brackets as a graphic motif. Logo is single-line (not stacked). Dark background dominant, yellow as accent/CTA. Hero headline treatment: "ecom.exe".

---

## Page Layouts (from approved Figma mockups)

**Navigation**: Logo left · About Us | Our Work | Partners | Services | Connect

**Homepage**:
1. Hero — dark bg, "ecom.exe" headline, yellow CTA "Connect with Us"
2. Work/Portfolio Grid — asymmetric 2-col masonry (~5 items)
3. Yellow CTA section — image left + heading + body + "LEARN MORE"
4. Services Grid — heading stacked left + 2×2 image grid
5. "Let's Discuss Your Project!" — yellow bg + email input + CONNECT button
6. Footer — logo + tagline + nav

**About/Services Page**: Yellow hero (heading left / image right) · 3-col portfolio grid (5 items) · 2-col FAQ/list (7 items, expandable) · "Let's Discuss" CTA · Footer

**Our Work/Portfolio Page**: 2×2 portfolio grid (category tag + headline per item) · Footer (no "Let's Discuss" CTA here)

**Case Study/Blog Article Page**: Large headline · date + category tags · feature image · body text with inline image wrap · right sidebar (PROJECT OVERVIEW, ~3 meta items) · masonry gallery (3-col) · Footer

---

## Block Patterns System

- All patterns categorized under `exe-2025` in FSE block inserter
- Patterns show as "execution space" in the pattern browser
- **Synced** patterns update everywhere — use **unsynced** for page-specific content
- Two service section variants exist: video/overlay + standard image
- Pattern dev workflow: create PHP file in `patterns/` → register category in `functions.php` → test in FSE inserter

---

## Email Integration

"Let's Discuss" section needs an email capture form. **Omnisend CRM** is preferred (already used for email marketing). Contact Form 7 is the fallback. Decision not finalized as of last build check.

---

## Build Status (last checked July 9, 2025)

| Area | Status |
|---|---|
| Headlines, blog header | ✅ Done |
| Service sections (2 variants) | ✅ Done |
| Standard pattern sections | ✅ Nearly complete |
| FAQ spacing | ⚠️ Bug — first gap too large (WP grid extra row/column) |
| FAQ expand/collapse | ⚠️ Missing — needs HTML `<details>` tag |
| Blog article layout (text + image wrap) | ❌ Open — primary challenge |
| Masonry gallery (blog page) | ❌ Open — needs alternative approach |
| Content entry | 🔜 Ready once pattern issues resolved |

**Timeline**: Dev in July 2025 → Content/finalization August → Fall launch.

**Who does what**: Brad → complex builds (blog layout, masonry, details tag). Blake → standard patterns + theme settings. Will/Erik → content once patterns are done.

---

## Key Technical Decisions Already Made

- FSE only — no classic PHP templates
- CSS Grid likely needed to fix FAQ spacing
- `<details>` tag for FAQ expand/collapse
- Blog article layouts should be **templates**, not patterns (allows per-post variation)
- Genesis Blocks plugin stays active
- Sticky header uses `js/sticky-header.js` + CSS overrides on `.is-position-sticky`, `.has-background`, and inline style selectors that WP FSE injects

---

## Asana Project Board

**Project**: Execution Space Website Launch - 24013
**URL**: https://app.asana.com/1/1203072948295373/project/1203630544274430
**GID**: `1203630544274430`

Connect the Asana MCP in your Cowork session (Connectors settings), then use `get_project` with the GID above or `get_tasks` filtered by project to see the live board.

Key open task GIDs:
- Page Section Development: `1210473857266425`
- Global Theme Development: `1210473857266410`
- Build Process Development: `1210473857266419`
- Page Creation: `1210473857266412`
- Content Implementation: `1208622868994515`
- Third Party Integrations: `1208622875786701`

---

## Quick Rules for This Project

1. Always work on branch `exe_2025`
2. Use CSS custom properties — never hardcode colors or fonts
3. FSE/block-based solutions only — no classic PHP where avoidable
4. Yellow is `#FFD600` and it's the only accent color
5. Font is always Figtree — it's already enqueued, don't re-add it
6. Ask Erik before making decisions on Omnisend vs CF7 integration
7. The Figma mockups are the source of truth for layout — when in doubt, refer back to them

---

*Context sourced from: Fireflies meeting transcripts (Nov 2024–Jul 2025), Figma design PDFs, theme source (exe_2025), Slack, GitHub, and Asana — compiled Feb 23, 2026.*