Components

The AirOps web design system for building landing pages, resource pages, and campaigns.

Buttons

Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.

Primary

The main conversion or next step.

Default
Hover
Focus
Pressed
Disabled
Loading
Error recovery
Icon left
Icon right

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-button brand-button-primary" href="https://www.airops.com/book-a-call">Work with us</a>
</div>
View prompt
Use the AirOps primary variant from /elements#buttons-primary (buttons/primary).
The main conversion or next step.
Use the following content fields.
- label (text, required). A short, verb-led action label.
- target (link | action, required). A URL for navigation or an action for a button.
- variant (primary | secondary | tertiary | mini, required). Match the emphasis and context of the action.
- state (default | hover | focus | pressed | disabled | loading | error-recovery, optional). Pointer and keyboard states are handled by CSS. Use native disabled and aria-busy for unavailable or pending actions.
- iconPlacement (left | right, optional). Place the icon before or after the visible label. Hide decorative icons from assistive technology.
Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.
Use an anchor for navigation and a button for an in-page action or form submission. Use Mini for compact utilities and disclosure controls such as View code.
Place an optional icon before or after the text. Keep a verb-led visible label and preserve the keyboard focus indicator.
Use the recovery treatment next to an error that the visitor can retry. Keep disabled controls out of the conversion path until the visitor can act.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
View button variations code

Disabled. Use a native disabled button for an unavailable in-page action.

<button class="brand-button brand-button-primary" type="button" disabled>Work with us</button>

Loading. Mark the button busy and prevent repeat submissions until the request settles. Announce the outcome nearby.

<button class="brand-button brand-button-primary" type="button" disabled aria-busy="true"><span class="brand-button-spinner" aria-hidden="true"></span> Submitting…</button>

Error recovery. After a recoverable error, offer a retry and explain what went wrong beside the button.

<button class="brand-button brand-button-primary is-error-recovery" type="button">Try again</button>

Icon left

<button class="brand-button brand-button-primary" type="button"><span class="brand-button-icon" aria-hidden="true">←</span><span>Back</span></button>

Icon right

<button class="brand-button brand-button-primary" type="button"><span>Work with us</span><span class="brand-button-icon" aria-hidden="true">→</span></button>

Secondary

A supporting action beside the primary.

Default
Hover
Focus
Pressed
Disabled
Loading
Error recovery
Icon left
Icon right

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-button brand-button-secondary" href="https://www.airops.com/pricing">See pricing</a>
</div>
View prompt
Use the AirOps secondary variant from /elements#buttons-secondary (buttons/secondary).
A supporting action beside the primary.
Use the following content fields.
- label (text, required). A short, verb-led action label.
- target (link | action, required). A URL for navigation or an action for a button.
- variant (primary | secondary | tertiary | mini, required). Match the emphasis and context of the action.
- state (default | hover | focus | pressed | disabled | loading | error-recovery, optional). Pointer and keyboard states are handled by CSS. Use native disabled and aria-busy for unavailable or pending actions.
- iconPlacement (left | right, optional). Place the icon before or after the visible label. Hide decorative icons from assistive technology.
Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.
Use an anchor for navigation and a button for an in-page action or form submission. Use Mini for compact utilities and disclosure controls such as View code.
Place an optional icon before or after the text. Keep a verb-led visible label and preserve the keyboard focus indicator.
Use the recovery treatment next to an error that the visitor can retry. Keep disabled controls out of the conversion path until the visitor can act.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
View button variations code

Disabled. Use a native disabled button for an unavailable in-page action.

<button class="brand-button brand-button-secondary" type="button" disabled>See pricing</button>

Loading. Mark the button busy and prevent repeat submissions until the request settles. Announce the outcome nearby.

<button class="brand-button brand-button-secondary" type="button" disabled aria-busy="true"><span class="brand-button-spinner" aria-hidden="true"></span> Loading…</button>

Error recovery. After a recoverable error, offer a retry and explain what went wrong beside the button.

<button class="brand-button brand-button-secondary is-error-recovery" type="button">Try again</button>

Icon left

<button class="brand-button brand-button-secondary" type="button"><span class="brand-button-icon" aria-hidden="true">←</span><span>Back</span></button>

Icon right

<button class="brand-button brand-button-secondary" type="button"><span>See pricing</span><span class="brand-button-icon" aria-hidden="true">→</span></button>

Tertiary

A related detail or low-emphasis route.

