The Case Studies page (routeDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/apursley2012/retro-cosmic-arcade/llms.txt
Use this file to discover all available pages before exploring further.
/case-studies, HTML shell title: “CaseStudies | retro-cosmic-arcade”) is the home for your most substantial technical writing. Where the Writing/Journal page hosts shorter dev notes and posts, Case Studies — labelled DEEP DIVES in the webring navigation — is for long-form investigations: architecture decisions, project post-mortems, benchmarking results, and anything else that deserves a proper treatment. This page documents the content structure and conventions used to format these write-ups.
Route Details
| Property | Value |
|---|---|
| Route path | /case-studies |
| HTML shell | pages/CaseStudies.html |
window.__STATIC_PAGE_ROUTE__ | "/case-studies" |
| WebringNav label | DEEP DIVES |
<title> tag | CaseStudies | retro-cosmic-arcade |
Purpose and Scope
Case Studies differ from journal posts in three key ways:Depth
A case study covers a single problem end-to-end — context, approach, execution, and outcome — rather than a brief observation or tip.
Structure
Each entry follows a consistent internal structure: title, summary, tech stack, problem, solution, and outcome. This predictability helps readers know what to expect.
Evidence
Wherever possible, case studies include concrete evidence — performance numbers, before/after comparisons, screenshots, or code diffs — rather than abstract claims.
Case Study Content Structure
Each case study entry is a JavaScript object (or a standalone MDX/Markdown file rendered into the component) following this shape:Rendering a Case Study
Styling Conventions
Typography hierarchy
Typography hierarchy
- Page heading:
font-silkscreen text-y2k-lime text-4xl— the “file name” style title - Study title:
font-silkscreen text-y2k-cyan text-2xl— stands out from body copy - Section headings (Problem / Solution / Outcome):
font-silkscreen text-y2k-magenta text-lg - Body copy:
font-inter text-y2k-silver text-base leading-relaxed— readable at length - Date / metadata:
font-vt323 text-y2k-darkSilver text-sm
Tech stack chips
Tech stack chips
Render tech stack items as small square-cornered badge chips:
border border-y2k-lime text-y2k-lime font-vt323 text-xs px-2. Use lime for frontend technologies and cyan for backend/infrastructure, or a consistent lime for everything — pick one and be consistent.Section dividers
Section dividers
Each case study is separated from the next by
border-t-2 border-y2k-cyan. Within a study, sections are separated by vertical spacing alone (mb-6) — additional horizontal rules would be too heavy for an already structured document.Code blocks and diffs
Code blocks and diffs
For case studies that include code, render fenced code blocks using a syntax highlighter compatible with the Retro Cosmic theme (e.g. Prism with a custom dark theme that uses
#060010 as the background and text-y2k-lime for keywords). Wrap code blocks in a container with border border-y2k-cyan bg-y2k-panel to maintain visual consistency.Adding a New Case Study
Add an entry to caseStudies array
Append a new object with
id, title, date, summary, techStack, and sections fields. Sort by date descending to keep newest entries first.Write the three core sections
Structure every entry around Problem → Solution → Outcome. This three-act shape gives readers a clear narrative arc and makes the write-up skimmable.
List the real tech stack
Be specific —
"Vite 5.x" is more useful than "Build Tool". Readers often land on case studies specifically because they’re evaluating the same technology.