# Execution Space Website — Full Project Context Brief
**For: Milton (Claude Cowork session on Gherkin PC)**
**Prepared: February 23, 2026**
**Project: 24013 — Execution Space Website Rebuild**

---

## 1. What We're Building

A full website rebuild for **Execution Space** (executionspace.com) — a digital commerce agency that specializes in Shopify builds, ecom strategy, and execution services for brands.

The site is being built as a **WordPress Full Site Editing (FSE) child theme** on top of **Twenty Twenty-Five (TT5)**. The theme is named **EXE 2025**. It lives in a GitHub repo, is developed locally via MAMP Pro, and deploys to WP Engine staging.

The site is a marketing/portfolio site — not ecommerce. Key sections: hero, services, work/portfolio (case studies), about, blog, and a persistent "Let's Discuss Your Project" lead-gen CTA.

---

## 2. The Team

| Person | Role |
|---|---|
| **Erik Christensen** | Owner / client / project lead (erik.christensen@executionspace.com) |
| **Brad Ryan** | Lead developer — handles complex coding, advanced patterns |
| **Blake Green** | Developer — handles theme settings, patterns, simpler implementations |
| **Will Alexander** | Content & project management |
| **Rizwan (Riz) Ali** | Designer — brand identity, visual design, Figma mockups |

---

## 3. Tech Stack & Repository

### WordPress / Hosting
- **Theme**: EXE 2025 — child theme of Twenty Twenty-Five (TT5)
- **Local dev**: MAMP Pro at `http://localhost:8890` (or similar)
- **Staging**: WP Engine — `executionspstg.wpenginepowered.com`
- **FSE approach**: `theme.json`, block patterns, template parts (no classic PHP templates)
- **Active plugins**: Genesis Blocks (confirmed useful, stays active)

### GitHub Repository
- **Repo**: `github.com/ExecutionSpace/executionspace-wordpress`
- **Primary branch**: `exe_2025`
- **Current HEAD**: `62aedcf` (as of Feb 23, 2026 — confirmed in sync with local)
- **Other branches**: `main`, `claude/prepare-repo-push-yFWHL`, `setup/codeowners`
- **PAT** (fine-grained, R/W): `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`

> ⚠️ VM proxy note: `github.com` is accessible from the Cowork VM but `api.github.com` is blocked. Git CLI operations work fine; REST API calls via curl do not.

### Theme File Structure (inside `exe_2025/`)
```
exe_2025/
├── style.css           # Theme declaration + full CSS variable system
├── functions.php       # Font enqueue + block pattern category registration
├── theme.json          # FSE block theme configuration
├── parts/
│   └── header.html     # FSE template part
├── patterns/
│   └── header.php      # Block pattern (and others under exe-2025 category)
├── js/
│   └── sticky-header.js # Sticky header scroll behavior
└── .gitignore          # WP-aware (ignores core, uploads, wp-config, twenty* themes)
```

---

## 4. Design System

### Typography
- **Font family**: Figtree (Google Fonts)
- **Weights**: 300, 400, 500, 600, 700, 800, 900
- **Scale**: H0 (hero display) → H1 → H2 → H3 → H4 → H5 → H6 → paragraph sizes
- **Responsive breakpoints**: 1024px and 768px

### Color Palette (CSS custom properties)
```css
--color-accent: #FFD600;           /* Yellow — primary brand accent */
--color-background-alt: #2B2B2B;   /* Dark grey — alternate bg sections */
--color-text: #FFFFFF;             /* Primary text (on dark) */
/* Also: background dark (#1A1A1A approx), text-alt shades, black (#000) */
```

### Button Variants
1. Dark background + yellow text (primary CTA on dark sections)
2. Yellow background + dark text (primary CTA on yellow sections)
3. Dark background + white text (secondary)
4. Text-only / black (tertiary)