Default
Hover
Focus
Pressed
Disabled
Loading
Error recovery
Icon left
Icon right

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-button brand-button-tertiary" href="https://www.airops.com/why-airops">Learn more <span aria-hidden="true">→</span></a>
</div>
View prompt
Use the AirOps tertiary variant from /elements#buttons-tertiary (buttons/tertiary).
A related detail or low-emphasis route.
Use the following content fields.
- label (text, required). A short, verb-led action label.
- target (link | action, required). A URL for navigation or an action for a button.
- variant (primary | secondary | tertiary | mini, required). Match the emphasis and context of the action.
- state (default | hover | focus | pressed | disabled | loading | error-recovery, optional). Pointer and keyboard states are handled by CSS. Use native disabled and aria-busy for unavailable or pending actions.
- iconPlacement (left | right, optional). Place the icon before or after the visible label. Hide decorative icons from assistive technology.
Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.
Use an anchor for navigation and a button for an in-page action or form submission. Use Mini for compact utilities and disclosure controls such as View code.
Place an optional icon before or after the text. Keep a verb-led visible label and preserve the keyboard focus indicator.
Use the recovery treatment next to an error that the visitor can retry. Keep disabled controls out of the conversion path until the visitor can act.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
View button variations code

Disabled. Use a native disabled button for an unavailable in-page action.

<button class="brand-button brand-button-tertiary" type="button" disabled>Learn more</button>

Loading. Mark the button busy and prevent repeat submissions until the request settles. Announce the outcome nearby.

<button class="brand-button brand-button-tertiary" type="button" disabled aria-busy="true"><span class="brand-button-spinner" aria-hidden="true"></span> Loading…</button>

Error recovery. After a recoverable error, offer a retry and explain what went wrong beside the button.

<button class="brand-button brand-button-tertiary is-error-recovery" type="button">Try again</button>

Icon left

<button class="brand-button brand-button-tertiary" type="button"><span class="brand-button-icon" aria-hidden="true">←</span><span>Back</span></button>

Icon right

<button class="brand-button brand-button-tertiary" type="button"><span>Learn more</span><span class="brand-button-icon" aria-hidden="true">→</span></button>

Mini

A compact utility or disclosure, such as View code.

Default
Hover
Focus
Pressed
Disabled
Loading
Error recovery
Icon left
Icon right

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <details>
    <summary class="brand-button brand-button-mini brand-button-disclosure">View code</summary>
    <p>Code for this example.</p>
  </details>
</div>
View prompt
Use the AirOps mini variant from /elements#buttons-mini (buttons/mini).
A compact utility or disclosure, such as View code.
Use the following content fields.
- label (text, required). A short, verb-led action label.
- target (link | action, required). A URL for navigation or an action for a button.
- variant (primary | secondary | tertiary | mini, required). Match the emphasis and context of the action.
- state (default | hover | focus | pressed | disabled | loading | error-recovery, optional). Pointer and keyboard states are handled by CSS. Use native disabled and aria-busy for unavailable or pending actions.
- iconPlacement (left | right, optional). Place the icon before or after the visible label. Hide decorative icons from assistive technology.
Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.
Use an anchor for navigation and a button for an in-page action or form submission. Use Mini for compact utilities and disclosure controls such as View code.
Place an optional icon before or after the text. Keep a verb-led visible label and preserve the keyboard focus indicator.
Use the recovery treatment next to an error that the visitor can retry. Keep disabled controls out of the conversion path until the visitor can act.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
View button variations code

Disabled. Use a native disabled button for an unavailable in-page action.

<button class="brand-button brand-button-mini" type="button" disabled>View code</button>

Loading. Mark the button busy and prevent repeat submissions until the request settles. Announce the outcome nearby.

<button class="brand-button brand-button-mini" type="button" disabled aria-busy="true"><span class="brand-button-spinner" aria-hidden="true"></span> Loading…</button>

Error recovery. After a recoverable error, offer a retry and explain what went wrong beside the button.

<button class="brand-button brand-button-mini is-error-recovery" type="button">Try again</button>

Icon left

<button class="brand-button brand-button-mini" type="button"><span class="brand-button-icon" aria-hidden="true">←</span><span>Back</span></button>

Icon right

<button class="brand-button brand-button-mini" type="button"><span>View code</span><span class="brand-button-icon" aria-hidden="true">→</span></button>
Usage and page block examples
  • Give each section one primary action. Use secondary for a supporting route, and tertiary for inline or low-emphasis actions.
  • Use an anchor for navigation and a button for an in-page action or form submission. Use Mini for compact utilities and disclosure controls such as View code.
  • Place an optional icon before or after the text. Keep a verb-led visible label and preserve the keyboard focus indicator.
  • Use the recovery treatment next to an error that the visitor can retry. Keep disabled controls out of the conversion path until the visitor can act.
