Skip to content
duxt

Pages

Every page of every collection, with its frontmatter and git metadata.

What Content ended up with, one block per collection. This is the panel that answers "is my page in the build at all" — and, more often, "why does this one look different from the others".

Columns

ColumnWhat it says
PathThe URL, prefix included — what queryCollection stores
TitleFrom the frontmatter; missing is a warning, not a guess
DescriptionWhether one exists at all; it feeds the cards, the OG image and llms.txt
IconThe Iconify name in the frontmatter
Last updatedFrom the git history, not from the file's mtime
ContributorsHow many people the history names
FileOpens the source file in your editor

Notes

A collection with no history at all is usually a remote source without history: true. Content clones with --depth 1, so the checkout holds a single commit and every page would appear to have been written by whoever cut the tip — the layer prefers no data to wrong data.

Collections beyond the first are collapsed. A site with five versions has five near-identical tables, and all five expanded is a page nobody reads.

The filter appears above a table of more than twelve rows. It hides rows that do not match anywhere in the row, counts what is left, and a reload brings everything back.

An empty collection is a finding, not an empty table — every URL under that prefix is a 404, and the panel says so where the rows would have been.

Was this page helpful?