# duxt

> duxt is a Nuxt layer: extend it and your docs/ folder becomes a site, with theme, search, API reference and llms.txt included. Point it at other repositories, or at tags of the same one, and each becomes a version.

## Pages

- [Documentation](https://duxt.app/.md): A Nuxt layer that turns a repository's docs folder into a versioned, multi-repo documentation site.
- [Add-ons](https://duxt.app/add-ons.md): Companion layers that extend a duxt site — each one its own package, added with one more entry in extends.
- [Meilisearch](https://duxt.app/add-ons/meilisearch.md): Add the official companion layer for atomic build-time indexing and optional browser search.
- [Typesense](https://duxt.app/add-ons/typesense.md): Consume duxt's one build hook into a Typesense collection — every source, version and language, upserted by a stable id.
- [Architecture decisions](https://duxt.app/adr.md): The decision log — every architecture decision recorded for duxt.
- [Build duxt as a layer carrying a module](https://duxt.app/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribute the theme as a Nuxt layer whose root is the package, rather than as a starter template.
- [Generate the collections from one source list](https://duxt.app/adr/0002-generate-the-collections-from-one-source-list.md): Compute Content collections from a compact sources list at config load time instead of having consumers declare them.
- [Decide the URL prefixes at build time](https://duxt.app/adr/0003-decide-the-url-prefixes-at-build-time.md): Whether a repository or version segment appears is settled by the source list before the first request, never per request.
- [Render Markdown components with MDC](https://duxt.app/adr/0004-render-markdown-components-with-mdc.md): Use Content's own MDC syntax for components inside Markdown rather than adopting MDX.
- [Ship the layer without owner-specific links](https://duxt.app/adr/0005-ship-the-layer-without-owner-specific-links.md): Every default that would name a specific project — repository, issue tracker, community, imprint — ships empty.
- [Rebuild on a schedule rather than refresh at runtime](https://duxt.app/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): A site reading another repository picks up its changes when it builds, and no runtime refresh is offered.
- [Serve translations as collections of their own](https://duxt.app/adr/0007-serve-translations-as-collections-of-their-own.md): Add a locale dimension to a source rather than a locale segment to the content path.
- [Build the theme on owned shadcn-vue components](https://duxt.app/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): The layer holds the source of its interface components rather than importing them from a component library or a ready-made documentation theme.
- [Take the SEO stack from the Nuxt SEO bundle](https://duxt.app/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): The layer installs @nuxtjs/seo and hands it the head tags and structured data it used to write by hand, keeping only the rules that depend on versions and translations.
- [Keep Content's per-collection search as the default](https://duxt.app/adr/0010-keep-contents-per-collection-search-as-the-default.md): One index across every source was measured against Content's one-index-per-collection search and is not the layer's default; the build-time hook makes it a provider layer instead.
- [Host the provider layers in a Turborepo monorepo](https://duxt.app/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): The layer moves to packages/duxt and the site to apps/www, every published package versions and tags on its own as <name>@vX.Y.Z, and the own-repository decision recorded in
- [Concepts](https://duxt.app/concepts.md): How the layer works — the sources model, the URL scheme, the collections and the checks.
- [What the build checks](https://duxt.app/concepts/build-checks.md): The silent failures this layer had, turned into messages.
- [Collections](https://duxt.app/concepts/collections.md): What Content builds from the sources, and the four things the schema adds.
- [Databases](https://duxt.app/concepts/databases.md): Which Content database adapters a duxt site can deploy on, which of them have been verified, and the one rule that keeps the layer out of the way.
- [Generated sections](https://duxt.app/concepts/generated-sections.md): An artefact plus a type, published as pages — what the registry is, and the two policies a type answers.
- [Keyboard shortcuts](https://duxt.app/concepts/keyboard-shortcuts.md): The four keys the theme binds, where each one applies, and where the reader is told about it.
- [Layers and overriding](https://duxt.app/concepts/layers.md): What a Nuxt layer gives you, what it takes away, and which paths do not resolve the way they read.
- [Localisation](https://duxt.app/concepts/localisation.md): Seven locales ship with the layer, and every configured string takes three forms.
- [Machine readers](https://duxt.app/concepts/machine-readers.md): What a model gets — llms.txt, the raw Markdown of any page, and a real MCP server.
- [SEO](https://duxt.app/concepts/seo.md): What every page emits for crawlers and social cards, which module writes it, and the one value the layer cannot guess.
- [Sources](https://duxt.app/concepts/sources.md): One list of sources becomes every collection, prefix and version the site serves.
- [Theming](https://duxt.app/concepts/theming.md): How the theme is put together — owned components, one token layer, and a dark mode that switches on a class.
- [URLs and versions](https://duxt.app/concepts/urls-and-versions.md): How the repository and version segments appear, and what a reader in an old version is told.
- [Conventions](https://duxt.app/conventions.md): Project-specific rules — the ones a reader could not infer from the code.
- [Branding](https://duxt.app/conventions/branding.md): The [d]uxt mark — where each asset is used, why the icon's brackets are redrawn, and the colours that are fixed.
- [Dependency security](https://duxt.app/conventions/dependency-security.md): Review dependency advisories without hiding affected paths.
- [Icons](https://duxt.app/conventions/icons.md): Four icon sets, and the one question that decides which of them draws a given mark.
- [Credits](https://duxt.app/credits.md): What duxt is built on, and what it was built after.
- [Dokumentation](https://duxt.app/de-DE.md): Eine Nuxt-Ebene, die den docs-Ordner eines Repositories in eine versionierte Dokumentationsseite über mehrere Repositories verwandelt.
- [Add-ons](https://duxt.app/de-DE/add-ons.md): Begleit-Layer, die eine duxt-Site erweitern — jede ein eigenes Paket, eingebunden mit einem weiteren Eintrag in extends.
- [Meilisearch](https://duxt.app/de-DE/add-ons/meilisearch.md): Ergänze die offizielle Companion-Layer für atomare Indizierung beim Build und optionale Browsersuche.
- [Typesense](https://duxt.app/de-DE/add-ons/typesense.md): duxts einen Build-Hook in eine Typesense-Collection überführen — jede Quelle, jede Version und jede Sprache, per stabiler ID aktualisiert.
- [Architekturentscheidungen](https://duxt.app/de-DE/adr.md): Das Entscheidungsprotokoll — jede Architekturentscheidung, die für duxt festgehalten wurde.
- [duxt als Ebene bauen, die ein Modul trägt](https://duxt.app/de-DE/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Das Theme als Nuxt-Ebene ausliefern, deren Wurzel das Paket ist, statt als Starter-Vorlage.
- [Die Collections aus einer Quellenliste erzeugen](https://duxt.app/de-DE/adr/0002-generate-the-collections-from-one-source-list.md): Content-Collections zur Ladezeit der Konfiguration aus einer kompakten Quellenliste berechnen, statt Konsumenten sie deklarieren zu lassen.
- [Die URL-Präfixe zur Build-Zeit entscheiden](https://duxt.app/de-DE/adr/0003-decide-the-url-prefixes-at-build-time.md): Ob ein Repository- oder Versionssegment erscheint, entscheidet die Quellenliste vor der ersten Anfrage, nie pro Anfrage.
- [Markdown-Komponenten mit MDC rendern](https://duxt.app/de-DE/adr/0004-render-markdown-components-with-mdc.md): Für Komponenten in Markdown Contents eigene MDC-Syntax nutzen, statt MDX einzuführen.
- [Die Ebene ohne betreiberspezifische Links ausliefern](https://duxt.app/de-DE/adr/0005-ship-the-layer-without-owner-specific-links.md): Jeder Standard, der ein bestimmtes Projekt benennen würde — Repository, Issue-Tracker, Community, Impressum —, wird leer ausgeliefert.
- [Nach Zeitplan neu bauen statt zur Laufzeit aktualisieren](https://duxt.app/de-DE/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): Eine Seite, die ein anderes Repository liest, übernimmt dessen Änderungen beim Bauen, und eine Aktualisierung zur Laufzeit wird nicht angeboten.
- [Übersetzungen als eigene Collections ausliefern](https://duxt.app/de-DE/adr/0007-serve-translations-as-collections-of-their-own.md): Einer Quelle eine Locale-Dimension hinzufügen statt dem Content-Pfad ein Locale-Segment.
- [Das Theme auf eigenen shadcn-vue-Komponenten bauen](https://duxt.app/de-DE/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): Die Ebene hält den Quelltext ihrer Interface-Komponenten selbst, statt sie aus einer Komponentenbibliothek oder einem fertigen Dokumentations-Theme zu importieren.
- [Den SEO-Unterbau aus dem Nuxt-SEO-Bündel nehmen](https://duxt.app/de-DE/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): Die Ebene installiert @nuxtjs/seo und übergibt ihm die Head-Tags und strukturierten Daten, die sie bislang von Hand schrieb — behalten werden nur die Regeln, die von Versionen und Übersetzungen abhängen.
- [Die Suche pro Collection von Content als Standard behalten](https://duxt.app/de-DE/adr/0010-keep-contents-per-collection-search-as-the-default.md): Ein einziger Index über alle Quellen wurde gegen Contents Suche mit einem Index pro Collection gemessen und ist nicht der Standard der Ebene; der Build-Hook macht ihn stattdessen zu einer Provider-Ebene.
- [Die Provider-Ebenen in einem Turborepo-Monorepo führen](https://duxt.app/de-DE/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): Die Ebene zieht nach packages/duxt und die Website nach apps/www, jedes veröffentlichte Paket versioniert und taggt für sich als <name>@vX.Y.Z, und die in
- [Konzepte](https://duxt.app/de-DE/concepts.md): Wie die Ebene funktioniert — das Quellenmodell, das URL-Schema, die Collections und die Prüfungen.
- [Was der Build prüft](https://duxt.app/de-DE/concepts/build-checks.md): Die stillen Fehlschläge dieser Ebene, in Meldungen verwandelt.
- [Collections](https://duxt.app/de-DE/concepts/collections.md): Was Content aus den Quellen baut, und die vier Dinge, die das Schema hinzufügt.
- [Datenbanken](https://duxt.app/de-DE/concepts/databases.md): Auf welchen Content-Datenbank-Adaptern eine duxt-Website laufen kann, welche davon geprüft sind und die eine Regel, die die Ebene aus dem Weg hält.
- [Generierte Sektionen](https://duxt.app/de-DE/concepts/generated-sections.md): Ein Artefakt plus ein Typ, als Seiten veröffentlicht — was die Registry ist, und welche zwei Richtlinien ein Typ beantwortet.
- [Tastenkürzel](https://duxt.app/de-DE/concepts/keyboard-shortcuts.md): Die vier Tasten, die das Theme belegt, wo jede davon gilt, und wo die Lesende davon erfährt.
- [Ebenen und Überschreiben](https://duxt.app/de-DE/concepts/layers.md): Was eine Nuxt-Ebene dir gibt, was sie dir nimmt, und welche Pfade nicht so auflösen, wie sie sich lesen.
- [Lokalisierung](https://duxt.app/de-DE/concepts/localisation.md): Sieben Locales bringt die Ebene mit, und jede konfigurierte Zeichenkette hat drei Formen.
- [Maschinelle Leser](https://duxt.app/de-DE/concepts/machine-readers.md): Was ein Modell bekommt — llms.txt, das rohe Markdown jeder Seite und ein echter MCP-Server.
- [SEO](https://duxt.app/de-DE/concepts/seo.md): Was jede Seite für Crawler und Social Cards ausgibt, welches Modul es schreibt, und der eine Wert, den die Ebene nicht erraten kann.
- [Quellen](https://duxt.app/de-DE/concepts/sources.md): Eine Liste von Quellen wird zu jeder Collection, jedem Präfix und jeder Version, die die Seite ausliefert.
- [Theming](https://duxt.app/de-DE/concepts/theming.md): Wie das Theme gebaut ist — eigene Komponenten, eine Token-Ebene und ein Dark Mode, der über eine Klasse schaltet.
- [URLs und Versionen](https://duxt.app/de-DE/concepts/urls-and-versions.md): Wie die Repository- und Versionssegmente erscheinen, und was einem Leser in einer alten Version gesagt wird.
- [Konventionen](https://duxt.app/de-DE/conventions.md): Projektspezifische Regeln — die, die sich aus dem Code nicht erschließen lassen.
- [Branding](https://duxt.app/de-DE/conventions/branding.md): Die Marke [d]uxt — wo welches Asset verwendet wird, warum die Klammern des Icons neu gezeichnet sind, und welche Farben feststehen.
- [Abhängigkeitssicherheit](https://duxt.app/de-DE/conventions/dependency-security.md): Sicherheitshinweise prüfen, ohne betroffene Pfade zu verbergen.
- [Icons](https://duxt.app/de-DE/conventions/icons.md): Vier Icon-Sätze, und die eine Frage, die entscheidet, welcher davon ein Zeichen malt.
- [Danksagungen](https://duxt.app/de-DE/credits.md): Worauf duxt aufbaut, und wem es nachempfunden ist.
- [Overview](https://duxt.app/de-DE/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/de-DE/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/de-DE/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/de-DE/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/de-DE/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/de-DE/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/de-DE/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/de-DE/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/de-DE/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/de-DE/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/de-DE/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/de-DE/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/de-DE/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/de-DE/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/de-DE/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/de-DE/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/de-DE/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/de-DE/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/de-DE/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/de-DE/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/de-DE/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/de-DE/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/de-DE/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/de-DE/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/de-DE/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/de-DE/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/de-DE/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/de-DE/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/de-DE/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/de-DE/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/de-DE/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/de-DE/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/de-DE/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/de-DE/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/de-DE/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/de-DE/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/de-DE/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/de-DE/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/de-DE/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/de-DE/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/de-DE/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/de-DE/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/de-DE/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/de-DE/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/de-DE/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/de-DE/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/de-DE/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/de-DE/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/de-DE/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/de-DE/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/de-DE/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/de-DE/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/de-DE/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/de-DE/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/de-DE/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/de-DE/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/de-DE/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/de-DE/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/de-DE/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/de-DE/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/de-DE/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/de-DE/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/de-DE/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/de-DE/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/de-DE/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/de-DE/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/de-DE/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/de-DE/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/de-DE/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/de-DE/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/de-DE/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/de-DE/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/de-DE/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/de-DE/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/de-DE/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Einführung](https://duxt.app/de-DE/getting-started.md): Was duxt ist, und was mit einer einzigen Konfigurationszeile ankommt.
- [Konfiguration](https://duxt.app/de-DE/getting-started/configuration.md): Eine Datei konfiguriert die ganze Seite — was hineingehört, und wie sie zusammengeführt wird.
- [Mit dem Starter beginnen](https://duxt.app/de-DE/getting-started/from-starter.md): Erstelle mit Nuxi eine sofort lauffähige duxt-Dokumentationsseite.
- [Installation](https://duxt.app/de-DE/getting-started/installation.md): Ebene einbinden, erweitern, Markdown schreiben.
- [Anleitungen](https://duxt.app/de-DE/guides.md): Eine Aufgabe je Seite, von vorn bis hinten — mehrere Repositories, mehrere Versionen, mehrere Sprachen und ein Deployment.
- [Deiner Website eine Marke geben](https://duxt.app/de-DE/guides/brand-your-site.md): Name, Wortmarke und Icons setzen, damit die Website als deine gelesen wird und nicht als die der Ebene.
- [Remote-Quellen und OG-Bilder cachen](https://duxt.app/de-DE/guides/cache-build-work.md): Öffentliche Repository-Downloads und gerenderte Social Cards sicher zwischen CI-Builds wiederverwenden.
- [Seiten-Feedback sammeln](https://duxt.app/de-DE/guides/collect-page-feedback.md): DuxtPageFeedback umhüllen und die Antwort dort behalten, wo deine Analytik ohnehin liegt.
- [Eine Seite ausliefern](https://duxt.app/de-DE/guides/deploy-a-site.md): Wo eine duxt-Seite laufen kann, was sie dort braucht, und warum Inhalte nicht zur Laufzeit aufgefrischt werden.
- [Eine Seite verschieben](https://duxt.app/de-DE/guides/move-a-page.md): redirectFrom im Frontmatter, in Routenregeln unter jedem Präfix übersetzt.
- [Das Theme überschreiben](https://duxt.app/de-DE/guides/override-the-theme.md): Eine Farbe ändern, eine Komponente ersetzen, ein shadcn-vue-Primitiv hinzufügen.
- [Terraform-Provider-Dokumentation veröffentlichen](https://duxt.app/de-DE/guides/publish-terraform-provider-docs.md): Einen tfplugindocs-Markdown-Baum als versionierte Provider-Referenz mit passender Navigation veröffentlichen.
- [Analytik-Ereignisse senden](https://duxt.app/de-DE/guides/send-analytics-events.md): Ein Callback, fünf Ereignisse, kein Anbieter — verdrahte duxts Leserinteraktionen mit der Analytik, die du ohnehin betreibst.
- [Mehrere Sprachen](https://duxt.app/de-DE/guides/several-languages.md): Die Oberfläche in mehreren Sprachen ausliefern — und die Seiten selbst übersetzen.
- [Mehrere Repositories](https://duxt.app/de-DE/guides/several-repositories.md): Die Dokumentation mehrerer Projekte von einer Seite ausliefern.
- [Mehrere Versionen](https://duxt.app/de-DE/guides/several-versions.md): Dieselbe Dokumentation an mehreren Refs ausliefern, mit Umschalter und Banner.
- [Referenz](https://duxt.app/de-DE/reference.md): Die öffentliche Oberfläche der Ebene — Konfigurationsschlüssel, Frontmatter, Komponenten, Composables und Endpunkte.
- [Bruno-Collections](https://duxt.app/de-DE/reference/bruno.md): Eine Bruno-Collection als request-zentrierte Referenz mit herunterladbarem Archiv.
- [Die Collection beziehen](https://duxt.app/de-DE/reference/bruno/getting-the-collection.md): Das Archiv ist an Version und Sprache der Seite gebunden; der Bruno-Link nicht.
- [Die Sektion deklarieren](https://duxt.app/de-DE/reference/bruno/section.md): Wo eine Bruno-Collection liegt, welche Seiten sie erzeugt und welche Optionen gelten.
- [Der Request-Client](https://duxt.app/de-DE/reference/bruno/try-it.md): Standardmäßig aus und nur auf ausdrücklich öffentliche Ziele gerichtet.
- [Was veröffentlicht wird](https://duxt.app/de-DE/reference/bruno/what-is-published.md): Environments, Zugangsdaten, Scripts und Tests erreichen keine Seite.
- [Changelog](https://duxt.app/de-DE/reference/changelog.md): Ein Release-Log, als Seiten veröffentlicht — eine Zeitleiste, eine Seite pro Release, und ein Feed.
- [Layout und Komponenten](https://duxt.app/de-DE/reference/changelog/components.md): Das Layout, in dem eine getrennte Historie rendert, und die zwei MDC-Komponenten, aus denen ihre Seiten bestehen.
- [Granularität](https://duxt.app/de-DE/reference/changelog/granularity.md): Eine Seite pro Release, oder die Datei als die eine Seite, als die sie geschrieben wurde.
- [Die Sektion deklarieren](https://duxt.app/de-DE/reference/changelog/section.md): Der Sektionstyp `changelog` — wo die Datei liegt, und welche zwei Richtlinien er beantwortet.
- [Was gelesen wird](https://duxt.app/de-DE/reference/changelog/what-is-read.md): Welche Überschriften zu Releases werden, welche zu Gruppen, und was mit dem Rest passiert.
- [Komponenten](https://duxt.app/de-DE/reference/components.md): Die eigenen Komponenten der Ebene, je eine Seite — wofür jede da ist, und was sie nimmt.
- [Bedienelemente](https://duxt.app/de-DE/reference/components/controls.md): Was ein Leser bedient — die Suche, die Umschalter, die Tastenkürzel-Übersicht und zwei Anzeigen.
- [DuxtLocale](https://duxt.app/de-DE/reference/components/controls/duxt-locale.md): Der Sprachumschalter.
- [DuxtProgress](https://duxt.app/de-DE/reference/components/controls/duxt-progress.md): Wie weit unten auf der Seite der Leser ist.
- [DuxtSearch](https://duxt.app/de-DE/reference/components/controls/duxt-search.md): Jede aktive Quelle durchsuchen und ihre lokal bewerteten Ergebnisse verschränken.
- [DuxtShortcuts](https://duxt.app/de-DE/reference/components/controls/duxt-shortcuts.md): Die Übersicht der Tastenkürzel, auf ?.
- [DuxtShortcutsTrigger](https://duxt.app/de-DE/reference/components/controls/duxt-shortcuts-trigger.md): Der Button, der die Übersicht der Tastenkürzel öffnet.
- [DuxtSkipLink](https://duxt.app/de-DE/reference/components/controls/duxt-skip-link.md): Das erste fokussierbare Element auf der Seite.
- [DuxtVersion](https://duxt.app/de-DE/reference/components/controls/duxt-version.md): Das Versions-Abzeichen, und der Umschalter, wenn es mehr als eine gibt.
- [DuxtVersionBanner](https://duxt.app/de-DE/reference/components/controls/duxt-version-banner.md): Der Balken, der einem Leser sagt, dass diese Version nicht die aktuelle ist.
- [Layout](https://duxt.app/de-DE/reference/components/layout.md): Die zwei Komponenten, die eine Seite rahmen — die Navigationsleiste und der Fußbereich.
- [DuxtAnnouncements](https://duxt.app/de-DE/reference/components/layout/duxt-announcements.md): Site-eigene Hinweise, je Platzierung nur gezeichnet, wenn es etwas zu sagen gibt.
- [DuxtFooter](https://duxt.app/de-DE/reference/components/layout/duxt-footer.md): Der Fußbereich: der Name der Seite, ihre rechtlichen Links und die eigene Zeile der Ebene.
- [DuxtHeader](https://duxt.app/de-DE/reference/components/layout/duxt-header.md): Die Navbar: Titel, Navigation, Suche und die Icon-Links.
- [Navigation](https://duxt.app/de-DE/reference/components/navigation.md): Sich zurechtfinden — die Sektionszeile, die Seitenleiste, die Spur, das Inhaltsverzeichnis und vor/zurück.
- [DuxtBreadcrumb](https://duxt.app/de-DE/reference/components/navigation/duxt-breadcrumb.md): Die Spur über dem Seitentitel.
- [DuxtNavigation](https://duxt.app/de-DE/reference/components/navigation/duxt-navigation.md): Der Baum der Seitenleiste.
- [DuxtNavigationLink](https://duxt.app/de-DE/reference/components/navigation/duxt-navigation-link.md): Ein Eintrag der Seitenleiste.
- [DuxtPageNav](https://duxt.app/de-DE/reference/components/navigation/duxt-page-nav.md): Zurück und weiter, begrenzt durch die Sektion.
- [DuxtSections](https://duxt.app/de-DE/reference/components/navigation/duxt-sections.md): Die zweite Navigationszeile — die obersten Teile der Dokumentation.
- [DuxtToc](https://duxt.app/de-DE/reference/components/navigation/duxt-toc.md): Das Inhaltsverzeichnis und der Nebenbereich darunter.
- [Seite](https://duxt.app/de-DE/reference/components/page.md): Die Komponenten, die zur Seite selbst gehören.
- [DuxtCodeBlock](https://duxt.app/de-DE/reference/components/page/duxt-code-block.md): Die Karte um einen Codeblock.
- [DuxtCopyPage](https://duxt.app/de-DE/reference/components/page/duxt-copy-page.md): Diese Seite an ein Modell übergeben — oder ihre Quelle lesen.
- [DuxtPageFeedback](https://duxt.app/de-DE/reference/components/page/duxt-page-feedback.md): „War diese Seite hilfreich?“ — ein Ereignis, und kein Backend.
- [DuxtPageInfo](https://duxt.app/de-DE/reference/components/page/duxt-page-info.md): Woher die Seite kommt: Bearbeiten-Link, letzte Änderung, Mitwirkende.
- [Composables](https://duxt.app/de-DE/reference/composables.md): Die Funktionen, die die Ebene deinen eigenen Komponenten offenlegt, je eine Seite.
- [Konfiguration und Inhalt](https://duxt.app/de-DE/reference/composables/config-and-content.md): Die zusammengeführte Konfiguration, und welche Collection die gerade gelesene Seite ausliefert.
- [useDuxtBreadcrumb()](https://duxt.app/de-DE/reference/composables/config-and-content/use-duxt-breadcrumb.md): Die Spur von der Sektion hinunter zu einer Seite.
- [useDuxtCollection()](https://duxt.app/de-DE/reference/composables/config-and-content/use-duxt-collection.md): Welche Collection diese Route bedient.
- [useDuxtConfig()](https://duxt.app/de-DE/reference/composables/config-and-content/use-duxt-config.md): Die zusammengeführte Konfiguration, jedes Textfeld bereits aufgelöst.
- [useDuxtNavigation()](https://duxt.app/de-DE/reference/composables/config-and-content/use-duxt-navigation.md): Der Navigationsbaum der Collection, die diese Route bedient.
- [useDuxtSection()](https://duxt.app/de-DE/reference/composables/config-and-content/use-duxt-section.md): Der Teil der Dokumentation, in dem diese Seite liegt.
- [Pfade und Versionen](https://duxt.app/de-DE/reference/composables/paths-and-versions.md): Eine URL lesen, eine zurückschreiben, und wissen, welche Version gerade gelesen wird.
- [useDuxtLink()](https://duxt.app/de-DE/reference/composables/paths-and-versions/use-duxt-link.md): Ein Dokumentationspfad, wieder als Link ausgeschrieben.
- [useDuxtPath()](https://duxt.app/de-DE/reference/composables/paths-and-versions/use-duxt-path.md): Der Pfad, unter dem die Dokumentation liegt, ohne Locale-Segment.
- [useDuxtSiteUrl()](https://duxt.app/de-DE/reference/composables/paths-and-versions/use-duxt-site-url.md): Der konfigurierte Ursprung, und Pfade absolut gemacht.
- [useDuxtVersion()](https://duxt.app/de-DE/reference/composables/paths-and-versions/use-duxt-version.md): Was der Umschalter zeigt, was das Banner sagt, ob indexiert wird.
- [Leseerlebnis](https://duxt.app/de-DE/reference/composables/reading.md): Suche, Überschriften, Fokus, Verlauf und die Entscheidungen, die ein Leser trifft.
- [useActiveHeading()](https://duxt.app/de-DE/reference/composables/reading/use-active-heading.md): Die Überschrift, die gerade im Blick ist.
- [useDuxtAnalytics()](https://duxt.app/de-DE/reference/composables/reading/use-duxt-analytics.md): Eine Leserinteraktion an das eigene Callback der Seite melden — oder an niemanden.
- [useDuxtPageFocus()](https://duxt.app/de-DE/reference/composables/reading/use-duxt-page-focus.md): Setzt den Fokus nach einer clientseitigen Navigation auf die Überschrift.
- [useDuxtSearch()](https://duxt.app/de-DE/reference/composables/reading/use-duxt-search.md): Jede aktive Quelle durchsuchen und ihre lokal bewerteten Ergebnisse verschränken.
- [useDuxtShortcuts()](https://duxt.app/de-DE/reference/composables/reading/use-duxt-shortcuts.md): Die Tasten, auf die das Theme hört.
- [useDuxtToast()](https://duxt.app/de-DE/reference/composables/reading/use-duxt-toast.md): Benachrichtigungen, gekapselt, damit keine Komponente die Bibliothek importiert.
- [useFuzzySearch()](https://duxt.app/de-DE/reference/composables/reading/use-fuzzy-search.md): Tippfehlertoleranz neben dem exakten Index.
- [usePackageManager()](https://duxt.app/de-DE/reference/composables/reading/use-package-manager.md): Der Paketmanager, den ein Leser gewählt hat.
- [useRecentPages()](https://duxt.app/de-DE/reference/composables/reading/use-recent-pages.md): Die zuletzt geöffneten Seiten bis zum konfigurierten Limit.
- [Konfiguration](https://duxt.app/de-DE/reference/configuration.md): Jeder Schlüssel unter duxt in app.config.ts — was er steuert, und wann er gelesen wird.
- [Devtools](https://duxt.app/de-DE/reference/devtools.md): Zehn Panels, die zeigen, was aus deinen Quellen geworden ist. Nur im Dev-Modus.
- [Cache](https://duxt.app/de-DE/reference/devtools/cache.md): Der Download-Cache von Content und ein Weg, einen Eintrag zu verwerfen.
- [Prüfungen](https://duxt.app/de-DE/reference/devtools/checks.md): Der Build-Validator, ausgeführt gegen das, was die Seite gerade ausliefert.
- [Config](https://duxt.app/de-DE/reference/devtools/config.md): Die zusammengeführte `duxt`-Config, und von welcher Seite der Zusammenführung jeder Wert kam.
- [i18n](https://duxt.app/de-DE/reference/devtools/i18n.md): Message-Keys pro Locale, gegen die Basissprache.
- [Seiten](https://duxt.app/de-DE/reference/devtools/pages.md): Jede Seite jeder Collection, mit ihrem Frontmatter und ihren Git-Metadaten.
- [Pfade](https://duxt.app/de-DE/reference/devtools/paths.md): URL einfügen und sehen, welche Quelle sie beansprucht und was sie dort findet.
- [Weiterleitungen](https://duxt.app/de-DE/reference/devtools/redirects.md): Jeder Redirect, den der Server ausliefert, und welche davon die Ebene geschrieben hat.
- [Suche](https://duxt.app/de-DE/reference/devtools/search.md): Was der Suchindex hält, durch dieselbe Abfrage, die der Dialog ausführt.
- [Quellen](https://duxt.app/de-DE/reference/devtools/sources.md): Was aus `duxt.sources` geworden ist — eine Collection je Quelle, Version und Sprache.
- [Versionen](https://duxt.app/de-DE/reference/devtools/versions.md): Welche Version — und welche Sprache — trägt welche Seite.
- [Endpunkte](https://duxt.app/de-DE/reference/endpoints.md): Alles, was die Seite außer Seiten ausliefert, je eine Seite.
- [/_duxt/devtools](https://duxt.app/de-DE/reference/endpoints/devtools.md): Die Route, unter der das Nuxt-Devtools-Panel ausgeliefert wird. Nur im Dev-Server.
- [/llms-full.txt](https://duxt.app/de-DE/reference/endpoints/llms-full-txt.md): Eine duxt-Erweiterung mit denselben Seiten in einer Markdown-Datei.
- [/llms.txt](https://duxt.app/de-DE/reference/endpoints/llms-txt.md): Die Dokumentation als Markdown-Index, nach llmstxt.org.
- [/mcp](https://duxt.app/de-DE/reference/endpoints/mcp.md): Ein MCP-Server über denselben Inhalten.
- [<seite>.md](https://duxt.app/de-DE/reference/endpoints/page-markdown.md): Der Quelltext jeder Seite, unter ihrer eigenen URL plus .md.
- [/rss.xml](https://duxt.app/de-DE/reference/endpoints/rss-xml.md): Der Feed, sobald eine Sektion benannt ist.
- [/sitemap.xml und /robots.txt](https://duxt.app/de-DE/reference/endpoints/sitemap-and-robots.md): Worauf ein Crawler gezeigt wird, und wovon er ferngehalten wird.
- [Frontmatter](https://duxt.app/de-DE/reference/frontmatter.md): Die Felder, die eine Seite über Titel und Beschreibung hinaus tragen darf, und die zwei, die der Build füllt.
- [Hooks](https://duxt.app/de-DE/reference/hooks.md): Der eine Build-Hook, den duxt aussendet, was er übergibt und warum es nur einen gibt.
- [MDC-Komponenten](https://duxt.app/de-DE/reference/mdc-components.md): Die Blöcke, die eine Markdown-Seite aufrufen kann, je eine Seite, mit ihren Props.
- [Accordion](https://duxt.app/de-DE/reference/mdc-components/accordion.md): Aufklappbare Abschnitte — eine FAQ, oder Antworten, aus denen ein Leser wählt.
- [Accordion-Element](https://duxt.app/de-DE/reference/mdc-components/accordion-item.md): Ein aufklappbarer Abschnitt.
- [Callout](https://duxt.app/de-DE/reference/mdc-components/callout.md): Ein Einschub, an dem der Leser innehalten soll — ein Tipp, eine Warnung, eine Gefahr.
- [Code-Gruppe](https://duxt.app/de-DE/reference/mdc-components/code-group.md): Mehrere Fences als ein Block mit Tabs, beschriftet mit dem Dateinamen.
- [Feld](https://duxt.app/de-DE/reference/mdc-components/field.md): Ein Parameter, eine Eigenschaft oder eine Option, mit Typ und Standard.
- [Feldgruppe](https://duxt.app/de-DE/reference/mdc-components/field-group.md): Eine Liste von Feldern als ein Block.
- [Dateibaum](https://duxt.app/de-DE/reference/mdc-components/file-tree.md): Eine Ordnerstruktur, mit Icons je Dateityp.
- [Mermaid](https://duxt.app/de-DE/reference/mdc-components/mermaid.md): Ein Diagramm aus einem Fence oder einem Prop.
- [Paketmanager](https://duxt.app/de-DE/reference/mdc-components/package-managers.md): Ein Befehl, ein Tab je Paketmanager, über Seiten hinweg gemerkt.
- [Seitenkarten](https://duxt.app/de-DE/reference/mdc-components/page-cards.md): Die Kinder einer Sektion, als Karten.
- [Partial](https://duxt.app/de-DE/reference/mdc-components/partial.md): Ein Block, einmal geschrieben und in jeder Quelle gerendert, die ihn braucht.
- [Vorschau](https://duxt.app/de-DE/reference/mdc-components/preview.md): Eine Komponente, so gerendert, wie die Seite sie rendert, mit ihrem Quelltext daneben.
- [Prose-Overrides](https://duxt.app/de-DE/reference/mdc-components/prose.md): Was die Ebene an schlichtem Markdown ändert — Links, Überschriften, Bilder, Code und Tabellen.
- [ProseA](https://duxt.app/de-DE/reference/mdc-components/prose/prose-a.md): Ein Link, aufgelöst gegen die Quelle, in der er geschrieben wurde.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/de-DE/reference/mdc-components/prose/prose-headings.md): Überschriften, jede mit einem Permalink-Anker.
- [ProseImg](https://duxt.app/de-DE/reference/mdc-components/prose/prose-img.md): Ein Bild: Theme-bewusst, responsiv und zoombar.
- [ProsePre](https://duxt.app/de-DE/reference/mdc-components/prose/prose-pre.md): Der Code-Block: Dateiname, Sprach-Icon, Kopier-Button.
- [ProseTable](https://duxt.app/de-DE/reference/mdc-components/prose/prose-table.md): Eine Tabelle, die scrollt statt der Seite.
- [Since](https://duxt.app/de-DE/reference/mdc-components/since.md): Die Version, in der etwas kam, neben einer Überschrift.
- [Schritte](https://duxt.app/de-DE/reference/mdc-components/steps.md): Eine geordnete Liste, gezeichnet als nummerierte Schritte an einer Schiene.
- [Tab](https://duxt.app/de-DE/reference/mdc-components/tab.md): Ein Panel einer Tab-Gruppe.
- [Tab-Gruppe](https://duxt.app/de-DE/reference/mdc-components/tab-group.md): Tabs für alles, was kein Code ist.
- [API-Referenz](https://duxt.app/de-DE/reference/openapi.md): Ein OpenAPI-Dokument, veröffentlicht als Referenzseiten mit einem Client, der echte Anfragen sendet.
- [Komponenten](https://duxt.app/de-DE/reference/openapi/components.md): Die drei MDC-Komponenten, aus denen eine generierte Referenzseite besteht.
- [Request-Samples](https://duxt.app/de-DE/reference/openapi/request-samples.md): Dieselbe Anfrage in zwölf Clients, und wie du eigene hinzufügst.
- [Die Sektion deklarieren](https://duxt.app/de-DE/reference/openapi/section.md): Der Sektionstyp `openapi` — wo das Dokument liegt, und was daraus wird.
- [Der Try-it-Client](https://duxt.app/de-DE/reference/openapi/try-it.md): Eine echte Anfrage, gesendet vom Browser des Lesers.
- [Quellen](https://duxt.app/de-DE/reference/sources.md): Die Felder eines Quelleneintrags, seine Refs, und die Optionen, die die URLs formen.
- [Releases](https://duxt.app/de-DE/releases.md)
- [0.1.0](https://duxt.app/de-DE/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/de-DE/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/de-DE/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/de-DE/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/de-DE/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/de-DE/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/de-DE/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/de-DE/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/de-DE/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/de-DE/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/de-DE/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/de-DE/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/de-DE/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/de-DE/releases/v0.9.0.md)
- [Overview](https://duxt.app/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Documentation](https://duxt.app/en-US.md): A Nuxt layer that turns a repository's docs folder into a versioned, multi-repo documentation site.
- [Add-ons](https://duxt.app/en-US/add-ons.md): Companion layers that extend a duxt site — each one its own package, added with one more entry in extends.
- [Meilisearch](https://duxt.app/en-US/add-ons/meilisearch.md): Add the official companion layer for atomic build-time indexing and optional browser search.
- [Typesense](https://duxt.app/en-US/add-ons/typesense.md): Consume duxt's one build hook into a Typesense collection — every source, version and language, upserted by a stable id.
- [Architecture decisions](https://duxt.app/en-US/adr.md): The decision log — every architecture decision recorded for duxt.
- [Build duxt as a layer carrying a module](https://duxt.app/en-US/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribute the theme as a Nuxt layer whose root is the package, rather than as a starter template.
- [Generate the collections from one source list](https://duxt.app/en-US/adr/0002-generate-the-collections-from-one-source-list.md): Compute Content collections from a compact sources list at config load time instead of having consumers declare them.
- [Decide the URL prefixes at build time](https://duxt.app/en-US/adr/0003-decide-the-url-prefixes-at-build-time.md): Whether a repository or version segment appears is settled by the source list before the first request, never per request.
- [Render Markdown components with MDC](https://duxt.app/en-US/adr/0004-render-markdown-components-with-mdc.md): Use Content's own MDC syntax for components inside Markdown rather than adopting MDX.
- [Ship the layer without owner-specific links](https://duxt.app/en-US/adr/0005-ship-the-layer-without-owner-specific-links.md): Every default that would name a specific project — repository, issue tracker, community, imprint — ships empty.
- [Rebuild on a schedule rather than refresh at runtime](https://duxt.app/en-US/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): A site reading another repository picks up its changes when it builds, and no runtime refresh is offered.
- [Serve translations as collections of their own](https://duxt.app/en-US/adr/0007-serve-translations-as-collections-of-their-own.md): Add a locale dimension to a source rather than a locale segment to the content path.
- [Build the theme on owned shadcn-vue components](https://duxt.app/en-US/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): The layer holds the source of its interface components rather than importing them from a component library or a ready-made documentation theme.
- [Take the SEO stack from the Nuxt SEO bundle](https://duxt.app/en-US/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): The layer installs @nuxtjs/seo and hands it the head tags and structured data it used to write by hand, keeping only the rules that depend on versions and translations.
- [Keep Content's per-collection search as the default](https://duxt.app/en-US/adr/0010-keep-contents-per-collection-search-as-the-default.md): One index across every source was measured against Content's one-index-per-collection search and is not the layer's default; the build-time hook makes it a provider layer instead.
- [Host the provider layers in a Turborepo monorepo](https://duxt.app/en-US/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): The layer moves to packages/duxt and the site to apps/www, every published package versions and tags on its own as <name>@vX.Y.Z, and the own-repository decision recorded in
- [Concepts](https://duxt.app/en-US/concepts.md): How the layer works — the sources model, the URL scheme, the collections and the checks.
- [What the build checks](https://duxt.app/en-US/concepts/build-checks.md): The silent failures this layer had, turned into messages.
- [Collections](https://duxt.app/en-US/concepts/collections.md): What Content builds from the sources, and the four things the schema adds.
- [Databases](https://duxt.app/en-US/concepts/databases.md): Which Content database adapters a duxt site can deploy on, which of them have been verified, and the one rule that keeps the layer out of the way.
- [Generated sections](https://duxt.app/en-US/concepts/generated-sections.md): An artefact plus a type, published as pages — what the registry is, and the two policies a type answers.
- [Keyboard shortcuts](https://duxt.app/en-US/concepts/keyboard-shortcuts.md): The four keys the theme binds, where each one applies, and where the reader is told about it.
- [Layers and overriding](https://duxt.app/en-US/concepts/layers.md): What a Nuxt layer gives you, what it takes away, and which paths do not resolve the way they read.
- [Localisation](https://duxt.app/en-US/concepts/localisation.md): Seven locales ship with the layer, and every configured string takes three forms.
- [Machine readers](https://duxt.app/en-US/concepts/machine-readers.md): What a model gets — llms.txt, the raw Markdown of any page, and a real MCP server.
- [SEO](https://duxt.app/en-US/concepts/seo.md): What every page emits for crawlers and social cards, which module writes it, and the one value the layer cannot guess.
- [Sources](https://duxt.app/en-US/concepts/sources.md): One list of sources becomes every collection, prefix and version the site serves.
- [Theming](https://duxt.app/en-US/concepts/theming.md): How the theme is put together — owned components, one token layer, and a dark mode that switches on a class.
- [URLs and versions](https://duxt.app/en-US/concepts/urls-and-versions.md): How the repository and version segments appear, and what a reader in an old version is told.
- [Conventions](https://duxt.app/en-US/conventions.md): Project-specific rules — the ones a reader could not infer from the code.
- [Branding](https://duxt.app/en-US/conventions/branding.md): The [d]uxt mark — where each asset is used, why the icon's brackets are redrawn, and the colours that are fixed.
- [Dependency security](https://duxt.app/en-US/conventions/dependency-security.md): Review dependency advisories without hiding affected paths.
- [Icons](https://duxt.app/en-US/conventions/icons.md): Four icon sets, and the one question that decides which of them draws a given mark.
- [Credits](https://duxt.app/en-US/credits.md): What duxt is built on, and what it was built after.
- [Overview](https://duxt.app/en-US/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/en-US/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/en-US/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/en-US/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/en-US/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/en-US/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/en-US/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/en-US/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/en-US/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/en-US/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/en-US/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/en-US/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/en-US/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/en-US/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/en-US/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/en-US/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/en-US/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/en-US/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/en-US/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/en-US/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/en-US/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/en-US/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/en-US/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/en-US/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/en-US/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/en-US/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/en-US/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/en-US/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/en-US/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/en-US/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/en-US/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/en-US/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/en-US/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/en-US/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/en-US/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/en-US/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/en-US/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/en-US/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/en-US/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/en-US/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/en-US/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/en-US/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/en-US/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/en-US/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/en-US/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/en-US/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/en-US/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/en-US/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/en-US/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/en-US/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/en-US/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/en-US/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/en-US/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/en-US/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/en-US/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/en-US/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/en-US/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/en-US/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/en-US/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/en-US/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/en-US/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/en-US/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/en-US/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/en-US/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/en-US/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/en-US/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/en-US/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/en-US/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/en-US/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/en-US/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/en-US/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/en-US/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/en-US/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/en-US/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/en-US/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Introduction](https://duxt.app/en-US/getting-started.md): What duxt is, and what arrives with a single line of config.
- [Configuration](https://duxt.app/en-US/getting-started/configuration.md): One file configures the whole site — what belongs in it, and how it merges.
- [Start from the starter](https://duxt.app/en-US/getting-started/from-starter.md): Create a ready-to-run duxt documentation site with Nuxi.
- [Installation](https://duxt.app/en-US/getting-started/installation.md): Add the layer, extend it, write Markdown.
- [Guides](https://duxt.app/en-US/guides.md): One task per page, start to finish — several repositories, several versions, several languages, and a deploy.
- [Brand your site](https://duxt.app/en-US/guides/brand-your-site.md): Set the name, the wordmark and the icons, so the site reads as yours rather than as the layer's.
- [Cache remote sources and OG images](https://duxt.app/en-US/guides/cache-build-work.md): Reuse downloaded public repositories and rendered social cards safely between CI builds.
- [Collect page feedback](https://duxt.app/en-US/guides/collect-page-feedback.md): Wrap DuxtPageFeedback, keep the answer where your analytics already live.
- [Deploy a site](https://duxt.app/en-US/guides/deploy-a-site.md): Where a duxt site can run, what it needs there, and why content is not refreshed at runtime.
- [Move a page](https://duxt.app/en-US/guides/move-a-page.md): redirectFrom in the frontmatter, turned into route rules under every prefix.
- [Override the theme](https://duxt.app/en-US/guides/override-the-theme.md): Change a colour, replace a component, add a shadcn-vue primitive.
- [Publish Terraform provider docs](https://duxt.app/en-US/guides/publish-terraform-provider-docs.md): Turn a tfplugindocs Markdown tree into a versioned provider reference with provider-aware navigation.
- [Send analytics events](https://duxt.app/en-US/guides/send-analytics-events.md): One callback, five events, no provider — wire duxt's reader interactions into the analytics you already run.
- [Several languages](https://duxt.app/en-US/guides/several-languages.md): Serve the interface in several languages, and translate the pages themselves.
- [Several repositories](https://duxt.app/en-US/guides/several-repositories.md): Serve the documentation of several projects from one site.
- [Several versions](https://duxt.app/en-US/guides/several-versions.md): Serve the same documentation at several refs, with a switcher and a banner.
- [Reference](https://duxt.app/en-US/reference.md): The layer's public surface — config keys, frontmatter, components, composables and endpoints.
- [Bruno collections](https://duxt.app/en-US/reference/bruno.md): A Bruno collection, published as request-centred reference pages with a downloadable archive.
- [Getting the collection](https://duxt.app/en-US/reference/bruno/getting-the-collection.md): The archive is pinned to the page you are on; the Bruno deep link is not.
- [Declaring the section](https://duxt.app/en-US/reference/bruno/section.md): The `bruno` section type — where the collection lives, and what it becomes.
- [The request client](https://duxt.app/en-US/reference/bruno/try-it.md): Off until a site turns it on, and pointed only at what the site declared public.
- [What is published](https://duxt.app/en-US/reference/bruno/what-is-published.md): Environments, credentials, scripts and tests never reach a page — and what that means for the archive.
- [Changelog](https://duxt.app/en-US/reference/changelog.md): A release log, published as pages — a timeline, a page per release, and a feed.
- [Layout and components](https://duxt.app/en-US/reference/changelog/components.md): The layout a split history renders in, and the two MDC components its pages are made of.
- [Granularity](https://duxt.app/en-US/reference/changelog/granularity.md): A page per release, or the file as the one page it was written as.
- [Declaring the section](https://duxt.app/en-US/reference/changelog/section.md): The `changelog` section type — where the file lives, and the two policies it answers.
- [What is read](https://duxt.app/en-US/reference/changelog/what-is-read.md): Which headings become releases, which become groups, and what happens to the rest.
- [Components](https://duxt.app/en-US/reference/components.md): The layer's own components, one page each — what each is for, and what it takes.
- [Controls](https://duxt.app/en-US/reference/components/controls.md): What a reader operates — search, the switchers, the shortcut sheet, and two indicators.
- [DuxtLocale](https://duxt.app/en-US/reference/components/controls/duxt-locale.md): The language switcher.
- [DuxtProgress](https://duxt.app/en-US/reference/components/controls/duxt-progress.md): How far down the page the reader is.
- [DuxtSearch](https://duxt.app/en-US/reference/components/controls/duxt-search.md): Search every active source and interleave its locally ranked results.
- [DuxtShortcuts](https://duxt.app/en-US/reference/components/controls/duxt-shortcuts.md): The keyboard shortcut sheet, on ?.
- [DuxtShortcutsTrigger](https://duxt.app/en-US/reference/components/controls/duxt-shortcuts-trigger.md): The button that opens the shortcut sheet.
- [DuxtSkipLink](https://duxt.app/en-US/reference/components/controls/duxt-skip-link.md): The first focusable element on the page.
- [DuxtVersion](https://duxt.app/en-US/reference/components/controls/duxt-version.md): The version badge, and the switcher when there is more than one.
- [DuxtVersionBanner](https://duxt.app/en-US/reference/components/controls/duxt-version-banner.md): The bar telling a reader this version is not the current one.
- [Layout](https://duxt.app/en-US/reference/components/layout.md): The three components that frame a page — the navbar, the footer and the site notices.
- [DuxtAnnouncements](https://duxt.app/en-US/reference/components/layout/duxt-announcements.md): The site's own notices: one strip per placement, drawn only when there is something to say.
- [DuxtFooter](https://duxt.app/en-US/reference/components/layout/duxt-footer.md): The footer: the site's name, its legal links, and the layer's own line.
- [DuxtHeader](https://duxt.app/en-US/reference/components/layout/duxt-header.md): The navbar: title, navigation, search, and the icon links.
- [Navigation](https://duxt.app/en-US/reference/components/navigation.md): Getting around — the section row, the sidebar, the trail, the contents and prev/next.
- [DuxtBreadcrumb](https://duxt.app/en-US/reference/components/navigation/duxt-breadcrumb.md): The trail above the page title.
- [DuxtNavigation](https://duxt.app/en-US/reference/components/navigation/duxt-navigation.md): The sidebar tree.
- [DuxtNavigationLink](https://duxt.app/en-US/reference/components/navigation/duxt-navigation-link.md): One entry of the sidebar.
- [DuxtPageNav](https://duxt.app/en-US/reference/components/navigation/duxt-page-nav.md): Previous and next, bounded by the section.
- [DuxtSections](https://duxt.app/en-US/reference/components/navigation/duxt-sections.md): The second navbar row — the top-level parts of the documentation.
- [DuxtToc](https://duxt.app/en-US/reference/components/navigation/duxt-toc.md): The table of contents, and the aside under it.
- [Page](https://duxt.app/en-US/reference/components/page.md): The components that belong to the page itself.
- [DuxtCodeBlock](https://duxt.app/en-US/reference/components/page/duxt-code-block.md): The card around a code block.
- [DuxtCopyPage](https://duxt.app/en-US/reference/components/page/duxt-copy-page.md): Hand this page to a model, or read its source.
- [DuxtPageFeedback](https://duxt.app/en-US/reference/components/page/duxt-page-feedback.md): Was this page helpful?
- [DuxtPageInfo](https://duxt.app/en-US/reference/components/page/duxt-page-info.md): Where the page came from: edit link, last updated, contributors.
- [Composables](https://duxt.app/en-US/reference/composables.md): The functions the layer exposes to your own components, one page each.
- [Config and content](https://duxt.app/en-US/reference/composables/config-and-content.md): The merged config, and which collection serves the page being read.
- [useDuxtBreadcrumb()](https://duxt.app/en-US/reference/composables/config-and-content/use-duxt-breadcrumb.md): The trail from the section down to a page.
- [useDuxtCollection()](https://duxt.app/en-US/reference/composables/config-and-content/use-duxt-collection.md): Which collection serves this route.
- [useDuxtConfig()](https://duxt.app/en-US/reference/composables/config-and-content/use-duxt-config.md): The merged config, every text field already resolved.
- [useDuxtNavigation()](https://duxt.app/en-US/reference/composables/config-and-content/use-duxt-navigation.md): The navigation tree for the collection serving this route.
- [useDuxtSection()](https://duxt.app/en-US/reference/composables/config-and-content/use-duxt-section.md): The part of the documentation this page is in.
- [Paths and versions](https://duxt.app/en-US/reference/composables/paths-and-versions.md): Reading a URL, writing one back out, and knowing which version is being read.
- [useDuxtLink()](https://duxt.app/en-US/reference/composables/paths-and-versions/use-duxt-link.md): A documentation path, written back out as a link.
- [useDuxtPath()](https://duxt.app/en-US/reference/composables/paths-and-versions/use-duxt-path.md): The path the documentation is at, locale stripped.
- [useDuxtSiteUrl()](https://duxt.app/en-US/reference/composables/paths-and-versions/use-duxt-site-url.md): The configured origin, and paths made absolute.
- [useDuxtVersion()](https://duxt.app/en-US/reference/composables/paths-and-versions/use-duxt-version.md): What the switcher shows, what the banner says, whether to index.
- [Reading experience](https://duxt.app/en-US/reference/composables/reading.md): Search, headings, focus, history, and the choices a reader makes.
- [useActiveHeading()](https://duxt.app/en-US/reference/composables/reading/use-active-heading.md): The heading currently in view.
- [useDuxtAnalytics()](https://duxt.app/en-US/reference/composables/reading/use-duxt-analytics.md): Report one reader interaction to the site's own callback, or to nobody.
- [useDuxtPageFocus()](https://duxt.app/en-US/reference/composables/reading/use-duxt-page-focus.md): Moves focus to the heading after a client-side navigation.
- [useDuxtSearch()](https://duxt.app/en-US/reference/composables/reading/use-duxt-search.md): Search every active source and interleave its locally ranked results.
- [useDuxtShortcuts()](https://duxt.app/en-US/reference/composables/reading/use-duxt-shortcuts.md): The keys the theme listens to.
- [useDuxtToast()](https://duxt.app/en-US/reference/composables/reading/use-duxt-toast.md): Notifications, wrapped so no component imports the library.
- [useFuzzySearch()](https://duxt.app/en-US/reference/composables/reading/use-fuzzy-search.md): Typo tolerance beside the exact index.
- [usePackageManager()](https://duxt.app/en-US/reference/composables/reading/use-package-manager.md): The package manager a reader picked.
- [useRecentPages()](https://duxt.app/en-US/reference/composables/reading/use-recent-pages.md): The most recent pages this reader opened, up to the configured limit.
- [Configuration](https://duxt.app/en-US/reference/configuration.md): Every key under duxt in app.config.ts — what it controls, and when it is read.
- [Devtools](https://duxt.app/en-US/reference/devtools.md): Ten panels that show what your sources became. Dev only.
- [Cache](https://duxt.app/en-US/reference/devtools/cache.md): Content's download cache, and a way to drop one entry.
- [Checks](https://duxt.app/en-US/reference/devtools/checks.md): The build validator, run against what the site is serving now.
- [Config](https://duxt.app/en-US/reference/devtools/config.md): The merged `duxt` config, and which side of the merge each value came from.
- [i18n](https://duxt.app/en-US/reference/devtools/i18n.md): Message keys per locale, against the base language.
- [Pages](https://duxt.app/en-US/reference/devtools/pages.md): Every page of every collection, with its frontmatter and git metadata.
- [Paths](https://duxt.app/en-US/reference/devtools/paths.md): Paste a URL, see which source claims it and what it finds there.
- [Redirects](https://duxt.app/en-US/reference/devtools/redirects.md): Every redirect the server ships, and which of them the layer wrote.
- [Search](https://duxt.app/en-US/reference/devtools/search.md): What the search index holds, through the same query the dialog runs.
- [Sources](https://duxt.app/en-US/reference/devtools/sources.md): What `duxt.sources` became — one collection per source, version and language.
- [Versions](https://duxt.app/en-US/reference/devtools/versions.md): Which version — and which language — carries which page.
- [Endpoints](https://duxt.app/en-US/reference/endpoints.md): Everything the site serves besides pages, one page each.
- [/_duxt/devtools](https://duxt.app/en-US/reference/endpoints/devtools.md): The route the Nuxt Devtools panel is served from. Dev only.
- [/llms-full.txt](https://duxt.app/en-US/reference/endpoints/llms-full-txt.md): A duxt extension with the same pages in one Markdown file.
- [/llms.txt](https://duxt.app/en-US/reference/endpoints/llms-txt.md): The documentation as a Markdown index, per llmstxt.org.
- [/mcp](https://duxt.app/en-US/reference/endpoints/mcp.md): An MCP server over the same content.
- [<page>.md](https://duxt.app/en-US/reference/endpoints/page-markdown.md): Any page source, at its own URL plus .md.
- [/rss.xml](https://duxt.app/en-US/reference/endpoints/rss-xml.md): The feed, once a section is named.
- [/sitemap.xml and /robots.txt](https://duxt.app/en-US/reference/endpoints/sitemap-and-robots.md): What a crawler is pointed at, and what it is kept out of.
- [Frontmatter](https://duxt.app/en-US/reference/frontmatter.md): The fields a page may carry beyond title and description, and the two the build fills in.
- [Hooks](https://duxt.app/en-US/reference/hooks.md): The one build-time hook duxt emits, what it hands you, and why there is only one.
- [MDC components](https://duxt.app/en-US/reference/mdc-components.md): The blocks a Markdown page can call, one page each, with their props.
- [Accordion](https://duxt.app/en-US/reference/mdc-components/accordion.md): Collapsible sections — a FAQ, or answers a reader picks from.
- [Accordion item](https://duxt.app/en-US/reference/mdc-components/accordion-item.md): One collapsible section.
- [Callout](https://duxt.app/en-US/reference/mdc-components/callout.md): An aside the reader is meant to stop at — a tip, a warning, a danger.
- [Code group](https://duxt.app/en-US/reference/mdc-components/code-group.md): Several fences as one tabbed block, labelled by filename.
- [Field](https://duxt.app/en-US/reference/mdc-components/field.md): One parameter, property or option, with its type and default.
- [Field group](https://duxt.app/en-US/reference/mdc-components/field-group.md): A list of fields as one block.
- [File tree](https://duxt.app/en-US/reference/mdc-components/file-tree.md): A folder structure, with icons per file type.
- [Mermaid](https://duxt.app/en-US/reference/mdc-components/mermaid.md): A diagram from a fence or a prop.
- [Package managers](https://duxt.app/en-US/reference/mdc-components/package-managers.md): One command, one tab per package manager, remembered across pages.
- [Page cards](https://duxt.app/en-US/reference/mdc-components/page-cards.md): A section's children, as cards.
- [Partial](https://duxt.app/en-US/reference/mdc-components/partial.md): A block written once and rendered in every source that needs it.
- [Preview](https://duxt.app/en-US/reference/mdc-components/preview.md): A component rendered as the page renders it, with its source beside it.
- [Prose overrides](https://duxt.app/en-US/reference/mdc-components/prose.md): What the layer changes about plain Markdown — links, headings, images, code and tables.
- [ProseA](https://duxt.app/en-US/reference/mdc-components/prose/prose-a.md): A link, resolved against the source it was written in.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/en-US/reference/mdc-components/prose/prose-headings.md): Headings, each with a permalink anchor.
- [ProseImg](https://duxt.app/en-US/reference/mdc-components/prose/prose-img.md): An image: theme-aware, responsive, and zoomable.
- [ProsePre](https://duxt.app/en-US/reference/mdc-components/prose/prose-pre.md): The code block: filename, language icon, copy button.
- [ProseTable](https://duxt.app/en-US/reference/mdc-components/prose/prose-table.md): A table that scrolls instead of the page.
- [Since](https://duxt.app/en-US/reference/mdc-components/since.md): The version something arrived in, beside a heading.
- [Steps](https://duxt.app/en-US/reference/mdc-components/steps.md): An ordered list drawn as numbered steps on a rail.
- [Tab](https://duxt.app/en-US/reference/mdc-components/tab.md): One panel of a tab group.
- [Tab group](https://duxt.app/en-US/reference/mdc-components/tab-group.md): Tabs for anything that is not code.
- [API reference](https://duxt.app/en-US/reference/openapi.md): An OpenAPI document, published as reference pages with a client that sends real requests.
- [Components](https://duxt.app/en-US/reference/openapi/components.md): The three MDC components a generated reference page is made of.
- [Request samples](https://duxt.app/en-US/reference/openapi/request-samples.md): The same request in twelve clients, and how to add your own.
- [Declaring the section](https://duxt.app/en-US/reference/openapi/section.md): The `openapi` section type — where the document lives, and what it becomes.
- [The try-it client](https://duxt.app/en-US/reference/openapi/try-it.md): A real request, sent by the reader's own browser.
- [Sources](https://duxt.app/en-US/reference/sources.md): The fields of a source entry, its refs, and the options that shape the URLs.
- [Releases](https://duxt.app/en-US/releases.md)
- [0.1.0](https://duxt.app/en-US/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/en-US/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/en-US/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/en-US/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/en-US/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/en-US/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/en-US/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/en-US/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/en-US/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/en-US/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/en-US/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/en-US/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/en-US/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/en-US/releases/v0.9.0.md)
- [Documentación](https://duxt.app/es-ES.md): Una capa de Nuxt que convierte la carpeta docs de un repositorio en un sitio de documentación versionado y multirrepositorio.
- [Complementos](https://duxt.app/es-ES/add-ons.md): Capas complementarias que amplían un sitio duxt — cada una es su propio paquete y se añade con una entrada más en extends.
- [Meilisearch](https://duxt.app/es-ES/add-ons/meilisearch.md): Añade la capa complementaria oficial para indexación atómica durante la compilación y búsqueda opcional en el navegador.
- [Typesense](https://duxt.app/es-ES/add-ons/typesense.md): Consume el único hook de compilación de duxt en una colección de Typesense — cada fuente, versión e idioma, con un id estable.
- [Decisiones de arquitectura](https://duxt.app/es-ES/adr.md): El registro de decisiones — toda decisión de arquitectura registrada para duxt.
- [Construir duxt como una capa que lleva un módulo](https://duxt.app/es-ES/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribuir el tema como una capa de Nuxt cuya raíz es el paquete, y no como una plantilla de inicio.
- [Generar las colecciones a partir de una sola lista de fuentes](https://duxt.app/es-ES/adr/0002-generate-the-collections-from-one-source-list.md): Calcular las colecciones de Content a partir de una lista de fuentes compacta al cargar la configuración, en vez de hacer que quien la consume las declare.
- [Decidir los prefijos de URL en tiempo de compilación](https://duxt.app/es-ES/adr/0003-decide-the-url-prefixes-at-build-time.md): Que aparezca un segmento de repositorio o de versión lo decide la lista de fuentes antes de la primera petición, nunca por petición.
- [Renderizar los componentes de Markdown con MDC](https://duxt.app/es-ES/adr/0004-render-markdown-components-with-mdc.md): Usar la sintaxis MDC propia de Content para los componentes dentro de Markdown en lugar de adoptar MDX.
- [Publicar la capa sin enlaces específicos del propietario](https://duxt.app/es-ES/adr/0005-ship-the-layer-without-owner-specific-links.md): Todo valor por defecto que nombraría un proyecto concreto — repositorio, gestor de incidencias, comunidad, aviso legal — se entrega vacío.
- [Recompilar según un calendario en vez de refrescar en tiempo de ejecución](https://duxt.app/es-ES/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): Un sitio que lee otro repositorio recoge sus cambios cuando compila, y no se ofrece ningún refresco en tiempo de ejecución.
- [Servir las traducciones como colecciones propias](https://duxt.app/es-ES/adr/0007-serve-translations-as-collections-of-their-own.md): Añadir una dimensión de locale a una fuente en lugar de un segmento de locale a la ruta de contenido.
- [Construir el tema sobre componentes shadcn-vue propios](https://duxt.app/es-ES/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): La capa guarda el código fuente de sus componentes de interfaz en lugar de importarlos de una biblioteca de componentes o de un tema de documentación ya hecho.
- [Tomar la base de SEO del paquete Nuxt SEO](https://duxt.app/es-ES/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): La capa instala @nuxtjs/seo y le cede las etiquetas de head y los datos estructurados que antes escribía a mano, conservando solo las reglas que dependen de versiones y traducciones.
- [Mantener la búsqueda por colección de Content como predeterminada](https://duxt.app/es-ES/adr/0010-keep-contents-per-collection-search-as-the-default.md): Un único índice sobre todas las fuentes se midió frente a la búsqueda de un índice por colección de Content y no es el valor predeterminado de la capa; el hook de compilación lo convierte en una capa proveedora.
- [Alojar las capas proveedoras en un monorepo de Turborepo](https://duxt.app/es-ES/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): La capa pasa a packages/duxt y el sitio a apps/www, cada paquete publicado versiona y etiqueta por su cuenta como <name>@vX.Y.Z, y la decisión de repositorios propios recogida en
- [Conceptos](https://duxt.app/es-ES/concepts.md): Cómo funciona la capa — el modelo de fuentes, el esquema de URL, las colecciones y las comprobaciones.
- [Qué comprueba la compilación](https://duxt.app/es-ES/concepts/build-checks.md): Los fallos silenciosos que tuvo esta capa, convertidos en mensajes.
- [Colecciones](https://duxt.app/es-ES/concepts/collections.md): Qué construye Content a partir de las fuentes, y las cuatro cosas que añade el esquema.
- [Bases de datos](https://duxt.app/es-ES/concepts/databases.md): En qué adaptadores de base de datos de Content puede desplegarse un sitio duxt, cuáles se han verificado y la única regla que mantiene la capa apartada.
- [Secciones generadas](https://duxt.app/es-ES/concepts/generated-sections.md): Un artefacto más un tipo, publicados como páginas — qué es el registro, y las dos políticas que responde un tipo.
- [Atajos de teclado](https://duxt.app/es-ES/concepts/keyboard-shortcuts.md): Las cuatro teclas que vincula el tema, dónde se aplica cada una y dónde se entera quien lee.
- [Capas y sobrescritura](https://duxt.app/es-ES/concepts/layers.md): Qué te da una capa de Nuxt, qué te quita, y qué rutas no se resuelven como se leen.
- [Localización](https://duxt.app/es-ES/concepts/localisation.md): La capa trae siete locales, y cada cadena configurada admite tres formas.
- [Lectores automáticos](https://duxt.app/es-ES/concepts/machine-readers.md): Qué obtiene un modelo — llms.txt, el Markdown en bruto de cualquier página y un servidor MCP real.
- [SEO](https://duxt.app/es-ES/concepts/seo.md): Qué emite cada página para los rastreadores y las tarjetas sociales, qué módulo lo escribe, y el único valor que la capa no puede adivinar.
- [Fuentes](https://duxt.app/es-ES/concepts/sources.md): Una lista de fuentes se convierte en cada colección, prefijo y versión que sirve el sitio.
- [Tematización](https://duxt.app/es-ES/concepts/theming.md): Cómo está montado el tema — componentes propios, una capa de tokens y un modo oscuro que conmuta por clase.
- [URL y versiones](https://duxt.app/es-ES/concepts/urls-and-versions.md): Cómo aparecen los segmentos de repositorio y versión, y qué se le dice a quien lee una versión antigua.
- [Convenciones](https://duxt.app/es-ES/conventions.md): Reglas propias del proyecto — las que no se deducen del código.
- [Identidad](https://duxt.app/es-ES/conventions/branding.md): La marca [d]uxt — dónde se usa cada recurso, por qué se han redibujado los corchetes del icono y qué colores son fijos.
- [Seguridad de dependencias](https://duxt.app/es-ES/conventions/dependency-security.md): Revisar avisos sin ocultar las rutas afectadas.
- [Iconos](https://duxt.app/es-ES/conventions/icons.md): Cuatro conjuntos de iconos, y la única pregunta que decide cuál de ellos dibuja una marca.
- [Créditos](https://duxt.app/es-ES/credits.md): Sobre qué está construido duxt, y en qué se fijó para construirse.
- [Overview](https://duxt.app/es-ES/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/es-ES/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/es-ES/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/es-ES/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/es-ES/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/es-ES/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/es-ES/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/es-ES/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/es-ES/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/es-ES/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/es-ES/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/es-ES/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/es-ES/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/es-ES/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/es-ES/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/es-ES/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/es-ES/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/es-ES/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/es-ES/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/es-ES/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/es-ES/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/es-ES/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/es-ES/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/es-ES/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/es-ES/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/es-ES/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/es-ES/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/es-ES/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/es-ES/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/es-ES/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/es-ES/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/es-ES/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/es-ES/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/es-ES/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/es-ES/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/es-ES/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/es-ES/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/es-ES/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/es-ES/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/es-ES/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/es-ES/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/es-ES/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/es-ES/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/es-ES/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/es-ES/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/es-ES/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/es-ES/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/es-ES/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/es-ES/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/es-ES/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/es-ES/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/es-ES/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/es-ES/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/es-ES/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/es-ES/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/es-ES/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/es-ES/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/es-ES/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/es-ES/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/es-ES/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/es-ES/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/es-ES/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/es-ES/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/es-ES/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/es-ES/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/es-ES/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/es-ES/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/es-ES/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/es-ES/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/es-ES/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/es-ES/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/es-ES/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/es-ES/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/es-ES/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/es-ES/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Introducción](https://duxt.app/es-ES/getting-started.md): Qué es duxt, y qué llega con una sola línea de configuración.
- [Configuración](https://duxt.app/es-ES/getting-started/configuration.md): Un archivo configura todo el sitio — qué va en él y cómo se combina.
- [Empezar con el starter](https://duxt.app/es-ES/getting-started/from-starter.md): Crea con Nuxi un sitio de documentación duxt listo para ejecutar.
- [Instalación](https://duxt.app/es-ES/getting-started/installation.md): Añade la capa, extiéndela, escribe Markdown.
- [Guías](https://duxt.app/es-ES/guides.md): Una tarea por página, de principio a fin — varios repositorios, varias versiones, varios idiomas y un despliegue.
- [Dale identidad a tu sitio](https://duxt.app/es-ES/guides/brand-your-site.md): Define el nombre, el logotipo y los iconos, para que el sitio se lea como tuyo y no como el de la capa.
- [Guardar fuentes remotas e imágenes OG en caché](https://duxt.app/es-ES/guides/cache-build-work.md): Reutiliza descargas de repositorios públicos y tarjetas sociales renderizadas entre builds de CI.
- [Recoger opiniones de página](https://duxt.app/es-ES/guides/collect-page-feedback.md): Envuelve DuxtPageFeedback y guarda la respuesta donde ya vive tu analítica.
- [Desplegar un sitio](https://duxt.app/es-ES/guides/deploy-a-site.md): Dónde puede ejecutarse un sitio duxt, qué necesita allí y por qué el contenido no se refresca en ejecución.
- [Mover una página](https://duxt.app/es-ES/guides/move-a-page.md): redirectFrom en el frontmatter, convertido en reglas de ruta bajo todos los prefijos.
- [Sobrescribir el tema](https://duxt.app/es-ES/guides/override-the-theme.md): Cambiar un color, reemplazar un componente, añadir una primitiva de shadcn-vue.
- [Publicar documentación de un proveedor de Terraform](https://duxt.app/es-ES/guides/publish-terraform-provider-docs.md): Convierte un árbol Markdown de tfplugindocs en una referencia versionada con navegación de proveedor.
- [Enviar eventos de analítica](https://duxt.app/es-ES/guides/send-analytics-events.md): Una función de retorno, cinco eventos, ningún proveedor — conecta las interacciones del lector en duxt con la analítica que ya tienes.
- [Varios idiomas](https://duxt.app/es-ES/guides/several-languages.md): Servir la interfaz en varios idiomas, y traducir también las páginas.
- [Varios repositorios](https://duxt.app/es-ES/guides/several-repositories.md): Servir la documentación de varios proyectos desde un solo sitio.
- [Varias versiones](https://duxt.app/es-ES/guides/several-versions.md): Servir la misma documentación en varias refs, con selector y aviso.
- [Referencia](https://duxt.app/es-ES/reference.md): La superficie pública de la capa — claves de configuración, frontmatter, componentes, composables y endpoints.
- [Colecciones Bruno](https://duxt.app/es-ES/reference/bruno.md): Una colección Bruno como referencia centrada en peticiones con un archivo descargable.
- [Obtener la colección](https://duxt.app/es-ES/reference/bruno/getting-the-collection.md): El archivo está fijado a la versión y el idioma; el enlace de Bruno no.
- [Declarar la sección](https://duxt.app/es-ES/reference/bruno/section.md): Dónde vive una colección Bruno, qué páginas produce y qué opciones acepta.
- [El cliente de peticiones](https://duxt.app/es-ES/reference/bruno/try-it.md): Apagado por defecto y dirigido solo a destinos declarados públicos.
- [Qué se publica](https://duxt.app/es-ES/reference/bruno/what-is-published.md): Entornos, credenciales, scripts y pruebas nunca llegan a una página.
- [Registro de cambios](https://duxt.app/es-ES/reference/changelog.md): Un registro de versiones, publicado como páginas — una línea de tiempo, una página por versión, y un feed.
- [Diseño y componentes](https://duxt.app/es-ES/reference/changelog/components.md): El diseño en el que renderiza un historial separado, y los dos componentes MDC de los que están hechas sus páginas.
- [Granularidad](https://duxt.app/es-ES/reference/changelog/granularity.md): Una página por versión, o el fichero como la única página que se escribió.
- [Declarar la sección](https://duxt.app/es-ES/reference/changelog/section.md): El tipo de sección `changelog` — dónde vive el fichero, y las dos políticas que responde.
- [Qué se lee](https://duxt.app/es-ES/reference/changelog/what-is-read.md): Qué encabezados pasan a ser versiones, cuáles grupos, y qué ocurre con el resto.
- [Componentes](https://duxt.app/es-ES/reference/components.md): Los componentes propios de la capa, con una página cada uno — para qué sirve cada uno y qué acepta.
- [Controles](https://duxt.app/es-ES/reference/components/controls.md): Lo que maneja un lector — la búsqueda, los selectores, la hoja de atajos y dos indicadores.
- [DuxtLocale](https://duxt.app/es-ES/reference/components/controls/duxt-locale.md): El selector de idioma.
- [DuxtProgress](https://duxt.app/es-ES/reference/components/controls/duxt-progress.md): Cuánto ha bajado el lector por la página.
- [DuxtSearch](https://duxt.app/es-ES/reference/components/controls/duxt-search.md): Busca en cada fuente activa e intercala sus resultados clasificados localmente.
- [DuxtShortcuts](https://duxt.app/es-ES/reference/components/controls/duxt-shortcuts.md): La hoja de atajos de teclado, con ?.
- [DuxtShortcutsTrigger](https://duxt.app/es-ES/reference/components/controls/duxt-shortcuts-trigger.md): El botón que abre la hoja de atajos.
- [DuxtSkipLink](https://duxt.app/es-ES/reference/components/controls/duxt-skip-link.md): El primer elemento enfocable de la página.
- [DuxtVersion](https://duxt.app/es-ES/reference/components/controls/duxt-version.md): El distintivo de versión, y el selector cuando hay más de una.
- [DuxtVersionBanner](https://duxt.app/es-ES/reference/components/controls/duxt-version-banner.md): La barra que le dice a un lector que esta versión no es la actual.
- [Diseño](https://duxt.app/es-ES/reference/components/layout.md): Los dos componentes que enmarcan una página — la barra de navegación y el pie.
- [DuxtAnnouncements](https://duxt.app/es-ES/reference/components/layout/duxt-announcements.md): Avisos propios del sitio, dibujados por ubicación solo cuando hay algo que decir.
- [DuxtFooter](https://duxt.app/es-ES/reference/components/layout/duxt-footer.md): El pie: el nombre del sitio, sus enlaces legales y la línea propia de la capa.
- [DuxtHeader](https://duxt.app/es-ES/reference/components/layout/duxt-header.md): La barra de navegación: título, navegación, búsqueda y los enlaces de iconos.
- [Navegación](https://duxt.app/es-ES/reference/components/navigation.md): Moverse por el sitio — la fila de secciones, la barra lateral, el rastro, la tabla de contenidos y anterior/siguiente.
- [DuxtBreadcrumb](https://duxt.app/es-ES/reference/components/navigation/duxt-breadcrumb.md): La miga de pan sobre el título de la página.
- [DuxtNavigation](https://duxt.app/es-ES/reference/components/navigation/duxt-navigation.md): El árbol de la barra lateral.
- [DuxtNavigationLink](https://duxt.app/es-ES/reference/components/navigation/duxt-navigation-link.md): Una entrada de la barra lateral.
- [DuxtPageNav](https://duxt.app/es-ES/reference/components/navigation/duxt-page-nav.md): Anterior y siguiente, limitados por la sección.
- [DuxtSections](https://duxt.app/es-ES/reference/components/navigation/duxt-sections.md): La segunda fila de la barra de navegación — las partes de primer nivel de la documentación.
- [DuxtToc](https://duxt.app/es-ES/reference/components/navigation/duxt-toc.md): La tabla de contenidos, y el aside que va debajo.
- [Página](https://duxt.app/es-ES/reference/components/page.md): Los componentes que pertenecen a la página misma.
- [DuxtCodeBlock](https://duxt.app/es-ES/reference/components/page/duxt-code-block.md): La tarjeta alrededor de un bloque de código.
- [DuxtCopyPage](https://duxt.app/es-ES/reference/components/page/duxt-copy-page.md): Entrega esta página a un modelo, o lee su código fuente.
- [DuxtPageFeedback](https://duxt.app/es-ES/reference/components/page/duxt-page-feedback.md): «¿Te ha resultado útil esta página?» — un evento, y ningún backend.
- [DuxtPageInfo](https://duxt.app/es-ES/reference/components/page/duxt-page-info.md): De dónde vino la página: enlace de edición, última actualización, quién ha contribuido.
- [Composables](https://duxt.app/es-ES/reference/composables.md): Las funciones que la capa expone a tus propios componentes, con una página cada una.
- [Configuración y contenido](https://duxt.app/es-ES/reference/composables/config-and-content.md): La configuración fusionada, y qué colección sirve la página que se está leyendo.
- [useDuxtBreadcrumb()](https://duxt.app/es-ES/reference/composables/config-and-content/use-duxt-breadcrumb.md): El rastro que va de la sección hasta una página.
- [useDuxtCollection()](https://duxt.app/es-ES/reference/composables/config-and-content/use-duxt-collection.md): Qué colección sirve esta ruta.
- [useDuxtConfig()](https://duxt.app/es-ES/reference/composables/config-and-content/use-duxt-config.md): La configuración fusionada, con cada campo de texto ya resuelto.
- [useDuxtNavigation()](https://duxt.app/es-ES/reference/composables/config-and-content/use-duxt-navigation.md): El árbol de navegación de la colección que sirve esta ruta.
- [useDuxtSection()](https://duxt.app/es-ES/reference/composables/config-and-content/use-duxt-section.md): La parte de la documentación en la que está esta página.
- [Rutas y versiones](https://duxt.app/es-ES/reference/composables/paths-and-versions.md): Leer una URL, escribir otra de vuelta, y saber qué versión se está leyendo.
- [useDuxtLink()](https://duxt.app/es-ES/reference/composables/paths-and-versions/use-duxt-link.md): Una ruta de documentación, escrita de vuelta como enlace.
- [useDuxtPath()](https://duxt.app/es-ES/reference/composables/paths-and-versions/use-duxt-path.md): La ruta en la que está la documentación, sin el locale.
- [useDuxtSiteUrl()](https://duxt.app/es-ES/reference/composables/paths-and-versions/use-duxt-site-url.md): El origen configurado, y rutas hechas absolutas.
- [useDuxtVersion()](https://duxt.app/es-ES/reference/composables/paths-and-versions/use-duxt-version.md): Qué muestra el selector, qué dice el aviso, si indexar.
- [Experiencia de lectura](https://duxt.app/es-ES/reference/composables/reading.md): Búsqueda, encabezados, foco, historial y las decisiones que toma un lector.
- [useActiveHeading()](https://duxt.app/es-ES/reference/composables/reading/use-active-heading.md): El encabezado que está ahora a la vista.
- [useDuxtAnalytics()](https://duxt.app/es-ES/reference/composables/reading/use-duxt-analytics.md): Informa de una interacción del lector a la función propia del sitio, o a nadie.
- [useDuxtPageFocus()](https://duxt.app/es-ES/reference/composables/reading/use-duxt-page-focus.md): Mueve el foco al encabezado tras una navegación en el cliente.
- [useDuxtSearch()](https://duxt.app/es-ES/reference/composables/reading/use-duxt-search.md): Busca en cada fuente activa e intercala sus resultados clasificados localmente.
- [useDuxtShortcuts()](https://duxt.app/es-ES/reference/composables/reading/use-duxt-shortcuts.md): Las teclas que escucha el tema.
- [useDuxtToast()](https://duxt.app/es-ES/reference/composables/reading/use-duxt-toast.md): Notificaciones, envueltas para que ningún componente importe la biblioteca.
- [useFuzzySearch()](https://duxt.app/es-ES/reference/composables/reading/use-fuzzy-search.md): Tolerancia a erratas junto al índice exacto.
- [usePackageManager()](https://duxt.app/es-ES/reference/composables/reading/use-package-manager.md): El gestor de paquetes que eligió un lector.
- [useRecentPages()](https://duxt.app/es-ES/reference/composables/reading/use-recent-pages.md): Las páginas abiertas más recientemente, hasta el límite configurado.
- [Configuración](https://duxt.app/es-ES/reference/configuration.md): Cada clave bajo duxt en app.config.ts — qué controla y cuándo se lee.
- [Devtools](https://duxt.app/es-ES/reference/devtools.md): Diez paneles que muestran en qué se convirtieron tus fuentes. Solo en desarrollo.
- [Cache](https://duxt.app/es-ES/reference/devtools/cache.md): La caché de descargas de Content, y una forma de tirar una entrada.
- [Comprobaciones](https://duxt.app/es-ES/reference/devtools/checks.md): El validador de compilación, ejecutado contra lo que el sitio sirve ahora.
- [Configuración](https://duxt.app/es-ES/reference/devtools/config.md): La configuración de `duxt` fusionada, y de qué lado de la fusión vino cada valor.
- [i18n](https://duxt.app/es-ES/reference/devtools/i18n.md): Claves de mensaje por idioma, frente al idioma base.
- [Páginas](https://duxt.app/es-ES/reference/devtools/pages.md): Todas las páginas de todas las colecciones, con su frontmatter y sus metadatos de git.
- [Rutas](https://duxt.app/es-ES/reference/devtools/paths.md): Pega una URL, mira qué fuente la reclama y qué encuentra ahí.
- [Redirecciones](https://duxt.app/es-ES/reference/devtools/redirects.md): Cada redirección que sirve el servidor, y cuáles escribió la capa.
- [Búsqueda](https://duxt.app/es-ES/reference/devtools/search.md): Qué contiene el índice de búsqueda, a través de la misma consulta que ejecuta el diálogo.
- [Fuentes](https://duxt.app/es-ES/reference/devtools/sources.md): En qué se convirtió `duxt.sources` — una colección por fuente, versión e idioma.
- [Versiones](https://duxt.app/es-ES/reference/devtools/versions.md): Qué versión — y qué idioma — lleva qué página.
- [Endpoints](https://duxt.app/es-ES/reference/endpoints.md): Todo lo que el sitio sirve además de las páginas, una página por cada uno.
- [/_duxt/devtools](https://duxt.app/es-ES/reference/endpoints/devtools.md): La ruta desde la que se sirve el panel de Nuxt Devtools. Solo en desarrollo.
- [/llms-full.txt](https://duxt.app/es-ES/reference/endpoints/llms-full-txt.md): Una extensión de duxt con las mismas páginas en un archivo Markdown.
- [/llms.txt](https://duxt.app/es-ES/reference/endpoints/llms-txt.md): La documentación como índice Markdown, según llmstxt.org.
- [/mcp](https://duxt.app/es-ES/reference/endpoints/mcp.md): Un servidor MCP sobre el mismo contenido.
- [<página>.md](https://duxt.app/es-ES/reference/endpoints/page-markdown.md): El código fuente de cualquier página, en su propia URL más .md.
- [/rss.xml](https://duxt.app/es-ES/reference/endpoints/rss-xml.md): El feed, una vez que se nombra una sección.
- [/sitemap.xml y /robots.txt](https://duxt.app/es-ES/reference/endpoints/sitemap-and-robots.md): Hacia dónde se apunta a un rastreador, y de qué se le mantiene fuera.
- [Frontmatter](https://duxt.app/es-ES/reference/frontmatter.md): Los campos que una página puede llevar más allá del título y la descripción, y los dos que rellena la compilación.
- [Hooks](https://duxt.app/es-ES/reference/hooks.md): El único hook de compilación que duxt emite, qué te entrega y por qué solo hay uno.
- [Componentes MDC](https://duxt.app/es-ES/reference/mdc-components.md): Los bloques que puede invocar una página Markdown, una página cada uno, con sus props.
- [Acordeón](https://duxt.app/es-ES/reference/mdc-components/accordion.md): Secciones plegables — una FAQ, o respuestas entre las que elige un lector.
- [Elemento de acordeón](https://duxt.app/es-ES/reference/mdc-components/accordion-item.md): Una sección plegable.
- [Callout](https://duxt.app/es-ES/reference/mdc-components/callout.md): Un apunte en el que el lector debe detenerse — un consejo, una advertencia, un peligro.
- [Grupo de código](https://duxt.app/es-ES/reference/mdc-components/code-group.md): Varios bloques de código como un único bloque con pestañas, etiquetados por nombre de archivo.
- [Campo](https://duxt.app/es-ES/reference/mdc-components/field.md): Un parámetro, propiedad u opción, con su tipo y su valor por defecto.
- [Grupo de campos](https://duxt.app/es-ES/reference/mdc-components/field-group.md): Una lista de campos como un único bloque.
- [Árbol de archivos](https://duxt.app/es-ES/reference/mdc-components/file-tree.md): Una estructura de carpetas, con iconos por tipo de archivo.
- [Mermaid](https://duxt.app/es-ES/reference/mdc-components/mermaid.md): Un diagrama a partir de un bloque de código o de una prop.
- [Gestores de paquetes](https://duxt.app/es-ES/reference/mdc-components/package-managers.md): Un comando, una pestaña por gestor de paquetes, recordado entre páginas.
- [Tarjetas de página](https://duxt.app/es-ES/reference/mdc-components/page-cards.md): Los hijos de una sección, como tarjetas.
- [Partial](https://duxt.app/es-ES/reference/mdc-components/partial.md): Un bloque escrito una vez y renderizado en cada fuente que lo necesita.
- [Vista previa](https://duxt.app/es-ES/reference/mdc-components/preview.md): Un componente representado tal como lo representa la página, con su código al lado.
- [Sobrescrituras de prosa](https://duxt.app/es-ES/reference/mdc-components/prose.md): Lo que la capa cambia en el Markdown plano — enlaces, encabezados, imágenes, código y tablas.
- [ProseA](https://duxt.app/es-ES/reference/mdc-components/prose/prose-a.md): Un enlace, resuelto contra la fuente en la que se escribió.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/es-ES/reference/mdc-components/prose/prose-headings.md): Encabezados, cada uno con un ancla de enlace permanente.
- [ProseImg](https://duxt.app/es-ES/reference/mdc-components/prose/prose-img.md): Una imagen: consciente del tema, adaptable y ampliable.
- [ProsePre](https://duxt.app/es-ES/reference/mdc-components/prose/prose-pre.md): El bloque de código: nombre de archivo, icono de lenguaje, botón de copiar.
- [ProseTable](https://duxt.app/es-ES/reference/mdc-components/prose/prose-table.md): Una tabla que se desplaza en lugar de la página.
- [Since](https://duxt.app/es-ES/reference/mdc-components/since.md): La versión en la que algo llegó, junto a un encabezado.
- [Pasos](https://duxt.app/es-ES/reference/mdc-components/steps.md): Una lista ordenada dibujada como pasos numerados sobre un raíl.
- [Pestaña](https://duxt.app/es-ES/reference/mdc-components/tab.md): Un panel de un grupo de pestañas.
- [Grupo de pestañas](https://duxt.app/es-ES/reference/mdc-components/tab-group.md): Pestañas para todo lo que no es código.
- [Referencia de la API](https://duxt.app/es-ES/reference/openapi.md): Un documento OpenAPI, publicado como páginas de referencia con un cliente que envía peticiones reales.
- [Componentes](https://duxt.app/es-ES/reference/openapi/components.md): Los tres componentes MDC de los que está hecha una página de referencia generada.
- [Muestras de peticiones](https://duxt.app/es-ES/reference/openapi/request-samples.md): La misma petición en doce clientes, y cómo añadir el tuyo.
- [Declarar la sección](https://duxt.app/es-ES/reference/openapi/section.md): El tipo de sección `openapi` — dónde vive el documento y en qué se convierte.
- [El cliente de pruebas](https://duxt.app/es-ES/reference/openapi/try-it.md): Una petición real, enviada por el propio navegador del lector.
- [Fuentes](https://duxt.app/es-ES/reference/sources.md): Los campos de una entrada de fuente, sus refs, y las opciones que dan forma a las URL.
- [Releases](https://duxt.app/es-ES/releases.md)
- [0.1.0](https://duxt.app/es-ES/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/es-ES/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/es-ES/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/es-ES/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/es-ES/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/es-ES/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/es-ES/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/es-ES/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/es-ES/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/es-ES/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/es-ES/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/es-ES/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/es-ES/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/es-ES/releases/v0.9.0.md)
- [Documentation](https://duxt.app/fr-FR.md): Une couche Nuxt qui transforme le dossier docs d’un dépôt en un site de documentation versionné et multi-dépôts.
- [Extensions](https://duxt.app/fr-FR/add-ons.md): Des layers compagnons qui étendent un site duxt — chacun est un paquet à part, ajouté par une entrée de plus dans extends.
- [Meilisearch](https://duxt.app/fr-FR/add-ons/meilisearch.md): Ajouter la couche complémentaire officielle pour une indexation atomique à la compilation et une recherche facultative dans le navigateur.
- [Typesense](https://duxt.app/fr-FR/add-ons/typesense.md): Consommez l’unique hook de build de duxt dans une collection Typesense — chaque source, version et langue, mise à jour par un id stable.
- [Décisions d’architecture](https://duxt.app/fr-FR/adr.md): Le journal des décisions — chaque décision d’architecture consignée pour duxt.
- [Construire duxt comme une couche portant un module](https://duxt.app/fr-FR/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribuer le thème comme une couche Nuxt dont la racine est le paquet, plutôt que comme un modèle de départ.
- [Générer les collections à partir d’une seule liste de sources](https://duxt.app/fr-FR/adr/0002-generate-the-collections-from-one-source-list.md): Calculer les collections Content à partir d’une liste de sources compacte au chargement de la configuration, au lieu de les faire déclarer par les consommateurs.
- [Décider les préfixes d’URL à la compilation](https://duxt.app/fr-FR/adr/0003-decide-the-url-prefixes-at-build-time.md): L’apparition d’un segment de dépôt ou de version est tranchée par la liste des sources avant la première requête, jamais par requête.
- [Rendre les composants Markdown avec MDC](https://duxt.app/fr-FR/adr/0004-render-markdown-components-with-mdc.md): Utiliser la syntaxe MDC propre à Content pour les composants dans le Markdown plutôt que d’adopter MDX.
- [Livrer la couche sans liens propres à un propriétaire](https://duxt.app/fr-FR/adr/0005-ship-the-layer-without-owner-specific-links.md): Toute valeur par défaut qui nommerait un projet précis — dépôt, gestionnaire de tickets, communauté, mentions légales — est livrée vide.
- [Recompiler de façon planifiée plutôt que rafraîchir à l’exécution](https://duxt.app/fr-FR/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): Un site qui lit un autre dépôt en récupère les changements quand il compile, et aucun rafraîchissement à l’exécution n’est proposé.
- [Servir les traductions comme des collections à part](https://duxt.app/fr-FR/adr/0007-serve-translations-as-collections-of-their-own.md): Ajouter une dimension de locale à une source plutôt qu’un segment de locale au chemin de contenu.
- [Bâtir le thème sur des composants shadcn-vue possédés](https://duxt.app/fr-FR/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): La couche détient le code source de ses composants d'interface plutôt que de les importer d'une bibliothèque de composants ou d'un thème de documentation tout fait.
- [Prendre le socle SEO dans le bundle Nuxt SEO](https://duxt.app/fr-FR/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): La couche installe @nuxtjs/seo et lui confie les balises de head et les données structurées qu'elle écrivait à la main, ne gardant que les règles qui dépendent des versions et des traductions.
- [Conserver la recherche par collection de Content comme défaut](https://duxt.app/fr-FR/adr/0010-keep-contents-per-collection-search-as-the-default.md): Un index unique sur toutes les sources a été mesuré face à la recherche à un index par collection de Content et n'est pas le défaut de la couche ; le hook de build en fait plutôt une couche fournisseur.
- [Héberger les couches fournisseurs dans un monorepo Turborepo](https://duxt.app/fr-FR/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): La couche passe dans packages/duxt et le site dans apps/www, chaque paquet publié se versionne et s'étiquette seul en <name>@vX.Y.Z, et la décision de dépôts dédiés consignée dans
- [Concepts](https://duxt.app/fr-FR/concepts.md): Comment fonctionne la couche — le modèle de sources, le schéma d’URL, les collections et les vérifications.
- [Ce que la compilation vérifie](https://duxt.app/fr-FR/concepts/build-checks.md): Les échecs silencieux qu’a connus cette couche, transformés en messages.
- [Collections](https://duxt.app/fr-FR/concepts/collections.md): Ce que Content construit à partir des sources, et les quatre choses qu’ajoute le schéma.
- [Bases de données](https://duxt.app/fr-FR/concepts/databases.md): Sur quels adaptateurs de base de données de Content un site duxt peut être déployé, lesquels ont été vérifiés, et la seule règle qui garde la couche à l’écart.
- [Sections générées](https://duxt.app/fr-FR/concepts/generated-sections.md): Un artefact plus un type, publiés en pages — ce qu’est le registre, et les deux politiques auxquelles un type répond.
- [Raccourcis clavier](https://duxt.app/fr-FR/concepts/keyboard-shortcuts.md): Les quatre touches que le thème lie, où chacune s'applique, et où la lectrice l'apprend.
- [Couches et surcharge](https://duxt.app/fr-FR/concepts/layers.md): Ce qu’une couche Nuxt vous donne, ce qu’elle vous retire, et quels chemins ne se résolvent pas comme ils se lisent.
- [Localisation](https://duxt.app/fr-FR/concepts/localisation.md): La couche fournit sept locales, et chaque chaîne configurée prend trois formes.
- [Lecteurs machines](https://duxt.app/fr-FR/concepts/machine-readers.md): Ce qu’obtient un modèle — llms.txt, le Markdown brut de n’importe quelle page et un vrai serveur MCP.
- [SEO](https://duxt.app/fr-FR/concepts/seo.md): Ce que chaque page émet pour les robots et les cartes sociales, quel module l'écrit, et la seule valeur que la couche ne peut pas deviner.
- [Sources](https://duxt.app/fr-FR/concepts/sources.md): Une liste de sources devient chaque collection, préfixe et version que le site sert.
- [Thématisation](https://duxt.app/fr-FR/concepts/theming.md): Comment le thème est construit — des composants possédés, une couche de jetons et un mode sombre qui bascule sur une classe.
- [URL et versions](https://duxt.app/fr-FR/concepts/urls-and-versions.md): Comment apparaissent les segments de dépôt et de version, et ce qu’on dit à un lecteur dans une ancienne version.
- [Conventions](https://duxt.app/fr-FR/conventions.md): Règles propres au projet — celles qu'on ne peut pas déduire du code.
- [Identité visuelle](https://duxt.app/fr-FR/conventions/branding.md): La marque [d]uxt — où sert chaque ressource, pourquoi les crochets de l'icône sont redessinés, et quelles couleurs sont fixes.
- [Sécurité des dépendances](https://duxt.app/fr-FR/conventions/dependency-security.md): Examiner les avis sans masquer les chemins concernés.
- [Icônes](https://duxt.app/fr-FR/conventions/icons.md): Quatre jeux d'icônes, et la seule question qui décide lequel dessine une marque.
- [Crédits](https://duxt.app/fr-FR/credits.md): Ce sur quoi duxt est construit, et ce d’après quoi il l’a été.
- [Overview](https://duxt.app/fr-FR/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/fr-FR/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/fr-FR/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/fr-FR/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/fr-FR/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/fr-FR/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/fr-FR/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/fr-FR/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/fr-FR/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/fr-FR/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/fr-FR/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/fr-FR/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/fr-FR/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/fr-FR/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/fr-FR/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/fr-FR/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/fr-FR/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/fr-FR/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/fr-FR/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/fr-FR/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/fr-FR/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/fr-FR/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/fr-FR/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/fr-FR/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/fr-FR/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/fr-FR/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/fr-FR/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/fr-FR/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/fr-FR/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/fr-FR/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/fr-FR/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/fr-FR/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/fr-FR/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/fr-FR/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/fr-FR/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/fr-FR/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/fr-FR/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/fr-FR/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/fr-FR/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/fr-FR/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/fr-FR/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/fr-FR/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/fr-FR/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/fr-FR/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/fr-FR/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/fr-FR/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/fr-FR/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/fr-FR/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/fr-FR/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/fr-FR/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/fr-FR/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/fr-FR/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/fr-FR/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/fr-FR/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/fr-FR/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/fr-FR/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/fr-FR/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/fr-FR/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/fr-FR/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/fr-FR/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/fr-FR/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/fr-FR/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/fr-FR/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/fr-FR/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/fr-FR/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/fr-FR/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/fr-FR/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/fr-FR/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/fr-FR/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/fr-FR/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/fr-FR/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/fr-FR/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/fr-FR/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/fr-FR/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/fr-FR/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Introduction](https://duxt.app/fr-FR/getting-started.md): Ce qu’est duxt, et ce qui arrive avec une seule ligne de configuration.
- [Configuration](https://duxt.app/fr-FR/getting-started/configuration.md): Un fichier configure tout le site — ce qu’il contient, et comment il fusionne.
- [Démarrer avec le starter](https://duxt.app/fr-FR/getting-started/from-starter.md): Créez avec Nuxi un site de documentation duxt prêt à démarrer.
- [Installation](https://duxt.app/fr-FR/getting-started/installation.md): Ajoutez la couche, étendez-la, écrivez du Markdown.
- [Guides](https://duxt.app/fr-FR/guides.md): Une tâche par page, du début à la fin — plusieurs dépôts, plusieurs versions, plusieurs langues et un déploiement.
- [Donner son identité à votre site](https://duxt.app/fr-FR/guides/brand-your-site.md): Définir le nom, le logo et les icônes, pour que le site se lise comme le vôtre et non comme celui de la couche.
- [Mettre en cache les sources distantes et images OG](https://duxt.app/fr-FR/guides/cache-build-work.md): Réutiliser les dépôts publics téléchargés et les cartes sociales rendues entre les builds CI.
- [Recueillir des retours](https://duxt.app/fr-FR/guides/collect-page-feedback.md): Enveloppez DuxtPageFeedback et gardez la réponse là où vit déjà votre analytique.
- [Déployer un site](https://duxt.app/fr-FR/guides/deploy-a-site.md): Où un site duxt peut tourner, ce qu’il lui faut là-bas, et pourquoi le contenu n’est pas rafraîchi à l’exécution.
- [Déplacer une page](https://duxt.app/fr-FR/guides/move-a-page.md): redirectFrom dans le frontmatter, transformé en règles de route sous chaque préfixe.
- [Surcharger le thème](https://duxt.app/fr-FR/guides/override-the-theme.md): Changer une couleur, remplacer un composant, ajouter une primitive shadcn-vue.
- [Publier la documentation d’un provider Terraform](https://duxt.app/fr-FR/guides/publish-terraform-provider-docs.md): Transformer un arbre Markdown tfplugindocs en référence versionnée avec une navigation adaptée au provider.
- [Envoyer des événements d’analytique](https://duxt.app/fr-FR/guides/send-analytics-events.md): Une fonction de rappel, cinq événements, aucun fournisseur — branchez les interactions des lecteurs de duxt sur l’analytique que vous utilisez déjà.
- [Plusieurs langues](https://duxt.app/fr-FR/guides/several-languages.md): Servir l’interface en plusieurs langues, et traduire les pages elles-mêmes.
- [Plusieurs dépôts](https://duxt.app/fr-FR/guides/several-repositories.md): Servir la documentation de plusieurs projets depuis un seul site.
- [Plusieurs versions](https://duxt.app/fr-FR/guides/several-versions.md): Servir la même documentation sur plusieurs refs, avec un sélecteur et un bandeau.
- [Référence](https://duxt.app/fr-FR/reference.md): La surface publique de la couche — clés de configuration, frontmatter, composants, composables et points de terminaison.
- [Collections Bruno](https://duxt.app/fr-FR/reference/bruno.md): Une collection Bruno publiée en référence centrée sur les requêtes, avec une archive téléchargeable.
- [Obtenir la collection](https://duxt.app/fr-FR/reference/bruno/getting-the-collection.md): L’archive est liée à la version et à la langue affichées ; le lien Bruno ne l’est pas.
- [Déclarer la section](https://duxt.app/fr-FR/reference/bruno/section.md): Où vit une collection Bruno, quelles pages elle produit et quelles options elle accepte.
- [Le client de requêtes](https://duxt.app/fr-FR/reference/bruno/try-it.md): Désactivé par défaut et dirigé uniquement vers une cible déclarée publique.
- [Ce qui est publié](https://duxt.app/fr-FR/reference/bruno/what-is-published.md): Environnements, identifiants, scripts et tests n’atteignent jamais une page.
- [Journal des versions](https://duxt.app/fr-FR/reference/changelog.md): Un journal de releases, publié en pages — une chronologie, une page par version, et un flux.
- [Mise en page et composants](https://duxt.app/fr-FR/reference/changelog/components.md): La mise en page dans laquelle se rend un historique éclaté, et les deux composants MDC dont ses pages sont faites.
- [Granularité](https://duxt.app/fr-FR/reference/changelog/granularity.md): Une page par version, ou le fichier comme l’unique page qu’il a été écrit.
- [Déclarer la section](https://duxt.app/fr-FR/reference/changelog/section.md): Le type de section `changelog` — où vit le fichier, et les deux politiques auxquelles il répond.
- [Ce qui est lu](https://duxt.app/fr-FR/reference/changelog/what-is-read.md): Quels titres deviennent des versions, lesquels des groupes, et ce qu’il advient du reste.
- [Composants](https://duxt.app/fr-FR/reference/components.md): Les composants propres à la couche, une page chacun — à quoi sert chacun, et ce qu’il prend.
- [Contrôles](https://duxt.app/fr-FR/reference/components/controls.md): Ce qu’actionne un lecteur — la recherche, les sélecteurs, la fiche des raccourcis et deux indicateurs.
- [DuxtLocale](https://duxt.app/fr-FR/reference/components/controls/duxt-locale.md): Le sélecteur de langue.
- [DuxtProgress](https://duxt.app/fr-FR/reference/components/controls/duxt-progress.md): Jusqu’où le lecteur est descendu dans la page.
- [DuxtSearch](https://duxt.app/fr-FR/reference/components/controls/duxt-search.md): Rechercher chaque source active et entrelacer ses résultats classés localement.
- [DuxtShortcuts](https://duxt.app/fr-FR/reference/components/controls/duxt-shortcuts.md): La fiche des raccourcis clavier, sur ?.
- [DuxtShortcutsTrigger](https://duxt.app/fr-FR/reference/components/controls/duxt-shortcuts-trigger.md): Le bouton qui ouvre la liste des raccourcis.
- [DuxtSkipLink](https://duxt.app/fr-FR/reference/components/controls/duxt-skip-link.md): Le premier élément focalisable de la page.
- [DuxtVersion](https://duxt.app/fr-FR/reference/components/controls/duxt-version.md): Le badge de version, et le sélecteur quand il y en a plusieurs.
- [DuxtVersionBanner](https://duxt.app/fr-FR/reference/components/controls/duxt-version-banner.md): Le bandeau qui dit au lecteur que cette version n’est pas la version courante.
- [Mise en page](https://duxt.app/fr-FR/reference/components/layout.md): Les deux composants qui encadrent une page — la barre de navigation et le pied de page.
- [DuxtAnnouncements](https://duxt.app/fr-FR/reference/components/layout/duxt-announcements.md): Les avis du site, dessinés par emplacement uniquement lorsqu’il y a quelque chose à annoncer.
- [DuxtFooter](https://duxt.app/fr-FR/reference/components/layout/duxt-footer.md): Le pied de page : le nom du site, ses liens légaux, et la ligne propre à la couche.
- [DuxtHeader](https://duxt.app/fr-FR/reference/components/layout/duxt-header.md): La barre de navigation : titre, navigation, recherche et liens en icônes.
- [Navigation](https://duxt.app/fr-FR/reference/components/navigation.md): Se déplacer — la rangée des sections, la barre latérale, le fil d’Ariane, le sommaire et précédent/suivant.
- [DuxtBreadcrumb](https://duxt.app/fr-FR/reference/components/navigation/duxt-breadcrumb.md): Le fil au-dessus du titre de page.
- [DuxtNavigation](https://duxt.app/fr-FR/reference/components/navigation/duxt-navigation.md): L’arbre de la barre latérale.
- [DuxtNavigationLink](https://duxt.app/fr-FR/reference/components/navigation/duxt-navigation-link.md): Une entrée de la barre latérale.
- [DuxtPageNav](https://duxt.app/fr-FR/reference/components/navigation/duxt-page-nav.md): Précédent et suivant, bornés par la section.
- [DuxtSections](https://duxt.app/fr-FR/reference/components/navigation/duxt-sections.md): La deuxième rangée de la barre de navigation — les parties de premier niveau de la documentation.
- [DuxtToc](https://duxt.app/fr-FR/reference/components/navigation/duxt-toc.md): Le sommaire, et l’encart en dessous.
- [Page](https://duxt.app/fr-FR/reference/components/page.md): Les composants qui appartiennent à la page elle-même.
- [DuxtCodeBlock](https://duxt.app/fr-FR/reference/components/page/duxt-code-block.md): La carte autour d’un bloc de code.
- [DuxtCopyPage](https://duxt.app/fr-FR/reference/components/page/duxt-copy-page.md): Donnez cette page à un modèle, ou lisez sa source.
- [DuxtPageFeedback](https://duxt.app/fr-FR/reference/components/page/duxt-page-feedback.md): « Cette page vous a-t-elle été utile ? » — un événement, et pas de backend.
- [DuxtPageInfo](https://duxt.app/fr-FR/reference/components/page/duxt-page-info.md): D’où vient la page : lien d’édition, dernière mise à jour, contributeurs.
- [Composables](https://duxt.app/fr-FR/reference/composables.md): Les fonctions que la couche expose à vos propres composants, une page chacune.
- [Configuration et contenu](https://duxt.app/fr-FR/reference/composables/config-and-content.md): La configuration fusionnée, et quelle collection sert la page en cours de lecture.
- [useDuxtBreadcrumb()](https://duxt.app/fr-FR/reference/composables/config-and-content/use-duxt-breadcrumb.md): Le fil qui descend de la section jusqu’à une page.
- [useDuxtCollection()](https://duxt.app/fr-FR/reference/composables/config-and-content/use-duxt-collection.md): Quelle collection sert cette route.
- [useDuxtConfig()](https://duxt.app/fr-FR/reference/composables/config-and-content/use-duxt-config.md): La configuration fusionnée, chaque champ de texte déjà résolu.
- [useDuxtNavigation()](https://duxt.app/fr-FR/reference/composables/config-and-content/use-duxt-navigation.md): L’arbre de navigation de la collection qui sert cette route.
- [useDuxtSection()](https://duxt.app/fr-FR/reference/composables/config-and-content/use-duxt-section.md): La partie de la documentation dans laquelle se trouve cette page.
- [Chemins et versions](https://duxt.app/fr-FR/reference/composables/paths-and-versions.md): Lire une URL, en écrire une en retour, et savoir quelle version est lue.
- [useDuxtLink()](https://duxt.app/fr-FR/reference/composables/paths-and-versions/use-duxt-link.md): Un chemin de documentation, réécrit en lien.
- [useDuxtPath()](https://duxt.app/fr-FR/reference/composables/paths-and-versions/use-duxt-path.md): Le chemin où se trouve la documentation, locale retirée.
- [useDuxtSiteUrl()](https://duxt.app/fr-FR/reference/composables/paths-and-versions/use-duxt-site-url.md): L’origine configurée, et les chemins rendus absolus.
- [useDuxtVersion()](https://duxt.app/fr-FR/reference/composables/paths-and-versions/use-duxt-version.md): Ce que montre le sélecteur, ce que dit la bannière, s’il faut indexer.
- [Expérience de lecture](https://duxt.app/fr-FR/reference/composables/reading.md): La recherche, les titres, le focus, l’historique, et les choix que fait un lecteur.
- [useActiveHeading()](https://duxt.app/fr-FR/reference/composables/reading/use-active-heading.md): Le titre actuellement en vue.
- [useDuxtAnalytics()](https://duxt.app/fr-FR/reference/composables/reading/use-duxt-analytics.md): Rapporter une interaction de lecteur à la fonction de rappel propre au site, ou à personne.
- [useDuxtPageFocus()](https://duxt.app/fr-FR/reference/composables/reading/use-duxt-page-focus.md): Déplace le focus vers le titre après une navigation côté client.
- [useDuxtSearch()](https://duxt.app/fr-FR/reference/composables/reading/use-duxt-search.md): Rechercher chaque source active et entrelacer ses résultats classés localement.
- [useDuxtShortcuts()](https://duxt.app/fr-FR/reference/composables/reading/use-duxt-shortcuts.md): Les touches que le thème écoute.
- [useDuxtToast()](https://duxt.app/fr-FR/reference/composables/reading/use-duxt-toast.md): Les notifications, enveloppées pour qu’aucun composant n’importe la bibliothèque.
- [useFuzzySearch()](https://duxt.app/fr-FR/reference/composables/reading/use-fuzzy-search.md): La tolérance aux fautes de frappe, à côté de l’index exact.
- [usePackageManager()](https://duxt.app/fr-FR/reference/composables/reading/use-package-manager.md): Le gestionnaire de paquets qu’un lecteur a choisi.
- [useRecentPages()](https://duxt.app/fr-FR/reference/composables/reading/use-recent-pages.md): Les pages ouvertes le plus récemment, jusqu’à la limite configurée.
- [Configuration](https://duxt.app/fr-FR/reference/configuration.md): Chaque clé sous duxt dans app.config.ts — ce qu’elle contrôle, et quand elle est lue.
- [Devtools](https://duxt.app/fr-FR/reference/devtools.md): Dix panneaux qui montrent ce que vos sources sont devenues. En développement seulement.
- [Cache](https://duxt.app/fr-FR/reference/devtools/cache.md): Le cache de téléchargement de Content, et un moyen d’en jeter une entrée.
- [Vérifications](https://duxt.app/fr-FR/reference/devtools/checks.md): Le validateur du build, appliqué à ce que le site sert en ce moment.
- [Config](https://duxt.app/fr-FR/reference/devtools/config.md): La configuration `duxt` fusionnée, et de quel côté de la fusion vient chaque valeur.
- [i18n](https://duxt.app/fr-FR/reference/devtools/i18n.md): Clés de message par langue, face à la langue de base.
- [Pages](https://duxt.app/fr-FR/reference/devtools/pages.md): Chaque page de chaque collection, avec son frontmatter et ses métadonnées git.
- [Chemins](https://duxt.app/fr-FR/reference/devtools/paths.md): Collez une URL et voyez quelle source la revendique et ce qu’elle y trouve.
- [Redirections](https://duxt.app/fr-FR/reference/devtools/redirects.md): Chaque redirection que sert le serveur, et lesquelles la couche a écrites.
- [Recherche](https://duxt.app/fr-FR/reference/devtools/search.md): Ce que contient l’index de recherche, via la requête même que lance la boîte de dialogue.
- [Sources](https://duxt.app/fr-FR/reference/devtools/sources.md): Ce que `duxt.sources` est devenu — une collection par source, version et langue.
- [Versions](https://duxt.app/fr-FR/reference/devtools/versions.md): Quelle version — et quelle langue — porte quelle page.
- [Points de terminaison](https://duxt.app/fr-FR/reference/endpoints.md): Tout ce que le site sert en dehors des pages, une page pour chacun.
- [/_duxt/devtools](https://duxt.app/fr-FR/reference/endpoints/devtools.md): La route depuis laquelle le panneau Nuxt Devtools est servi. En développement seulement.
- [/llms-full.txt](https://duxt.app/fr-FR/reference/endpoints/llms-full-txt.md): Une extension duxt avec les mêmes pages dans un fichier Markdown.
- [/llms.txt](https://duxt.app/fr-FR/reference/endpoints/llms-txt.md): La documentation en index Markdown, selon llmstxt.org.
- [/mcp](https://duxt.app/fr-FR/reference/endpoints/mcp.md): Un serveur MCP sur le même contenu.
- [<page>.md](https://duxt.app/fr-FR/reference/endpoints/page-markdown.md): La source de n’importe quelle page, à son URL suivie de .md.
- [/rss.xml](https://duxt.app/fr-FR/reference/endpoints/rss-xml.md): Le flux, une fois qu’une section est nommée.
- [/sitemap.xml et /robots.txt](https://duxt.app/fr-FR/reference/endpoints/sitemap-and-robots.md): Ce vers quoi un robot est dirigé, et ce dont on le tient à l’écart.
- [Frontmatter](https://duxt.app/fr-FR/reference/frontmatter.md): Les champs qu’une page peut porter au-delà du titre et de la description, et les deux que la compilation remplit.
- [Hooks](https://duxt.app/fr-FR/reference/hooks.md): L’unique hook de build que duxt émet, ce qu’il vous remet et pourquoi il n’y en a qu’un.
- [Composants MDC](https://duxt.app/fr-FR/reference/mdc-components.md): Les blocs qu’une page Markdown peut appeler, une page chacun, avec leurs props.
- [Accordion](https://duxt.app/fr-FR/reference/mdc-components/accordion.md): Des sections repliables — une FAQ, ou des réponses parmi lesquelles le lecteur choisit.
- [Élément d'accordéon](https://duxt.app/fr-FR/reference/mdc-components/accordion-item.md): Une section repliable.
- [Callout](https://duxt.app/fr-FR/reference/mdc-components/callout.md): Un encadré où le lecteur est censé s’arrêter — une astuce, un avertissement, un danger.
- [Groupe de code](https://duxt.app/fr-FR/reference/mdc-components/code-group.md): Plusieurs blocs de code en un seul bloc à onglets, étiquetés par nom de fichier.
- [Champ](https://duxt.app/fr-FR/reference/mdc-components/field.md): Un paramètre, une propriété ou une option, avec son type et sa valeur par défaut.
- [Groupe de champs](https://duxt.app/fr-FR/reference/mdc-components/field-group.md): Une liste de champs, en un seul bloc.
- [Arborescence de fichiers](https://duxt.app/fr-FR/reference/mdc-components/file-tree.md): Une structure de dossiers, avec une icône par type de fichier.
- [Mermaid](https://duxt.app/fr-FR/reference/mdc-components/mermaid.md): Un diagramme depuis un bloc ou une prop.
- [Gestionnaires de paquets](https://duxt.app/fr-FR/reference/mdc-components/package-managers.md): Une commande, un onglet par gestionnaire de paquets, mémorisé d’une page à l’autre.
- [Cartes de page](https://duxt.app/fr-FR/reference/mdc-components/page-cards.md): Les enfants d’une section, en cartes.
- [Partial](https://duxt.app/fr-FR/reference/mdc-components/partial.md): Un bloc écrit une fois et rendu dans chaque source qui en a besoin.
- [Aperçu](https://duxt.app/fr-FR/reference/mdc-components/preview.md): Un composant rendu tel que la page le rend, avec sa source à côté.
- [Surcharges de prose](https://duxt.app/fr-FR/reference/mdc-components/prose.md): Ce que la couche change au Markdown ordinaire — liens, titres, images, code et tableaux.
- [ProseA](https://duxt.app/fr-FR/reference/mdc-components/prose/prose-a.md): Un lien, résolu selon la source dans laquelle il a été écrit.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/fr-FR/reference/mdc-components/prose/prose-headings.md): Des titres, chacun avec une ancre de permalien.
- [ProseImg](https://duxt.app/fr-FR/reference/mdc-components/prose/prose-img.md): Une image : consciente du thème, adaptative et agrandissable.
- [ProsePre](https://duxt.app/fr-FR/reference/mdc-components/prose/prose-pre.md): Le bloc de code : nom de fichier, icône de langage, bouton de copie.
- [ProseTable](https://duxt.app/fr-FR/reference/mdc-components/prose/prose-table.md): Un tableau qui défile à la place de la page.
- [Since](https://duxt.app/fr-FR/reference/mdc-components/since.md): La version dans laquelle une chose est arrivée, à côté d’un titre.
- [Étapes](https://duxt.app/fr-FR/reference/mdc-components/steps.md): Une liste ordonnée dessinée en étapes numérotées sur un rail.
- [Tab](https://duxt.app/fr-FR/reference/mdc-components/tab.md): Un panneau d’un groupe d’onglets.
- [Groupe d'onglets](https://duxt.app/fr-FR/reference/mdc-components/tab-group.md): Des onglets pour tout ce qui n’est pas du code.
- [Référence de l’API](https://duxt.app/fr-FR/reference/openapi.md): Un document OpenAPI, publié en pages de référence avec un client qui envoie de vraies requêtes.
- [Composants](https://duxt.app/fr-FR/reference/openapi/components.md): Les trois composants MDC dont est faite une page de référence générée.
- [Échantillons de requête](https://duxt.app/fr-FR/reference/openapi/request-samples.md): La même requête dans douze clients, et comment ajouter le vôtre.
- [Déclarer la section](https://duxt.app/fr-FR/reference/openapi/section.md): Le type de section `openapi` — où vit le document, et ce qu’il devient.
- [Le client d’essai](https://duxt.app/fr-FR/reference/openapi/try-it.md): Une vraie requête, envoyée par le navigateur du lecteur lui-même.
- [Sources](https://duxt.app/fr-FR/reference/sources.md): Les champs d’une entrée de source, ses refs, et les options qui façonnent les URL.
- [Releases](https://duxt.app/fr-FR/releases.md)
- [0.1.0](https://duxt.app/fr-FR/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/fr-FR/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/fr-FR/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/fr-FR/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/fr-FR/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/fr-FR/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/fr-FR/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/fr-FR/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/fr-FR/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/fr-FR/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/fr-FR/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/fr-FR/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/fr-FR/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/fr-FR/releases/v0.9.0.md)
- [Introduction](https://duxt.app/getting-started.md): What duxt is, and what arrives with a single line of config.
- [Configuration](https://duxt.app/getting-started/configuration.md): One file configures the whole site — what belongs in it, and how it merges.
- [Start from the starter](https://duxt.app/getting-started/from-starter.md): Create a ready-to-run duxt documentation site with Nuxi.
- [Installation](https://duxt.app/getting-started/installation.md): Add the layer, extend it, write Markdown.
- [Guides](https://duxt.app/guides.md): One task per page, start to finish — several repositories, several versions, several languages, and a deploy.
- [Brand your site](https://duxt.app/guides/brand-your-site.md): Set the name, the wordmark and the icons, so the site reads as yours rather than as the layer's.
- [Cache remote sources and OG images](https://duxt.app/guides/cache-build-work.md): Reuse downloaded public repositories and rendered social cards safely between CI builds.
- [Collect page feedback](https://duxt.app/guides/collect-page-feedback.md): Wrap DuxtPageFeedback, keep the answer where your analytics already live.
- [Deploy a site](https://duxt.app/guides/deploy-a-site.md): Where a duxt site can run, what it needs there, and why content is not refreshed at runtime.
- [Move a page](https://duxt.app/guides/move-a-page.md): redirectFrom in the frontmatter, turned into route rules under every prefix.
- [Override the theme](https://duxt.app/guides/override-the-theme.md): Change a colour, replace a component, add a shadcn-vue primitive.
- [Publish Terraform provider docs](https://duxt.app/guides/publish-terraform-provider-docs.md): Turn a tfplugindocs Markdown tree into a versioned provider reference with provider-aware navigation.
- [Send analytics events](https://duxt.app/guides/send-analytics-events.md): One callback, five events, no provider — wire duxt's reader interactions into the analytics you already run.
- [Several languages](https://duxt.app/guides/several-languages.md): Serve the interface in several languages, and translate the pages themselves.
- [Several repositories](https://duxt.app/guides/several-repositories.md): Serve the documentation of several projects from one site.
- [Several versions](https://duxt.app/guides/several-versions.md): Serve the same documentation at several refs, with a switcher and a banner.
- [Documentação](https://duxt.app/pt-BR.md): Uma camada Nuxt que transforma a pasta docs de um repositório num site de documentação versionado e multirrepositório.
- [Extensões](https://duxt.app/pt-BR/add-ons.md): Camadas complementares que estendem um site duxt — cada uma é um pacote próprio, adicionado com mais uma entrada em extends.
- [Meilisearch](https://duxt.app/pt-BR/add-ons/meilisearch.md): Adicione a camada complementar oficial para indexação atômica durante o build e busca opcional no navegador.
- [Typesense](https://duxt.app/pt-BR/add-ons/typesense.md): Consuma o único hook de build do duxt em uma coleção do Typesense — cada fonte, versão e idioma, atualizados por um id estável.
- [Decisões de arquitetura](https://duxt.app/pt-BR/adr.md): O registo de decisões — todas as decisões de arquitetura registadas para o duxt.
- [Construir o duxt como uma camada que transporta um módulo](https://duxt.app/pt-BR/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribuir o tema como uma camada Nuxt cuja raiz é o pacote, e não como um modelo inicial.
- [Gerar as coleções a partir de uma só lista de fontes](https://duxt.app/pt-BR/adr/0002-generate-the-collections-from-one-source-list.md): Calcular as coleções do Content a partir de uma lista de fontes compacta ao carregar a configuração, em vez de fazer quem a consome declará-las.
- [Decidir os prefixos de URL em tempo de compilação](https://duxt.app/pt-BR/adr/0003-decide-the-url-prefixes-at-build-time.md): Se um segmento de repositório ou de versão aparece é decidido pela lista de fontes antes do primeiro pedido, nunca por pedido.
- [Desenhar os componentes Markdown com MDC](https://duxt.app/pt-BR/adr/0004-render-markdown-components-with-mdc.md): Usar a própria sintaxe MDC do Content para componentes dentro do Markdown, em vez de adotar MDX.
- [Entregar a camada sem ligações específicas do proprietário](https://duxt.app/pt-BR/adr/0005-ship-the-layer-without-owner-specific-links.md): Toda a predefinição que nomearia um projeto concreto — repositório, gestor de issues, comunidade, aviso legal — é entregue vazia.
- [Recompilar de forma agendada em vez de atualizar em tempo de execução](https://duxt.app/pt-BR/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): Um site que lê outro repositório apanha as suas alterações quando compila, e não é oferecida nenhuma atualização em tempo de execução.
- [Servir as traduções como coleções próprias](https://duxt.app/pt-BR/adr/0007-serve-translations-as-collections-of-their-own.md): Acrescentar uma dimensão de locale a uma fonte, em vez de um segmento de locale ao caminho de conteúdo.
- [Construir o tema sobre componentes shadcn-vue próprios](https://duxt.app/pt-BR/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): A camada guarda o código-fonte dos seus componentes de interface em vez de os importar de uma biblioteca de componentes ou de um tema de documentação já feito.
- [Tirar a base de SEO do pacote Nuxt SEO](https://duxt.app/pt-BR/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): A camada instala o @nuxtjs/seo e entrega-lhe as etiquetas de head e os dados estruturados que antes escrevia à mão, guardando apenas as regras que dependem de versões e traduções.
- [Manter a pesquisa por coleção do Content como padrão](https://duxt.app/pt-BR/adr/0010-keep-contents-per-collection-search-as-the-default.md): Um único índice sobre todas as fontes foi medido contra a pesquisa de um índice por coleção do Content e não é o padrão da camada; o hook de compilação transforma-o antes numa camada fornecedora.
- [Alojar as camadas fornecedoras num monorepo Turborepo](https://duxt.app/pt-BR/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): A camada passa para packages/duxt e o site para apps/www, cada pacote publicado versiona e marca por si como <name>@vX.Y.Z, e a decisão de repositórios próprios registada em
- [Conceitos](https://duxt.app/pt-BR/concepts.md): Como a camada funciona — o modelo de fontes, o esquema de URL, as coleções e as verificações.
- [O que a compilação verifica](https://duxt.app/pt-BR/concepts/build-checks.md): As falhas silenciosas que esta camada teve, transformadas em mensagens.
- [Coleções](https://duxt.app/pt-BR/concepts/collections.md): O que o Content constrói a partir das fontes, e as quatro coisas que o esquema acrescenta.
- [Bases de dados](https://duxt.app/pt-BR/concepts/databases.md): Em que adaptadores de base de dados do Content um site duxt pode ser implementado, quais foram verificados e a única regra que mantém a camada fora do caminho.
- [Secções geradas](https://duxt.app/pt-BR/concepts/generated-sections.md): Um artefacto mais um tipo, publicados como páginas — o que é o registo, e as duas políticas que um tipo responde.
- [Atalhos de teclado](https://duxt.app/pt-BR/concepts/keyboard-shortcuts.md): As quatro teclas que o tema vincula, onde cada uma se aplica e onde quem lê fica a saber.
- [Camadas e substituição](https://duxt.app/pt-BR/concepts/layers.md): O que uma camada Nuxt te dá, o que te tira, e que caminhos não resolvem como se leem.
- [Localização](https://duxt.app/pt-BR/concepts/localisation.md): A camada traz sete locales, e cada texto configurado assume três formas.
- [Leitores automáticos](https://duxt.app/pt-BR/concepts/machine-readers.md): O que um modelo recebe — llms.txt, o Markdown em bruto de qualquer página e um verdadeiro servidor MCP.
- [SEO](https://duxt.app/pt-BR/concepts/seo.md): O que cada página emite para rastreadores e cartões sociais, que módulo o escreve, e o único valor que a camada não consegue adivinhar.
- [Fontes](https://duxt.app/pt-BR/concepts/sources.md): Uma lista de fontes torna-se cada coleção, prefixo e versão que o site serve.
- [Tematização](https://duxt.app/pt-BR/concepts/theming.md): Como o tema está montado — componentes próprios, uma camada de tokens e um modo escuro que comuta por classe.
- [URL e versões](https://duxt.app/pt-BR/concepts/urls-and-versions.md): Como aparecem os segmentos de repositório e versão, e o que é dito a quem lê uma versão antiga.
- [Convenções](https://duxt.app/pt-BR/conventions.md): Regras próprias do projeto — as que não se deduzem do código.
- [Identidade](https://duxt.app/pt-BR/conventions/branding.md): A marca [d]uxt — onde é usado cada recurso, por que os parênteses do ícone foram redesenhados, e que cores são fixas.
- [Segurança das dependências](https://duxt.app/pt-BR/conventions/dependency-security.md): Rever avisos sem esconder os caminhos afetados.
- [Ícones](https://duxt.app/pt-BR/conventions/icons.md): Quatro conjuntos de ícones, e a única pergunta que decide qual deles desenha uma marca.
- [Créditos](https://duxt.app/pt-BR/credits.md): Aquilo em que o duxt assenta, e aquilo de que partiu.
- [Overview](https://duxt.app/pt-BR/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/pt-BR/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/pt-BR/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/pt-BR/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/pt-BR/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/pt-BR/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/pt-BR/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/pt-BR/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/pt-BR/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/pt-BR/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/pt-BR/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/pt-BR/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/pt-BR/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/pt-BR/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/pt-BR/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/pt-BR/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/pt-BR/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/pt-BR/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/pt-BR/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/pt-BR/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/pt-BR/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/pt-BR/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/pt-BR/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/pt-BR/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/pt-BR/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/pt-BR/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/pt-BR/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/pt-BR/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/pt-BR/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/pt-BR/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/pt-BR/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/pt-BR/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/pt-BR/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/pt-BR/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/pt-BR/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/pt-BR/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/pt-BR/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/pt-BR/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/pt-BR/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/pt-BR/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/pt-BR/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/pt-BR/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/pt-BR/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/pt-BR/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/pt-BR/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/pt-BR/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/pt-BR/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/pt-BR/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/pt-BR/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/pt-BR/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/pt-BR/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/pt-BR/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/pt-BR/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/pt-BR/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/pt-BR/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/pt-BR/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/pt-BR/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/pt-BR/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/pt-BR/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/pt-BR/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/pt-BR/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/pt-BR/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/pt-BR/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/pt-BR/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/pt-BR/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/pt-BR/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/pt-BR/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/pt-BR/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/pt-BR/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/pt-BR/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/pt-BR/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/pt-BR/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/pt-BR/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/pt-BR/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/pt-BR/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Introdução](https://duxt.app/pt-BR/getting-started.md): O que é o duxt, e o que chega com uma única linha de configuração.
- [Configuração](https://duxt.app/pt-BR/getting-started/configuration.md): Um ficheiro configura o site inteiro — o que lhe pertence e como é combinado.
- [Começar com o starter](https://duxt.app/pt-BR/getting-started/from-starter.md): Cria com o Nuxi um site de documentação duxt pronto a executar.
- [Instalação](https://duxt.app/pt-BR/getting-started/installation.md): Adicione a camada, estenda-a, escreva Markdown.
- [Guias](https://duxt.app/pt-BR/guides.md): Uma tarefa por página, do início ao fim — vários repositórios, várias versões, vários idiomas e uma implementação.
- [Dá identidade ao teu site](https://duxt.app/pt-BR/guides/brand-your-site.md): Define o nome, o logótipo e os ícones, para que o site se leia como teu e não como o da camada.
- [Guardar fontes remotas e imagens OG em cache](https://duxt.app/pt-BR/guides/cache-build-work.md): Reutilizar downloads de repositórios públicos e cartões sociais renderizados entre builds de CI.
- [Recolher opiniões da página](https://duxt.app/pt-BR/guides/collect-page-feedback.md): Envolve o DuxtPageFeedback e guarda a resposta onde a tua analítica já vive.
- [Implementar um site](https://duxt.app/pt-BR/guides/deploy-a-site.md): Onde um site duxt pode correr, do que precisa lá, e porque o conteúdo não é atualizado em execução.
- [Mover uma página](https://duxt.app/pt-BR/guides/move-a-page.md): redirectFrom no frontmatter, transformado em regras de rota sob todos os prefixos.
- [Substituir o tema](https://duxt.app/pt-BR/guides/override-the-theme.md): Mudar uma cor, substituir um componente, acrescentar uma primitiva shadcn-vue.
- [Publicar documentação de um provider Terraform](https://duxt.app/pt-BR/guides/publish-terraform-provider-docs.md): Transformar uma árvore Markdown do tfplugindocs numa referência versionada com navegação própria do provider.
- [Enviar eventos de analítica](https://duxt.app/pt-BR/guides/send-analytics-events.md): Um callback, cinco eventos, nenhum fornecedor — liga as interações dos leitores do duxt à analítica que já tens a correr.
- [Vários idiomas](https://duxt.app/pt-BR/guides/several-languages.md): Servir a interface em vários idiomas, e traduzir também as páginas.
- [Vários repositórios](https://duxt.app/pt-BR/guides/several-repositories.md): Servir a documentação de vários projetos a partir de um só site.
- [Várias versões](https://duxt.app/pt-BR/guides/several-versions.md): Servir a mesma documentação em várias refs, com seletor e aviso.
- [Referência](https://duxt.app/pt-BR/reference.md): A superfície pública da camada — chaves de configuração, frontmatter, componentes, composables e endpoints.
- [Coleções Bruno](https://duxt.app/pt-BR/reference/bruno.md): Uma coleção Bruno publicada como referência centrada em pedidos, com um arquivo descarregável.
- [Obter a coleção](https://duxt.app/pt-BR/reference/bruno/getting-the-collection.md): O arquivo está ligado à versão e idioma visíveis; a ligação Bruno não.
- [Declarar a secção](https://duxt.app/pt-BR/reference/bruno/section.md): Onde vive uma coleção Bruno, que páginas produz e que opções aceita.
- [O cliente de pedidos](https://duxt.app/pt-BR/reference/bruno/try-it.md): Desligado por omissão e dirigido apenas a destinos declarados públicos.
- [O que é publicado](https://duxt.app/pt-BR/reference/bruno/what-is-published.md): Environments, credenciais, scripts e testes nunca chegam a uma página.
- [Registo de alterações](https://duxt.app/pt-BR/reference/changelog.md): Um registo de versões, publicado como páginas — uma cronologia, uma página por versão, e um feed.
- [Esquema e componentes](https://duxt.app/pt-BR/reference/changelog/components.md): O esquema em que um histórico dividido renderiza, e os dois componentes MDC de que as suas páginas são feitas.
- [Granularidade](https://duxt.app/pt-BR/reference/changelog/granularity.md): Uma página por versão, ou o ficheiro como a única página que foi escrito.
- [Declarar a secção](https://duxt.app/pt-BR/reference/changelog/section.md): O tipo de secção `changelog` — onde vive o ficheiro, e as duas políticas que responde.
- [O que é lido](https://duxt.app/pt-BR/reference/changelog/what-is-read.md): Que títulos passam a versões, quais a grupos, e o que acontece ao resto.
- [Componentes](https://duxt.app/pt-BR/reference/components.md): Os componentes da própria camada, uma página cada — para que serve cada um e o que recebe.
- [Controlos](https://duxt.app/pt-BR/reference/components/controls.md): O que o leitor opera — a pesquisa, os seletores, a folha de atalhos e dois indicadores.
- [DuxtLocale](https://duxt.app/pt-BR/reference/components/controls/duxt-locale.md): O seletor de idioma.
- [DuxtProgress](https://duxt.app/pt-BR/reference/components/controls/duxt-progress.md): Até onde o leitor já desceu na página.
- [DuxtSearch](https://duxt.app/pt-BR/reference/components/controls/duxt-search.md): Pesquisa cada fonte ativa e intercala os seus resultados ordenados localmente.
- [DuxtShortcuts](https://duxt.app/pt-BR/reference/components/controls/duxt-shortcuts.md): A folha de atalhos de teclado, na tecla ?.
- [DuxtShortcutsTrigger](https://duxt.app/pt-BR/reference/components/controls/duxt-shortcuts-trigger.md): O botão que abre a folha de atalhos.
- [DuxtSkipLink](https://duxt.app/pt-BR/reference/components/controls/duxt-skip-link.md): O primeiro elemento focável da página.
- [DuxtVersion](https://duxt.app/pt-BR/reference/components/controls/duxt-version.md): O distintivo de versão, e o seletor quando há mais do que uma.
- [DuxtVersionBanner](https://duxt.app/pt-BR/reference/components/controls/duxt-version-banner.md): A barra que diz ao leitor que esta versão não é a atual.
- [Layout](https://duxt.app/pt-BR/reference/components/layout.md): Os dois componentes que emolduram uma página — a barra de navegação e o rodapé.
- [DuxtAnnouncements](https://duxt.app/pt-BR/reference/components/layout/duxt-announcements.md): Avisos do próprio site, desenhados por posição apenas quando existe algo a anunciar.
- [DuxtFooter](https://duxt.app/pt-BR/reference/components/layout/duxt-footer.md): O rodapé: o nome do site, as suas ligações legais e a linha da própria camada.
- [DuxtHeader](https://duxt.app/pt-BR/reference/components/layout/duxt-header.md): A barra de navegação: título, navegação, pesquisa e as ligações de ícone.
- [Navegação](https://duxt.app/pt-BR/reference/components/navigation.md): Circular pela documentação — a linha de secções, a barra lateral, o trilho, o índice e anterior/seguinte.
- [DuxtBreadcrumb](https://duxt.app/pt-BR/reference/components/navigation/duxt-breadcrumb.md): O trilho por cima do título da página.
- [DuxtNavigation](https://duxt.app/pt-BR/reference/components/navigation/duxt-navigation.md): A árvore da barra lateral.
- [DuxtNavigationLink](https://duxt.app/pt-BR/reference/components/navigation/duxt-navigation-link.md): Uma entrada da barra lateral.
- [DuxtPageNav](https://duxt.app/pt-BR/reference/components/navigation/duxt-page-nav.md): Anterior e seguinte, limitados pela secção.
- [DuxtSections](https://duxt.app/pt-BR/reference/components/navigation/duxt-sections.md): A segunda linha da barra de navegação — as partes de topo da documentação.
- [DuxtToc](https://duxt.app/pt-BR/reference/components/navigation/duxt-toc.md): O índice, e o aside por baixo dele.
- [Página](https://duxt.app/pt-BR/reference/components/page.md): Os componentes que pertencem à própria página.
- [DuxtCodeBlock](https://duxt.app/pt-BR/reference/components/page/duxt-code-block.md): O cartão à volta de um bloco de código.
- [DuxtCopyPage](https://duxt.app/pt-BR/reference/components/page/duxt-copy-page.md): Entrega esta página a um modelo, ou lê o seu código-fonte.
- [DuxtPageFeedback](https://duxt.app/pt-BR/reference/components/page/duxt-page-feedback.md): «Esta página foi útil?» — um evento, e sem backend.
- [DuxtPageInfo](https://duxt.app/pt-BR/reference/components/page/duxt-page-info.md): De onde veio a página: ligação de edição, última atualização, contribuidores.
- [Composables](https://duxt.app/pt-BR/reference/composables.md): As funções que a camada expõe aos teus próprios componentes, uma página cada.
- [Configuração e conteúdo](https://duxt.app/pt-BR/reference/composables/config-and-content.md): A configuração fundida, e que coleção serve a página que está a ser lida.
- [useDuxtBreadcrumb()](https://duxt.app/pt-BR/reference/composables/config-and-content/use-duxt-breadcrumb.md): O trilho da secção até uma página.
- [useDuxtCollection()](https://duxt.app/pt-BR/reference/composables/config-and-content/use-duxt-collection.md): Que coleção serve esta rota.
- [useDuxtConfig()](https://duxt.app/pt-BR/reference/composables/config-and-content/use-duxt-config.md): A configuração fundida, com todos os campos de texto já resolvidos.
- [useDuxtNavigation()](https://duxt.app/pt-BR/reference/composables/config-and-content/use-duxt-navigation.md): A árvore de navegação da coleção que serve esta rota.
- [useDuxtSection()](https://duxt.app/pt-BR/reference/composables/config-and-content/use-duxt-section.md): A parte da documentação em que esta página está.
- [Caminhos e versões](https://duxt.app/pt-BR/reference/composables/paths-and-versions.md): Ler um URL, escrever outro de volta, e saber que versão está a ser lida.
- [useDuxtLink()](https://duxt.app/pt-BR/reference/composables/paths-and-versions/use-duxt-link.md): Um caminho de documentação, reescrito como ligação.
- [useDuxtPath()](https://duxt.app/pt-BR/reference/composables/paths-and-versions/use-duxt-path.md): O caminho em que a documentação está, com o locale retirado.
- [useDuxtSiteUrl()](https://duxt.app/pt-BR/reference/composables/paths-and-versions/use-duxt-site-url.md): A origem configurada, e caminhos tornados absolutos.
- [useDuxtVersion()](https://duxt.app/pt-BR/reference/composables/paths-and-versions/use-duxt-version.md): O que o seletor mostra, o que o aviso diz, se se deve indexar.
- [Experiência de leitura](https://duxt.app/pt-BR/reference/composables/reading.md): Pesquisa, cabeçalhos, foco, histórico e as escolhas que um leitor faz.
- [useActiveHeading()](https://duxt.app/pt-BR/reference/composables/reading/use-active-heading.md): O cabeçalho que está à vista neste momento.
- [useDuxtAnalytics()](https://duxt.app/pt-BR/reference/composables/reading/use-duxt-analytics.md): Comunicar uma interação do leitor ao callback do próprio site, ou a ninguém.
- [useDuxtPageFocus()](https://duxt.app/pt-BR/reference/composables/reading/use-duxt-page-focus.md): Move o foco para o cabeçalho depois de uma navegação do lado do cliente.
- [useDuxtSearch()](https://duxt.app/pt-BR/reference/composables/reading/use-duxt-search.md): Pesquisa cada fonte ativa e intercala os seus resultados ordenados localmente.
- [useDuxtShortcuts()](https://duxt.app/pt-BR/reference/composables/reading/use-duxt-shortcuts.md): As teclas que o tema escuta.
- [useDuxtToast()](https://duxt.app/pt-BR/reference/composables/reading/use-duxt-toast.md): Notificações, embrulhadas para que nenhum componente importe a biblioteca.
- [useFuzzySearch()](https://duxt.app/pt-BR/reference/composables/reading/use-fuzzy-search.md): Tolerância a gralhas ao lado do índice exato.
- [usePackageManager()](https://duxt.app/pt-BR/reference/composables/reading/use-package-manager.md): O gestor de pacotes que um leitor escolheu.
- [useRecentPages()](https://duxt.app/pt-BR/reference/composables/reading/use-recent-pages.md): As páginas abertas mais recentemente, até ao limite configurado.
- [Configuração](https://duxt.app/pt-BR/reference/configuration.md): Cada chave sob duxt em app.config.ts — o que controla e quando é lida.
- [Devtools](https://duxt.app/pt-BR/reference/devtools.md): Dez painéis que mostram no que as tuas fontes se tornaram. Apenas em desenvolvimento.
- [Cache](https://duxt.app/pt-BR/reference/devtools/cache.md): A cache de descargas do Content, e uma forma de deitar fora uma entrada.
- [Checks](https://duxt.app/pt-BR/reference/devtools/checks.md): O validador da compilação, aplicado ao que o site está a servir agora.
- [Config](https://duxt.app/pt-BR/reference/devtools/config.md): A configuração `duxt` fundida, e de que lado da fusão vem cada valor.
- [i18n](https://duxt.app/pt-BR/reference/devtools/i18n.md): Chaves de mensagem por idioma, contra o idioma base.
- [Pages](https://duxt.app/pt-BR/reference/devtools/pages.md): Todas as páginas de todas as coleções, com o frontmatter e os metadados de git.
- [Paths](https://duxt.app/pt-BR/reference/devtools/paths.md): Cola um URL e vê que fonte o reclama e o que encontra lá.
- [Redirects](https://duxt.app/pt-BR/reference/devtools/redirects.md): Todos os redireccionamentos que o servidor serve, e quais deles a camada escreveu.
- [Search](https://duxt.app/pt-BR/reference/devtools/search.md): O que o índice de pesquisa contém, pela mesma consulta que a caixa de diálogo faz.
- [Sources](https://duxt.app/pt-BR/reference/devtools/sources.md): No que `duxt.sources` se tornou — uma coleção por fonte, versão e idioma.
- [Versions](https://duxt.app/pt-BR/reference/devtools/versions.md): Que versão — e que idioma — leva que página.
- [Endpoints](https://duxt.app/pt-BR/reference/endpoints.md): Tudo o que o site serve além das páginas, uma página cada.
- [/_duxt/devtools](https://duxt.app/pt-BR/reference/endpoints/devtools.md): A rota a partir da qual o painel das Nuxt Devtools é servido. Apenas em desenvolvimento.
- [/llms-full.txt](https://duxt.app/pt-BR/reference/endpoints/llms-full-txt.md): Uma extensão do duxt com as mesmas páginas num ficheiro Markdown.
- [/llms.txt](https://duxt.app/pt-BR/reference/endpoints/llms-txt.md): A documentação como índice Markdown, segundo llmstxt.org.
- [/mcp](https://duxt.app/pt-BR/reference/endpoints/mcp.md): Um servidor MCP sobre o mesmo conteúdo.
- [<page>.md](https://duxt.app/pt-BR/reference/endpoints/page-markdown.md): O código-fonte de qualquer página, no seu próprio URL mais .md.
- [/rss.xml](https://duxt.app/pt-BR/reference/endpoints/rss-xml.md): O feed, assim que uma secção for nomeada.
- [/sitemap.xml e /robots.txt](https://duxt.app/pt-BR/reference/endpoints/sitemap-and-robots.md): Para onde um rastreador é apontado, e aquilo de que é mantido fora.
- [Frontmatter](https://duxt.app/pt-BR/reference/frontmatter.md): Os campos que uma página pode ter além do título e da descrição, e os dois que a compilação preenche.
- [Hooks](https://duxt.app/pt-BR/reference/hooks.md): O único hook de build que o duxt emite, o que ele entrega e por que existe apenas um.
- [Componentes MDC](https://duxt.app/pt-BR/reference/mdc-components.md): Os blocos que uma página Markdown pode invocar, uma página cada, com as suas props.
- [Accordion](https://duxt.app/pt-BR/reference/mdc-components/accordion.md): Secções recolhíveis — um FAQ, ou respostas que o leitor escolhe.
- [Item de accordion](https://duxt.app/pt-BR/reference/mdc-components/accordion-item.md): Uma secção recolhível.
- [Callout](https://duxt.app/pt-BR/reference/mdc-components/callout.md): Um aparte em que o leitor deve parar — uma dica, um aviso, um perigo.
- [Grupo de código](https://duxt.app/pt-BR/reference/mdc-components/code-group.md): Vários blocos de código como um só bloco com separadores, rotulados pelo nome do ficheiro.
- [Campo](https://duxt.app/pt-BR/reference/mdc-components/field.md): Um parâmetro, propriedade ou opção, com o seu tipo e valor por omissão.
- [Grupo de campos](https://duxt.app/pt-BR/reference/mdc-components/field-group.md): Uma lista de campos como um só bloco.
- [Árvore de ficheiros](https://duxt.app/pt-BR/reference/mdc-components/file-tree.md): Uma estrutura de pastas, com ícones por tipo de ficheiro.
- [Mermaid](https://duxt.app/pt-BR/reference/mdc-components/mermaid.md): Um diagrama a partir de um bloco de código ou de uma prop.
- [Gestores de pacotes](https://duxt.app/pt-BR/reference/mdc-components/package-managers.md): Um comando, um separador por gestor de pacotes, memorizado de página em página.
- [Cartões de página](https://duxt.app/pt-BR/reference/mdc-components/page-cards.md): Os filhos de uma secção, como cartões.
- [Partial](https://duxt.app/pt-BR/reference/mdc-components/partial.md): Um bloco escrito uma vez e apresentado em todas as fontes que dele precisam.
- [Pré-visualização](https://duxt.app/pt-BR/reference/mdc-components/preview.md): Um componente desenhado tal como a página o desenha, com o seu código-fonte ao lado.
- [Substituições de prosa](https://duxt.app/pt-BR/reference/mdc-components/prose.md): O que a camada muda no Markdown simples — ligações, cabeçalhos, imagens, código e tabelas.
- [ProseA](https://duxt.app/pt-BR/reference/mdc-components/prose/prose-a.md): Uma ligação, resolvida em função da fonte em que foi escrita.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/pt-BR/reference/mdc-components/prose/prose-headings.md): Cabeçalhos, cada um com a sua âncora permanente.
- [ProseImg](https://duxt.app/pt-BR/reference/mdc-components/prose/prose-img.md): Uma imagem: consciente do tema, adaptável e ampliável.
- [ProsePre](https://duxt.app/pt-BR/reference/mdc-components/prose/prose-pre.md): O bloco de código: nome do ficheiro, ícone da linguagem, botão de copiar.
- [ProseTable](https://duxt.app/pt-BR/reference/mdc-components/prose/prose-table.md): Uma tabela que se desloca em vez da página.
- [Since](https://duxt.app/pt-BR/reference/mdc-components/since.md): A versão em que algo apareceu, ao lado de um cabeçalho.
- [Passos](https://duxt.app/pt-BR/reference/mdc-components/steps.md): Uma lista ordenada desenhada como passos numerados sobre uma calha.
- [Tab](https://duxt.app/pt-BR/reference/mdc-components/tab.md): Um painel de um grupo de separadores.
- [Grupo de separadores](https://duxt.app/pt-BR/reference/mdc-components/tab-group.md): Separadores para tudo o que não seja código.
- [Referência da API](https://duxt.app/pt-BR/reference/openapi.md): Um documento OpenAPI, publicado como páginas de referência com um cliente que envia pedidos reais.
- [Componentes](https://duxt.app/pt-BR/reference/openapi/components.md): Os três componentes MDC de que é feita uma página de referência gerada.
- [Amostras de pedido](https://duxt.app/pt-BR/reference/openapi/request-samples.md): O mesmo pedido em doze clientes, e como acrescentar o teu.
- [Declarar a secção](https://duxt.app/pt-BR/reference/openapi/section.md): O tipo de secção `openapi` — onde vive o documento, e no que se torna.
- [O cliente de ensaio](https://duxt.app/pt-BR/reference/openapi/try-it.md): Um pedido real, enviado pelo próprio navegador do leitor.
- [Fontes](https://duxt.app/pt-BR/reference/sources.md): Os campos de uma entrada de fonte, as suas refs, e as opções que moldam os URL.
- [Releases](https://duxt.app/pt-BR/releases.md)
- [0.1.0](https://duxt.app/pt-BR/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/pt-BR/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/pt-BR/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/pt-BR/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/pt-BR/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/pt-BR/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/pt-BR/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/pt-BR/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/pt-BR/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/pt-BR/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/pt-BR/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/pt-BR/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/pt-BR/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/pt-BR/releases/v0.9.0.md)
- [Documentação](https://duxt.app/pt-PT.md): Uma camada Nuxt que transforma a pasta docs de um repositório num site de documentação versionado e multirrepositório.
- [Extensões](https://duxt.app/pt-PT/add-ons.md): Camadas complementares que estendem um site duxt — cada uma é um pacote próprio, adicionado com mais uma entrada em extends.
- [Meilisearch](https://duxt.app/pt-PT/add-ons/meilisearch.md): Adicione a camada complementar oficial para indexação atômica durante o build e busca opcional no navegador.
- [Typesense](https://duxt.app/pt-PT/add-ons/typesense.md): Consuma o único hook de build do duxt em uma coleção do Typesense — cada fonte, versão e idioma, atualizados por um id estável.
- [Decisões de arquitetura](https://duxt.app/pt-PT/adr.md): O registo de decisões — todas as decisões de arquitetura registadas para o duxt.
- [Construir o duxt como uma camada que transporta um módulo](https://duxt.app/pt-PT/adr/0001-build-duxt-as-a-layer-carrying-a-module.md): Distribuir o tema como uma camada Nuxt cuja raiz é o pacote, e não como um modelo inicial.
- [Gerar as coleções a partir de uma só lista de fontes](https://duxt.app/pt-PT/adr/0002-generate-the-collections-from-one-source-list.md): Calcular as coleções do Content a partir de uma lista de fontes compacta ao carregar a configuração, em vez de fazer quem a consome declará-las.
- [Decidir os prefixos de URL em tempo de compilação](https://duxt.app/pt-PT/adr/0003-decide-the-url-prefixes-at-build-time.md): Se um segmento de repositório ou de versão aparece é decidido pela lista de fontes antes do primeiro pedido, nunca por pedido.
- [Desenhar os componentes Markdown com MDC](https://duxt.app/pt-PT/adr/0004-render-markdown-components-with-mdc.md): Usar a própria sintaxe MDC do Content para componentes dentro do Markdown, em vez de adotar MDX.
- [Entregar a camada sem ligações específicas do proprietário](https://duxt.app/pt-PT/adr/0005-ship-the-layer-without-owner-specific-links.md): Toda a predefinição que nomearia um projeto concreto — repositório, gestor de issues, comunidade, aviso legal — é entregue vazia.
- [Recompilar de forma agendada em vez de atualizar em tempo de execução](https://duxt.app/pt-PT/adr/0006-rebuild-on-a-schedule-rather-than-refresh-at-runtime.md): Um site que lê outro repositório apanha as suas alterações quando compila, e não é oferecida nenhuma atualização em tempo de execução.
- [Servir as traduções como coleções próprias](https://duxt.app/pt-PT/adr/0007-serve-translations-as-collections-of-their-own.md): Acrescentar uma dimensão de locale a uma fonte, em vez de um segmento de locale ao caminho de conteúdo.
- [Construir o tema sobre componentes shadcn-vue próprios](https://duxt.app/pt-PT/adr/0008-build-the-theme-on-owned-shadcn-vue-components.md): A camada guarda o código-fonte dos seus componentes de interface em vez de os importar de uma biblioteca de componentes ou de um tema de documentação já feito.
- [Tirar a base de SEO do pacote Nuxt SEO](https://duxt.app/pt-PT/adr/0009-take-the-seo-stack-from-the-nuxt-seo-bundle.md): A camada instala o @nuxtjs/seo e entrega-lhe as etiquetas de head e os dados estruturados que antes escrevia à mão, guardando apenas as regras que dependem de versões e traduções.
- [Manter a pesquisa por coleção do Content como padrão](https://duxt.app/pt-PT/adr/0010-keep-contents-per-collection-search-as-the-default.md): Um único índice sobre todas as fontes foi medido contra a pesquisa de um índice por coleção do Content e não é o padrão da camada; o hook de compilação transforma-o antes numa camada fornecedora.
- [Alojar as camadas fornecedoras num monorepo Turborepo](https://duxt.app/pt-PT/adr/0011-host-the-provider-layers-in-a-turborepo-monorepo.md): A camada passa para packages/duxt e o site para apps/www, cada pacote publicado versiona e marca por si como <name>@vX.Y.Z, e a decisão de repositórios próprios registada em
- [Conceitos](https://duxt.app/pt-PT/concepts.md): Como a camada funciona — o modelo de fontes, o esquema de URL, as coleções e as verificações.
- [O que a compilação verifica](https://duxt.app/pt-PT/concepts/build-checks.md): As falhas silenciosas que esta camada teve, transformadas em mensagens.
- [Coleções](https://duxt.app/pt-PT/concepts/collections.md): O que o Content constrói a partir das fontes, e as quatro coisas que o esquema acrescenta.
- [Bases de dados](https://duxt.app/pt-PT/concepts/databases.md): Em que adaptadores de base de dados do Content um site duxt pode ser implementado, quais foram verificados e a única regra que mantém a camada fora do caminho.
- [Secções geradas](https://duxt.app/pt-PT/concepts/generated-sections.md): Um artefacto mais um tipo, publicados como páginas — o que é o registo, e as duas políticas que um tipo responde.
- [Atalhos de teclado](https://duxt.app/pt-PT/concepts/keyboard-shortcuts.md): As quatro teclas que o tema vincula, onde cada uma se aplica e onde quem lê fica a saber.
- [Camadas e substituição](https://duxt.app/pt-PT/concepts/layers.md): O que uma camada Nuxt te dá, o que te tira, e que caminhos não resolvem como se leem.
- [Localização](https://duxt.app/pt-PT/concepts/localisation.md): A camada traz sete locales, e cada texto configurado assume três formas.
- [Leitores automáticos](https://duxt.app/pt-PT/concepts/machine-readers.md): O que um modelo recebe — llms.txt, o Markdown em bruto de qualquer página e um verdadeiro servidor MCP.
- [SEO](https://duxt.app/pt-PT/concepts/seo.md): O que cada página emite para rastreadores e cartões sociais, que módulo o escreve, e o único valor que a camada não consegue adivinhar.
- [Fontes](https://duxt.app/pt-PT/concepts/sources.md): Uma lista de fontes torna-se cada coleção, prefixo e versão que o site serve.
- [Tematização](https://duxt.app/pt-PT/concepts/theming.md): Como o tema está montado — componentes próprios, uma camada de tokens e um modo escuro que comuta por classe.
- [URL e versões](https://duxt.app/pt-PT/concepts/urls-and-versions.md): Como aparecem os segmentos de repositório e versão, e o que é dito a quem lê uma versão antiga.
- [Convenções](https://duxt.app/pt-PT/conventions.md): Regras próprias do projeto — as que não se deduzem do código.
- [Identidade](https://duxt.app/pt-PT/conventions/branding.md): A marca [d]uxt — onde é usado cada recurso, por que os parênteses do ícone foram redesenhados, e que cores são fixas.
- [Segurança das dependências](https://duxt.app/pt-PT/conventions/dependency-security.md): Rever avisos sem esconder os caminhos afetados.
- [Ícones](https://duxt.app/pt-PT/conventions/icons.md): Quatro conjuntos de ícones, e a única pergunta que decide qual deles desenha uma marca.
- [Créditos](https://duxt.app/pt-PT/credits.md): Aquilo em que o duxt assenta, e aquilo de que partiu.
- [Overview](https://duxt.app/pt-PT/demo.md): Explore an invented freight API, a Bruno collection, a sample changelog and a Terraform provider reference, all in one demo area.
- [Consignments](https://duxt.app/pt-PT/demo/bruno.md): The same invented shipping API the OpenAPI reference beside this one describes, written the other way round — as a Bruno collection somebody actually ran.
- [Consignments](https://duxt.app/pt-PT/demo/bruno/consignments.md): Creating and reading consignments.
- [Create a consignment](https://duxt.app/pt-PT/demo/bruno/consignments/create-a-consignment.md): The one request in this collection that books something: this site answers every request here, and this is the one that hands back a consignment.
- [Get a consignment](https://duxt.app/pt-PT/demo/bruno/consignments/get-a-consignment.md): A Bruno path parameter, written :reference. The try-it client draws a box for it, prefilled with the value the collection committed.
- [List consignments](https://duxt.app/pt-PT/demo/bruno/consignments/list-consignments.md): A disabled parameter, which is the shape ~ makes: cursor is kept in the file and not sent, and the page shows it struck through rather than hiding a line the collection has.
- [Ping](https://duxt.app/pt-PT/demo/bruno/ping.md): The cheapest request in the collection: it proves the base URL resolves and the token is being sent.
- [Signed echo](https://duxt.app/pt-PT/demo/bruno/signed-echo.md): What redaction looks like when the value is real. Bruno mirrors a query parameter into the url line as well as into params:query, so both are held to the same rule: api_key keeps its name and loses its value in the table AND in the URL above it, and the try-it box for it opens empty rather than prefilled.
- [Tracking](https://duxt.app/pt-PT/demo/bruno/tracking.md): Where a consignment is, and what has happened to it.
- [Tracking events](https://duxt.app/pt-PT/demo/bruno/tracking/tracking-events.md): This request carries a pre-request script and a test. Neither is printed on this page and neither is run by it — the page says they exist, and the download is where they live.
- [Changelog](https://duxt.app/pt-PT/demo/changelog.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [Changelog (flat)](https://duxt.app/pt-PT/demo/changelog-flat.md): The documentation site's own log. www is private and never published, so the
numbers below mark this site's milestones rather than releases of the
@kirchdev/duxt package — release-please writes that changelog at the
repository root, and the site serves it at /releases.
- [0.1.0](https://duxt.app/pt-PT/demo/changelog/v0.1.0.md)
- [0.2.0](https://duxt.app/pt-PT/demo/changelog/v0.2.0.md)
- [0.3.0](https://duxt.app/pt-PT/demo/changelog/v0.3.0.md)
- [0.4.0](https://duxt.app/pt-PT/demo/changelog/v0.4.0.md)
- [0.4.1](https://duxt.app/pt-PT/demo/changelog/v0.4.1.md)
- [0.5.0](https://duxt.app/pt-PT/demo/changelog/v0.5.0.md)
- [Diagrams](https://duxt.app/pt-PT/demo/diagrams.md): Several diagrams, an editable source and a theme that follows the reader.
- [Images](https://duxt.app/pt-PT/demo/images.md): Every shape ProseImg has to draw — a dark twin, a narrow original, a vector, an animation and an image that refuses to zoom.
- [Harbour](https://duxt.app/pt-PT/demo/openapi.md): An invented freight API, written for this documentation site.
- [Batches](https://duxt.app/pt-PT/demo/openapi/batches.md): Operations that act on many consignments at once.
- [Run a batch](https://duxt.app/pt-PT/demo/openapi/batches/runbatch.md): Takes a list of instructions and applies them in order. This endpoint needs no authentication, which is why it takes nothing destructive.
- [Consignments](https://duxt.app/pt-PT/demo/openapi/consignments.md): Everything that is a consignment — a load of freight, with a reference on it and a berth to end up at.
- [Cancel a consignment](https://duxt.app/pt-PT/demo/openapi/consignments/cancelconsignment.md): Deprecated. Use the batch endpoint, which takes the same identifiers and reports what it could not do.
- [Book a consignment](https://duxt.app/pt-PT/demo/openapi/consignments/createconsignment.md): Books one consignment and tells you where it ended up.
- [Read a consignment](https://duxt.app/pt-PT/demo/openapi/consignments/getconsignment.md): GET /consignments/{consignmentId}
- [List consignments](https://duxt.app/pt-PT/demo/openapi/consignments/listconsignments.md): Returns a page of consignments, newest first.
- [Update a consignment](https://duxt.app/pt-PT/demo/openapi/consignments/updateconsignment.md): The one FLAT body in this document, and deliberately so: every other request body here carries an array or a map, which the try-it client cannot draw as a form. Without this endpoint the form view — and the toggle between it and the JSON editor — would never render on this site, and a view nothing renders is a view whose failures nobody sees. Four properties, one of each kind of box: text, enum, boolean, number.
- [Demo](https://duxt.app/pt-PT/demo/openapi/demo.md): The one part of this document that is real: an endpoint this very site answers, so the try-it client on the landing page sends a request and gets something back rather than failing against a host that does not exist.
- [Book a demo consignment](https://duxt.app/pt-PT/demo/openapi/demo/echoconsignment.md): Takes a consignment and hands it back with an id and a timestamp, exactly as POST /consignments would, except that this one is answered, by this site.
- [Vessels](https://duxt.app/pt-PT/demo/openapi/vessels.md): The ships consignments travel on, and what they are carrying.
- [Replace a vessel's manifest](https://duxt.app/pt-PT/demo/openapi/vessels/replacemanifest.md): The whole manifest at once — a PUT, because half a manifest is not a smaller manifest, it is a wrong one.
- [Webhooks](https://duxt.app/pt-PT/demo/openapi/webhooks.md)
- [A consignment changed](https://duxt.app/pt-PT/demo/openapi/webhooks/post-consignmentchanged.md): Sent to the address registered for your account whenever a consignment you can see changes. Answer with any 2xx.
- [A source of its own](https://duxt.app/pt-PT/demo/source.md): Why the demo API and changelog share a source beside the documentation.
- [linear Provider](https://duxt.app/pt-PT/demo/terraform.md): Manage Linear https://linear.app workspace configuration — teams, labels, workflow states, views, git automation, webhooks and workspace settings — as code. An API key is scoped to a single workspace, so managing several workspaces needs one aliased provider per workspace.
- [linear_custom_view](https://duxt.app/pt-PT/demo/terraform/data-sources/custom_view.md): Looks up a Linear custom view by UUID or name.
Reading the filter of an existing view is the quickest way to work out what to put in a linear_custom_view resource's filter_json.
- [linear_custom_views](https://duxt.app/pt-PT/demo/terraform/data-sources/custom_views.md): Lists every Linear custom view the API key can see.
- [linear_label](https://duxt.app/pt-PT/demo/terraform/data-sources/label.md): Looks up an issue label by UUID or name. Covers both workspace and team labels — which one you got is visible from whether team_id came back set.
- [linear_labels](https://duxt.app/pt-PT/demo/terraform/data-sources/labels.md): Lists issue labels, either of one team or of the whole workspace.
- [linear_organization](https://duxt.app/pt-PT/demo/terraform/data-sources/organization.md): Reads the Linear workspace the API key belongs to. Takes no arguments — the key determines the workspace.
Use it to branch a configuration on what the workspace has enabled, e.g. only declaring linear_customer_tier resources when customers_enabled is true.
- [linear_team](https://duxt.app/pt-PT/demo/terraform/data-sources/team.md): Looks up a Linear team by UUID or by team key — useful for referencing a team this configuration does not manage.
- [linear_teams](https://duxt.app/pt-PT/demo/terraform/data-sources/teams.md): Lists every Linear team in the workspace.
- [linear_template](https://duxt.app/pt-PT/demo/terraform/data-sources/template.md): Reads a Linear template by UUID.
There is no lookup by name: Linear exposes no template collection to search, only templatesForIntegration, which is scoped to an integration rather than the workspace.
- [linear_user](https://duxt.app/pt-PT/demo/terraform/data-sources/user.md): Looks up a Linear user by UUID or email — the usual way to resolve the user_id a linear_team_membership or linear_triage_responsibility needs.
- [linear_users](https://duxt.app/pt-PT/demo/terraform/data-sources/users.md): Lists the users of the Linear workspace.
- [linear_workflow_state](https://duxt.app/pt-PT/demo/terraform/data-sources/workflow_state.md): Looks up a workflow state of a Linear team, by UUID or by team and name.
Useful for pointing a linear_git_automation_state at a state this configuration does not manage.
- [linear_workflow_states](https://duxt.app/pt-PT/demo/terraform/data-sources/workflow_states.md): Lists workflow states, either of one team or of the whole workspace.
- [linear_agent_skill](https://duxt.app/pt-PT/demo/terraform/resources/agent_skill.md): Manages a Linear agent skill — a named instruction agents can be asked to follow.
Scope it to a team via team_id, or leave that unset to make it available across the workspace.
- [linear_custom_view](https://duxt.app/pt-PT/demo/terraform/resources/custom_view.md): Manages a Linear custom view — a saved, filtered list of issues, projects, initiatives or feed items.
The filter goes through as a JSON object rather than typed HCL. Linear's IssueFilter alone has 122 top-level fields and nests arbitrarily, and the server normalises what it stores, so a typed schema would freeze against a moving API and a plain string would report drift on every plan. The *_json attributes are compared semantically instead.
Set exactly one of filter_json, project_filter_json, initiative_filter_json or feed_item_filter_json — which one decides what the view lists.

resource "linear_custom_view" "in_review" {
  name    = "In Review"
  team_id = linear_team.eng.id
  shared  = true

  filter_json = jsonencode({
    state  = { type = { eq = "started" } }
    labels = { some = { name = { eq = "ai" } } }
  })
}
- [linear_customer_status](https://duxt.app/pt-PT/demo/terraform/resources/customer_status.md): Manages a customer status in Linear — one stage of the workspace's customer lifecycle.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Statuses are workspace-wide, not per team.
- [linear_customer_tier](https://duxt.app/pt-PT/demo/terraform/resources/customer_tier.md): Manages a customer tier in Linear — the band a customer is segmented into, which customer requests are weighed by.
Requires Linear Customers to be enabled for the workspace; see customers_enabled on linear_workspace_settings. Tiers are workspace-wide, not per team.
- [linear_email_intake_address](https://duxt.app/pt-PT/demo/terraform/resources/email_intake_address.md): Manages a Linear email intake address — the mailbox inbound mail becomes issues through, together with the auto-replies sent back.
The address itself is generated by Linear rather than chosen, so address is read-only.
- [linear_emoji](https://duxt.app/pt-PT/demo/terraform/resources/emoji.md): Manages a custom emoji in the Linear workspace.
Linear has no update mutation for emoji, so changing either attribute replaces the resource.
- [linear_git_automation_state](https://duxt.app/pt-PT/demo/terraform/resources/git_automation_state.md): Manages one git automation rule of a Linear team: when the given git event fires, linked issues move to the given workflow state.
Each Linear GitAutomationState covers exactly one event, so five events means five resources. Combined with linear_git_automation_target_branch this also expresses per-branch overrides — a rule with target_branch_id set applies only to pull requests targeting that branch pattern and overrides the team's default rule for the same event.
- [linear_git_automation_target_branch](https://duxt.app/pt-PT/demo/terraform/resources/git_automation_target_branch.md): Manages a target branch pattern for a Linear team's git automation. Reference it from linear_git_automation_state.target_branch_id to scope automation rules to pull requests against branches matching this pattern.
- [linear_initiative_label](https://duxt.app/pt-PT/demo/terraform/resources/initiative_label.md): Manages a initiative label in Linear. initiative labels are their own entity with their own mutations — they are not issue labels applied to initiatives.
- [linear_integrations_settings](https://duxt.app/pt-PT/demo/terraform/resources/integrations_settings.md): Manages which events a Linear integration posts — the notification matrix behind an already-connected Slack or Microsoft Teams integration.
Connecting the integration itself is an OAuth flow and not something a provider can manage declaratively; this resource configures what an existing connection does. Attach it to exactly one of a team, project, initiative or custom view — all four are fixed at creation, since Linear's update mutation takes only the toggles.
- [linear_project_label](https://duxt.app/pt-PT/demo/terraform/resources/project_label.md): Manages a project label in Linear. project labels are their own entity with their own mutations — they are not issue labels applied to projects.
- [linear_project_status](https://duxt.app/pt-PT/demo/terraform/resources/project_status.md): Manages a project status in Linear — where a project stands, workspace-wide.
Destroying the resource archives the status; Linear has no hard delete for project statuses.
- [linear_release_pipeline](https://duxt.app/pt-PT/demo/terraform/resources/release_pipeline.md): Manages a Linear release pipeline — how a set of teams ships, and which paths in the repository count towards a release.
Destroying the resource archives the pipeline.
- [linear_release_stage](https://duxt.app/pt-PT/demo/terraform/resources/release_stage.md): Manages a stage of a Linear release pipeline — one step a release passes through.
Destroying the resource archives the stage.
- [linear_team](https://duxt.app/pt-PT/demo/terraform/resources/team.md): Manages a Linear team — the container for issues, cycles, workflow states and templates.
Cycle configuration lives here rather than in a resource of its own: Linear generates cycles itself once cycles_enabled is set, so a cycle resource would fight the generator.
- [linear_team_label](https://duxt.app/pt-PT/demo/terraform/resources/team_label.md): Manages an issue label scoped to a single Linear team.
For a label available to every team, use linear_workspace_label. The scope is fixed at creation — Linear has no mutation that moves a label between team and workspace scope.
- [linear_team_membership](https://duxt.app/pt-PT/demo/terraform/resources/team_membership.md): Manages the membership of a user in a Linear team, including whether they own it.
Destroying the resource removes the user from the team; it does not deactivate the user.
- [linear_template](https://duxt.app/pt-PT/demo/terraform/resources/template.md): Manages a Linear template — the pre-filled shape new issues, projects or documents start from.
The template body is deeply nested and its schema follows the entity it templates, so it goes through as raw JSON in template_json rather than typed HCL.
- [linear_time_schedule](https://duxt.app/pt-PT/demo/terraform/resources/time_schedule.md): Manages a Linear time schedule — the on-call rota a linear_triage_responsibility rotates through.
Entries are absolute time windows, not a recurrence rule: Linear stores who is on call between two instants. A rota that repeats has to be generated, which is what the external schedule integrations do — point external_id and external_url at one to keep the provenance visible.
- [linear_triage_responsibility](https://duxt.app/pt-PT/demo/terraform/resources/triage_responsibility.md): Manages who is responsible for a Linear team's triage inbox.
Drive it either from a rota — set time_schedule_id to a linear_time_schedule — or from a fixed list of people via manual_user_ids. The team needs triage_enabled for this to have any effect.
- [linear_view_preferences](https://duxt.app/pt-PT/demo/terraform/resources/view_preferences.md): Manages the workspace-wide display preferences of a Linear custom view — its layout, grouping, ordering and which columns are shown.
The preferences object has over 250 fields whose set follows what Linear's UI offers, so it goes through as JSON rather than typed HCL. Only the keys the configuration sets are read back, so drift is reported for the preferences under management and no others.

resource "linear_view_preferences" "in_review" {
  custom_view_id = linear_custom_view.in_review.id
  view_type      = "customView"

  preferences_json = jsonencode({
    layout       = "board"
    issueGrouping = "assignee"
    viewOrdering = "priority"
  })
}
- [linear_webhook](https://duxt.app/pt-PT/demo/terraform/resources/webhook.md): Manages a Linear webhook — the outbound HTTP callback Linear fires when the subscribed resources change.
Scope it either to one team via team_id or to every public team via all_public_teams; both are fixed at creation, since Linear's webhookUpdate takes neither.
- [linear_workflow_state](https://duxt.app/pt-PT/demo/terraform/resources/workflow_state.md): Manages a workflow state (issue status) of a Linear team.
Destroying the resource archives the state — Linear has no hard delete for workflow states. A state that still holds issues cannot be archived until they are moved.
- [linear_workspace_label](https://duxt.app/pt-PT/demo/terraform/resources/workspace_label.md): Manages a workspace-wide issue label in Linear — available to every team.
For a label scoped to a single team, use linear_team_label. The scope is fixed at creation — Linear has no mutation that moves a label between workspace and team scope.
- [linear_workspace_settings](https://duxt.app/pt-PT/demo/terraform/resources/workspace_settings.md): Manages the settings of the Linear workspace the API key belongs to.
This is a singleton and manage-not-create: applying it adopts the existing workspace rather than creating one, and destroying the resource only drops it from state — no workspace is deleted and no setting is reset. Declare it at most once per provider instance.
Every attribute is optional and computed: whatever the configuration leaves out keeps its live value. With this many settings on one resource, the alternative would be an apply that silently resets an entire workspace.
Member invitation, team-creation and label-management restrictions moved into security_settings_json on Linear's side; they are exposed there and nowhere else, so there is exactly one way in.
- [The four versions](https://duxt.app/pt-PT/demo/versions.md): One artefact at four versions, and the four things a reader can be told about the one they are in.
- [Introdução](https://duxt.app/pt-PT/getting-started.md): O que é o duxt, e o que chega com uma única linha de configuração.
- [Configuração](https://duxt.app/pt-PT/getting-started/configuration.md): Um ficheiro configura o site inteiro — o que lhe pertence e como é combinado.
- [Começar com o starter](https://duxt.app/pt-PT/getting-started/from-starter.md): Cria com o Nuxi um site de documentação duxt pronto a executar.
- [Instalação](https://duxt.app/pt-PT/getting-started/installation.md): Adicione a camada, estenda-a, escreva Markdown.
- [Guias](https://duxt.app/pt-PT/guides.md): Uma tarefa por página, do início ao fim — vários repositórios, várias versões, vários idiomas e uma implementação.
- [Dá identidade ao teu site](https://duxt.app/pt-PT/guides/brand-your-site.md): Define o nome, o logótipo e os ícones, para que o site se leia como teu e não como o da camada.
- [Guardar fontes remotas e imagens OG em cache](https://duxt.app/pt-PT/guides/cache-build-work.md): Reutilizar downloads de repositórios públicos e cartões sociais renderizados entre builds de CI.
- [Recolher opiniões da página](https://duxt.app/pt-PT/guides/collect-page-feedback.md): Envolve o DuxtPageFeedback e guarda a resposta onde a tua analítica já vive.
- [Implementar um site](https://duxt.app/pt-PT/guides/deploy-a-site.md): Onde um site duxt pode correr, do que precisa lá, e porque o conteúdo não é atualizado em execução.
- [Mover uma página](https://duxt.app/pt-PT/guides/move-a-page.md): redirectFrom no frontmatter, transformado em regras de rota sob todos os prefixos.
- [Substituir o tema](https://duxt.app/pt-PT/guides/override-the-theme.md): Mudar uma cor, substituir um componente, acrescentar uma primitiva shadcn-vue.
- [Publicar documentação de um provider Terraform](https://duxt.app/pt-PT/guides/publish-terraform-provider-docs.md): Transformar uma árvore Markdown do tfplugindocs numa referência versionada com navegação própria do provider.
- [Enviar eventos de analítica](https://duxt.app/pt-PT/guides/send-analytics-events.md): Um callback, cinco eventos, nenhum fornecedor — liga as interações dos leitores do duxt à analítica que já tens a correr.
- [Vários idiomas](https://duxt.app/pt-PT/guides/several-languages.md): Servir a interface em vários idiomas, e traduzir também as páginas.
- [Vários repositórios](https://duxt.app/pt-PT/guides/several-repositories.md): Servir a documentação de vários projetos a partir de um só site.
- [Várias versões](https://duxt.app/pt-PT/guides/several-versions.md): Servir a mesma documentação em várias refs, com seletor e aviso.
- [Referência](https://duxt.app/pt-PT/reference.md): A superfície pública da camada — chaves de configuração, frontmatter, componentes, composables e endpoints.
- [Coleções Bruno](https://duxt.app/pt-PT/reference/bruno.md): Uma coleção Bruno publicada como referência centrada em pedidos, com um arquivo descarregável.
- [Obter a coleção](https://duxt.app/pt-PT/reference/bruno/getting-the-collection.md): O arquivo está ligado à versão e idioma visíveis; a ligação Bruno não.
- [Declarar a secção](https://duxt.app/pt-PT/reference/bruno/section.md): Onde vive uma coleção Bruno, que páginas produz e que opções aceita.
- [O cliente de pedidos](https://duxt.app/pt-PT/reference/bruno/try-it.md): Desligado por omissão e dirigido apenas a destinos declarados públicos.
- [O que é publicado](https://duxt.app/pt-PT/reference/bruno/what-is-published.md): Environments, credenciais, scripts e testes nunca chegam a uma página.
- [Registo de alterações](https://duxt.app/pt-PT/reference/changelog.md): Um registo de versões, publicado como páginas — uma cronologia, uma página por versão, e um feed.
- [Esquema e componentes](https://duxt.app/pt-PT/reference/changelog/components.md): O esquema em que um histórico dividido renderiza, e os dois componentes MDC de que as suas páginas são feitas.
- [Granularidade](https://duxt.app/pt-PT/reference/changelog/granularity.md): Uma página por versão, ou o ficheiro como a única página que foi escrito.
- [Declarar a secção](https://duxt.app/pt-PT/reference/changelog/section.md): O tipo de secção `changelog` — onde vive o ficheiro, e as duas políticas que responde.
- [O que é lido](https://duxt.app/pt-PT/reference/changelog/what-is-read.md): Que títulos passam a versões, quais a grupos, e o que acontece ao resto.
- [Componentes](https://duxt.app/pt-PT/reference/components.md): Os componentes da própria camada, uma página cada — para que serve cada um e o que recebe.
- [Controlos](https://duxt.app/pt-PT/reference/components/controls.md): O que o leitor opera — a pesquisa, os seletores, a folha de atalhos e dois indicadores.
- [DuxtLocale](https://duxt.app/pt-PT/reference/components/controls/duxt-locale.md): O seletor de idioma.
- [DuxtProgress](https://duxt.app/pt-PT/reference/components/controls/duxt-progress.md): Até onde o leitor já desceu na página.
- [DuxtSearch](https://duxt.app/pt-PT/reference/components/controls/duxt-search.md): Pesquisa cada fonte ativa e intercala os seus resultados ordenados localmente.
- [DuxtShortcuts](https://duxt.app/pt-PT/reference/components/controls/duxt-shortcuts.md): A folha de atalhos de teclado, na tecla ?.
- [DuxtShortcutsTrigger](https://duxt.app/pt-PT/reference/components/controls/duxt-shortcuts-trigger.md): O botão que abre a folha de atalhos.
- [DuxtSkipLink](https://duxt.app/pt-PT/reference/components/controls/duxt-skip-link.md): O primeiro elemento focável da página.
- [DuxtVersion](https://duxt.app/pt-PT/reference/components/controls/duxt-version.md): O distintivo de versão, e o seletor quando há mais do que uma.
- [DuxtVersionBanner](https://duxt.app/pt-PT/reference/components/controls/duxt-version-banner.md): A barra que diz ao leitor que esta versão não é a atual.
- [Layout](https://duxt.app/pt-PT/reference/components/layout.md): Os dois componentes que emolduram uma página — a barra de navegação e o rodapé.
- [DuxtAnnouncements](https://duxt.app/pt-PT/reference/components/layout/duxt-announcements.md): Avisos do próprio site, desenhados por posição apenas quando existe algo a anunciar.
- [DuxtFooter](https://duxt.app/pt-PT/reference/components/layout/duxt-footer.md): O rodapé: o nome do site, as suas ligações legais e a linha da própria camada.
- [DuxtHeader](https://duxt.app/pt-PT/reference/components/layout/duxt-header.md): A barra de navegação: título, navegação, pesquisa e as ligações de ícone.
- [Navegação](https://duxt.app/pt-PT/reference/components/navigation.md): Circular pela documentação — a linha de secções, a barra lateral, o trilho, o índice e anterior/seguinte.
- [DuxtBreadcrumb](https://duxt.app/pt-PT/reference/components/navigation/duxt-breadcrumb.md): O trilho por cima do título da página.
- [DuxtNavigation](https://duxt.app/pt-PT/reference/components/navigation/duxt-navigation.md): A árvore da barra lateral.
- [DuxtNavigationLink](https://duxt.app/pt-PT/reference/components/navigation/duxt-navigation-link.md): Uma entrada da barra lateral.
- [DuxtPageNav](https://duxt.app/pt-PT/reference/components/navigation/duxt-page-nav.md): Anterior e seguinte, limitados pela secção.
- [DuxtSections](https://duxt.app/pt-PT/reference/components/navigation/duxt-sections.md): A segunda linha da barra de navegação — as partes de topo da documentação.
- [DuxtToc](https://duxt.app/pt-PT/reference/components/navigation/duxt-toc.md): O índice, e o aside por baixo dele.
- [Página](https://duxt.app/pt-PT/reference/components/page.md): Os componentes que pertencem à própria página.
- [DuxtCodeBlock](https://duxt.app/pt-PT/reference/components/page/duxt-code-block.md): O cartão à volta de um bloco de código.
- [DuxtCopyPage](https://duxt.app/pt-PT/reference/components/page/duxt-copy-page.md): Entrega esta página a um modelo, ou lê o seu código-fonte.
- [DuxtPageFeedback](https://duxt.app/pt-PT/reference/components/page/duxt-page-feedback.md): «Esta página foi útil?» — um evento, e sem backend.
- [DuxtPageInfo](https://duxt.app/pt-PT/reference/components/page/duxt-page-info.md): De onde veio a página: ligação de edição, última atualização, contribuidores.
- [Composables](https://duxt.app/pt-PT/reference/composables.md): As funções que a camada expõe aos teus próprios componentes, uma página cada.
- [Configuração e conteúdo](https://duxt.app/pt-PT/reference/composables/config-and-content.md): A configuração fundida, e que coleção serve a página que está a ser lida.
- [useDuxtBreadcrumb()](https://duxt.app/pt-PT/reference/composables/config-and-content/use-duxt-breadcrumb.md): O trilho da secção até uma página.
- [useDuxtCollection()](https://duxt.app/pt-PT/reference/composables/config-and-content/use-duxt-collection.md): Que coleção serve esta rota.
- [useDuxtConfig()](https://duxt.app/pt-PT/reference/composables/config-and-content/use-duxt-config.md): A configuração fundida, com todos os campos de texto já resolvidos.
- [useDuxtNavigation()](https://duxt.app/pt-PT/reference/composables/config-and-content/use-duxt-navigation.md): A árvore de navegação da coleção que serve esta rota.
- [useDuxtSection()](https://duxt.app/pt-PT/reference/composables/config-and-content/use-duxt-section.md): A parte da documentação em que esta página está.
- [Caminhos e versões](https://duxt.app/pt-PT/reference/composables/paths-and-versions.md): Ler um URL, escrever outro de volta, e saber que versão está a ser lida.
- [useDuxtLink()](https://duxt.app/pt-PT/reference/composables/paths-and-versions/use-duxt-link.md): Um caminho de documentação, reescrito como ligação.
- [useDuxtPath()](https://duxt.app/pt-PT/reference/composables/paths-and-versions/use-duxt-path.md): O caminho em que a documentação está, com o locale retirado.
- [useDuxtSiteUrl()](https://duxt.app/pt-PT/reference/composables/paths-and-versions/use-duxt-site-url.md): A origem configurada, e caminhos tornados absolutos.
- [useDuxtVersion()](https://duxt.app/pt-PT/reference/composables/paths-and-versions/use-duxt-version.md): O que o seletor mostra, o que o aviso diz, se se deve indexar.
- [Experiência de leitura](https://duxt.app/pt-PT/reference/composables/reading.md): Pesquisa, cabeçalhos, foco, histórico e as escolhas que um leitor faz.
- [useActiveHeading()](https://duxt.app/pt-PT/reference/composables/reading/use-active-heading.md): O cabeçalho que está à vista neste momento.
- [useDuxtAnalytics()](https://duxt.app/pt-PT/reference/composables/reading/use-duxt-analytics.md): Comunicar uma interação do leitor ao callback do próprio site, ou a ninguém.
- [useDuxtPageFocus()](https://duxt.app/pt-PT/reference/composables/reading/use-duxt-page-focus.md): Move o foco para o cabeçalho depois de uma navegação do lado do cliente.
- [useDuxtSearch()](https://duxt.app/pt-PT/reference/composables/reading/use-duxt-search.md): Pesquisa cada fonte ativa e intercala os seus resultados ordenados localmente.
- [useDuxtShortcuts()](https://duxt.app/pt-PT/reference/composables/reading/use-duxt-shortcuts.md): As teclas que o tema escuta.
- [useDuxtToast()](https://duxt.app/pt-PT/reference/composables/reading/use-duxt-toast.md): Notificações, embrulhadas para que nenhum componente importe a biblioteca.
- [useFuzzySearch()](https://duxt.app/pt-PT/reference/composables/reading/use-fuzzy-search.md): Tolerância a gralhas ao lado do índice exato.
- [usePackageManager()](https://duxt.app/pt-PT/reference/composables/reading/use-package-manager.md): O gestor de pacotes que um leitor escolheu.
- [useRecentPages()](https://duxt.app/pt-PT/reference/composables/reading/use-recent-pages.md): As páginas abertas mais recentemente, até ao limite configurado.
- [Configuração](https://duxt.app/pt-PT/reference/configuration.md): Cada chave sob duxt em app.config.ts — o que controla e quando é lida.
- [Devtools](https://duxt.app/pt-PT/reference/devtools.md): Dez painéis que mostram no que as tuas fontes se tornaram. Apenas em desenvolvimento.
- [Cache](https://duxt.app/pt-PT/reference/devtools/cache.md): A cache de descargas do Content, e uma forma de deitar fora uma entrada.
- [Checks](https://duxt.app/pt-PT/reference/devtools/checks.md): O validador da compilação, aplicado ao que o site está a servir agora.
- [Config](https://duxt.app/pt-PT/reference/devtools/config.md): A configuração `duxt` fundida, e de que lado da fusão vem cada valor.
- [i18n](https://duxt.app/pt-PT/reference/devtools/i18n.md): Chaves de mensagem por idioma, contra o idioma base.
- [Pages](https://duxt.app/pt-PT/reference/devtools/pages.md): Todas as páginas de todas as coleções, com o frontmatter e os metadados de git.
- [Paths](https://duxt.app/pt-PT/reference/devtools/paths.md): Cola um URL e vê que fonte o reclama e o que encontra lá.
- [Redirects](https://duxt.app/pt-PT/reference/devtools/redirects.md): Todos os redireccionamentos que o servidor serve, e quais deles a camada escreveu.
- [Search](https://duxt.app/pt-PT/reference/devtools/search.md): O que o índice de pesquisa contém, pela mesma consulta que a caixa de diálogo faz.
- [Sources](https://duxt.app/pt-PT/reference/devtools/sources.md): No que `duxt.sources` se tornou — uma coleção por fonte, versão e idioma.
- [Versions](https://duxt.app/pt-PT/reference/devtools/versions.md): Que versão — e que idioma — leva que página.
- [Endpoints](https://duxt.app/pt-PT/reference/endpoints.md): Tudo o que o site serve além das páginas, uma página cada.
- [/_duxt/devtools](https://duxt.app/pt-PT/reference/endpoints/devtools.md): A rota a partir da qual o painel das Nuxt Devtools é servido. Apenas em desenvolvimento.
- [/llms-full.txt](https://duxt.app/pt-PT/reference/endpoints/llms-full-txt.md): Uma extensão do duxt com as mesmas páginas num ficheiro Markdown.
- [/llms.txt](https://duxt.app/pt-PT/reference/endpoints/llms-txt.md): A documentação como índice Markdown, segundo llmstxt.org.
- [/mcp](https://duxt.app/pt-PT/reference/endpoints/mcp.md): Um servidor MCP sobre o mesmo conteúdo.
- [<page>.md](https://duxt.app/pt-PT/reference/endpoints/page-markdown.md): O código-fonte de qualquer página, no seu próprio URL mais .md.
- [/rss.xml](https://duxt.app/pt-PT/reference/endpoints/rss-xml.md): O feed, assim que uma secção for nomeada.
- [/sitemap.xml e /robots.txt](https://duxt.app/pt-PT/reference/endpoints/sitemap-and-robots.md): Para onde um rastreador é apontado, e aquilo de que é mantido fora.
- [Frontmatter](https://duxt.app/pt-PT/reference/frontmatter.md): Os campos que uma página pode ter além do título e da descrição, e os dois que a compilação preenche.
- [Hooks](https://duxt.app/pt-PT/reference/hooks.md): O único hook de build que o duxt emite, o que ele entrega e por que existe apenas um.
- [Componentes MDC](https://duxt.app/pt-PT/reference/mdc-components.md): Os blocos que uma página Markdown pode invocar, uma página cada, com as suas props.
- [Accordion](https://duxt.app/pt-PT/reference/mdc-components/accordion.md): Secções recolhíveis — um FAQ, ou respostas que o leitor escolhe.
- [Item de accordion](https://duxt.app/pt-PT/reference/mdc-components/accordion-item.md): Uma secção recolhível.
- [Callout](https://duxt.app/pt-PT/reference/mdc-components/callout.md): Um aparte em que o leitor deve parar — uma dica, um aviso, um perigo.
- [Grupo de código](https://duxt.app/pt-PT/reference/mdc-components/code-group.md): Vários blocos de código como um só bloco com separadores, rotulados pelo nome do ficheiro.
- [Campo](https://duxt.app/pt-PT/reference/mdc-components/field.md): Um parâmetro, propriedade ou opção, com o seu tipo e valor por omissão.
- [Grupo de campos](https://duxt.app/pt-PT/reference/mdc-components/field-group.md): Uma lista de campos como um só bloco.
- [Árvore de ficheiros](https://duxt.app/pt-PT/reference/mdc-components/file-tree.md): Uma estrutura de pastas, com ícones por tipo de ficheiro.
- [Mermaid](https://duxt.app/pt-PT/reference/mdc-components/mermaid.md): Um diagrama a partir de um bloco de código ou de uma prop.
- [Gestores de pacotes](https://duxt.app/pt-PT/reference/mdc-components/package-managers.md): Um comando, um separador por gestor de pacotes, memorizado de página em página.
- [Cartões de página](https://duxt.app/pt-PT/reference/mdc-components/page-cards.md): Os filhos de uma secção, como cartões.
- [Partial](https://duxt.app/pt-PT/reference/mdc-components/partial.md): Um bloco escrito uma vez e apresentado em todas as fontes que dele precisam.
- [Pré-visualização](https://duxt.app/pt-PT/reference/mdc-components/preview.md): Um componente desenhado tal como a página o desenha, com o seu código-fonte ao lado.
- [Substituições de prosa](https://duxt.app/pt-PT/reference/mdc-components/prose.md): O que a camada muda no Markdown simples — ligações, cabeçalhos, imagens, código e tabelas.
- [ProseA](https://duxt.app/pt-PT/reference/mdc-components/prose/prose-a.md): Uma ligação, resolvida em função da fonte em que foi escrita.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/pt-PT/reference/mdc-components/prose/prose-headings.md): Cabeçalhos, cada um com a sua âncora permanente.
- [ProseImg](https://duxt.app/pt-PT/reference/mdc-components/prose/prose-img.md): Uma imagem: consciente do tema, adaptável e ampliável.
- [ProsePre](https://duxt.app/pt-PT/reference/mdc-components/prose/prose-pre.md): O bloco de código: nome do ficheiro, ícone da linguagem, botão de copiar.
- [ProseTable](https://duxt.app/pt-PT/reference/mdc-components/prose/prose-table.md): Uma tabela que se desloca em vez da página.
- [Since](https://duxt.app/pt-PT/reference/mdc-components/since.md): A versão em que algo apareceu, ao lado de um cabeçalho.
- [Passos](https://duxt.app/pt-PT/reference/mdc-components/steps.md): Uma lista ordenada desenhada como passos numerados sobre uma calha.
- [Tab](https://duxt.app/pt-PT/reference/mdc-components/tab.md): Um painel de um grupo de separadores.
- [Grupo de separadores](https://duxt.app/pt-PT/reference/mdc-components/tab-group.md): Separadores para tudo o que não seja código.
- [Referência da API](https://duxt.app/pt-PT/reference/openapi.md): Um documento OpenAPI, publicado como páginas de referência com um cliente que envia pedidos reais.
- [Componentes](https://duxt.app/pt-PT/reference/openapi/components.md): Os três componentes MDC de que é feita uma página de referência gerada.
- [Amostras de pedido](https://duxt.app/pt-PT/reference/openapi/request-samples.md): O mesmo pedido em doze clientes, e como acrescentar o teu.
- [Declarar a secção](https://duxt.app/pt-PT/reference/openapi/section.md): O tipo de secção `openapi` — onde vive o documento, e no que se torna.
- [O cliente de ensaio](https://duxt.app/pt-PT/reference/openapi/try-it.md): Um pedido real, enviado pelo próprio navegador do leitor.
- [Fontes](https://duxt.app/pt-PT/reference/sources.md): Os campos de uma entrada de fonte, as suas refs, e as opções que moldam os URL.
- [Releases](https://duxt.app/pt-PT/releases.md)
- [0.1.0](https://duxt.app/pt-PT/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/pt-PT/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/pt-PT/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/pt-PT/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/pt-PT/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/pt-PT/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/pt-PT/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/pt-PT/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/pt-PT/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/pt-PT/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/pt-PT/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/pt-PT/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/pt-PT/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/pt-PT/releases/v0.9.0.md)
- [Reference](https://duxt.app/reference.md): The layer's public surface — config keys, frontmatter, components, composables and endpoints.
- [Bruno collections](https://duxt.app/reference/bruno.md): A Bruno collection, published as request-centred reference pages with a downloadable archive.
- [Getting the collection](https://duxt.app/reference/bruno/getting-the-collection.md): The archive is pinned to the page you are on; the Bruno deep link is not.
- [Declaring the section](https://duxt.app/reference/bruno/section.md): The `bruno` section type — where the collection lives, and what it becomes.
- [The request client](https://duxt.app/reference/bruno/try-it.md): Off until a site turns it on, and pointed only at what the site declared public.
- [What is published](https://duxt.app/reference/bruno/what-is-published.md): Environments, credentials, scripts and tests never reach a page — and what that means for the archive.
- [Changelog](https://duxt.app/reference/changelog.md): A release log, published as pages — a timeline, a page per release, and a feed.
- [Layout and components](https://duxt.app/reference/changelog/components.md): The layout a split history renders in, and the two MDC components its pages are made of.
- [Granularity](https://duxt.app/reference/changelog/granularity.md): A page per release, or the file as the one page it was written as.
- [Declaring the section](https://duxt.app/reference/changelog/section.md): The `changelog` section type — where the file lives, and the two policies it answers.
- [What is read](https://duxt.app/reference/changelog/what-is-read.md): Which headings become releases, which become groups, and what happens to the rest.
- [Components](https://duxt.app/reference/components.md): The layer's own components, one page each — what each is for, and what it takes.
- [Controls](https://duxt.app/reference/components/controls.md): What a reader operates — search, the switchers, the shortcut sheet, and two indicators.
- [DuxtLocale](https://duxt.app/reference/components/controls/duxt-locale.md): The language switcher.
- [DuxtProgress](https://duxt.app/reference/components/controls/duxt-progress.md): How far down the page the reader is.
- [DuxtSearch](https://duxt.app/reference/components/controls/duxt-search.md): Search every active source and interleave its locally ranked results.
- [DuxtShortcuts](https://duxt.app/reference/components/controls/duxt-shortcuts.md): The keyboard shortcut sheet, on ?.
- [DuxtShortcutsTrigger](https://duxt.app/reference/components/controls/duxt-shortcuts-trigger.md): The button that opens the shortcut sheet.
- [DuxtSkipLink](https://duxt.app/reference/components/controls/duxt-skip-link.md): The first focusable element on the page.
- [DuxtVersion](https://duxt.app/reference/components/controls/duxt-version.md): The version badge, and the switcher when there is more than one.
- [DuxtVersionBanner](https://duxt.app/reference/components/controls/duxt-version-banner.md): The bar telling a reader this version is not the current one.
- [Layout](https://duxt.app/reference/components/layout.md): The three components that frame a page — the navbar, the footer and the site notices.
- [DuxtAnnouncements](https://duxt.app/reference/components/layout/duxt-announcements.md): The site's own notices: one strip per placement, drawn only when there is something to say.
- [DuxtFooter](https://duxt.app/reference/components/layout/duxt-footer.md): The footer: the site's name, its legal links, and the layer's own line.
- [DuxtHeader](https://duxt.app/reference/components/layout/duxt-header.md): The navbar: title, navigation, search, and the icon links.
- [Navigation](https://duxt.app/reference/components/navigation.md): Getting around — the section row, the sidebar, the trail, the contents and prev/next.
- [DuxtBreadcrumb](https://duxt.app/reference/components/navigation/duxt-breadcrumb.md): The trail above the page title.
- [DuxtNavigation](https://duxt.app/reference/components/navigation/duxt-navigation.md): The sidebar tree.
- [DuxtNavigationLink](https://duxt.app/reference/components/navigation/duxt-navigation-link.md): One entry of the sidebar.
- [DuxtPageNav](https://duxt.app/reference/components/navigation/duxt-page-nav.md): Previous and next, bounded by the section.
- [DuxtSections](https://duxt.app/reference/components/navigation/duxt-sections.md): The second navbar row — the top-level parts of the documentation.
- [DuxtToc](https://duxt.app/reference/components/navigation/duxt-toc.md): The table of contents, and the aside under it.
- [Page](https://duxt.app/reference/components/page.md): The components that belong to the page itself.
- [DuxtCodeBlock](https://duxt.app/reference/components/page/duxt-code-block.md): The card around a code block.
- [DuxtCopyPage](https://duxt.app/reference/components/page/duxt-copy-page.md): Hand this page to a model, or read its source.
- [DuxtPageFeedback](https://duxt.app/reference/components/page/duxt-page-feedback.md): Was this page helpful?
- [DuxtPageInfo](https://duxt.app/reference/components/page/duxt-page-info.md): Where the page came from: edit link, last updated, contributors.
- [Composables](https://duxt.app/reference/composables.md): The functions the layer exposes to your own components, one page each.
- [Config and content](https://duxt.app/reference/composables/config-and-content.md): The merged config, and which collection serves the page being read.
- [useDuxtBreadcrumb()](https://duxt.app/reference/composables/config-and-content/use-duxt-breadcrumb.md): The trail from the section down to a page.
- [useDuxtCollection()](https://duxt.app/reference/composables/config-and-content/use-duxt-collection.md): Which collection serves this route.
- [useDuxtConfig()](https://duxt.app/reference/composables/config-and-content/use-duxt-config.md): The merged config, every text field already resolved.
- [useDuxtNavigation()](https://duxt.app/reference/composables/config-and-content/use-duxt-navigation.md): The navigation tree for the collection serving this route.
- [useDuxtSection()](https://duxt.app/reference/composables/config-and-content/use-duxt-section.md): The part of the documentation this page is in.
- [Paths and versions](https://duxt.app/reference/composables/paths-and-versions.md): Reading a URL, writing one back out, and knowing which version is being read.
- [useDuxtLink()](https://duxt.app/reference/composables/paths-and-versions/use-duxt-link.md): A documentation path, written back out as a link.
- [useDuxtPath()](https://duxt.app/reference/composables/paths-and-versions/use-duxt-path.md): The path the documentation is at, locale stripped.
- [useDuxtSiteUrl()](https://duxt.app/reference/composables/paths-and-versions/use-duxt-site-url.md): The configured origin, and paths made absolute.
- [useDuxtVersion()](https://duxt.app/reference/composables/paths-and-versions/use-duxt-version.md): What the switcher shows, what the banner says, whether to index.
- [Reading experience](https://duxt.app/reference/composables/reading.md): Search, headings, focus, history, and the choices a reader makes.
- [useActiveHeading()](https://duxt.app/reference/composables/reading/use-active-heading.md): The heading currently in view.
- [useDuxtAnalytics()](https://duxt.app/reference/composables/reading/use-duxt-analytics.md): Report one reader interaction to the site's own callback, or to nobody.
- [useDuxtPageFocus()](https://duxt.app/reference/composables/reading/use-duxt-page-focus.md): Moves focus to the heading after a client-side navigation.
- [useDuxtSearch()](https://duxt.app/reference/composables/reading/use-duxt-search.md): Search every active source and interleave its locally ranked results.
- [useDuxtShortcuts()](https://duxt.app/reference/composables/reading/use-duxt-shortcuts.md): The keys the theme listens to.
- [useDuxtToast()](https://duxt.app/reference/composables/reading/use-duxt-toast.md): Notifications, wrapped so no component imports the library.
- [useFuzzySearch()](https://duxt.app/reference/composables/reading/use-fuzzy-search.md): Typo tolerance beside the exact index.
- [usePackageManager()](https://duxt.app/reference/composables/reading/use-package-manager.md): The package manager a reader picked.
- [useRecentPages()](https://duxt.app/reference/composables/reading/use-recent-pages.md): The most recent pages this reader opened, up to the configured limit.
- [Configuration](https://duxt.app/reference/configuration.md): Every key under duxt in app.config.ts — what it controls, and when it is read.
- [Devtools](https://duxt.app/reference/devtools.md): Ten panels that show what your sources became. Dev only.
- [Cache](https://duxt.app/reference/devtools/cache.md): Content's download cache, and a way to drop one entry.
- [Checks](https://duxt.app/reference/devtools/checks.md): The build validator, run against what the site is serving now.
- [Config](https://duxt.app/reference/devtools/config.md): The merged `duxt` config, and which side of the merge each value came from.
- [i18n](https://duxt.app/reference/devtools/i18n.md): Message keys per locale, against the base language.
- [Pages](https://duxt.app/reference/devtools/pages.md): Every page of every collection, with its frontmatter and git metadata.
- [Paths](https://duxt.app/reference/devtools/paths.md): Paste a URL, see which source claims it and what it finds there.
- [Redirects](https://duxt.app/reference/devtools/redirects.md): Every redirect the server ships, and which of them the layer wrote.
- [Search](https://duxt.app/reference/devtools/search.md): What the search index holds, through the same query the dialog runs.
- [Sources](https://duxt.app/reference/devtools/sources.md): What `duxt.sources` became — one collection per source, version and language.
- [Versions](https://duxt.app/reference/devtools/versions.md): Which version — and which language — carries which page.
- [Endpoints](https://duxt.app/reference/endpoints.md): Everything the site serves besides pages, one page each.
- [/_duxt/devtools](https://duxt.app/reference/endpoints/devtools.md): The route the Nuxt Devtools panel is served from. Dev only.
- [/llms-full.txt](https://duxt.app/reference/endpoints/llms-full-txt.md): A duxt extension with the same pages in one Markdown file.
- [/llms.txt](https://duxt.app/reference/endpoints/llms-txt.md): The documentation as a Markdown index, per llmstxt.org.
- [/mcp](https://duxt.app/reference/endpoints/mcp.md): An MCP server over the same content.
- [<page>.md](https://duxt.app/reference/endpoints/page-markdown.md): Any page source, at its own URL plus .md.
- [/rss.xml](https://duxt.app/reference/endpoints/rss-xml.md): The feed, once a section is named.
- [/sitemap.xml and /robots.txt](https://duxt.app/reference/endpoints/sitemap-and-robots.md): What a crawler is pointed at, and what it is kept out of.
- [Frontmatter](https://duxt.app/reference/frontmatter.md): The fields a page may carry beyond title and description, and the two the build fills in.
- [Hooks](https://duxt.app/reference/hooks.md): The one build-time hook duxt emits, what it hands you, and why there is only one.
- [MDC components](https://duxt.app/reference/mdc-components.md): The blocks a Markdown page can call, one page each, with their props.
- [Accordion](https://duxt.app/reference/mdc-components/accordion.md): Collapsible sections — a FAQ, or answers a reader picks from.
- [Accordion item](https://duxt.app/reference/mdc-components/accordion-item.md): One collapsible section.
- [Callout](https://duxt.app/reference/mdc-components/callout.md): An aside the reader is meant to stop at — a tip, a warning, a danger.
- [Code group](https://duxt.app/reference/mdc-components/code-group.md): Several fences as one tabbed block, labelled by filename.
- [Field](https://duxt.app/reference/mdc-components/field.md): One parameter, property or option, with its type and default.
- [Field group](https://duxt.app/reference/mdc-components/field-group.md): A list of fields as one block.
- [File tree](https://duxt.app/reference/mdc-components/file-tree.md): A folder structure, with icons per file type.
- [Mermaid](https://duxt.app/reference/mdc-components/mermaid.md): A diagram from a fence or a prop.
- [Package managers](https://duxt.app/reference/mdc-components/package-managers.md): One command, one tab per package manager, remembered across pages.
- [Page cards](https://duxt.app/reference/mdc-components/page-cards.md): A section's children, as cards.
- [Partial](https://duxt.app/reference/mdc-components/partial.md): A block written once and rendered in every source that needs it.
- [Preview](https://duxt.app/reference/mdc-components/preview.md): A component rendered as the page renders it, with its source beside it.
- [Prose overrides](https://duxt.app/reference/mdc-components/prose.md): What the layer changes about plain Markdown — links, headings, images, code and tables.
- [ProseA](https://duxt.app/reference/mdc-components/prose/prose-a.md): A link, resolved against the source it was written in.
- [ProseH2, ProseH3, ProseH4](https://duxt.app/reference/mdc-components/prose/prose-headings.md): Headings, each with a permalink anchor.
- [ProseImg](https://duxt.app/reference/mdc-components/prose/prose-img.md): An image: theme-aware, responsive, and zoomable.
- [ProsePre](https://duxt.app/reference/mdc-components/prose/prose-pre.md): The code block: filename, language icon, copy button.
- [ProseTable](https://duxt.app/reference/mdc-components/prose/prose-table.md): A table that scrolls instead of the page.
- [Since](https://duxt.app/reference/mdc-components/since.md): The version something arrived in, beside a heading.
- [Steps](https://duxt.app/reference/mdc-components/steps.md): An ordered list drawn as numbered steps on a rail.
- [Tab](https://duxt.app/reference/mdc-components/tab.md): One panel of a tab group.
- [Tab group](https://duxt.app/reference/mdc-components/tab-group.md): Tabs for anything that is not code.
- [API reference](https://duxt.app/reference/openapi.md): An OpenAPI document, published as reference pages with a client that sends real requests.
- [Components](https://duxt.app/reference/openapi/components.md): The three MDC components a generated reference page is made of.
- [Request samples](https://duxt.app/reference/openapi/request-samples.md): The same request in twelve clients, and how to add your own.
- [Declaring the section](https://duxt.app/reference/openapi/section.md): The `openapi` section type — where the document lives, and what it becomes.
- [The try-it client](https://duxt.app/reference/openapi/try-it.md): A real request, sent by the reader's own browser.
- [Sources](https://duxt.app/reference/sources.md): The fields of a source entry, its refs, and the options that shape the URLs.
- [Releases](https://duxt.app/releases.md)
- [0.1.0](https://duxt.app/releases/v0.1.0.md)
- [0.2.0](https://duxt.app/releases/v0.2.0.md)
- [0.3.0](https://duxt.app/releases/v0.3.0.md)
- [0.3.1](https://duxt.app/releases/v0.3.1.md)
- [0.3.2](https://duxt.app/releases/v0.3.2.md)
- [0.3.3](https://duxt.app/releases/v0.3.3.md)
- [0.3.4](https://duxt.app/releases/v0.3.4.md)
- [0.4.0](https://duxt.app/releases/v0.4.0.md)
- [0.5.0](https://duxt.app/releases/v0.5.0.md)
- [0.6.0](https://duxt.app/releases/v0.6.0.md)
- [0.7.0](https://duxt.app/releases/v0.7.0.md)
- [0.8.0](https://duxt.app/releases/v0.8.0.md)
- [0.8.1](https://duxt.app/releases/v0.8.1.md)
- [0.9.0](https://duxt.app/releases/v0.9.0.md)