Content fields
  • label (text, required). A short, verb-led action label.
  • target (link | action, required). A URL for navigation or an action for a button.
  • variant (primary | secondary | tertiary | mini, required). Match the emphasis and context of the action.
  • state (default | hover | focus | pressed | disabled | loading | error-recovery, optional). Pointer and keyboard states are handled by CSS. Use native disabled and aria-busy for unavailable or pending actions.
  • iconPlacement (left | right, optional). Place the icon before or after the visible label. Hide decorative icons from assistive technology.
Token references
color.deepGreencolor.offWhitestroke.defaultradius.controlstypography.core.button

Cards

Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.

Text card

Present a headline and supporting copy for one idea.

See where your brand stands

Understand where buyers discover your brand and which opportunities are worth pursuing.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <div class="brand-card-copy">
      <h3>See where your brand stands</h3>
      <p>Understand where buyers discover your brand and which opportunities are worth pursuing.</p>
    </div>
  </article>
</div>
View prompt
Use the AirOps text card variant from /elements#cards-content (cards/content).
Present a headline and supporting copy for one idea.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Linked text card

Make the entire surface one link when there is one destination.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-card-preview brand-card-link" href="https://www.airops.com/platform">
    <div class="brand-card-copy"><h3>AirOps platform</h3><p>Explore how the platform connects research, strategy, and execution.</p></div>
    <span class="brand-button brand-button-tertiary">Explore the platform <span class="brand-button-icon" aria-hidden="true">→</span></span>
  </a>
</div>
View prompt
Use the AirOps linked text card variant from /elements#cards-linked (cards/linked).
Make the entire surface one link when there is one destination.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Thumbnail and title card

Use a thumbnail and short title in a dense resource list.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-card-preview brand-card-link brand-card-horizontal" href="https://www.airops.com/blog">
    <img src="/brand/image-library/brand-story-city.jpg" alt="" width="64" height="64" loading="lazy">
    <div class="brand-card-copy"><p class="brand-card-meta">Insights</p><h3>AI search research</h3></div>
  </a>
</div>
View prompt
Use the AirOps thumbnail and title card variant from /elements#cards-horizontal (cards/horizontal).
Use a thumbnail and short title in a dense resource list.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Icon card

Explain one capability with a short headline and a single next step.

Find opportunities

Identify the questions, themes, and channels your team can act on.

Explore the platform

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <span class="brand-card-symbol" aria-hidden="true">↗</span>
    <div class="brand-card-copy"><h3>Find opportunities</h3><p>Identify the questions, themes, and channels your team can act on.</p></div>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/platform">Explore the platform</a>
  </article>
</div>
View prompt
Use the AirOps icon card variant from /elements#cards-feature (cards/feature).
Explain one capability with a short headline and a single next step.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Quote and attribution card

Present a short approved quote with a named source.

“We were able to focus our energy on the highest-value initiatives for the business in a matter of weeks.”
Nick Fairbairn
SVP of Growth, Chime

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <figure class="brand-card-preview brand-card-quote">
    <blockquote>“We were able to focus our energy on the highest-value initiatives for the business in a matter of weeks.”</blockquote>
    <figcaption><strong>Nick Fairbairn</strong><br>SVP of Growth, Chime</figcaption>
  </figure>
</div>
View prompt
Use the AirOps quote and attribution card variant from /elements#cards-quote (cards/quote).
Present a short approved quote with a named source.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Logo and title card

Pair an approved customer mark with a case study destination.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <img class="brand-card-logo" src="https://www.airops.com/images/Company-Logo-chime.svg" alt="Chime" width="98" height="38" loading="lazy">
    <div class="brand-card-copy"><p class="brand-card-meta">Customer story</p><h3>How Chime prioritized its highest-value initiatives</h3></div>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/customer-stories">Browse customer stories</a>
  </article>
</div>
View prompt
Use the AirOps logo and title card variant from /elements#cards-customer-story (cards/customer-story).
Pair an approved customer mark with a case study destination.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Text and button card

Present a single action on a deep green surface.

Choose where to start

Talk with AirOps about building an AI search strategy.

Work with us

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview brand-card-conversion">
    <div class="brand-card-copy"><h3>Choose where to start</h3><p>Talk with AirOps about building an AI search strategy.</p></div>
    <a class="brand-button brand-button-secondary" href="https://www.airops.com/book-a-call">Work with us</a>
  </article>
