TheDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/sys-core/llms.txt
Use this file to discover all available pages before exploring further.
caseStudies.js module exports an array c of case study objects rendered in the Case Studies section of the portfolio. Each entry is framed as a military mission report or flight operations briefing: a structured after-action review with a defined objective, a chronological mission timeline, documented anomalies encountered in the field, and a measured outcome. The metaphor maps naturally to the structure of a real engineering post-mortem and encourages honest, detailed storytelling about complex projects.
Data Shape
Field Metaphor Guide
| Field | Mission Metaphor | Plain-Language Meaning |
|---|---|---|
title | Mission designation | Project name and subtitle |
duration | Mission clock | Total elapsed time from kick-off to delivery |
crew | Crew manifest | Team size and roles |
techDeployed | Deployed systems | Technology stack |
objective | Mission objective | What you set out to build or fix |
preFlight | Pre-flight analysis | State of the system before work began; why action was needed |
timeline | Mission timeline | Chronological phases of the project |
anomalies | Anomalies detected | Technical blockers, surprises, and how they were resolved |
outcome | Mission outcome | Measurable results delivered |
future | Follow-on mission | Planned improvements or next phase |
Current Entries
cs1 — PROJECT ORION: E-Commerce Replatforming
| Field | Value |
|---|---|
| Duration | 6 MONTHS |
| Crew | 4 ENGINEERS, 1 DESIGNER |
| Tech Deployed | Next.js, Shopify Storefront API, Tailwind CSS, Framer Motion |
| Objective | Migrate a legacy monolithic e-commerce platform to a headless architecture to improve Lighthouse scores and conversion rates. |
| Pre-Flight | Initial scans revealed a 4.5s Time to Interactive and a bloated 2 MB JavaScript bundle. The legacy system was tightly coupled, making incremental updates dangerous. |
| Anomalies | Severe rate-limiting from the inventory API during high-traffic load testing. Mitigated by implementing a Redis caching layer at the edge. |
| Outcome | Reduced TTI to 1.2s. Conversion rate increased by 18%. Weekly deployments instead of monthly. |
| Future | Personalised product recommendations using edge middleware and a lightweight ML model. |
| Phase | Description |
|---|---|
| T-MINUS 6M | Architecture design and technology selection. |
| T-MINUS 4M | Core component library construction and Shopify API integration. |
| T-MINUS 2M | Checkout flow implementation and edge-case handling. |
| T-ZERO | Staged rollout to 10% of traffic, monitoring for anomalies. |
cs2 — OPERATION NEBULA: Real-time Collaboration Tool
| Field | Value |
|---|---|
| Duration | 3 MONTHS |
| Crew | 2 ENGINEERS |
| Tech Deployed | React, Yjs, WebRTC, Canvas API |
| Objective | Build a local-first, real-time collaborative whiteboard that works offline and syncs when reconnected. |
| Pre-Flight | Standard WebSocket approaches failed under poor network conditions. A robust conflict resolution strategy was required. |
| Anomalies | Memory leaks during prolonged sessions with thousands of vector objects. Resolved by implementing spatial hashing and culling off-screen elements. |
| Outcome | A resilient collaborative tool where users can work offline indefinitely and sync seamlessly upon reconnection. |
| Future | Adding voice channels and cursor presence history. |
| Phase | Description |
|---|---|
| PHASE 1 | CRDT evaluation and local storage wrapper implementation. |
| PHASE 2 | Canvas rendering engine optimisation for 60fps panning. |
| PHASE 3 | WebRTC signalling server and peer-to-peer sync logic. |
Adding New Entries
- Open
data/caseStudies.js. - Append a new object to the array following the
cs{n}id convention. - Frame the
titleas a mission codename followed by a colon and a plain subtitle, e.g."MISSION ATLAS: Design System Overhaul". - Write
preFlightas a concise situation report — describe measurable symptoms of the problem, not just a vague statement that “things were slow.” - Build the
timelinearray with one phase object per major milestone. Use mission-clock notation (T-MINUS 3M) for time-boxed projects orPHASE {n}for iterative work. - Document real anomalies in the
anomaliesfield — specific technical blockers and their resolutions are more compelling than generic challenges. - Populate
outcomewith concrete, quantified results wherever possible.
Field Reference
Unique identifier for the case study. Follow the
cs{n} pattern (e.g.
"cs1", "cs3").Mission designation string rendered as the case study heading. Convention:
"CODENAME: Plain Subtitle" (e.g. "PROJECT ORION: E-Commerce Replatforming").Human-readable project duration in all caps, e.g.
"6 MONTHS" or
"3 MONTHS". Displayed in the mission metadata block.Team composition in all caps, e.g.
"4 ENGINEERS, 1 DESIGNER". Gives
visitors context on team size and role distribution.Array of technology names used on the project. Rendered as tag chips in the
mission header.
One to two sentences stating the mission goal. This is the “north star” of the
case study — everything else in the document should connect back to it.
Pre-mission situation analysis. Describe the state of the system or problem
before work began, ideally with measurable data points (latency, bundle size,
error rate). This is the engineering equivalent of a problem statement.
Ordered array of mission phases from project kick-off to delivery. Each phase
has a
phase label (e.g. "T-MINUS 6M", "PHASE 1") and a single-sentence
description of the work completed.Phase label. Use mission-clock notation (
T-MINUS 6M, T-ZERO) for
time-boxed projects or sequential labels (PHASE 1, PHASE 2) for iterative
work.One-sentence summary of the work completed during this phase.
A paragraph documenting significant technical blockers, unexpected failures,
or risks encountered during the project, and how each was resolved. Be
specific — generic challenges are far less compelling than named failures with
concrete fixes.
The measurable result of the project. Quantify wherever possible: latency
reductions, conversion rate lifts, bundle size savings, deployment frequency
improvements.
Planned follow-on work or the next phase of the project. Even a one-sentence
forward-looking statement demonstrates that you think beyond the immediate
delivery.