Marigold
v18.0.0-beta.4
Marigold
v18.0.0-beta.4

Application

MarigoldProvider
RouterProvider

Layout

AppShellbeta
Aside
Aspect
Center
Columns
Container
Grid
Inline
Inset
Pagebeta
Panelbeta
Scrollable
Split
Stack
Tiles

Actions

Buttonupdated
ButtonGroupbeta
Link
LinkButton
ToggleButtonbeta

Form

Autocomplete
Calendar
Checkbox
ComboBox
DateField
DatePicker
DateRangePickerbeta
FileField
Form
NumberField
Radio
RangeCalendaralpha
SearchField
SegmentedControlbeta
Select
SelectListupdated
Slider
Switchupdated
TagFieldbeta
TextArea
TextField
TimeField

Collection

Cardupdated
Table
Tag
ActionBaralpha

Navigation

Accordion
Breadcrumbs
Pagination
Sidebarbeta
Tabs
TopNavigationbeta

Overlay

ActionMenualpha
ContextualHelp
Dialog
Drawer
Menuupdated
Toastbeta
Tooltip

Content

Badge
Descriptionalpha
Divider
EmptyStatebeta
ErrorStatebeta
Headline
Keyboardbeta
List
Loader
SectionMessage
SVG
Text
TextValuealpha
Titlealpha

Formatters

DateFormat
NumericFormat

Hooks and Utils

cn
cva
extendTheme
parseFormData
useAsyncListData
useLandmark
useListData
useTheme
VisuallyHidden
Components

Title

Heading primitive that participates in container slot context.

The <Title> component is a heading designed to live inside a container surface such as <Panel>, <Dialog>, <Drawer>, <EmptyState>, or <SectionMessage>. The container decides the heading level and how the title fits into the surrounding layout, so consumers can drop a <Title> in without thinking about it.

For top-level page headings reach for <Headline> instead.

Anatomy

Text

A title is a single heading element with no parts of its own.

Appearance

<Title> carries no styling of its own. Its appearance comes entirely from the surrounding container, which keeps the look consistent across panels, dialogs, drawers, and other surfaces. Pair it with <Description> when the region also needs a help line.

Styling is inferred automatically from the surrounding context. See Slot-Driven Composition for how this works.

Usage

Reach for <Title> whenever a container surface labels its content with a heading. For top-level page headings or any heading that should not adapt to a surrounding container, use <Headline> instead.

A container can define the heading level, spacing, and visual style for the title region through its slot context. The consumer just writes the title text and the container takes care of the rest.

Storage usage

42% of your storage quota is currently in use.

import { Description, Panel, Title } from '@marigold/components';export default () => (  <Panel>    <Panel.Header>      <Title>Storage usage</Title>      <Description>42% of your storage quota is currently in use.</Description>    </Panel.Header>  </Panel>);

Do

Keep <Title> content to a short, descriptive label. A noun phrase like 'Members', 'Delete project', or 'Recent activity' names what the region contains, while a <Description> below carries any extra detail.

Don't

Don't override the level prop unless the document outline calls for it. The container picks a level that fits the surrounding context.

Heading level

The level prop controls the rendered HTML element (<h1> to <h6>). When <Title> is used inside a container, the container supplies the level for you so the document outline stays correct without consumers having to think about it. Set level explicitly only when using <Title> outside a container, or when the document outline calls for a different level than the container's default.

Accessibility

<Title> renders a real heading element, so screen readers announce it as a heading at the level it renders. The level prop maps directly to the underlying <h1> to <h6> element, which means assistive technologies can navigate the page by headings just like they would with handwritten markup.

A Title used without a container still renders as a plain heading. It contributes to the document outline but has no programmatic relationship to anything else. Containers that pair a Title with a <Description> wire the relationship through their slot context, so consumers don't need to set aria-describedby manually.

Props

Did you know? You can explore, test, and customize props live in Marigold's storybook. Watch the effects they have in real-time!
View Title stories

Title

Prop

Type

Accessibility props (4)

Prop

Type

Alternative components

  • Headline: Use for top-level page headings or any heading that should not adapt to a surrounding container.
  • Description: The help-line partner for Title in container surfaces.
  • Text: Use for paragraph text and body copy.
Last update: 2 months ago

TextValue

Inline label primitive for selection items.

DateFormat

Helper component for formatting date values based on the current language and locale-specific conventions.

On this page

AnatomyAppearanceUsageHeading levelAccessibilityPropsTitleAlternative components