</div>
View prompt
Use the AirOps text and button card variant from /elements#cards-conversion (cards/conversion).
Present a single action on a deep green surface.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Label, text, and button card

Introduce who a plan serves and link to the current pricing page.

Plan overview

Pro

For small teams building content for one brand or project.

Explore plans

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <div class="brand-card-copy"><p class="brand-card-meta">Plan overview</p><h3>Pro</h3><p>For small teams building content for one brand or project.</p></div>
    <a class="brand-button brand-button-secondary" href="https://www.airops.com/pricing">Explore plans</a>
  </article>
</div>
View prompt
Use the AirOps label, text, and button card variant from /elements#cards-plan (cards/plan).
Introduce who a plan serves and link to the current pricing page.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Image and text card

An editorial resource or story with an approved image.

Discover the latest research

See how people find and evaluate brands in AI search.

Browse research

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <div class="brand-card-media">
      <img src="/brand/image-library/brand-story-transit.jpg" alt="" width="520" height="176" loading="lazy">
    </div>
    <div class="brand-card-copy">
      <h3>Discover the latest research</h3>
      <p>See how people find and evaluate brands in AI search.</p>
    </div>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/blog">Browse research <span class="brand-button-icon" aria-hidden="true">→</span></a>
  </article>
</div>
View prompt
Use the AirOps image and text card variant from /elements#cards-media (cards/media).
An editorial resource or story with an approved image.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Image, label, and text card

Combine a topic, image, headline, and route into a resource collection.

Insights

Discover how buyers find brands

Research and analysis on how AI changes discovery.

Browse insights

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <div class="brand-card-media"><img src="/brand/image-library/brand-story-city.jpg" alt="" width="520" height="176" loading="lazy"></div>
    <div class="brand-card-copy"><p class="brand-card-meta">Insights</p><h3>Discover how buyers find brands</h3><p>Research and analysis on how AI changes discovery.</p></div>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/blog">Browse insights <span class="brand-button-icon" aria-hidden="true">→</span></a>
  </article>
</div>
View prompt
Use the AirOps image, label, and text card variant from /elements#cards-editorial (cards/editorial).
Combine a topic, image, headline, and route into a resource collection.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Image and two-button card

Combine media, supporting copy, and a secondary route when readers need a choice.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <article class="brand-card-preview">
    <div class="brand-card-media"><img src="/brand/image-library/business.jpg" alt="" width="520" height="176" loading="lazy"></div>
    <div class="brand-card-copy"><p class="brand-card-meta">Platform</p><h3>Explore AirOps</h3><p>Get familiar with the platform or talk with the team.</p></div>
    <div class="brand-card-actions">
      <a class="brand-button brand-button-primary" href="https://www.airops.com/platform">See the platform</a>
      <a class="brand-button brand-button-tertiary" href="https://www.airops.com/book-a-call">Talk to the team</a>
    </div>
  </article>
</div>
View prompt
Use the AirOps image and two-button card variant from /elements#cards-two-actions (cards/two-actions).
Combine media, supporting copy, and a secondary route when readers need a choice.
Use the following content fields.
- title (text, required). A short, descriptive headline.
- summary (text, required). One or two sentences explaining the destination.
- action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
- image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
- secondaryAction (link, optional). A separate action with a distinct purpose.
- metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Use one card treatment per collection. Keep card titles, media crops, and action placement consistent across a row.
  • Use a flat white surface with a linen stroke, or deep green for a high-emphasis action. Use the shared card radius and padding to keep the collection consistent.
  • Use a single anchor for a fully linked card. With two actions, keep both controls separate and preserve their focus order.
  • Use the shared button styles for card actions. Use Primary for conversion on a light surface, Secondary for an alternate or inverse action, Tertiary for a directional text link, and Mini for compact details.
Content fields
  • title (text, required). A short, descriptive headline.
  • summary (text, required). One or two sentences explaining the destination.
  • action (link, optional). A label and URL for the primary destination. Required for linked and conversion cards.
  • image (asset, optional). Required for the media variant. Include alt text when the image communicates information.
  • secondaryAction (link, optional). A separate action with a distinct purpose.
  • metadata (tag | attribution, optional). Supply the context required by the variant, such as a topic label or a quote attribution.
Token references
color.whitecolor.mutedstroke.defaultradius.contentCardtypography.core.h5

Form fields

Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.