### Brand Direction
- Typography-forward, brackets as a graphic element (established in Dec 2024 design check-in with Riz)
- Logo: **single line** (not stacked — decision made July 2025)
- Dark background as the dominant palette with yellow (#FFD600) as the accent
- "ecom.exe" as a hero headline treatment — technical/execution positioning

---

## 5. Site Architecture & Page Designs

All designs were created by Rizwan in Figma. The approved mockups are available in the project's design PDF.

### Navigation
- Logo left, links right: **About Us | Our Work | Partners | Services | Connect**

### Homepage
1. **Hero** — Dark bg, "ecom.exe" headline (yellow accent), subheading: *"Seamless execution for your digital commerce needs"*, yellow "Connect with Us" CTA
2. **Work/Portfolio Grid** — Asymmetric 2-column masonry-style grid (5 items approx)
3. **Yellow CTA Section** — Image left + section heading + body text + "LEARN MORE" button
4. **Services Grid** — Section heading (stacked left) + 2×2 image grid
5. **"Let's Discuss Your Project!"** — Yellow background section with email input field + "CONNECT" button (Omnisend integration — see §7)
6. **Footer** — Logo + tagline + nav links

### About / Services Page
1. **Yellow Hero** — Section heading left + large image right
2. **Portfolio Grid** — 3-column layout (3+2 = 5 items), each with image + headline + description
3. **Two-Column FAQ/List Section** — Headline + 7 expandable items (requires HTML `<details>` tag for expand/collapse — CSS only has spacing right now)
4. **"Let's Discuss" CTA** (same as homepage)
5. **Footer**

### Our Work / Portfolio Page
- **2×2 portfolio grid** — each item has Category tag + Headline
- Footer (no "Let's Discuss" CTA on this page)

### Case Study / Blog Article Page
1. Large article headline
2. Date + category tags (e.g., WORK, E-COMMERCE)
3. Large feature image
4. Article body text with **inline image** (text wraps around image — this has been the hardest layout to implement)
5. **Right sidebar**: PROJECT OVERVIEW with ~3 project meta items
6. **Masonry gallery** below article (multiple images, 3-column — also complex)
7. Footer

---

## 6. Block Patterns System

- All patterns are categorized under `exe-2025`
- Patterns are **synced** (update across all pages when modified) — note: unsynced versions may be needed for page-specific content
- Pattern naming convention: stored under "execution space" in FSE pattern browser
- Two service section pattern variants exist:
  - Video/overlay capability version
  - Standard image layout version

---

## 7. Email / Lead-Gen Integration

The "Let's Discuss Your Project!" section has an email capture form. Two options were discussed:

| Option | Status |
|---|---|
| **Omnisend CRM** | Preferred — already used by Execution Space for email marketing |
| **Contact Form 7** | Alternative / fallback |

Decision was leaning toward Omnisend but not finalized as of July 2025.

---

## 8. Build Status (as of July 9, 2025)

Blake Green had reworked all website pages by this point. Status by section:

| Section | Status |
|---|---|
| Headlines / blog header | ✅ Complete |
| Service sections (2 variants) | ✅ Complete |
| Most standard pattern sections | ✅ Nearly complete |
| FAQ — spacing | ⚠️ Bug: First gap larger than rest (extra row/column in WP grid) |
| FAQ — functionality | ⚠️ Missing expand/collapse — needs HTML `<details>` tag |
| Blog article layout (text + image wrap) | ❌ Primary challenge — text-image positioning issues |
| Masonry gallery (blog) | ❌ Complex — alternative solution needed |
| Content entry | 🔜 Ready to begin once pattern issues resolved |

**Timeline established July 2025:** Development in July → Content + finalization in August → Fall launch target

**Division of labor:**
- Brad Ryan → complex coding (blog layout, masonry, details tag)
- Blake Green → theme settings, standard patterns, simpler implementations
- Will Alexander → content integration + page building (coordinate with Erik)

---

## 9. Key Technical Notes & Decisions

- **CSS Grid** may be needed to fix FAQ spacing alignment between mockup and implementation
- **`<details>` tag** is the proposed solution for FAQ expand/collapse (no additional CSS needed)
- **Template vs. Pattern distinction** — blog layouts should use templates (not patterns) to allow content variation per post
- **Genesis Blocks** plugin confirmed useful and stays active
- The theme uses **WordPress Full Site Editing** — no classic PHP templates; everything is block-based
- Sticky header is implemented via `js/sticky-header.js` with CSS overrides targeting `.is-position-sticky`, `.has-background`, and inline style attribute selectors (WordPress FSE adds these automatically)
- `.gitignore` excludes WP core files, uploads, `wp-config.php`, `twenty*` themes, and logs

---

## 10. Project History (Key Meetings)

### Nov 13, 2024 — Website Project Working Session
Early planning phase. Discussed homepage copy, service buckets, A/B testing for key messaging. Decision to add case studies section (profiling Shopify work from Little Rocket). Riz brought in for branding + assets. WordPress setup discussed. Target was early December launch (didn't happen — project stretched into 2025).

### Dec 13, 2024 — Creative Check-in (with Riz)
Rizwan presented visual "charrettes" (design explorations). Focus on typography and bracket graphics as brand identity. Erik and Will gave feedback. PDF of designs sent to team. Next review scheduled for Dec 27.

### June 18, 2025 — Execution Space Website Meeting *(most important architecture meeting)*
- Confirmed: child theme of TT5, pattern-based development
- WP Engine staging environment set up
- July 11 target for header + homepage sections
- Brad leading dev on complex items
- Fall 2025 as launch target
- Figma designs approved — used as reference for all pattern builds

### June 23, 2025 — Stand-up
Mentioned WordPress / WP Engine staging setup and active development.

### July 2, 2025 — Execution Space Website Meeting
- Navigation patterns discussed and being built
- Footer pattern in progress
- Hero banner layout being implemented
- Email integration debate: Omnisend vs CF7 (leaning Omnisend)
- Workflow: patterns categorized under exe-2025 in FSE block inserter

### July 9, 2025 — Execution Space Website Meeting *(most recent build status check)*
- Blake had reworked all pages; most sections nearly complete
- Blog article layout = primary open issue
- Masonry gallery = secondary open issue
- FAQ spacing + functionality = identified bugs
- Content entry phase ready to start (Will + Erik to coordinate)
- July dev / August content timeline confirmed

---

## 11. Slack / Communication

The team communicates primarily in Slack. Relevant channel for website is `#website`. Erik also posts weekly status updates in `#status-team`. The GitHub repo was mentioned in `#project-management` as the source of truth for theme changes.

---

## 12. What Milton Needs to Know to Be Useful

When helping with this project, Milton should:

1. **Always work against the `exe_2025` branch** of `github.com/ExecutionSpace/executionspace-wordpress`
2. **Theme is FSE / block-based** — solutions should use `theme.json`, block patterns, and template parts rather than classic PHP where possible
3. **Design tokens are CSS custom properties** — use `--color-accent`, `--color-background-alt` etc., not hardcoded hex values
4. **The big open items are**: blog article layout (text wrapping around image), masonry gallery, FAQ expand/collapse
5. **Pattern development workflow**: create pattern PHP file → register in `functions.php` category → test in FSE pattern inserter → sync if reusable across pages, unsync if page-specific
6. **Staging URL**: `executionspstg.wpenginepowered.com` — changes pushed to GitHub are deployed to staging
7. **Font**: Always Figtree (already enqueued in `functions.php` from Google Fonts)
8. **The yellow** is `#FFD600` — it's the primary accent/CTA color

---

---

## 13. Asana Project Board

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

The Asana MCP connector is available in Cowork. Once connected, Milton can query this project directly using the GID above.

### Key Open Tasks (with GIDs)

| Task | GID | Notes |
|---|---|---|
| Page Section Development | `1210473857266425` | Core build task — pattern sections per page |
| Global Theme Development | `1210473857266410` | Header, Footer, Navigation, Mobile Nav |
| Build Process Development | `1210473857266419` | Styles, file structure, CSS variables |
| Page Creation | `1210473857266412` | All required pages scaffolded |
| Content Implementation | `1208622868994515` | Will + Erik to populate once patterns done |
| Third Party Integrations | `1208622875786701` | Omnisend, tracking, etc. |
| Sitemap Development | `1208622748198445` | Supports content + dev |
| Temporary Landing Page | `1208914465330363` | Privacy policy, contact form, support chat, tracking |
| Remove Partner Page Redirect | `1208838807657356` | Cloudflare redirect rule to remove |
| Device Testing | `1208622875786705` | Post-build QA |
| User Testing | `1208622875786707` | Post-build QA |
| V2 Copy Deck | `1208310406302991` | Assigned to Erik |

### Completed Tasks (for reference)
Wireframing, staging environment setup, brief development, content deck development, brainstorming, landing page update — all marked complete.

> **To use Asana from Milton**: ensure the Asana connector is enabled in your Cowork session (Connectors settings), then use `get_project` with GID `1203630544274430` or `get_tasks` filtered by that project to see the full board.

---

*Context compiled from: Fireflies meeting transcripts (Nov 2024 – Jul 2025), project design PDFs (Figma exports), theme source code (exe_2025 zip), Slack search, GitHub repo state, and Asana project board.*