Page blocks

Full-screen hero

Loading preview…
When to use

Introduce AirOps and its primary conversion path on the homepage.

Duplicate the approved homepage hero only for home-style pages. Confirm the media, motion and form dependencies in Webflow.

Required content
H1, supporting copy, and primary action.
Optional content
Approved hero media and lead-capture variant.
Variants and states
Media-led homepage hero. Use the solution hero for a focused audience or channel.
Responsive behavior
Keep the primary copy above the fold and verify media crop and contrast.
Accessibility
Use one H1 and a readable still treatment.
Dependencies
Approved hero artwork and conversion destination.

Authoring fields headingdescriptionprimaryActioneyebrowmediaform

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Announcement bar

When to use

Highlight a time-sensitive launch or announcement in a rounded link.

Reuse the announcement slot above the global header. Confirm expiration and campaign attribution.

Required content
Short announcement and one destination.
Optional content
Campaign label and end date.
Variants and states
Single linked message, with the bar omitted when there is no active announcement.
Responsive behavior
Let the message wrap without covering the main navigation.
Accessibility
Give the link a meaningful destination label. Keep the announcement in reading order.
Dependencies
Shared header and approved destination.

Authoring fields messagedestinationexpiresAt

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Customer logo rail

When to use

Show an approved set of customer marks alongside a claim.

Reuse the shared logo rail and approved logo set. The portable example uses text fixtures.

Required content
Approved marks and accessible company names.
Optional content
Proof label.
Variants and states
Production marquee or static rail.
Responsive behavior
Use a wrapping rail or the approved animation. Keep logo sizes legible.
Accessibility
Expose each company name once and support reduced motion.
Dependencies
Approved marks and permission for their use.

Authoring fields customersheading

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Thesis text

When to use

State the shift in the market and give readers one reason to learn more.

Reuse the homepage thesis section. Keep the statement and its follow-up link in the same content wrapper.

Required content
One editorial statement and a clear destination.
Optional content
Contextual secondary action.
Variants and states
Centered thesis with an outlined link and scroll-driven word reveal.
Responsive behavior
Keep the original centered measure, with natural line breaks and a legible link.
Accessibility
Expose a complete heading at every viewport. Text reveal, if enabled, must respect reduced-motion preferences.
Dependencies
Approved narrative copy and Why AirOps destination.

Authoring fields thesisactionsupportingAction

The published layout uses local code for its scroll effects in this preview.

Four-part story

When to use

Explain how AirOps helps a team move from understanding the market to executing a strategy.

Reuse the homepage playbook section. Populate the existing four rows, maintaining their order and media alignment.

Required content
Section heading and exactly four chapters, each with a heading and explanation.
Optional content
Intro, approved illustrations, and a progress accent.
Variants and states
Four consecutive homepage chapters with alternating copy and media.
Responsive behavior
Preserve the chapter order and keep each visual associated with its explanation when the layout stacks.
Accessibility
Use a heading for every chapter and keep essential information in text. Respect reduced motion for progress effects.
Dependencies
Approved illustrations and production scroll effects when used.

Authoring fields headingchaptersintroductionprogressIndicator

The published layout uses local code for its scroll effects in this preview.

Customer testimonial grid

When to use

Lead with a customer video and reinforce it with a logo rail and supporting customer quotes.

Reuse the homepage testimonial section. Confirm video permission, poster, quote attributions, and all customer logos before publishing.

Required content
Featured customer quote, attribution, logo, approved video, and supporting quotes.
Optional content
Logo rail and links to case studies.
Variants and states
Featured video card with a mosaic of supporting logos and quotes.
Responsive behavior
Stack the featured quote and video on small screens and keep the supporting quotes in reading order.
Accessibility
Give the poster link a descriptive name and provide captions on the approved video.
Dependencies
Approved quotes, logos, video, poster and the shared marquee for the logo rail.

Authoring fields featuredTestimonialvideosupportingTestimonialslogoscaseStudyLinks

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Research scroller

When to use

Pair a short list of reports with a sticky visual panel that updates during scrolling.

Reuse the homepage research section. Bind each report row to its corresponding visual and scroll trigger by position.

Required content
Section heading and an ordered list of reports, each with title, summary, link, and visuals.
Optional content
Section introduction and scroll progress.
Variants and states
Linked sticky report views on desktop and stacked report cards on narrower screens.
Responsive behavior
Keep image and text order in sync on desktop. Show each report’s media with its text when stacked.
Accessibility
Keep report links keyboard reachable and allow direct selection from the report headings. Keep summaries available on mobile.
Dependencies
Published report links, approved report images, and the scroll behavior paired to the report order.

