Component Audit

This audit compares the component library with current Pages, schemas, layouts, and component dependencies. It is a cleanup guide, not an instruction to delete files without a final build and visual check.

#High-confidence removal candidates

These editor-visible components have no references in current site content, layouts, schemas, or other components:

The following hidden components also have no detected references and can be reviewed as a cleanup batch:

Remove only as a connected legacy feature

Legacy site settings and test content

Publishing workflow issue

The Blog collection has collection-level code that removes draft and future-dated posts from production. Stories, Resources, and Events expose a Draft field but do not have equivalent build logic, so records marked as drafts can still be generated and included in collections. Align these collections with the Blog draft handling before treating the switch as a publication control.

Components to keep even though editors cannot add them directly

Several hidden components are active dependencies: buttons, cards for the active collections, Section Header, shared Media, background-image helpers, Story Banner, SVG/category icons, signup form, link panels, social-share buttons, and the Error component. Their hidden status prevents editors from adding a low-level building block without its parent component.