AddThisFeature

Announcement Bar

Put a timed message across the top of the site without shipping a deploy.

simple Engagement

What it adds

An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.

What your agent is told to do

5
  1. 1

    Extend the existing Service Incident Banner rather than adding a second bar. It already handles scheduling, targeting, dismissal, and severity; this is a marketing-styled variant of the same component, and two independent bars will eventually stack on top of each other.

  2. 2

    Let an operator set the message, an optional link, background and text colours, and a start and end time from an admin screen. Requiring a deploy to run a weekend promotion means it goes live late.

  3. 3

    Insert the bar into the document flow so it pushes fixed headers and sticky navigation down. Overlaying it on top of the header hides navigation on exactly the pages people arrived on.

  4. 4

    Define precedence when an announcement and an incident banner are both active. Show the incident and suppress the promotion; a sale strip above an outage notice looks negligent.

  5. 5

    Do not make the bar a full-width interstitial or an auto-expanding panel. A strip a visitor can read in one line and dismiss in one click is the whole point.

Edge cases it handles

8
  • A dismissal must be remembered per visitor and per announcement, so closing one message does not suppress the next one, and editing the message brings the bar back for people who dismissed the old text.
  • The bar must push fixed and sticky headers down rather than sitting over them, and must release that space cleanly when dismissed without leaving a gap or shifting the page under a scrolling reader.
  • Scheduled start and end times must be entered in a stated zone and evaluated against real time, so a sale that ends at midnight ends at midnight for the audience it was set for, not for the server.
  • Operators will choose colours that make the text unreadable. Compute contrast against the configured background and either warn in the admin screen or force a legible text colour.
  • The bar must be announced to assistive technology as it appears without stealing focus from whatever the visitor is doing, and its close control must be reachable and labelled by keyboard.
  • An anonymous visitor with no account still needs their dismissal remembered. Store it locally and key it to the announcement identifier, and accept that clearing site data brings it back.
  • On a narrow screen a long message wraps to three lines and eats the viewport. Cap the length in the admin screen and truncate gracefully rather than letting it grow.
  • An expired announcement must disappear on its own. A promotion still showing a week after the sale ended damages more than it ever earned.

Definition of done

9
  • Operators can publish, schedule, edit, and expire an announcement without a deploy.
  • The bar shares the existing banner component rather than being a second independent strip.
  • Fixed and sticky headers are pushed down, not covered, and no layout shift occurs on dismissal.
  • Dismissal is remembered per visitor and per announcement, and resets when the message is edited.
  • Text contrast against any configured background meets the accessible minimum.
  • The bar is announced to screen readers without moving focus, and its close control is keyboard-reachable.
  • An active incident banner takes precedence over a promotional announcement.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.