Use Cases Page

src/pages/use-cases.astro

Purpose

Documents real production issues that only surfaced under real traffic and how Bluebox caught them. Each example is a self-contained card that can be read in 10 seconds or expanded for the full investigation.

Content standards

Card structure (always follow this order):

1. Problem what broke or degraded, in plain language. One or two sentences max.
2. What Bluebox did the investigation steps: detection, hypothesis testing, evidence. Stick to what actually happened.
3. Result quantified outcome. Time to root cause, performance delta, what changed.

Data first:

• Every card must have a measurable win (time saved, latency recovered, defects caught).
• Always show the comparison: with Bluebox vs. without Bluebox / the manual way.
• Numbers should come from the customer or the team who ran the investigation. Do not invent metrics.

Writing rules:

• No marketing language. Write like an engineer explaining what happened.
• Ideally sourced from real customer examples. Blog posts are a valid starting point but not the only source.

Screenshots:

• The expanded view should include screenshots. Each investigation step ideally has a supporting image showing what Bluebox surfaced (telemetry overview, hypothesis table, post-deploy monitoring, etc.).
• Add screenshots to the steps array via the img and imgAlt fields.

Adding a new example

1. Add a new object to the useCases array in use-cases.astro.
2. Follow the existing data shape: id, stage, title, subtitle, accentColor, compact, problem, steps, results, callout, timeComparison, blog.
3. Add it to ucDisplay to control display order.
4. Update astro.config.mjs if sitemap priority needs adjusting.

Roadmap note

Current examples are all investigation-based (detect, diagnose, fix). Once other categories exist (e.g. performance, reliability, security), add a category tag to each card and a filter UI at the top of the page.

Hero copy: The current headline and subtitle are scoped to investigation-based examples, which is all the page shows for now. Keep them as-is until the page has enough variety to justify more generic copy. When adding new categories, revisit both lines so they stay truthful to what the page actually shows.