Collections
Case Studies
Vendor + client + problem, solution, and measured results — served at /cases/[slug].
Case studies show what a vendor actually delivered. The structured fields (client, problem, solution, results) render as a summary above the story, so buyers can scan the outcome before reading the detail.
Files live in content/cases/en/ (or de/, es/, fr/). English entries are served at /cases/[slug]; other locales keep their folder in the URL.
Frontmatter Fields
| Field | Type | Required | Notes |
|---|---|---|---|
title | string | Yes | Max 120 characters. Lead with the outcome. |
description | string | Yes | Max 200. Used in cards and meta description. |
company | slug | Yes | The vendor that delivered the work (organizations). |
client.name | string | Yes | Client name, or a descriptor such as 'A top-10 European bank' when anonymised. |
client.industry / client.size / client.location / client.url | — | No | size uses company-size values, e.g. '501-1000'. |
products / services | slug[] | No | Listings used in the engagement. The case study also appears on those listing pages. |
problem | string | Yes | Max 600 characters. |
solution | string | Yes | Max 600 characters. |
results | array | Yes | At least one { value, metric }, e.g. { value: '38%', metric: 'faster onboarding' }. The first one is the headline on cards. |
testimonial | object | No | { quote, author, role }. |
authors / organizations | slug[] | No | Byline. |
publishedAt | date | Yes | |
industries, tags | string[] | No | |
featured, draft | boolean | No | Featured entries sort first. |
Template
---
title: ''
description: ''
company: ''
client:
name: ''
industry: ''
products: []
services: []
problem: ''
solution: ''
results:
- value: ''
metric: ''
publishedAt: 2026-01-01
---
The full story: context, approach, rollout, and what's next.