Authoring fields headingreportsintroductionshowProgress

The published layout uses local code for its scroll effects in this preview.

Pricing cards

When to use

Help buyers identify which plan fits their team.

Reuse the Pricing plan presentation and check terms and destinations against the owner’s current source.

Required content
Plan names, intended audience, key capabilities, and plan-specific CTA.
Optional content
Price, billing terms, or an approved recommendation.
Variants and states
Self-serve and sales-led plans.
Responsive behavior
Stack cards or use the existing mobile plan selector.
Accessibility
Distinguish CTA destinations in accessible names. Keep price qualifiers visible.
Dependencies
Current commercial terms and approved links.

Authoring fields planscommercialTerms

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Half-screen hero

When to use

Introduce a marketing page with a focused headline and a compact opening section.

Reuse the Pricing page opener. Replace the headline, supporting copy, and actions with the approved content for the page.

Required content
Page heading and supporting message.
Optional content
Eyebrow and approved actions.
Variants and states
Compact centered hero, sourced from Pricing.
Responsive behavior
Let the heading and actions wrap while leaving room for the section below.
Accessibility
Use one H1 and clear action labels.
Dependencies
Approved copy and action destinations.

Authoring fields headingdescriptioneyebrowactions

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Form hero

When to use

Lead with an offer and collect one response in the same section.

Reuse the Newsletter opener. Connect the approved form and check its confirmation and error states in the publishing environment.

Required content
Page heading, offer, labeled form, and primary action.
Optional content
Eyebrow, proof line, and supporting visual.
Variants and states
Split hero with an email form and editorial visual, sourced from the newsletter.
Responsive behavior
Keep the form with its supporting copy and stack the visual below it.
Accessibility
Use visible input labels and announce validation or submission status.
Dependencies
Approved form, routing, consent copy, and confirmation.

Authoring fields headingofferformactionLabeleyebrowvisualproof

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Card

When to use

Group a short explanation, visual, and destination into one reusable marketing surface.

Reuse the shared Card and Card body. Preserve the image slot and link destination, then place it inside the supported grid.

Required content
Title, concise description, and a clear destination.
Optional content
Image or illustration and supporting label.
Variants and states
Linked card with the original AirOps card and card-body hierarchy.
Responsive behavior
Keep the card content in reading order and let the card fit its container.
Accessibility
Use a meaningful heading and link name. Supply alternative text for informative imagery.
Dependencies
Approved media, destination, and shared card classes.

Authoring fields titledescriptiondestinationmediaeyebrow

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Global footer

When to use

Give visitors consistent resource, support, and legal links at the end of a page.

Use the shared Footer instance. Review new links centrally so all pages stay consistent.

Required content
Brand link, named link groups, and legal links.
Optional content
Social channels and contact link.
Variants and states
Shared footer with centrally managed groups.
Responsive behavior
Stack link groups in the same reading order on mobile.
Accessibility
Use a footer landmark, group headings, and descriptive link names.
Dependencies
Approved shared destinations and legal routes.

Authoring fields brandLinklinkGroupslegalLinkscontactsocialLinks

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Global navigation

When to use

Provide consistent site destinations and the primary contact action.

Insert the shared Nav instance in the page shell. Verify any changes to shared destinations with the site owner.

Required content
Logo or wordmark, main destinations, and shared CTA.
Optional content
Grouped resources and sign-in.
Variants and states
Inline links and grouped destinations.
Responsive behavior
Wrap links and preserve the disclosure at narrow widths.
Accessibility
Use semantic navigation and named links. Keep grouped navigation keyboard operable.
Dependencies
Shared marketing header. Contact and sign-in destinations.

Authoring fields brandLinkprimaryLinksprimaryActionlinkGroupssignIn

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Section and destination navigation

When to use

Guide readers to adjacent product and strategy destinations.

Use the shared Main Pages Nav where the template calls for those destinations.

Required content
Named group and two or more distinct destinations.
Optional content
Short contextual description per link.
Variants and states
Shared linked cards and inline page navigation.
Responsive behavior
Stack long destination names and keep links visually distinct.
Accessibility
Name the navigation landmark and accurately describe each destination.
Dependencies
Current marketing URLs and navigation priorities.

Authoring fields headinglinksdescriptions

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Feature split

When to use

