Two artifacts on the site are declared and unused, and one collection is declared and empty.
_rulesets/ is empty
_config.yml declares a rulesets collection with output: true and permalink: /rulesets/:path/, and _rulesets/ contains zero files. The live /rulesets/ pages are static HTML in rulesets/ (experience-*.html), generated separately from the Spotlight catalog.
So the collection is dead configuration. Either generate _rulesets/*.md from the catalog as scripts/generate-spotlight.py's docstring says it does, or drop the collection from _config.yml.
Two data files nothing reads
_data/specifications.yaml_data/showcase.yaml
Neither is referenced by any layout, include, or page — verified by grepping site.data.specifications and site.data.showcase across _layouts/, _includes/ and the root HTML. They are maintained-looking files that render nowhere.
Either wire them into a page or delete them. The specifications.yaml content overlaps what /common/ already covers per-artifact, so deletion is probably right.
Why bother
Dead configuration is a trap for the next person: it looks like the mechanism for something, so they extend it, and nothing appears. The layout-renders-a-fixed-key-set problem has already bitten twice on this site — a new frontmatter key is invisible until the layout learns it. Same class of surprise.
Two artifacts on the site are declared and unused, and one collection is declared and empty.
_rulesets/is empty_config.ymldeclares arulesetscollection withoutput: trueandpermalink: /rulesets/:path/, and_rulesets/contains zero files. The live/rulesets/pages are static HTML inrulesets/(experience-*.html), generated separately from the Spotlight catalog.So the collection is dead configuration. Either generate
_rulesets/*.mdfrom the catalog asscripts/generate-spotlight.py's docstring says it does, or drop the collection from_config.yml.Two data files nothing reads
_data/specifications.yaml_data/showcase.yamlNeither is referenced by any layout, include, or page — verified by grepping
site.data.specificationsandsite.data.showcaseacross_layouts/,_includes/and the root HTML. They are maintained-looking files that render nowhere.Either wire them into a page or delete them. The
specifications.yamlcontent overlaps what/common/already covers per-artifact, so deletion is probably right.Why bother
Dead configuration is a trap for the next person: it looks like the mechanism for something, so they extend it, and nothing appears. The layout-renders-a-fixed-key-set problem has already bitten twice on this site — a new frontmatter key is invisible until the layout learns it. Same class of surprise.