OpenQase

OpenQase is a curated collection of quantum computing business cases, cross-referenced by industry, algorithm, and persona. The CMS is built from scratch to manage these metadata relationships and is provided as open source. The case studies and other data are accessible via the website, the REST API, or (upcoming) MCP.

Quick Start

Prerequisites

• Node.js 18+
• Supabase CLI + Docker

Setup

git clone https://github.com/openqase/openqase.git
cd openqase
npm install
cp .env.example .env.local   # then add your Supabase credentials

Start local Supabase and pull the schema:

supabase start
supabase link --project-ref <your-project-ref>
supabase db pull

Run the dev server:

npm run dev           # http://localhost:3000

Build for production:

npm run build
npm run start

Architecture

OpenQase uses a hybrid static/dynamic architecture:

• Static generation for all public content (case studies, algorithms, personas, industries, blog)
• Dynamic rendering for admin CMS and API routes
• On-demand revalidation when content is published/updated, with 1-hour ISR safety net
• Unified content fetching with React.cache() deduplication

Tech Stack

| Layer | Technology | |-------|-----------| | Framework | Next.js 16 (App Router) | | Database | Supabase (Postgres + Auth + RLS) | | UI | shadcn/ui + Tailwind CSS | | Email | Beehiiv (newsletter) + Resend (transactional) | | Caching | Redis (Upstash) with in-memory fallback | | Deployment | Vercel | | Testing | Vitest (235+ tests) |

Content Types

| Type | Public URL | Admin | |------|-----------|-------| | Case Studies | /case-study/[slug] | /admin/case-studies | | Algorithms | /paths/algorithm/[slug] | /admin/algorithms | | Industries | /paths/industry/[slug] | /admin/industries | | Personas | /paths/persona/[slug] | /admin/personas | | Blog Posts | /blog/[slug] | /admin/blog | | Quantum Software | /paths/quantum-software/[slug] | /admin/quantum-software | | Quantum Hardware | /paths/quantum-hardware/[slug] | /admin/quantum-hardware | | Quantum Companies | /paths/quantum-companies/[slug] | /admin/quantum-companies | | Partner Companies | /paths/partner-companies/[slug] | /admin/partner-companies |

Content is cross-referenced via bidirectional junction tables — see API & Relationships Architecture for details.

Project Structure

openqase/
├── src/
│   ├── app/              # Next.js App Router pages
│   │   ├── admin/        # Admin CMS (dynamic)
│   │   ├── api/          # REST API routes
│   │   ├── case-study/   # Case studies (static)
│   │   ├── paths/        # Algorithms, industries, personas, etc. (static)
│   │   └── blog/         # Blog (static)
│   ├── components/       # React components
│   └── lib/              # Content fetchers, Supabase clients, utilities
├── docs/                 # Documentation
├── scripts/              # Import, migration, and admin scripts
└── supabase/             # Database migrations

Documentation

Getting Started

• Installation Guide — setup and local development
• Environment Variables — configuration reference
• Contributing Guide — commit conventions and standards

API

• API Reference — all REST endpoints with examples
• OpenAPI Spec — Swagger/Postman compatible
• API Architecture — patterns and best practices

Architecture

• Unified Content Fetching — static content system
• API & Relationships — junction tables and cross-references
• Authentication — auth patterns and RLS policies
• Caching — Redis caching and rate limiting
• Schema Overview — database schema

Content

• Admin CMS Guide — content management workflows
• Import System — bulk content import
• Content Strategy — content approach and guidelines
• Email System — newsletter and transactional email

Project

• Project Plan — vision, strategy, and roadmap
• Changelog — version history
• Roadmap — public roadmap

Contributing

See CONTRIBUTING.md for guidelines. In brief:

1. Fork the repo and create a feature branch
2. Follow existing patterns — use unified content fetching for public content
3. Run npm test and npm run lint before submitting
4. Open a PR against main

Links

• Website
• GitHub Issues
• GitHub Milestones

License

This project is open source. The software code is freely available; case study content is accessible via the website and API.