Skip to main content

Documentation Index

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

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

The Case Studies page goes deeper than the Projects gallery. Where "Spells I've Cast" gives a quick overview of each project, "Rituals Performed" presents the full ceremony — the problem, the process, the decisions made, and the outcomes achieved. These are the detailed engineering logs that demonstrate how the developer thinks, not just what they have built.

​
Route & Static Shell

The Case Studies page is served from pages/CaseStudies.html. Its static shell sets the hash to /case-studies on load. 
<script>
  window.__STATIC_PAGE_ROUTE__ = "/case-studies";
  if (!window.location.hash || window.location.hash === "#/" || window.location.hash === "#") {
    window.location.hash = "/case-studies";
  }
</script>
The route uses a hyphenated slug (/case-studies) while the HTML file uses PascalCase (CaseStudies.html). This is consistent with the project’s convention of human-readable URL slugs mapped to descriptively named static files.

​
Section Headings

ElementText
Section heading"Rituals Performed"
Subheading"Detailed logs of complex conjurations"
The heading "Rituals Performed" is rendered in font-heading (Cinzel Decorative) with witch-teal-glow (#2dd4bf) coloring. The subheading "Detailed logs of complex conjurations" uses font-body (Cormorant Garamond) and signals that this section requires more engagement from the reader — these are not summaries, but full accounts.

​
Visual Design

The page uses the midnight-base (#0a0e1a) background with individual case study entries displayed as large, text-forward cards or full-width sections. Framer Motion animates each entry into view as the page loads.
The word “ritual” implies a repeatable, documented process — not magic for its own sake, but a structured methodology that can be studied and reproduced. This framing positions case studies as evidence of engineering discipline.

​
Case Study Entry Structure

Each case study entry is a detailed record of a single engineering challenge.
FieldDescription
TitleThe name of the ritual / project
ChallengeThe problem or constraint the ritual was designed to address
ApproachThe methodology and tools employed during the conjuration
OutcomeThe measurable or qualitative result of the work
TechnologiesLanguages, frameworks, and services involved
Case studies may link back to their corresponding entry in "Spells I've Cast" (the Projects page) for a high-level overview, or outward to a live deployment or repository. This creates a navigational relationship between the two sections.

​
Animation Details

ElementAnimation
Section headingFade in + upward translate on mount
SubheadingShort delayed fade-in
Case study entriesStaggered fade-in, each with slight vertical offset
Text contentRevealed progressively; may use scroll-triggered animations

​
Navigation Context

In the site’s thematic navigation, the Case Studies page is linked as “Rituals Performed”, matching the section heading and continuing the arcane chapter-title pattern used across all navigation links.

​
Typography & Color Reference

TokenHexUsage on this page
midnight-base#0a0e1aPage background
witch-teal-glow#2dd4bfSection heading, entry accents
witch-teal-bright#5eead4Entry titles, highlighted terms
witch-teal-dark#0e3a3aEntry card or section divider backgrounds
font-headingCinzel DecorativeSection heading, entry titles
font-bodyCormorant GaramondSubheading, entry body and detail text

Build docs developers (and LLMs) love

Get started for freeTalk to us