Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/mystery-haunting/llms.txt

Use this file to discover all available pages before exploring further.

The Autopsy Reports page (route: /case-studies) reimagines the classic portfolio case study as a forensic investigation file. Each project breakdown is rendered as a weathered parchment card complete with a radial dot grid background, a bold RESOLVED stamp rotated at −15°, and a corner toe-tag bearing the case ID. The page title reads “AUTOPSY REPORTS” with the subtitle “Post-mortem analysis of critical failures”, setting the stage for a tongue-in-cheek deep-dive into real engineering challenges.

​
Current Case Studies

Case #TitleCauseTime of IncidentSurvivors
001The Memory Leak MassacreUnclosed WebSocket Connections3:00 AM0 (All nodes crashed)
002Curse of the Infinite LoopMissing Dependency ArrayFriday 4:59 PMOnly the intern
Each card shares the same hardcoded notes block:
Subject was found unresponsive in the production environment. Initial analysis showed severe bloating in the heap memory. Surgical intervention required refactoring 400 lines of legacy code. Patient is now stable but requires monitoring.

​
Card Design

Each case study is rendered as a parchment-style card on a grid layout. The visual anatomy of a card consists of the following elements:
  • Parchment background — a warm off-white (#f4f1ea) base layered with a repeating radial dot grid, evoking aged paper found in a coroner’s filing cabinet.
  • RESOLVED stamp — a bold red stamp mark rotated −15° and overlaid on the card face, indicating the case has been closed.
  • Toe-tag label — a small corner element displaying the case ID (e.g. #001), styled to look like a physical tag tied to the document.
  • Narrative notes — body copy within each card tells the autopsy story in forensic language: heap bloat autopsies, legacy code surgery reports, and incident timelines.

​
Customization

Add a new object to the caseStudies array in the page source. Each entry requires an id, title, cause, time, and survivors field.
const caseStudies = [
  {
    id: '001',
    title: 'The Memory Leak Massacre',
    cause: 'Unclosed WebSocket Connections',
    time: '3:00 AM',
    survivors: '0 (All nodes crashed)'
  },
  {
    id: '002',
    title: 'Curse of the Infinite Loop',
    cause: 'Missing Dependency Array',
    time: 'Friday 4:59 PM',
    survivors: 'Only the intern'
  },
  // Add new entries here
];
The grid layout will automatically accommodate additional cards — each new entry is rendered using the same parchment card template, so the stamp, toe-tag, and radial dot grid pattern are applied without any extra configuration.
The Notes field text is hardcoded in the JSX template — update it in the source to customize each case study’s narrative. Look for the <p> block inside the card component beneath the cause display. The current text reads: “Subject was found unresponsive in the production environment. Initial analysis showed severe bloating in the heap memory. Surgical intervention required refactoring 400 lines of legacy code. Patient is now stable but requires monitoring.”

Build docs developers (and LLMs) love

Get started for freeTalk to us