Explain one capability through a concrete outcome and visual proof.

Reuse the closest narrative split on Solutions and populate the copy, media and optional action slots.

Required content
Outcome headline, description, and visual or media.
Optional content
Supporting points and contextual link.
Variants and states
Light, dark, and mirrored sections. Keep a consistent content order.
Responsive behavior
Stack text before its illustration. Keep labels readable without zoom.
Accessibility
Preserve the heading hierarchy and provide a text equivalent for meaningful data.
Dependencies
Approved product or editorial image.

Authoring fields headingdescriptionmediasupportingPointsaction

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Feature card grid

When to use

Present related capabilities at the same level of importance.

Use the card and card-body instances inside the page section. Choose variants consistently across cards.

Required content
Section heading plus two or more titled cards.
Optional content
Supporting visuals and links.
Variants and states
Static capability grid or linked solution cards.
Responsive behavior
Allow cards to wrap and keep all content visible.
Accessibility
Use a real heading for each card and meaningful link text.
Dependencies
Approved capability copy and assets.

Authoring fields headingcardsaction

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Interactive product showcase

When to use

Show multiple perspectives on one workflow or capability.

Reuse the Platform showcase and bind the existing view controls to their corresponding content and media.

Required content
Labeled views, a screenshot or mockup per view, and a short explanation.
Optional content
Product link and caption.
Variants and states
Market, owned content, and external content views. Portable demo uses native disclosures.
Responsive behavior
Keep view labels visible and media legible at narrow widths.
Accessibility
Use keyboard-operable controls and associate each view with its panel.
Dependencies
Production switcher and approved product media.

Authoring fields headingviewsproductLinkcaption

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

FAQ accordion

When to use

Answer specific questions about the page’s offer.

Reuse the existing FAQ section and populate its question and rich-text slots.

Required content
Question and answer pairs.
Optional content
Links to approved sources in answers.
Variants and states
Collapsed and expanded disclosure, with one or multiple answers open according to the production template.
Responsive behavior
Let long questions and answers wrap.
Accessibility
Provide keyboard and touch operation, prominent focus, and a clear expanded state.
Dependencies
Existing accordion and approved answers.

Authoring fields questionsheadingsupportingLinks

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Customer testimonial

When to use

Support a claim with a specific customer experience.

Reuse the quote section from Home or Enterprise. Confirm exact wording and attribution before publishing.

Required content
Approved quote, person name, title and company.
Optional content
Portrait or case study link.
Variants and states
Single quote or multi-quote sequence.
Responsive behavior
Allow long quotes and attribution to wrap independently.
Accessibility
Use a blockquote and readable attribution. Label any carousel navigation.
Dependencies
Customer approval and source evidence.

Authoring fields quotenametitlecompanyportraitcaseStudy

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Customer story card

When to use

Introduce a customer story through an approved outcome or metric.

Use the Customer Stories listing card. Fill metric and label only when both were approved together.

Required content
Customer, outcome headline, and destination.
Optional content
Verified metric, supporting label, logo, or cover image.
Variants and states
Featured lead card or compact listing card.
Responsive behavior
Keep the metric and its label together on narrow screens.
Accessibility
Keep the metric available as text and use a descriptive story link.
Dependencies
Case study and approved claims.

Authoring fields customerheadingstorymetricmetricLabelcover

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Comparison table

When to use

Compare plans, products, or approaches using consistent evaluation criteria.

Reuse the appropriate Pricing or Compare matrix and document the source and date for commercial claims.

Required content
Column labels, named criteria, and evidence for each claim.
Optional content
Definitions, source links, and category grouping.
Variants and states
Plan feature matrix and competitor comparison. Sample cells use placeholders.
Responsive behavior
Retain headers when scrolling or selecting a plan.
Accessibility
Provide a caption, row and column scope, and text for all status values.
Dependencies
Current plan or competitor evidence.

Authoring fields captioncolumnsrowsevidencedefinitions

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Competitor comparison summary

When to use

Communicate the practical tradeoffs before a detailed comparison.

Reuse a comparison landing-page section. Cite current evidence for each claim and route the primary CTA consistently.

Required content
Named comparison, audience-fit summary, and evidence-linked differences.
Optional content
Review context or product preview.
Variants and states
Competitor hero or evaluation summary.
Responsive behavior
Stack the claims and keep any supporting media secondary.
Accessibility
Use a logical heading and text labels for all comparisons.
Dependencies
Reviewed competitor and product claims.

