---
title: Components
description: Every c15t Astro component, from ConsentScript and ConsentBanner to
the server island banner, the preference dialog, its link and the IAB TCF
surfaces, with import paths and links to each reference.
group: frameworks
lastModified: "2026-10-10T16:01:45+01:00"
---
## Where the components go
Every component reads `Astro.locals.c15t`, which the integration's middleware
sets on each request. Put them in the layout that wraps every page:
```astro title="src/layouts/base.astro"
---
import { ClientRouter } from 'astro:transitions';
import {
ConsentBanner,
ConsentDialog,
ConsentDialogLink,
ConsentScript,
} from 'c15t/astro/components';
interface Props {
title: string;
}
const { title } = Astro.props;
---
{title}
```
The `c15t()` integration in `astro.config.mjs` plays the part a provider plays
in React or Vue. It holds the configuration every component reads. See
[Integration options](/docs/frameworks/astro/integration).
## Component reference
Import the components by name from `c15t/astro/components`. Astro compiles
the `.astro` files it re-exports, so a page ships only what it renders.
`ConsentBannerDeferred` is the exception: it renders a server island, which
Astro refuses to build on a site without an adapter, so import it from its
own path.
|Component|Import from|Renders|
|--|--|--|
|[`ConsentScript`](/docs/frameworks/astro/components/consent-script)|`c15t/astro/components`|Inline scripts for the boot payload and color scheme, and the theme `