A publication becomes easier to maintain when editors can express structure with native content tools instead of asking for a new template every time. This field guide uses the same Ghost cards a Dossier customer would use in normal editorial work.
Start with hierarchy, not decoration
Headings should tell a reader where they are. Cards should carry information that is genuinely different from the surrounding prose: evidence, media, downloads, calls to action or supporting context.

Use callouts for decisions and caveats
Make supporting material easy to inspect
Methodology and limits
Let technical material remain technical
Research publications often need code, configuration or data structures. Those elements should be readable without making the whole article feel like developer documentation.
const publication = {
content: 'portable',
membership: 'native',
archive: 'structured',
distribution: ['web', 'email', 'audio']
};
export default publication;Show related evidence visually
Support downloads without leaving the reading flow
Native media can live inside the article
Demo audio briefingA short Dossier system-map demo clip
Calls to action should feel editorial
A publication can invite membership or sell a companion resource without turning every page into a conversion funnel.
Systems Research Pack
A fictional companion pack used here to demonstrate Ghost's native product-card styling inside Dossier.
Follow Dossier
Get new essays, briefs and audio when they are published.
The point is restraint
Rich content works best when each card has a reason to exist.
Dossier is designed so native Ghost cards can appear inside serious editorial work without forcing the publication into a generic blog aesthetic. The theme should make complex content feel more organized, not more decorated.
This article is part of the Dossier demo publication and intentionally exercises a broad range of native Ghost content styles.

Comments