Dev Case Studies

208 real development case studies from 117 countries, searchable, filterable and fully cited.

Part of the ImpactMojo Learning Platform and the OpenStacks for Change initiative.

---

About

Dev Case Studies is a practitioner-oriented library of real-world development case studies drawn from across the Global South and beyond. Each case documents a programme, intervention, or policy with evidence of outcomes, whether positive, negative or mixed, and ties every claim back to a citable source.

The library sets evidence beside theory, so that practitioners, students and researchers can see what development work looks like in practice. Read more on the About and method page.

---

Features

Feature	Description
208 case studies	Spanning 117 countries across the Global South and beyond, with about 960 cited references.
Search & filter	Full-text search plus faceted filters by topic, region and decade, plus an experimental research-question matcher.
Insights dashboard	Live statistics on how the collection is distributed across topics, regions, and decades. Click a bar to filter.
Evidence tiers	Every study is auto-tagged strong / moderate / emerging based on reference count and causal-identification methods.
Saved studies	Bookmark cases to a personal reading list stored in your browser. No account is required.
Reading experience	Reading-time estimates, a scroll progress bar, share links, and per-study Cornell notes you can export as Markdown.
Related studies map	A small literature map surfaces cases connected by shared topic or region.
Light / dark / system theme	Persisted theme with a three-way toggle.
Fast and durable	Zero runtime dependencies. Static HTML, CSS and vanilla JS.

---

Tech stack

Layer	Technology	Purpose
Frontend	Vanilla HTML / CSS / JavaScript	No-framework, no-runtime-dependency search and browse
Data	Per-study JSON (source of truth)	Case study content and metadata
Build	Zero-dependency Node (ESM) pipeline	Validates data and generates the card index, search index, stats, and sitemap
CI	GitHub Actions	Validates the schema, fails on data drift, and checks links
Hosting	GitHub Pages	Static site deployment

---

Project structure

dev-case-studies/
├── index.html            # Library: search, filter, insights dashboard
├── study.html            # Individual case study view
├── about.html            # About and method
├── css/style.css         # Design system (light/dark)
├── js/app.js             # Search, filter, render, bookmarks, insights
├── scripts/
│   ├── build.mjs         # Validate studies + generate derived data
│   └── serve.mjs         # Zero-dependency local dev server
├── data/
│   ├── studies/          # ← source of truth: one JSON per case study
│   ├── master-list.json  # generated card index (do not edit)
│   ├── search-index.json # generated search index (do not edit)
│   ├── stats.json        # generated dashboard statistics (do not edit)
│   └── README.md         # data model & pipeline docs
├── sitemap.xml           # generated
└── package.json          # npm scripts (build / validate / dev)

---

Local development

git clone https://github.com/Varnasr/dev-case-studies.git
cd dev-case-studies

npm run dev        # serve locally on http://localhost:8000
npm run build      # regenerate master-list, search index, stats, sitemap
npm run validate   # CI check: validate the data & fail if artefacts drift

No dependencies are installed. The build and dev server use only the Node standard library (Node ≥ 18).

The data model and the recognised study-content headings are documented in data/README.md.

---

Contributing

Contributions are welcome, whether additional case studies, corrections or improved citations.

To add a case study:

1. Create data/studies/<slug>.json following the data model. Include:
   • programme name, country, region, topic, and years of operation
   • a description of 200 to 400 words with cited evidence of outcomes
   • at least two verifiable sources in a ## References section
2. Run npm run build and commit the regenerated data files.
3. Open a pull request. CI (npm run validate) will fail if the generated data is out of sync.

---

Part of the ImpactMojo ecosystem

Related repositories:

• ImpactMojo, the main platform
• development-discourses, 500+ curated open-access research papers
• ImpactLex, a dictionary of development sector terms

---

License

MIT License. See LICENSE for details.

---

Citation

Sri Raman, V. (2025). Dev Case Studies: 208 real development case studies from 117 countries [Dataset].
ImpactMojo. https://github.com/Varnasr/dev-case-studies