Skip to content

feat(landing): alerting homepage section + redesigned /features/alerting page#249

Open
Makisuo wants to merge 1 commit into
mainfrom
feat/landing-alerting-page
Open

feat(landing): alerting homepage section + redesigned /features/alerting page#249
Makisuo wants to merge 1 commit into
mainfrom
feat/landing-alerting-page

Conversation

@Makisuo

@Makisuo Makisuo commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

What changed

New homepage section (Alerting.astro) — centered stage with the firing-incident artifact (live/LiveAlertFeed.astro, SSR-only, reduced-motion-gated pulse), chips for every notification destination (Slack, Discord, PagerDuty, email, webhook, Hazel), and a 3-card feature strip. Localized in en/ja/ko (messages + regenerated paraglide output).

Redesigned /features/alerting — rebuilt from hero → single card → text grids to the same quality bar as the Kubernetes feature page:

  • Rule evaluation: a live-frame mock with the rule expression and an SVG evaluation chart — signal crossing the dashed 2% threshold, breach segment in severity-red, "for 5m" persistence bracket, fired marker — connected by an arrow to the resulting incident card. Footer states the preview result plainly.
  • Group fan-out: three region rows (one firing with its delivery log, two quiet), one incident per group.
  • Destinations grid: brand icons + a mono delivery sample line per destination.
  • Incident lifecycle: Triggered → Notified → Renotified → Auto-resolved timeline with severity-colored dots and tabular timestamps.

FAQ/detail-grid/SEO content unchanged so AI-extraction copy stays intact.

Notes for review

  • All mock data is consistent across artifacts (same 4.7% / eu-west-1 incident everywhere).
  • Feature-page copy is hardcoded English, matching the other feature pages; only the homepage section is localized.
  • Verified in the browser at desktop and mobile widths: no horizontal overflow, islands hydrate, no console errors beyond the known Clerk dev-key noise.

🤖 Generated with Claude Code


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.

…ing page

Adds the Alerting homepage section (firing-incident artifact, destination
chips, feature strip) with en/ja/ko messages, and rebuilds the alerting
feature page to the k8s-page quality bar: rule-preview evaluation chart
(threshold + persistence window + fired marker) paired with the live
incident card, a group fan-out artifact, an icon-rich destinations grid
with delivery samples, and an incident-lifecycle timeline.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pullfrog

pullfrog Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Your Pullfrog Router balance is exhausted.

You have a card on file but auto-reload is disabled, so runs paused once your balance went past the overdraft buffer.

Top up balance → · Enable auto-reload →

Pullfrog  | ⚠️ this action is pinned to a commit SHA, which freezes the cleanup step — switch to @v0 or keep the SHA fresh with Dependabot | Rerun failed job ➔View workflow run | via Pullfrog | Using Claude Opus𝕏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant