Banner

​

What it is

“Banner” is the term this documentation’s own pages already use for a message that is about the whole product rather than the page the reader happens to be on — the kind of notice that would still be relevant if the reader navigated somewhere else. Alert’s own page names this job directly: “Announce something across the whole product | Banner | A page-level alert is about this page. Product-wide messages outlive it.” No component fulfilling that job exists in Titan. This was checked, not assumed:

• No directory, file, or export named Banner, Callout, SystemMessage, or similar exists anywhere in the core, legacy-web, or shared packages.
• Neither of the package’s top-level export barrels (index.js and components/index.js) references anything of the kind.
• No Storybook story matching banner, callout, notification, or message exists in the live Storybook index, beyond the unrelated Alerts stories.

​

Live example

None exists. There is nothing to embed.

​

Exports

None. There is no Banner export, themed or unthemed, in any package this checkout covers.

​

Choose Banner when

There is no component to choose. If the underlying need is a message that should reach every user of the product regardless of the page they’re on, that need is real and currently unmet — see Choose something else when for what teams reach for instead today.

​

Choose something else when

​

Anatomy

Not applicable. There is no component.

​

Variants, sizes, and states

Not applicable.

​

Edge and failure states

Not applicable — there is nothing to fail.

​

Tokens

None exist for this concept. If a Banner is composed ad hoc from Alert’s tokens, see Alert’s tokens for what’s actually available; none of it was designed with a product-wide, persistent placement in mind.

​

Composition

Not applicable in the sense of a documented pattern. Anyone building a stand-in today is making an undocumented decision, not following one — see Open issues.

​

Content

Not applicable — no component exists to write content for. If a stand-in is built from Alert, Alert’s content rules are the closest existing guidance, though they were written for a page-scoped message, not a product-wide one.

​

Accessibility

Not applicable. There is nothing shipped to verify.

​

Constraints

​

Known issues

​

Why it works this way

This page exists to close a loop, not to describe a component. Alert’s own page already promises a Banner as the answer to “announce something across the whole product” — a promise made by this same documentation set, not invented here. Leaving that promise unverified would mean a reader follows the link, finds nothing, and cannot tell whether that’s a bug in the docs or a real, confirmed gap. It is the second one: real, checked, and recorded, rather than quietly broken.

​

Status

There is no package, version, or export to report. No Banner component ships in @invoca/titan-core, or in any other package covered by this research, as of this pass.

​

Related

• Alert — the page-scoped message this concept is meant to sit beside, and the component whose own page first names this gap
• Toast — the transient counterpart; also not a substitute for a persistent, product-wide notice