
A Collection item's frontmatter holds only the structured facts that code reads: what cards, filters, stats, site
search, the MCP tools and the Markdown Representation's header need (title, cover, years, authors, Volumes, formats…).
Everything a reader reads or looks at is written in the MDX body: prose, tables, and every image carousel, with its
images listed literally (<ImageCarousel images={[…]} />). The page component renders only what it derives from the
facts (title, badges, information pills) plus the chrome (breadcrumb, previous/next, structured data), and loads the
body.
This replaced a split where a Game page drew one carousel from metadata.gallery in code and a second, the gameplay
screenshots, from its MDX: the same kind of content lived in two places, and where a photo belonged depended on who had
added it.
gallery exists.mdx-to-markdown already converts a literal
ImageCarousel), so generators must not also render them from metadata.<MangaInformation />): the
MDX decides where it goes and its data still comes only from the frontmatter. Such slots are listed in
componentsRenderedByTheirGenerator, since the generator already renders their facts.