Authoring fields headingaudienceFitclaimsreviewmedia

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Featured resource

When to use

Draw attention to one timely article, recap, or report.

Use the featured item treatment from the Blog, Research, or Customer Stories index and pin a current record.

Required content
Title, description, destination, and approved cover asset.
Optional content
Category, date, and author.
Variants and states
Featured article, report, or story with an optional metric.
Responsive behavior
Stack the asset and copy while maintaining reading order.
Accessibility
Use one clear link target and meaningful media text.
Dependencies
Published source resource and approved cover.

Authoring fields headingexcerptresourcecovercategorydateauthor

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Resource card and grid

When to use

Display a collection of articles, research, or prompts.

Reuse the collection’s listing card and keep the visible fields tied to the collection data.

Required content
Title, destination, and usable category or collection context.
Optional content
Excerpt, image, date, author.
Variants and states
Compact article, featured report, and recap cards.
Responsive behavior
Use a single column on narrow screens and allow variable copy lengths.
Accessibility
Give the card link a name tied to its title. Avoid nested interactive links.
Dependencies
Published content records and resolved URLs.

Authoring fields headingresourcecollectionexcerptcoverdateauthor

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Filterable resource listing

When to use

Help visitors narrow a collection by topic, event type, or search.

Use the appropriate collection filter and confirm how it interacts with search, pagination and empty results.

Required content
Result records, a category vocabulary, and clear search or filter labels.
Optional content
Multiple facets, pagination, and result counts.
Variants and states
Editorial topics, event type, glossary search, and a no-results state.
Responsive behavior
Place filters above results and keep reset options reachable.
Accessibility
Label every filter. Announce changes and show a meaningful empty state without moving focus.
Dependencies
Production CMS query and collection filter behavior. The example filters local sample records.

Authoring fields recordscategoriessearchLabelfacetspagination

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Collection pagination

When to use

Move through a long listing using navigable page URLs.

Reuse the existing pagination instance and verify how the target template preserves filter values.

Required content
Current page and available previous or next destinations.
Optional content
Numbered pages and a total count.
Variants and states
Next-only listing and previous/next navigation.
Responsive behavior
Keep next and previous visible with fewer numbered links if needed.
Accessibility
Name the landmark, identify the current page, and use real links.
Dependencies
Target collection’s pagination URL and query behavior.

Authoring fields currentPagedestinationstotalPages

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Article byline

When to use

Attribute an article or report to its contributors.

Use the article metadata slots. Validate the author reference and date in the actual article template.

Required content
Author name and published date. If sourced from the documented Sanity author model, populate its required fields.
Optional content
Updated date, portrait, and link to author profile.
Variants and states
Single and multiple authors. Title and company appear where the template supports them.
Responsive behavior
Wrap contributor and metadata rows without reordering them.
Accessibility
Use machine-readable dates and include descriptive names for author links.
Dependencies
Author record, approved profile destination, and date formatting.

Authoring fields authorpublishedAtupdatedAtprofile

Verified authors schema

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Article table of contents

When to use

Give readers a way to navigate a long article or report.

Reuse the article TOC and confirm generated links match the rendered headings.

Required content
Headings and matching unique anchor IDs.
Optional content
Nested subsection links.
Variants and states
Visible table of contents and collapsible mobile disclosure.
Responsive behavior
Keep section links reachable without covering the article.
Accessibility
Use a named navigation landmark with descriptive links and maintain heading order.
Dependencies
Template-generated heading anchors.

Authoring fields headingLinksnestedLinks

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Editorial article body

When to use

Present a structured long-form article or report.

Use the article template’s rich-text body and check embeds, table headers, and source links in preview.

Required content
Body copy, meaningful headings, and verified sources for factual claims.
Optional content
Images, figures, callouts, inline tables, and pull quotes.
Variants and states
Article, research report, and technical explainer.
Responsive behavior
Keep paragraphs readable and allow long tables to scroll within the block.
Accessibility
Keep headings in order and label non-text content and tables.
Dependencies
Template rich-text renderer, asset pipeline, and linking policy.

Authoring fields bodysourcesmediatables

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Breadcrumb navigation

When to use

Show where a nested detail page sits in a collection.

Reuse the template or partner breadcrumb and link to the correct parent collection.

Required content
Parent names and URLs, plus the current page label.
Optional content
Additional meaningful hierarchy levels.
Variants and states
Template, partner, and related nested detail paths.
Responsive behavior
Wrap long link or page names and preserve order.
Accessibility
Name the navigation and identify the current page without requiring it to be a link.
Dependencies
Actual route hierarchy.