Form and field states

Work with us

AirOps works as an extension of your team to build the strategy, systems, and channel presence you need to win in AI search.

By submitting this form, you agree to AirOps processing your information in accordance with our Privacy Policy, including to communicate with you about our products, services, and events.

Form field states

Email field

An address the visitor can type or autofill.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <label class="brand-input">
    <span>Work email <b aria-hidden="true">*</b></span>
    <input name="email" type="email" autocomplete="email" placeholder="name@example.com" required>
  </label>
</div>
View prompt
Use the AirOps email field variant from /elements#form-fields-email (form-fields/email).
An address the visitor can type or autofill.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Select field

A short set of mutually exclusive choices.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <label class="brand-input">
    <span>Team size</span>
    <select name="team-size">
      <option value="">Choose your team size</option>
      <option value="1-10">1–10</option>
      <option value="11-50">11–50</option>
      <option value="51-plus">51+</option>
    </select>
  </label>
</div>
View prompt
Use the AirOps select field variant from /elements#form-fields-select (form-fields/select).
A short set of mutually exclusive choices.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Validation error

A field that needs a specific correction.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <label class="brand-input is-error">
    <span>Website URL</span>
    <input name="site" type="url" value="example.com" aria-invalid="true" aria-describedby="site-error">
    <small id="site-error">Enter a complete URL, including https://.</small>
  </label>
</div>
View prompt
Use the AirOps validation error variant from /elements#form-fields-invalid (form-fields/invalid).
A field that needs a specific correction.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Checkbox

An independent choice or opt-in.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <label class="brand-choice">
    <input name="subscribe" type="checkbox" value="yes">
    <span>Send me occasional AirOps research updates</span>
  </label>
</div>
View prompt
Use the AirOps checkbox variant from /elements#form-fields-checkbox (form-fields/checkbox).
An independent choice or opt-in.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Radio group

A short list where the visitor can choose one option.

How often do you publish?

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <fieldset class="brand-choice-group">
    <legend>How often do you publish?</legend>
    <label class="brand-choice"><input type="radio" name="cadence" value="weekly"> Weekly</label>
    <label class="brand-choice"><input type="radio" name="cadence" value="monthly"> Monthly</label>
  </fieldset>
</div>
View prompt
Use the AirOps radio group variant from /elements#form-fields-radio (form-fields/radio).
A short list where the visitor can choose one option.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Textarea

A field for a longer response in the visitor’s own words.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <label class="brand-input">
    <span>What would you like to improve?</span>
    <textarea name="goal" rows="3" placeholder="Tell us about your content goals"></textarea>
  </label>
</div>
View prompt
Use the AirOps textarea variant from /elements#form-fields-textarea (form-fields/textarea).
A field for a longer response in the visitor’s own words.
Use the following content fields.
- label (text, required). The persistent visible label.
- name (text, required). A unique submission key for this field.
- type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
- required (boolean, optional). Set required when the visitor must provide a value.
- options (list of label and value, optional). Required for select or radio choices.
- hint (text, optional). Additional input guidance.
- error (text, optional). Required while the field is invalid. State the correction.
Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Keep the label above the field. Use placeholder text for an example, and keep required indicators and help text visible.
  • Use the right input type and autocomplete value. Connect hint and error text with aria-describedby and set aria-invalid only when invalid.
  • Use the approved form provider in the publishing workspace and verify the success, error, and routing behavior.
Content fields
  • label (text, required). The persistent visible label.
  • name (text, required). A unique submission key for this field.
  • type (email | select | url | checkbox | radio | textarea, required). The control type shown by the selected variant.
  • required (boolean, optional). Set required when the visitor must provide a value.
  • options (list of label and value, optional). Required for select or radio choices.
  • hint (text, optional). Additional input guidance.
  • error (text, optional). Required while the field is invalid. State the correction.
Token references
color.inkcolor.deepGreencolor.warmGraytypography.core.bodyspacing

Disclosure

Keep the summary concise and make each panel answer one question. Use closed panels for optional detail.

Accordion row

An FAQ answer or supplementary detail.

How do I choose a plan?

Start with your team size, how often you publish, and the support you need.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <details class="brand-disclosure">
    <summary>How do I choose a plan?</summary>
    <p>Start with your team size, how often you publish, and the support you need.</p>
  </details>
