Skip to main content

Documentation Index

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

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

The Case Studies page appears as “Deep Dyes” in the navigation bar. It is designed for longer-form project writeups that go beyond the summary shown on the Projects page — this is where you demonstrate not just what you built, but how you thought through it, what decisions you made, and what you learned along the way.

​
File location

pages/CaseStudies.html

​
Difference from the Projects page

The Projects page and the Case Studies page serve different purposes and different audiences:
Projects pageCase Studies page
High-level portfolio summariesDetailed problem-process-outcome narratives
Broad overview of your workSelected projects explored in depth
Quick to scanDesigned for visitors who want to read
Category badges and short excerptsTechnical decisions, methods, and outcomes
The README describes Case Studies as “detailed case studies and technical breakdowns.” Use this page for the two or three projects where the thinking behind the work is as impressive as the result itself.

​
MarbledCard usage

Case Studies use the same MarbledCard component as the Projects page. The excerpt prop serves as the entry-point text that convinces a visitor to read further. The “Read Study” call-to-action is built into the component and renders automatically: 
<MarbledCard
  title="Rebuilding the Design System"
  excerpt="How we migrated a 200-component library from styled-components to Tailwind without a single regression in production."
  category="Architecture"
  delay={0}
/>

<MarbledCard
  title="Search at Scale"
  excerpt="Designing and shipping a full-text search feature for a platform with 4 million records and a sub-200ms latency requirement."
  category="Performance"
  delay={0.1}
/>

​
Content guidelines

A strong case study covers five areas in roughly this order:
  1. Problem statement — what was broken, slow, missing, or wrong before you got involved
  2. Approach — how you scoped and tackled the problem, including any alternatives you considered
  3. Technologies and decisions — the specific tools, patterns, or architectural choices you made and why
  4. Outcomes — measurable results, user feedback, or qualitative improvements
  5. Lessons learned — what you would do differently, or what the project taught you
Keep the entry card excerpt focused on the problem and outcome. The full writeup can live in the card body or link out to a separate page or article.

Build docs developers (and LLMs) love

Get started for freeTalk to us