Authoring fields parentscurrentPage

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Event card

When to use

Help visitors choose an upcoming event or replay.

Use the event listing card and verify date, time zone and whether the destination is registration or replay.

Required content
Title, event type, destination, and date or replay status.
Optional content
Time zone, location, speaker, cover.
Variants and states
Webinar, in-person, and replay.
Responsive behavior
Keep status and date near the title.
Accessibility
Express status in text and provide a descriptive link.
Dependencies
Official event schedule and approved event asset.

Authoring fields headingeventTypeeventstatusdateTimetimezonelocationcover

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Event registration section

When to use

Collect registrations for one event with a clear date and next step.

Use the event-detail form slot. Swap it for replay or closed-registration content once the event ends.

Required content
Event name, date, time zone, and approved registration path.
Optional content
Speaker, agenda, location, consent copy.
Variants and states
Open registration, closed registration, and replay.
Responsive behavior
Move details above the form when stacked.
Accessibility
Keep field labels, valid date information, and submission feedback available to assistive technology.
Dependencies
Event form owner, registration destination, confirmation, and tracking.

Authoring fields eventNamedateTimetimezoneregistrationspeakeragendaconsentCopy

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Research download section

When to use

Connect an overview or report to the full research artifact.

Reuse the report download treatment. Check whether the source report uses a direct link or a gated follow-up.

Required content
Report title, format, value proposition, and current file or approved capture route.
Optional content
Cover image, file size, methodology, or an access form.
Variants and states
Direct download and gated download.
Responsive behavior
Keep the action and file details grouped.
Accessibility
Name the document and format in the destination label.
Dependencies
Published artifact and, where applicable, an approved form and delivery workflow.

Authoring fields reportTitleformatsummaryreportcoverfileSizemethodologyform

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Research highlights rail

When to use

Introduce several featured reports and let a visitor choose what to read.

Start from the Research hub featured list or the homepage research highlight treatment.

Required content
Report titles, summaries, and destinations.
Optional content
Report cover, topic, and publication date.
Variants and states
Research hub gallery or homepage highlights.
Responsive behavior
Wrap features into a vertical sequence and preserve reading order.
Accessibility
Keep titles and links text-based. Provide keyboard navigation if using a moving presentation.
Dependencies
Current selection of published research.

Authoring fields reportsheadingtopic

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Closing conversion section

When to use

Close the page with one clear action tied to the visitor’s intent.

Reuse the shared CTA. Confirm destination, accessibility and any form follow-up.

Required content
Headline, supporting context, and action.
Optional content
Work-email capture.
Variants and states
Linked action and single-field capture.
Responsive behavior
Stack action and input when necessary.
Accessibility
Label inputs and announce form feedback.
Dependencies
Approved destination, consent, tracking, and existing form integration when used.

Authoring fields headingdescriptionactionform

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Lead capture form

When to use

Capture contact information for a specified next step.

Use the existing form embed and the correct form ID for the campaign. Test submissions in a safe preview with the form owner.

Required content
Purpose, labeled fields, submit action, and routed confirmation.
Optional content
Company field and applicable consent copy.
Variants and states
Single-email capture and multi-field intake. Example shows a local completion state.
Responsive behavior
Stack inputs, action, and feedback on mobile.
Accessibility
Use native validation, programmatic labels and an announced result.
Dependencies
Approved HubSpot form, routing, validation, consent, and analytics.

Authoring fields purposefieldsactionLabelconfirmationroutingconsentCopy

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Newsletter signup

When to use

Give readers a clear reason to subscribe and set expectations.

Use the newsletter form and confirm the list, subscription flow, and approved consent copy.

Required content
Value proposition, labeled email, subscription action, and confirmation.
Optional content
Cadence, example issue, or applicable consent copy.
Variants and states
Standalone signup page and embedded section.
Responsive behavior
Stack form controls when space is limited.
Accessibility
Keep the label visible and announce submission outcomes.
Dependencies
Approved subscriber list and subscription confirmation.

Authoring fields valuePropositionemailLabelactionLabelconfirmationsubscriberListcadenceexampleIssue

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Booking section

When to use

Route a qualified visitor to the approved booking flow.

Use the existing Work with us destination or the campaign’s approved booking integration. Verify routing with the owner.