</div>
View prompt
Use the AirOps accordion row variant from /elements#disclosure-accordion (disclosure/accordion).
An FAQ answer or supplementary detail.
Use the following content fields.
- summary (text, required). The question or label that opens the panel.
- content (rich text, required). The answer or supporting detail.
Keep the summary concise and make each panel answer one question. Use closed panels for optional detail.
Keep the native details and summary elements so visitors can open the content with the keyboard.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Keep the summary concise and make each panel answer one question. Use closed panels for optional detail.
  • Keep the native details and summary elements so visitors can open the content with the keyboard.
Content fields
  • summary (text, required). The question or label that opens the panel.
  • content (rich text, required). The answer or supporting detail.
Token references
color.inkcolor.bodystroke.defaultspacing

Tables

Use a table when visitors compare the same attributes across rows. Include a caption, scoped headings, and consistent units.

Tables and dense data

Campaign performance comparison
CampaignStatusLeadsConversionPipeline
AI visibility reportLive82412.8%$1.24M
Content operations guideLive1,16418.2%$1.86M
Workflow benchmarkReview6089.6%$780K

Comparison table

Structured comparisons where column headings matter.

Example publishing workflows
WorkflowUseExample cadence
Content auditReview existing pagesMonthly
Page refreshUpdate priority pagesWeekly

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <div class="table-spec-scroll" role="region" aria-label="Example publishing workflows" tabindex="0">
    <table class="brand-table brand-table-compact">
      <caption>Example publishing workflows</caption>
      <thead><tr><th scope="col">Workflow</th><th scope="col">Use</th><th scope="col">Example cadence</th></tr></thead>
      <tbody>
        <tr><th scope="row">Content audit</th><td>Review existing pages</td><td>Monthly</td></tr>
        <tr><th scope="row">Page refresh</th><td>Update priority pages</td><td>Weekly</td></tr>
      </tbody>
    </table>
  </div>
</div>
View prompt
Use the AirOps comparison table variant from /elements#tables-comparison (tables/comparison).
Structured comparisons where column headings matter.
Use the following content fields.
- caption (text, required). Name the comparison.
- columns (list of text, required). Order the shared attributes consistently.
- rows (list of row headings and cells, required). Include the same attributes and consistent units across rows.
Use a table when visitors compare the same attributes across rows. Include a caption, scoped headings, and consistent units.
Keep horizontal overflow in the table region on narrow screens. Make the region focusable and keep row labels short.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Use a table when visitors compare the same attributes across rows. Include a caption, scoped headings, and consistent units.
  • Keep horizontal overflow in the table region on narrow screens. Make the region focusable and keep row labels short.
Content fields
  • caption (text, required). Name the comparison.
  • columns (list of text, required). Order the shared attributes consistently.
  • rows (list of row headings and cells, required). Include the same attributes and consistent units across rows.
Token references
color.whitecolor.offWhitecolor.linenradius.controlstypography.core.smallText

Notices and states

Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.

Announcement banner

A single link for a timely launch or announcement.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-announcement" href="https://aisearchstandard.org/">
    Read the AI Search Measurement Standard <span aria-hidden="true">→</span>
  </a>
</div>
View prompt
Use the AirOps announcement banner variant from /elements#feedback-banner (feedback/banner).
A single link for a timely launch or announcement.
Use the following content fields.
- heading (text, required). Name the announcement, status, or problem in plain language.
- message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
- action (link | action, optional). Provide the relevant destination or recovery action.
Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Inline notice

Share context beside the content or action it affects.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <aside class="brand-notice" aria-label="Registration information">
    <strong>Recording included</strong>
    <p>We’ll send the replay to registered attendees after the event.</p>
  </aside>
</div>
View prompt
Use the AirOps inline notice variant from /elements#feedback-alert (feedback/alert).
Share context beside the content or action it affects.
Use the following content fields.
- heading (text, required). Name the announcement, status, or problem in plain language.
- message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
- action (link | action, optional). Provide the relevant destination or recovery action.
Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Empty state

Explain why a listing has no results and give the reader a way forward.

No matching resources

Try a broader topic or browse the full resource collection.

Browse all resources

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <section class="brand-empty">
    <h4>No matching resources</h4>
    <p>Try a broader topic or browse the full resource collection.</p>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/blog">Browse all resources <span aria-hidden="true">→</span></a>
  </section>
</div>
View prompt
Use the AirOps empty state variant from /elements#feedback-empty (feedback/empty).
Explain why a listing has no results and give the reader a way forward.
Use the following content fields.
- heading (text, required). Name the announcement, status, or problem in plain language.
- message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
- action (link | action, optional). Provide the relevant destination or recovery action.
Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Error state

