Skip to content

docs: document profile priority and missing profile behavior #2083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cderv merged 1 commit into from
Jun 23, 2026
+6 −0
Merged

docs: document profile priority and missing profile behavior #2083

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/projects/profiles.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,6 +127,12 @@ quarto render
quarto render --profile advanced,production
```

When multiple profiles are active and their configurations contain the same scalar key, the **first-listed profile takes priority**. For example, with `--profile advanced,production`, the `advanced` profile's values win any scalar conflicts. Arrays and objects follow standard [metadata merging](quarto-projects.qmd#metadata-merging) rules (arrays are union-concatenated, objects are deep-merged).

::: {.callout-warning}
If a profile is specified but no corresponding `_quarto-{name}.yml` file exists, the profile is **silently ignored** with no warning or error. This can lead to unexpected behavior if you mistype a profile name.
:::

## Profile Content

You can also specify that content within your project only be included when a certain profile is active. You do this using the `.content-visible` class along with the `when-profile` attribute to a div or span. For example, here we defined a div that is included only for the `advanced` profile:
Expand Down
Loading