Required content
Action, next-step expectation, and approved calendar or routing URL.
Optional content
Short eligibility or scheduling note.
Variants and states
Embedded booking and a linked handoff.
Responsive behavior
Allow booking embeds to resize without hiding the fallback link.
Accessibility
Title embeds and provide a keyboard-accessible link alternative.
Dependencies
Approved scheduling or qualification service.

Authoring fields actionnextStepeligibilityembed

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Newsletter issue preview

When to use

Show prospective subscribers what an issue contains.

Use the newsletter preview card and populate it from a representative approved issue.

Required content
Sender or publication, subject, and approved excerpt.
Optional content
Issue date and public archive link.
Variants and states
Sample issue card and archive teaser.
Responsive behavior
Allow sender, subject, and excerpt to wrap.
Accessibility
Make the preview text readable without an image. Give issue links meaningful labels.
Dependencies
Approved public excerpt and archive URL, if provided.

Authoring fields publicationsubjectexcerptissueDatearchive

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Program or offer eligibility

When to use

Help visitors determine whether a program or promotion applies to them before they act.

Use the eligibility section or offer body from the appropriate campaign, then validate the latest criteria and destination with the owner.

Required content
Approved criteria, next step, and a current destination.
Optional content
Application window, terms link, and review timeline.
Variants and states
Program application criteria and time-limited offer terms.
Responsive behavior
Keep criteria and any time limit close to the action.
Accessibility
Use literal text for requirements and deadlines. Explain ambiguous criteria beside the action.
Dependencies
Current program or offer terms and an approved handoff.

Authoring fields criteriaactionexpiresAttermstimeline

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Glossary definition

When to use

Explain a term clearly and make structured examples and related entries available.

Create or update a glossary record and let the production template render optional sections when their fields are populated.

Required content
Sanity title and definition.
Optional content
Metaphor, example, key concepts, use cases, benefits, FAQs, and related terms.
Variants and states
Short definition or extended entry with populated optional sections.
Responsive behavior
Keep definitions and examples in one readable flow.
Accessibility
Use clear heading levels and descriptive related-term links.
Dependencies
Sanity glossary schema and route mapping.

Authoring fields titledefinitionmetaphorexampleuseCaseskeyConceptsrelatedTerms

Verified glossary schema

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Prompt example block

When to use

Give readers a sample prompt and explain the context needed to adapt it.

Use the prompt detail layout. Keep the prompt and commentary separate and resolve placeholders before use.

Required content
Prompt text, purpose, and clearly indicated placeholders.
Optional content
Input example, output description, or related prompts.
Variants and states
Single example and topic-grouped prompt list.
Responsive behavior
Wrap long prompt text and preserve paragraph breaks.
Accessibility
Make prompts selectable text and include instructions outside the example.
Dependencies
Published prompt entry or approved sample content.

Authoring fields promptpurposeplaceholderssampleInputexpectedOutputrelatedPrompts

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Topic resource hub

When to use

Orient readers around a topic and give them clear paths to supporting material.

Reuse the topic-hub layout and confirm that each child page belongs in that collection.

Required content
Topic definition and grouped resource links.
Optional content
Webinars, FAQs, or suggested next step.
Variants and states
Topic overview and hub with several supporting resource groups.
Responsive behavior
Keep groups in reading order and wrap links.
Accessibility
Label each resource group and distinguish repeated link destinations.
Dependencies
Approved topic taxonomy and current resource links.

Authoring fields topicdefinitionresourceGroupsfaqsaction

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Directory search and results

When to use

Help visitors find a named item or organization in a directory.

Use the directory’s approved search and query layer. Verify the empty state and how results resolve to detail routes.

Required content
Labeled search, result name and destination, and no-results feedback.
Optional content
Domain, metrics, result count, and categories.
Variants and states
Brand or domain search, taxonomy filter, and empty state.
Responsive behavior
Place search above results and keep row labels visible.
Accessibility
Announce result counts and keep search and destination links keyboard reachable.
Dependencies
Approved directory data source and search behavior. Example uses local sample records.

Authoring fields searchLabelresultsemptyMessagecategoriesresultCount

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Product demonstration embed

When to use

Place a maintained web UI asset inside a marketing feature section.

Use the checked-in embed instructions and confirm which embed revision appears on the intended live route. The example shows a self-contained fixture.