Explain an interruption and offer a recovery path.

Registration is unavailable

Check the event listing for registration details and upcoming sessions.

View events

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <section class="brand-notice brand-notice-error">
    <h4>Registration is unavailable</h4>
    <p>Check the event listing for registration details and upcoming sessions.</p>
    <a class="brand-button brand-button-tertiary" href="https://www.airops.com/events">View events <span aria-hidden="true">→</span></a>
  </section>
</div>
View prompt
Use the AirOps error state variant from /elements#feedback-error (feedback/error).
Explain an interruption and offer a recovery path.
Use the following content fields.
- heading (text, required). Name the announcement, status, or problem in plain language.
- message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
- action (link | action, optional). Provide the relevant destination or recovery action.
Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Loading status

Tell the reader content is on its way.

Loading resources…

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <p class="brand-loading" role="status"><span aria-hidden="true"></span> Loading resources…</p>
</div>
View prompt
Use the AirOps loading status variant from /elements#feedback-loading (feedback/loading).
Tell the reader content is on its way.
Use the following content fields.
- heading (text, required). Name the announcement, status, or problem in plain language.
- message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
- action (link | action, optional). Provide the relevant destination or recovery action.
Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Use a banner for a timely announcement and an inline notice for information that belongs next to a specific action or block.
  • Explain how to recover from errors or empty results. Reserve aria-live or role=alert for updates a visitor needs announced when they occur.
  • Use a loading message when a visitor is waiting. Update the message or announce the outcome once loading completes.
Content fields
  • heading (text, required). Name the announcement, status, or problem in plain language.
  • message (text, optional). Explain the impact or next action. Keep time-sensitive information factual.
  • action (link | action, optional). Provide the relevant destination or recovery action.
Token references
color.deepGreencolor.chalkcolor.linenstroke.defaultradius.pills

Editorial elements

Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.

Editorial metric numbers

42%

Growth in qualified pipeline · Q3

18 hrs

Saved per campaign · Monthly average

3.4×

Return on content investment · FY26

Section heading

Introduce a section with a clear outcome and brief context.

Research

See how AI search is changing

Explore findings about where buyers look and which sources they trust.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <header class="brand-section-heading">
    <p class="brand-eyebrow">Research</p>
    <h4>See how AI search is changing</h4>
    <p>Explore findings about where buyers look and which sources they trust.</p>
  </header>
</div>
View prompt
Use the AirOps section heading variant from /elements#editorial-section-heading (editorial/section-heading).
Introduce a section with a clear outcome and brief context.
Use the following content fields.
- content (text, optional). Supply the heading, label, metric value, or caption the variant calls for. A separator needs no copy.
- context (text, optional). Explain what a metric measures, its period, and the basis for comparison.
Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.
Match heading levels to the page outline and use short tags that carry meaning without relying on their color.
Use approved figures and provide their units and measurement context when publishing a statistic.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Pill and tag

Identify a category or content type in a collection.

ResearchAI search

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <div class="brand-tag-group"><span class="brand-tag">Research</span><span class="brand-tag">AI search</span></div>
</div>
View prompt
Use the AirOps pill and tag variant from /elements#editorial-tag (editorial/tag).
Identify a category or content type in a collection.
Use the following content fields.
- content (text, optional). Supply the heading, label, metric value, or caption the variant calls for. A separator needs no copy.
- context (text, optional). Explain what a metric measures, its period, and the basis for comparison.
Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.
Match heading levels to the page outline and use short tags that carry meaning without relying on their color.
Use approved figures and provide their units and measurement context when publishing a statistic.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Statistic

Present one contextualized measurement.

12
Example count of pages reviewed in a quarterly content audit

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <figure class="brand-statistic">
    <strong>12</strong>
    <figcaption>Example count of pages reviewed in a quarterly content audit</figcaption>
  </figure>
</div>
View prompt
Use the AirOps statistic variant from /elements#editorial-statistic (editorial/statistic).
Present one contextualized measurement.
Use the following content fields.
- content (text, optional). Supply the heading, label, metric value, or caption the variant calls for. A separator needs no copy.
- context (text, optional). Explain what a metric measures, its period, and the basis for comparison.
Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.
Match heading levels to the page outline and use short tags that carry meaning without relying on their color.
Use approved figures and provide their units and measurement context when publishing a statistic.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Separator

Mark the transition between distinct topics.

Evaluate your visibility


Prioritize pages to improve

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <div class="brand-divider-example">
    <p>Evaluate your visibility</p>
    <hr class="brand-divider">
    <p>Prioritize pages to improve</p>
  </div>
