# Brease Documentation > The complete developer documentation for the Brease headless CMS and the brease-next Next.js integration package. Brease is a headless CMS for agencies and teams: content editors work in the CMS, and developers use brease-next to fetch and render that content. This index links to the raw Markdown of every documentation page. Each link points to a clean `.md` file; the human-readable HTML page lives at the same URL without the `.md` suffix. ## Introduction - [Brease Documentation](https://docs.brease.io/index.md): The complete developer documentation for the Brease headless CMS and the brease-next integration package. - [Core Concepts](https://docs.brease.io/docs/core-concepts.md): Brease CMS is organized around a set of core entities. ## Content Modeling - [Entity Hierarchy](https://docs.brease.io/docs/entity-hierarchy.md): Every piece of content in Brease follows a strict ownership and scoping chain. - [Sections & Elements](https://docs.brease.io/docs/sections-and-elements.md): Sections and elements are the building blocks of all page content in Brease. - [Collections & Entries](https://docs.brease.io/docs/collections-and-entries.md): Collections let you manage repeatable, structured data — FAQs, team members, products, and more. - [Templates & Page Types](https://docs.brease.io/docs/templates-and-page-types.md): Templates and Page Types help you standardize page layouts and attach page-level metadata across your site. - [Navigations & Redirects](https://docs.brease.io/docs/navigations-and-redirects.md): Navigations and redirects are managed per environment in the CMS and consumed on the frontend via brease-next. - [Multi-Locale Content](https://docs.brease.io/docs/multi-locale.md): Brease supports multi-locale content out of the box. - [Element Types Reference](https://docs.brease.io/docs/element-types.md): Brease supports 14+ element types for defining content fields in sections and collections. ## CMS Guide - [Editor (Definitions)](https://docs.brease.io/docs/editor.md): The Editor is where developers define content structures — the schemas that determine what content editors can fill in. - [Page Builder](https://docs.brease.io/docs/page-builder.md): The Builder is where content editors fill in page content. - [Collection Manager](https://docs.brease.io/docs/collection-manager.md): The Manager is where content editors create and manage collection entries. ## brease-next Package - [Getting Started](https://docs.brease.io/docs/getting-started.md): This guide walks you through setting up brease-next in a Next.js project. - [API Reference](https://docs.brease.io/docs/api-reference.md): Complete reference for all brease-next exports: functions, types, components, and utilities. - [Components](https://docs.brease.io/docs/components.md): The brease-next package exports five React components for rendering CMS content. - [Context & Hooks](https://docs.brease.io/docs/context-and-hooks.md): The BreaseContext server component and useBrease() hook provide a data layer that fetches navigations, page data, collections, and locales on the server and… - [SEO & Metadata](https://docs.brease.io/docs/seo-and-metadata.md): The brease-next package provides functions and components for generating SEO metadata, robots.txt, sitemaps, structured data, and custom code injection -- al… - [Preview Integration](https://docs.brease.io/docs/preview-integration.md): Brease CMS includes a live preview feature that renders your Next.js site inside an iframe and sends real-time content updates as editors make changes. - [CLI Scaffolding](https://docs.brease.io/docs/cli.md): The brease-next CLI creates a fully configured Next.js project connected to your Brease CMS site. ## Implementation Patterns - [Project Setup Guide](https://docs.brease.io/docs/project-setup.md): Two paths to get a Brease-powered Next.js site running: the CLI scaffold (recommended) or manual setup. - [Pages & Dynamic Routes](https://docs.brease.io/docs/pages-and-routes.md): Brease sites use a single optional catch-all route ([[...slug]]) to handle every page, including the homepage. - [Collection Patterns](https://docs.brease.io/docs/collection-patterns.md): Collections in Brease represent structured, repeatable data — FAQs, team members, testimonials, partner logos, feature lists, pricing tiers, and similar cont… - [Navigation Patterns](https://docs.brease.io/docs/navigation-patterns.md): Navigations in Brease are managed in the CMS and fetched automatically by BreaseContext. - [Multi-Locale Sites](https://docs.brease.io/docs/locale-patterns.md): Brease supports multi-locale sites out of the box. - [Media & Images](https://docs.brease.io/docs/media-patterns.md): The BreaseImage component wraps Next.js Image with automatic Brease variant support, responsive srcSet generation, and smart fallbacks. - [Structured Data & Custom Code](https://docs.brease.io/docs/structured-data-patterns.md): Brease provides two components for injecting page-level metadata into your rendered output: BreaseStructuredData for JSON-LD structured data and BreaseCustom… - [Deployment](https://docs.brease.io/docs/deployment.md): This page covers building for production, configuring hosting platforms, ISR revalidation, robots.txt, sitemaps, and a pre-deployment checklist. ## Optional - [Examples](https://docs.brease.io/docs/examples.md): Complete, production-ready examples showing real implementations using brease-next. - [Troubleshooting](https://docs.brease.io/docs/troubleshooting.md): Common issues and solutions when using brease-next package. - [Changelog](https://docs.brease.io/docs/changelog.md): Version history for the brease-next package.