This is an enterprise-ready monorepo starter for content-driven websites, combining Strapi v5 (headless CMS) as the backend and Next.js 16 (App Router) as the frontend, managed with Turborepo and pnpm. In production, it provides a visual page builder with dynamic zones in Strapi, rendered server-side by Next.js with ISR and cache revalidation via Strapi document middleware. The system includes end-user authentication (Better Auth + Strapi JWT), localization (next-intl), media handling (imgproxy), SEO helpers, preview mode, optional CDN purge (Azure Front Door), and observability (Sentry, Azure Monitor). It is not a data research repository; the hybrid nature comes from data seeding workflows and Strapi config-sync exports that version content-model layouts and permissions, but the dominant character is a full-stack web application starter. The architecture is a monorepo with two primary apps (`apps/strapi` and `apps/ui`), shared packages (`packages/design-system`, `packages/logging`, `packages/eslint-config`, `packages/shared-data`, `packages/strapi-types`), a Docusaurus documentation site (`apps/docs`), and a Playwright QA workspace (`qa/tests/playwright`). Key entry points include the Strapi bootstrap and admin panel extensions, the Next.js middleware chain (`proxy.ts`) implementing basic auth, redirects, auth guard, and security headers, catch-all ISR pages, and API routes for revalidation, CDN purge, and Strapi proxying. The primary data flow is content authored in Strapi → published → document middleware triggers UI revalidation → Next.js fetches Strapi content via server-side API clients and renders pages with ISR. External dependencies are modern and pinned (Next.js 16, React 19, Strapi v5, TailwindCSS v4, Better Auth). The codebase demonstrates high craftsmanship with clean abstractions: a composable proxy middleware chain, pluggable CDN and telemetry providers, a typed Strapi API client with pagination, a hierarchy service computing fullPath changes with redirect compaction, and a shared logging package with OpenTelemetry correlation. Testing is comprehensive with Vitest unit tests and Playwright e2e/visual/SEO/accessibility suites. Some scaffolding remains incomplete (e.g., `removeThisWhenYouNeedMe` markers), and the two rich-text editors (CKEditor and TipTap) introduce duplicate rendering paths. Overall, this is a strong, well-documented starter suitable for teams building content-rich websites with a modern stack.
This repository is a starter template for Nuxt 4 applications, created by Anthony Fu. It provides a pre-configured setup with modern tooling including Vue 3, Vite, UnoCSS for atomic CSS, Pinia for state management, PWA support via @vite-pwa/nuxt, and auto-imports for composables and components. The architecture follows Nuxt's file-based routing and SSR model, with a Nitro server layer for API endpoints (e.g., a simple pageview counter). The codebase demonstrates clean, idiomatic usage of Nuxt 4 features like `useState`, `useFetch`, layout system, and the Composition API. It is not a production application but a foundation for building Nuxt projects, with several reusable configuration modules and composables.
Nellavio is a production-grade, open-source Next.js dashboard starter designed for building modern SaaS products, internal tools, and admin panels. It provides 90+ reusable UI components, 60+ chart variations, authentication (Better Auth) with RBAC, i18n (next-intl), theme switching, and extensive data visualization pages (analytics, orders, customers, products, calendar, charts showcase). The architecture follows App Router with clear separation: server components for data fetching (Apollo Client GraphQL with mock fallback), client components for interactive views, Zustand for global state, and TanStack Table for data tables. The codebase is well-tested with Vitest, Storybook, and CI/CD (GitHub Actions). Despite some hardcoded demo data and recent migrations (Clerk→Better-Auth, Tremor→Recharts), the engineering practices are strong, making it a solid foundation for bootstrapping dashboard-centric applications.
Vitesse is an opinionated Vue 3 + Vite starter template created by Anthony Fu. It provides a pre-configured development environment with file-based routing, auto-importing of components and APIs, state management via Pinia, internationalization (i18n) with lazy-loaded locale files, PWA support, Markdown-as-Vue-components, and utility-first CSS via UnoCSS. The template uses static site generation (SSG) via vite-ssg and includes critical CSS extraction. It is designed to accelerate the setup of modern Vue applications by integrating a curated set of plugins and tools. The codebase is well-structured, with clear separation of concerns: pages, layouts, composables, stores, and modules. The i18n module demonstrates a reusable pattern for lazy-loading translations using Vite's glob imports. While the template is primarily a collection of configurations and boilerplate, it exhibits high craftsmanship in its integration choices and adherence to Vue 3 best practices.
This is the official Laravel skeleton application, the default starting point for new Laravel projects created via `composer create-project laravel/laravel`. It provides a minimal, well-structured web application foundation with a single welcome page, default authentication scaffolding (routes only), database migrations for users/cache/jobs, a basic User model, and standard configuration files for all major Laravel services. The repository itself contains no business logic or custom features; it is a clean, maintained template that reflects the current best practices of the Laravel ecosystem (PHP 8.3+, Vite 8, Tailwind 4, PHP 8 attributes). Its primary purpose is to serve as a foundation for developers to build upon, not as a functional application in its own right.
Materio is a free admin dashboard starter template built on Next.js 14 App Router, MUI v5, and Tailwind CSS, published by ThemeSelection. It ships as two parallel, functionally identical codebases: javascript-version/ and typescript-version/. Everything in the repo is static UI - hardcoded demo data, mock ApexCharts, placeholder auth forms - there is no API layer, database, or authentication logic. Its job is to be a polished starting point for admin applications, and it executes that role well: an extensive per-component MUI theme override system, a custom collapsible vertical menu subsystem, and a cookie-persisted settings context for dark/light mode. Architecturally it follows Next.js App Router conventions: root layout (app/layout.jsx), a dashboard layout that wraps the VerticalLayout shell (navigation, navbar, footer), and a blank layout for login/register/error pages. The most interesting engineering lives in src/@menu (a self-contained vertical navigation layer with context-driven collapse/expand and breakpoint behavior), src/@core/theme (dozens of isolated MUI component overrides), and a few genuinely reusable React hooks (useObjectCookie, useImageVariant). All dashboard data is fabricated; adopters must wire real data and backend logic themselves. The template is actively maintained (last commit March 2026, one open issue, automated issue triage workflows). Drift risks are version pinning to Next.js 14 / MUI v5.15 and the maintenance cost of keeping JS and TS variants in sync.
Starter template for Cucumber-JVM with Java and Maven. It is not a production application: the only production source file is an empty Belly class, while all meaningful code lives in the test tree. RunCucumberTest is a JUnit Platform Suite that boots the Cucumber engine, cucumber.properties supplies glue and plugin configuration, and belly.feature defines one scenario whose step definitions are bound via annotations. Running `./mvnw test` executes the suite and prints pretty output; one step passes, one is intentionally aborted with a TODO, and one is undefined. The repository's actual purpose is to demonstrate a minimal Cucumber setup and serve as a starting point for BDD projects. Architecturally this is a Maven build with test-scoped dependencies only: cucumber-java, cucumber-junit-platform-engine, junit-platform-suite, and assertj-core. Dependencies are imported through BOMs, Java 17 is configured as the release target, and the Maven wrapper pins Maven 3.10.0. The primary data flow is Gherkin -> Cucumber engine -> annotated JUnit step methods -> AssertJ assertions. There is no web server, API, or business logic. The repository includes CI that runs the tests on Ubuntu and Windows across Java 17 and 21, Renovate for dependency updates, and a Zizmor workflow for GitHub Actions security analysis, indicating active project maintenance.
This is a production-ready, multi-tenant SaaS starter kit built with Next.js (Pages Router), NextAuth.js, Prisma ORM (PostgreSQL), and Tailwind CSS. The system provides comprehensive enterprise features: email/password authentication, magic link, OAuth (Google, GitHub), SAML/SSO via BoxyHQ Jackson, directory sync (SCIM), webhooks via Svix, audit logging via Retraced, Stripe billing, API keys, and team-based role management (RBAC). The architecture follows a monolith with API routes under /pages/api, middleware for session validation, and a component-based frontend. Data flows center around team creation and management: users register (or SSO), create or join teams via invitations, then configure team-level SSO, directory sync, webhooks, billing, and API keys. The codebase demonstrates solid engineering practices with Zod validation, reusable UI components, and a clear separation of concerns, but shows signs of feature creep and some legacy patterns (e.g., Pages Router). It is well-suited for developers building a SaaS platform who need a jump-start on authentication, team management, and enterprise integrations.
This repository is a curated list of open-source SaaS boilerplates and starter templates. It is a static, community-driven directory (an 'awesome list') that links to external projects across various tech stacks (React/Next.js, Node.js, Django, Flutter, etc.). The repository contains no executable code, API endpoints, or data pipelines—it functions solely as a discoverability resource for developers seeking pre-built SaaS foundations. The architecture is a single README file with a table of contents and categorized sections. There are no software artifacts to analyze; the value lies in the curation and presentation of external projects, not in any implemented system.