Required content
Approved embed URL, an iframe title, and supported parent domain.
Optional content
Caption, fallback link, and auto-resize behavior.
Variants and states
Static fixture, native webpage embed, or maintained iframe asset.
Responsive behavior
Verify width, minimum height, and scrolling at the target breakpoints.
Accessibility
Use a meaningful iframe title and provide a readable summary or fallback.
Dependencies
Embed host, parent-origin policy, and any supported sizing integration.

Authoring fields embedUrltitleallowedParentOrigincaptionfallbackresizeBehavior

Embed source and integration instructions

This portable example uses sample content. Its published AirOps capture is pending.

Release note entry

When to use

Explain a shipped change and route readers to the relevant details.

Reuse the changelog entry. Set the date and check the shareable link before publishing.

Required content
Release title, date, summary, and stable anchor.
Optional content
Product area, screenshot, and documentation link.
Variants and states
Major release and shorter maintenance update.
Responsive behavior
Wrap titles while keeping date and release context together.
Accessibility
Use an article heading and machine-readable timestamp.
Dependencies
Confirmed shipped status and published release evidence.

Authoring fields titledatesummaryanchorproductAreamediadocumentation

The gallery shows published AirOps HTML and assets. The live page runs the production scripts and forms.

Page recipes
Implementation reference

Component index

Open Webflow

Read-only audit limited to Homepage, Why AirOps, Platform, and Solutions.

24 components across 4 pages

Section

Layout

Theme-aware page region and outer content boundary.

.section.container.slot.cc-section

Home · Why AirOps · Platform · Solutions

4pages

Content wrap

Layout

Controls content alignment, direction, and internal flow.

.content-wrap-component.slot.cc-content-wrap

Home · Why AirOps · Platform · Solutions

4pages

Grid row

Layout

Responsive twelve-column row with variant-driven alignment.

.row-component.row

Home · Why AirOps · Platform · Solutions

4pages

Grid column

Layout

Width-bearing child of Grid Row. Column size is a component property.

.col.slot.cc-column

Home · Why AirOps · Platform · Solutions

4pages

Card

Layout

Surface, border, radius, overflow, and hover behavior.

.card.slot.cc-card

Home · Why AirOps · Platform · Solutions

4pages

Card body

Layout

Card padding and content alignment. Always nest inside Card.

.card-body.slot.cc-card-body

Home · Why AirOps · Platform · Solutions

4pages

Spacer

Foundation

Variant-controlled vertical rhythm; do not replace with one-off margins.

.spacer-component

Home · Why AirOps · Platform · Solutions

4pages

Border

Foundation

Shared border behavior used between structured content regions.

.u-border

Why AirOps · Platform · Solutions

3pages

Heading

Content

Semantic heading with a selectable visual size.

.heading-component-mast.heading-text

Home · Why AirOps · Platform · Solutions

4pages

Plain text

Content

Body copy with size and maximum-width controls.

.plain-text-component.plain-text

Home · Why AirOps · Platform · Solutions

4pages

Rich text

Content

Long-form and accordion answer formatting.

.rich-text-component.w-richtext

Why AirOps · Platform · Solutions

3pages

Image

Media

Aspect ratio, radius, fit, and optional overlay wrapper.

.image-component.u-img-cover.img-component_bg-overlay

Home · Why AirOps · Platform · Solutions

4pages

Icon

Media

Current-color SVG wrapper paired with Icon Size variants.

.icon.icon-embed

Home · Why AirOps · Platform · Solutions

4pages

Primary button

Actions

Highest-emphasis action. Variant is selected on the Button component.

.btn.btn-icon.btn-text

Home · Why AirOps · Platform · Solutions

4pages

Secondary button

Actions

Webflow: Secondry Button

Outlined action for a supporting path.

.btn.btn-icon.btn-text

Home · Why AirOps · Platform · Solutions

4pages

Text button

Actions

Tertiary, low-chrome action with directional icon support.

.btn.btn-icon.btn-text

Home · Why AirOps · Platform · Solutions

4pages

Navigation

Navigation

Webflow: Nav

Responsive global navigation with fixed and relative modes.

.nav.container.cc-nav.nav-menu.nav-link.nav-bg

Home · Why AirOps · Platform · Solutions

4pages

Main pages nav

Navigation

Card-based navigation for primary site areas.

.card.cc-main-pages-nav

Home · Why AirOps · Platform · Solutions

4pages

Footer

Navigation

Global footer composition and link groups.

.section.cc-footer.footer-flex.footer-link.footer-logo

Home · Why AirOps · Platform · Solutions

4pages

Accordion

Interactive

Progressive disclosure for page-specific FAQs.

