Sources
What `duxt.sources` became — one collection per source, version and language.
The first panel to open, because everything else in the tab is downstream of it. One row per resolved source: what a consumer wrote as a handful of entries, expanded into the collections Content actually generated and the URL prefix each one serves.
Columns
| Column | What it says |
|---|---|
Prefix | The URL segment this collection is served under; / for the unprefixed one |
Collection | The generated collection name, as queryCollection takes it, tagged with its type where it is a generated section |
Repository | Where the pages come from, linked when it is known |
Folder / artefact | The path inside that repository — a docs folder, or the artefact a section was built from |
Ref | The branch or tag, and which of the two it is |
Version | The slug in the URL, default when it is served without a segment |
Status | current, deprecated or eol, straight from the source |
Reserved segments | Folder names inside this source that a prefix has already claimed |
Notes
A repository segment appears only when there is more than one repository, and
a version segment only when there is more than one ref — a segment that can hold
one value distinguishes nothing. sourceOptions.showRepo and showVersion force
them back on.
Reserved segments are the trap this column exists for. If a source is served
under /sdk and its docs folder contains a v1-9/ directory, the prefix wins and
that folder is unreachable. The Checks panel reports
it as an error; this column shows which names are taken before it happens.
A generated section is a collection like any other, which is what lets the
rest of the layer work on it unchanged — and what made it indistinguishable here
from a docs tree whose folder happened to be called CHANGELOG.md. The tag
beside the collection name is its type, so changelog and openapi rows read
as what they are, and the summary counts them. What the artefact itself had to
say is a finding rather than a column, and is reported on the
Checks panel.
The footer names the file the list was read from — useful on a site where
app.config.ts is not where you expected it.