A catalog of connected content modules including a process, table, metric card, quote, image, media tile, and disclosure panel.

Overview

Visual elements are selectable Content capabilities for making documents, blog posts, newsletters, announcements, and other published material easier to understand and act on. Read the Authoring Overview first, then choose an element only when it improves the information relationship you want the reader to see.

Catalog

Name	Description
`ContentStepSequence`	Show an ordered process or checklist with `ContentStep` representing each step node within `ContentStepSequence`.
`ContentTable`	Compare structured values in a semantic table.
`ContentSearchableSortableTable`	Search and sort a structured dataset.
`ContentFigure`	Explain an informative chart, map, screenshot, or diagram.
`ContentMetricCard`	Highlight a verified metric with context.
`ContentLinkCard`	Present a relevant next reading or action.
`ContentMultiColumnGroup`	Group two or three parallel elements.
`ContentSlideGallery`	Present a sequence of visual slides.
`ContentImage`	Embed an informative image.
`ContentAttributedQuote`	Present an attributed personal perspective.
`ContentSplitPanel`	Compare two related views.
`ContentAudioEmbed`	Add a short briefing or podcast excerpt.
`ContentVideoEmbed`	Add a demonstration or visual briefing.
`ContentDisclosure`	Disclose optional methodology or background.

For AI agents

The machine-readable authoring manifest (JSON) is intended for authoring agents and skills such as autonomous-blogger. An agent can read the catalog before choosing elements, plan the document structure, generate GoVisit MDX from the public contracts, and submit it to GoVisit for validation, private rendering, and publication. The manifest describes the capabilities and constraints without exposing the private component implementations.

Naming rules

Content element names describe reusable rendering, structure, or interaction capabilities. They are shared across GoVisit, inHotel, and future publishing contexts.

Use the Content prefix so the name is distinct from HTML elements and ordinary Markdown.
Name the observable capability the renderer guarantees, such as Table, SearchableSortableTable, Image, Embed, or Disclosure.
Keep editorial purpose, audience, channel, and accessibility guidance out of the canonical name. For example, use ContentImage, then document when an image is informative and require meaningful alternative text.
Add modifiers only for behavior or structure that is part of the public contract.
Keep variant names related to their base capability: ContentTable and ContentSearchableSortableTable.
Keep stable capability identities separate from display labels and legacy aliases in the machine-readable manifest.

Use the page guidance and manifest metadata for “use when,” accessibility, evidence, and fallback recommendations; do not encode those recommendations into the element name.