.accordion-component

Why AirOps · Platform · Solutions

3pages

Slider

Interactive

Swipeable hero, testimonial, and expert-card tracks.

.swiper-slide.swiper-wrapper

Home · Why AirOps

2pages

Tabs

Interactive

Platform category navigation with separate menu, link, and pane primitives.

.tabs-menu.tabs-link.tabs-pane

Platform

1page

Marquee

Interactive

Continuous customer-logo rail with duplicated groups.

.marquee-component.marquee-wrapper.marquee-content.marquee-group

Home · Why AirOps · Platform · Solutions

4pages

HubSpot single field

Forms

Webflow: Hubspot Single Field Embed

Embedded single-field capture in the shared conversion CTA.

.hubspot-form-embed.cc-single-field

Home · Why AirOps · Platform · Solutions

4pages

Composition

Compose primitives before adding custom classes.

Surface behavior belongs to Card. Padding and alignment belong to Card Body. Content flow belongs to Content Wrap.

1

Card owns surface, border, radius, overflow, and hover.

2

Card Body owns padding and alignment.

3

Content Wrap owns direction and spacing between content.

4

Heading, Plain Text, and Button stay reusable and variant-driven.

Card composition

<div class="card">
  <div class="slot cc-card">
    <div class="card-body">
      <div class="slot cc-card-body">
        <div class="content-wrap-component">…</div>
      </div>
    </div>
  </div>
</div>

Image composition

<div class="image-component">
  <img class="u-img-cover" alt="" src="…">
  <div class="img-component_bg-overlay"></div>
</div>

Button anatomy

<a class="btn" href="…">
  <span class="btn-icon">…</span>
  <span class="btn-text">Work with us</span>
</a>

Class reference

Layout

.section

Page region; receives theme and section-level variants.

.container

Width boundary. Pair with a context class such as cc-nav.

.row

Flex grid row. Grid Row component owns responsive behavior.

.col

Grid column. Width comes from a Webflow component variant.

.slot

Component insertion point; pair with the matching cc-* class.

Content

.heading-component-mast

Heading component wrapper.

.heading-text

Rendered semantic heading; visual size is variant-driven.

.plain-text-component

Plain Text component wrapper and max width.

.plain-text

Rendered body text.

.image-component

Aspect-ratio and radius wrapper.

.u-img-cover

Cover-fit image inside Image.

Actions and navigation

.btn

Shared button surface and interaction root.

.btn-text

Visible label. Keep duplicated animated labels aria-hidden.

.btn-icon

Optional 16px icon slot.

.nav

Global navigation root.

.nav-link

Desktop and mobile navigation link.

.footer-link

Footer link treatment.

Utilities

.u-mode-dark / u-mode-light

Theme text and surface descendants as a group.

.u-w-100 / u-h-100

Fill the available width or height.

.u-text-center

Center text without creating a component variant.

.u-d-flex / u-d-none

Display utilities.

.u-sm-d-none / u-sm-d-block

Small-breakpoint visibility utilities.

.u-font-medium / u-font-semibold

Approved local weight overrides.

.u-link-cover

Expand a link across its positioned parent.

.u-sr-only

Visually hidden, screen-reader-accessible text.

Implementation

01

Use component properties

Choose size, theme, alignment, and behavior in the Webflow component. Never author or depend on generated .w-variant-* GUIDs.

02

Preserve the hierarchy

Keep Section → Container → Row → Column and Card → Card Body → Content Wrap intact. Each layer owns a different layout responsibility.

03

Prefer utilities for one job

Use an approved .u-* utility for a single local adjustment. Create a component or variant when the pattern repeats.

04

Keep semantics independent

Heading visual size is selectable, but the HTML level must follow document hierarchy. Icons inherit currentColor; decorative icons remain hidden from assistive technology.

05

Respect responsive ownership

Base styles live at Desktop. The source library uses 991px, 767px, and 479px down breakpoints, plus 1280px, 1440px, and 1920px up contexts.

06

Bring dependencies with behavior

Accordion, Slider, Tabs, Marquee, HubSpot forms, and animated buttons require their site modules or embeds. Static markup alone is not a complete port.

50pxButton height
16pxButton inline padding
8pxButton radius
22pxCard Body padding
8pxImage radius
12Grid columns

Measured from the authenticated AirOps Webflow Designer at the Desktop base breakpoint. Values shown here describe the audited live homepage instance; component variants and responsive contexts may intentionally override them.