</div>
View prompt
Use the AirOps separator variant from /elements#editorial-divider (editorial/divider).
Mark the transition between distinct topics.
Use the following content fields.
- content (text, optional). Supply the heading, label, metric value, or caption the variant calls for. A separator needs no copy.
- context (text, optional). Explain what a metric measures, its period, and the basis for comparison.
Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.
Match heading levels to the page outline and use short tags that carry meaning without relying on their color.
Use approved figures and provide their units and measurement context when publishing a statistic.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Use section headings to orient readers, tags to identify categories, and separators to mark meaningful transitions.
  • Match heading levels to the page outline and use short tags that carry meaning without relying on their color.
  • Use approved figures and provide their units and measurement context when publishing a statistic.
Content fields
  • content (text, optional). Supply the heading, label, metric value, or caption the variant calls for. A separator needs no copy.
  • context (text, optional). Explain what a metric measures, its period, and the basis for comparison.
Token references
color.inkcolor.deepGreencolor.linentypography.core.h3typography.core.metaspacing

Media

Choose image crops and video posters that support the surrounding message. Preserve a consistent aspect ratio across a collection.

Image with caption

Add visual context or document an image credit.

A street between tall buildings in a city
From the AirOps editorial image library

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <figure class="brand-media-figure">
    <img src="/brand/image-library/brand-story-city.jpg" alt="A street between tall buildings in a city" width="960" height="540" loading="lazy">
    <figcaption>From the AirOps editorial image library</figcaption>
  </figure>
</div>
View prompt
Use the AirOps image with caption variant from /elements#media-image (media/image).
Add visual context or document an image credit.
Use the following content fields.
- image (image URL and alt text, required). Use an approved asset and meaningful alt text for informative imagery.
- caption (text, optional). Use a caption when context or credit is needed.
- video (player URL and title, optional). Required for the video variant. Use an approved player and include captions.
Choose image crops and video posters that support the surrounding message. Preserve a consistent aspect ratio across a collection.
Provide a labeled play link and a captioned source video. Leave playback under the visitor’s control.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.

Video poster

Introduce a customer video and let visitors choose when to play it.

View code
<!-- Include the shared stylesheet once per page. -->
<link rel="stylesheet" href="/brand/elements.css">

<div class="ao-elements">
  <a class="brand-media-figure brand-video-poster" href="https://player.mediadelivery.net/play/658936/e887b5e5-9bcd-4d37-bcf9-d1f3358e2ba3">
    <span class="brand-video-frame">
      <img src="https://www.airops.com/images/nick-fairbain_1.avif" alt="" width="960" height="540" loading="lazy">
      <span class="brand-play" aria-hidden="true">▶</span>
    </span>
    <span>Watch the Chime customer story</span>
  </a>
</div>
View prompt
Use the AirOps video poster variant from /elements#media-video (media/video).
Introduce a customer video and let visitors choose when to play it.
Use the following content fields.
- image (image URL and alt text, required). Use an approved asset and meaningful alt text for informative imagery.
- caption (text, optional). Use a caption when context or credit is needed.
- video (player URL and title, optional). Required for the video variant. Use an approved player and include captions.
Choose image crops and video posters that support the surrounding message. Preserve a consistent aspect ratio across a collection.
Provide a labeled play link and a captioned source video. Leave playback under the visitor’s control.
Use the variant markup and shared stylesheet /brand/elements.css from /elements/catalog.json. Replace sample copy, assets, and destinations with approved content. Check the result at narrow and wide breakpoints.
Usage and page block examples
  • Choose image crops and video posters that support the surrounding message. Preserve a consistent aspect ratio across a collection.
  • Provide a labeled play link and a captioned source video. Leave playback under the visitor’s control.
Content fields
  • image (image URL and alt text, required). Use an approved asset and meaningful alt text for informative imagery.
  • caption (text, optional). Use a caption when context or credit is needed.
  • video (player URL and title, optional). Required for the video variant. Use an approved player and include captions.
Token references
color.canvascolor.deepGreencolor.offWhiteradius.contentCardstroke.default

Accessibility

  • Keyboard focus remains visible.
  • Text and controls maintain readable contrast.
  • Status is never communicated by color alone.
  • Labels describe the action or field meaningfully.
  • Heading order stays semantic.
  • Components are checked at their intended viewport and zoom.

Page recipes

Choose a page goal, follow the suggested block order, then use the element variants above for individual controls and content.

All page recipes