status-page-generator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pages: Status Page

页面类型：Status Page

Guides status page design for communicating service health, uptime, and incidents. Typically at

status.*

subdomain. Reduces support during outages, builds trust.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

用于指导Status Page的设计，以同步服务健康状态、uptime和故障事件。通常部署在

status.*

子域名下，可减少故障期间的咨询量，建立用户信任。

调用规则：首次调用时如果适用，可先用1-2句话说明该技能覆盖的内容及其价值，再提供核心输出。如果是后续调用或者用户要求跳过说明，直接给出核心输出即可。

Initial Assessment

初步评估

Check for product marketing context first: If

.claude/product-marketing-context.md

.cursor/product-marketing-context.md

exists, read it for product and service components.

Identify:

Service components: API, dashboard, billing, etc.
Monitoring: What tools feed status (PagerDuty, Datadog, etc.)
Audience: Customers, developers, internal
Hosting: Self-hosted vs. third-party (Statuspage, Better Uptime, etc.)

优先检查产品营销上下文：如果存在

.claude/product-marketing-context.md

或

.cursor/product-marketing-context.md

文件，请先读取文件内容，了解产品和服务组件信息。

需要识别的信息：

服务组件：API、dashboard、计费模块等
监控工具：为状态页提供数据的工具（PagerDuty、Datadog等）
受众：客户、开发者、内部人员
部署方式：自托管 vs 第三方服务（Statuspage、Better Uptime等）

Status Page Structure

Status Page 结构

Section	Purpose
Overall status	Operational, Degraded, Outage, Maintenance
Components	Per service: status, uptime %
Incidents	Active and past; timeline, updates
Subscribe	Email, SMS, RSS for notifications
Uptime history	90-day or custom range (optional)

板块	用途
整体状态	正常运行、性能下降、服务中断、维护中
服务组件	每个服务的单独状态、uptime百分比
故障事件	活跃和历史故障，包含时间线、更新说明
订阅功能	支持通过邮箱、短信、RSS获取通知
uptime历史	90天或自定义时间范围的历史数据（可选）

Best Practices

最佳实践

Communication

沟通层面

Clear status: Operational, Degraded, Partial Outage, Major Outage
Incident updates: Timely, honest, actionable
Post-mortem: Link to post-incident review when public
Maintenance: Schedule ahead, notify subscribers

状态定义清晰：正常运行、性能下降、部分中断、严重中断
故障更新：及时、坦诚、提供可执行的应对方案
故障复盘：公开的故障事后回顾报告可添加对应链接
维护通知：提前排期，通知所有订阅用户

Design

设计层面

Scannable: Status at a glance; green/yellow/red
Mobile: Critical for on-the-go checks
Accessible: Color + text; don't rely on color alone
No login required: Public status, no auth

易扫读：一眼就能看清状态，使用绿/黄/红配色标识
移动端适配：方便用户随时随地查看状态
可访问性：同时使用颜色+文字标识，不要仅依赖颜色区分状态
无需登录：公开状态页不需要身份验证即可访问

Technical

技术层面

Independent hosting: Status page should stay up when main product is down
Subdomain: status.yourdomain.com
Integrations: Slack, PagerDuty, etc. for incident creation
Historical data: Uptime %, incident count

独立部署：Status Page要在主产品故障时仍可正常访问
子域名部署：使用status.yourdomain.com作为访问地址
集成能力：支持对接Slack、PagerDuty等工具自动创建故障事件
历史数据：存储uptime百分比、故障次数等数据

Output Format

输出格式

Structure (components, incident format)
Status definitions and colors
Incident template (title, updates, resolution)
Subscribe options
Hosting recommendation (self vs. third-party)

结构：服务组件、故障事件展示格式
状态：定义说明和对应配色
故障模板：标题、更新记录、解决说明
订阅：可选的订阅渠道
部署建议：自托管或第三方服务的选择建议