跳到正文
VibeFather
免费注册

用这个模板做的 2 个案例

同一份提示词,不同的 [VARIABLES] 变量。点一个在上方预览。

关于这个模板

服务状态页是一个专注的单页模板,适合那些需要传达可靠性、又不想把系统健康变成营销页面的产品。它适用于 SaaS 团队、开发者平台、在线服务和内部产品,这些团队想要一个清晰的页面来展示当前可用性、组件历史、事件更新和通知偏好。

首屏将一目了然的整体状态信息与详细的 90 天健康面板并排放置。下方有六行组件,对齐当前状态、每日正常运行时间条和精确的样本百分比,让访客可以快速发现问题或查看某种模式。事件部分包括已解决的故障和已完成的维护,每项都有带时间戳的更新,可在可展开的时间线中查看。订阅区域提供邮箱验证、事件和维护偏好设置,以及一个诚实的仅本地成功状态,适合静态演示。

视觉系统使用暖调米白表面、深绿色字体、细边框、紧凑的等宽数据和克制的状态颜色。Manrope、Inter 和 IBM Plex Mono 让标题、说明和测量数据保持区分,同时不会让界面显得杂乱。布局从宽屏的运维仪表盘自适应为移动端可读的堆叠行。固定的样本日期、平实语言的事件更新和无障碍状态标签让页面感觉像在真实运行,而非装饰。

该模板使用 Vite、React、TypeScript 和 Tailwind CSS 构建,不需要后端、第三方 API 或远程资源。变量用于更改品牌、服务类型、受众和支持地址,内容文件则保存组件记录和事件叙述,便于直接调整。CSS 和 Lucide 图标提供完整的视觉层;无需照片或生成的素材。

模板提示词

在线演示就是用这份提示词原样做出来的,没有额外补充。其他案例只是改了 [VARIABLES] 变量的值。 提示词保持英文原版,国内常用的 AI 编程工具都能直接理解;下面附中文参考译文。

# Service Status Page

Build this website exactly as described below. Replace the [VARIABLES] with your own values; keep everything else.

## Brief
Build an original single-page service status website for [BRAND], an invented [SERVICE] for [AUDIENCE]. Present a coherent set of fictional operational data: an overall healthy state, six components with fixed 90-day uptime histories, four resolved or completed incident entries with timestamped updates, and a subscription form with an honest static-demo confirmation. Keep all variable-driven copy, component records, daily status values, and incident narratives in src/content.ts; rewrite the service-specific details when the variables change while preserving the layout, record counts, and interaction model.

- Audience: The primary readers are [AUDIENCE] checking whether [BRAND] is available, plus support and operations teams who need a concise public incident record.
- Goal: Let a visitor understand overall health within five seconds, compare component reliability over 90 days, inspect exactly how past incidents progressed, and choose local demo notification preferences without implying that a real subscription occurred.
- Tone: Calm, precise, accountable, and quietly confident. Use plain operational language, useful timestamps, and direct explanations; never turn the page into a sales pitch or manufacture urgency.

## Stack
- Framework: Vite 6 + React 19 + TypeScript
- Styling: Tailwind CSS 4
- Libraries: lucide-react (ISC), @tailwindcss/vite (MIT), @fontsource-variable/manrope (OFL), @fontsource-variable/inter (OFL), @fontsource/ibm-plex-mono (OFL)
- Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs.
- Setup:
  - Set the npm build script to tsc -b && vite build; configure Vite with base: './', build.sourcemap: false, and an empty outDir named dist.
  - Use @tailwindcss/vite and @import "tailwindcss" in src/index.css; define the listed colors, fonts, spacing, shadows, and keyframes as CSS custom properties and Tailwind theme tokens.
  - Import Manrope Variable, Inter Variable, and IBM Plex Mono weights 400 and 500 from their Fontsource packages in src/main.tsx so every font file is bundled locally.
  - Keep all default and variable-derived copy, the fixed October sample reference date, six component records, four incident records, and every 90-day status series in src/content.ts; never scatter brand-specific copy through components.
  - Use small React components for the header, aggregate health chart, component row, incident accordion, and subscribe form. Use React state only for chart inspection, incident expansion, and form validation or confirmation; do not add a router or global state library.
  - Represent the 90 daily values as typed arrays committed in src/content.ts, ordered oldest to newest and ending on the fixed sample date October 25. Do not use random values, current-time requests, or remote data.

## Variables
- [BRAND] — Brand name (default: "Fablegrid"). An invented product or company name; use it in the header, hero copy, subscribe panel, footer, and document title.
- [SERVICE] — Service description (default: "cloud application platform"). A lowercase phrase describing the service whose health is being reported.
- [AUDIENCE] — Primary audience (default: "product engineering teams"). The people who rely on this service; rewrite component descriptions and incident language to suit them.
- [SUPPORT_EMAIL] — Support email (default: "[email protected]"). A support address appropriate to the invented brand; use a reserved .example domain for demo content.
- [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/service-status-page in the footer (default: yes; delete this line to remove it)

The copy under Pages & Sections is written for the default values. If your values differ, rewrite every headline, paragraph, label and image for them — same length, tone and structure. Layout, colors, type and motion stay as described.
Keep all copy, image paths and links in one content file (for example `src/content.ts`), keyed by section, so the content can be swapped later without touching components.

## Design
### Colors
- Canvas `#F3F6F2` — Page background with a faint 32 px CSS grid at 3 percent ink opacity.
- Surface `#FFFFFF` — Component table, incident cards, form fields, and tooltip surfaces.
- Ink `#13241D` — Primary headings, body emphasis, and dark text.
- Muted `#63736B` — Secondary copy, timestamps, labels, and chart axis text.
- Line `#D8E1DA` — Hairline borders, row separators, and inactive tracks.
- Operational `#16865A` — Healthy status text, icons, and light-surface uptime bars.
- Operational Soft `#E3F4E9` — Overall-state badge and healthy pill backgrounds.
- Degraded `#C48618` — Degraded-performance bars and amber status indicators.
- Outage `#D6574B` — Outage bars and error indicators; always pair with text or an icon.
- Panel `#10291F` — Hero aggregate chart and subscribe panel background.
- Panel Text `#F2FAF5` — Primary text on dark panels.
- Panel Muted `#A8BDB1` — Secondary text and labels on dark panels.
- Panel Bar `#48D28D` — Healthy bars on the dark aggregate chart.

### Typography
- Display and section headings: Manrope Variable (OFL), weights 500/600/700
- Body, navigation, controls, and operational copy: Inter Variable (OFL), weights 400/500/600
- Uptime values, timestamps, chart labels, and compact metadata: IBM Plex Mono (OFL), weights 400/500

### Layout & motion
- Spacing: Use an 8 px base rhythm. The content container is max-width 1180 px with 32 px desktop gutters and 20 px mobile gutters. Header height is 72 px. Hero padding is 72 px top and 80 px bottom on desktop, 40 px top and 56 px bottom on mobile. Major sections use 88 px desktop and 60 px mobile vertical padding. Cards use 28 px desktop and 20 px mobile padding; component rows use 22 px vertical spacing. Keep body copy measure below 64 characters.
- Radius: Use 20 px for the aggregate chart and subscribe panel, 14 px for component and incident cards, 10 px for inputs and buttons, 3 px for uptime bars, and fully rounded status pills. Borders remain 1 px; use shadows sparingly with 0 18 px 50 px rgba(19,36,29,0.10) only on the hero chart and visible tooltip.
- Motion: On initial load, fade and translate the hero copy and chart upward by 12 px over 420 ms with an 80 ms stagger; never hide the core status while waiting for animation.
- Motion: Grow healthy chart bars from 65 percent to full height over 320 ms with small grouped delays capped at 360 ms; degraded and outage bars appear without bouncing.
- Motion: Expand and collapse incident updates with a 180 ms opacity and grid-row transition while rotating the chevron 180 degrees; preserve keyboard focus and aria-expanded.
- Motion: Reveal chart inspection tooltips with a 120 ms fade and 4 px upward movement, clipped or flipped so they never cause horizontal overflow.
- Motion: Use a 160 ms color transition on buttons, navigation anchors, filter states, and form focus rings; smooth-scroll anchor navigation only when reduced motion is not requested.
- Motion: Under prefers-reduced-motion, remove entrance transforms, bar stagger, smooth scrolling, and accordion animation while leaving every state immediately visible and usable.
- Imagery: Use no photographs, generated bitmaps, people, or decorative stock illustrations. The first-screen visual anchor is a rich, code-built 90-day aggregate health panel with 90 individual bars, precise metrics, a legend, grid lines, and inspection tooltips. Build the small original [BRAND] glyph from three simple CSS status bars, and use currentColor Lucide icons everywhere else.

## Pages & Sections
### [BRAND] Service Status (`index.html`)
1. **Header and overall status hero** — Create a slim shared header with an original three-bar status glyph, the wordmark '[BRAND] status', anchor links labeled 'Components', 'Incidents', and 'Subscribe', and a compact 'All systems operational' pill. The hero eyebrow reads 'SAMPLE STATUS · UPDATED 2 MIN AGO'. Show a large CheckCircle2 icon, the H1 'All systems operational', and the sentence 'The latest sample health for [BRAND]'s [SERVICE], built for [AUDIENCE].' Add two anchor CTAs: primary 'View component history' and secondary 'Get incident updates'. Under them, show compact metadata '6 / 6 components available' and '0 active incidents'. The adjacent visual panel is titled '90-day platform health', displays '99.98%' in large mono type with 'aggregate uptime' beneath, and contains exactly 90 vertical daily bars covering the fixed sample range Jul 28–Oct 25. Use 86 green bars, amber bars at zero-based indices 61, 82, and 88, and one red bar at index 73. Add hover inspection with day date, daily state, and sample uptime; provide the same daily details in an accessible off-screen table rather than making 90 separate tab stops. Finish the panel with the range labels 'Jul 28' and 'Oct 25', a three-item legend 'Operational', 'Degraded', 'Outage', and a footer row reading '90 days monitored' and '4 days with notes'.
   Layout: Place the header inside the 1180 px container with the brand at left, navigation centered, and status pill at right; on mobile keep the brand and pill on the first row and put the three anchors in a second horizontally spaced row. The hero uses a five-column / seven-column grid with 56 px gap on desktop. Left copy is vertically centered, with a 58 px / 1.04 Manrope H1 at 600 weight and -0.04 em tracking. The dark chart panel occupies the right seven columns, has 28 px padding, a faint internal grid, and a 152 px-high bar field. Bars use flexible equal widths with 2 px gaps and rounded top corners. On screens below 800 px, stack copy above the chart with a 32 px gap, reduce the H1 to 40 px, keep the chart at least 250 px wide, and retain all 90 bars using narrower gaps rather than horizontal scrolling.
   Motion: Use the specified hero entrance and grouped bar-grow animation. The CTAs and navigation receive subtle color and underline transitions; tooltips appear only on pointer inspection and never shift layout.
2. **Current components** — Heading: 'Components'. Supporting copy: 'Current state and the last 90 days, using fixed sample data.' Add a right-aligned legend and the label '90 days ago / Today'. Render exactly six component rows: 'Web application' with description 'Customer-facing application and session delivery' and '100.00%'; 'Public API' with 'REST endpoints and authentication' and '99.99%'; 'Developer dashboard' with 'Configuration, usage, and team controls' and '100.00%'; 'Background jobs' with 'Queues, scheduled work, and retries' and '99.96%'; 'Webhooks' with 'Outbound event delivery' and '99.92%'; 'Media delivery' with 'Asset processing and edge downloads' and '99.98%'. Every current-state pill reads 'Operational'. Each row has its own 90-bar strip: Public API is amber at index 82, Background jobs at 61, Webhooks red at 73, Media delivery amber at 88, and every other daily bar is green. Use the same fixed Jul 28–Oct 25 reference dates as the aggregate chart. Include concise per-row accessible summaries such as 'Public API: 99.99 percent uptime over 90 days; one degraded day; currently operational.' When variables change, rename and describe components to fit the new [SERVICE], while retaining six rows and the same visual status distribution.
   Layout: Use one white 14 px-radius card with separate rows rather than six floating cards. The section heading and legend share a baseline row. On desktop, each component row is a grid with a 250 px name-and-description column, a flexible daily-bar column, an 82 px right-aligned mono percentage, and a 112 px right-aligned status pill. Bars are 30 px high with 2 px gaps. Row separators are Line at 1 px. On mobile, each row becomes a padded block: name and status pill on the first line, description next, full-width bars next, and percentage plus '90-day uptime' on the final line. Never truncate component names or clip tooltips at 390 px.
   Motion: Rows do not animate on scroll. Uptime strips gently brighten on row hover; individual bar tooltips fade in over 120 ms. All information remains visible without hover or motion.
3. **Incident history** — Heading: 'Incident history'. Supporting copy: 'A clear record of what happened, what changed, and when service recovered.' Provide three filter buttons, 'All 4', 'Incidents 3', and 'Maintenance 1', with All selected initially. Render four newest-first entries. First, badge 'Resolved', title 'Media processing delays', date 'Oct 22', duration '26 min', affected component 'Media delivery', with updates: '11:08 Investigating — We are investigating longer processing queues for uploaded media.'; '11:21 Identified — A stalled worker pool has been isolated and pending jobs are moving to healthy capacity.'; '11:34 Resolved — Processing times are back to normal and all queued jobs have completed.' Second, badge 'Resolved', title 'Elevated API latency in the EU region', date 'Oct 18', duration '38 min', component 'Public API', with updates: '14:12 Investigating — We are investigating elevated response times for API requests in the EU region.'; '14:24 Identified — A saturated cache node has been isolated. Traffic is shifting to healthy capacity.'; '14:50 Resolved — Latency has returned to normal. No data loss occurred.' Third, badge 'Resolved', title 'Webhook delivery interruption', date 'Oct 9', duration '1 hr 12 min', component 'Webhooks', with updates: '09:06 Investigating — Some webhook deliveries are failing while event ingestion remains available.'; '09:41 Monitoring — Failed events are replaying successfully after we restored the delivery worker.'; '10:18 Resolved — The replay is complete and delivery success has returned to normal.' Fourth, badge 'Completed', title 'Scheduled database maintenance', date 'Sep 27', duration '20 min', component 'Background jobs', with updates: '21:55 Scheduled — Maintenance will begin at 22:00. Background jobs may pause briefly while web requests continue.'; '22:00 In progress — The primary database is being updated and queued work is temporarily paused.'; '22:20 Completed — Maintenance is complete and all paused jobs have resumed.' Open the first entry by default and collapse the other three. Allow multiple entries to be open, and rewrite incident narratives for a changed [SERVICE] without retaining cloud-specific details that no longer fit.
   Layout: Keep filters in a small segmented row below the heading, wrapping naturally on mobile. Use a vertical stack of white 14 px-radius cards with 16 px gaps. Each closed header shows a small status dot and badge at left, title and affected component in the center, then date, duration, and chevron at right. The expanded update timeline sits below a 1 px separator with a vertical Line rail, 10 px status dots, mono timestamps, bold update state, and plain explanation. On mobile, place badge and date on the first row, title on the second, component and duration on the third, and right-align the chevron; timeline timestamps sit above their update copy if space is below 360 px. Filtering changes visibility without leaving blank wrappers.
   Motion: Accordion updates use the 180 ms expansion and chevron transition. Filter changes use a 140 ms fade, with no large list reordering or scroll jumps. Reduced-motion users get instantaneous state changes.
4. **Subscribe to updates** — Create a dark panel with eyebrow 'STATUS NOTIFICATIONS', heading 'Know when things change.', and copy 'Choose the sample updates you would receive from [BRAND].' The form label reads 'Work email', with placeholder '[email protected]', an email input, and a primary button 'Subscribe to updates'. Include two checked checkboxes labeled 'Incident updates' and 'Maintenance notices', plus the small line 'Demo form only. Your address is not transmitted or stored.' Validate for a nonempty, plausible email and at least one selected notice type; show specific inline errors below the relevant control. On valid submission, replace the button contents with a check and 'Preferences saved locally', then show the confirmation 'Demo subscription confirmed for this session. No email was sent.' Keep the entered address out of localStorage and provide a 'Reset preferences' text button that restores the initial form. Include a small support line 'Questions about service health? [SUPPORT_EMAIL]'.
   Layout: The Panel-colored 20 px-radius section uses a two-column grid: explanatory copy and a Bell icon on the left five columns, form on the right seven columns, separated by 56 px. Inputs are Surface with 10 px radius, 48 px minimum height, and a visible focus ring; the submit button uses Panel Bar with Ink text. Checkboxes sit in one row on desktop and stack on narrow screens. On mobile, stack the columns with 28 px gap and make the button full width. Error and success text must reserve space or reflow without clipping.
   Motion: Use only short focus, hover, error, and confirmation transitions. The confirmation check draws in over 180 ms unless reduced motion is requested; never simulate a network loading delay.
5. **Footer** — Repeat the original three-bar glyph and '[BRAND] status'. Add 'Operational communication for [AUDIENCE].' and the explicit note 'All service names, metrics, and incidents on this page are fictional sample data.' Include text links 'Components', 'Incidents', and 'Subscribe' pointing to './index.html#components', './index.html#incidents', and './index.html#subscribe', plus the support address [SUPPORT_EMAIL]. Set the document title to '[BRAND] Service Status' and use the same three-bar glyph as a locally generated SVG favicon.
   Layout: Use a top border, 32 px vertical padding, and a desktop row with brand and sample-data note at left and anchor links at right. On mobile, stack brand, note, links, and support address with 16 px gaps. Keep footer copy in Muted and metadata in 12 px IBM Plex Mono.
   Motion: No entrance animation; only subtle link color transitions.

## Assets
- image: No bitmap images. Render the aggregate health visualization, all daily uptime strips, the three-bar brand glyph, grid texture, and SVG favicon entirely with local HTML, CSS, React, and SVG; do not call an image generator or use placeholder-image services.
- icon: Install and import CheckCircle2, ChevronDown, Bell, Mail, Activity, ArrowDownRight, RotateCcw, and AlertCircle from lucide-react (ISC). Use currentColor at 16–20 px, with aria-hidden on decorative icons and visible text labels for meaning.
- font: Self-host Manrope Variable through @fontsource-variable/manrope (OFL), Inter Variable through @fontsource-variable/inter (OFL), and IBM Plex Mono 400 and 500 through @fontsource/ibm-plex-mono (OFL). Import only the required files from npm and list each package, author or project, source URL, and license in ASSETS.md.

## Don'ts
- Do not add a backend, serverless function, API route, database, authentication, analytics, third-party status feed, external API request, or form submission to any service; all operational data is fixed local sample data and the subscribe interaction is session-local only.
- Do not claim that emails, alerts, monitoring, uptime checks, or incident updates are actually running. Never display a fake network spinner, randomly refresh health data, or persist email addresses.
- Do not use real status-provider or technology-company names, logos, slogans, product copy, actual incidents, domains, or real uptime figures presented as fact; every brand, metric, and incident must remain explicitly fictional sample content.
- Do not copy an existing status page's exact palette, layout, copy, illustrations, icons, or composition, and do not use brand-specific mascots, custom fonts, or logo sets.
- Do not use photographs, AI-generated bitmaps, stock illustrations, remote images, placeholder-image services, recognizable people, or recognizable brand assets; the polished code-built health panel is the visual anchor.
- Do not load scripts, styles, fonts, icons, or assets from a CDN. Use only the named local npm dependencies and self-hosted Fontsource files, with no commercial or restrictively licensed source.
- Do not output source maps, copy src into dist, exceed a 20 MB dist directory, use absolute asset URLs, or require more than the single npm run build command.
- Do not add client-side routing, bare-directory links, empty href attributes, SEO metadata, Open Graph tags, JSON-LD, sitemap files, or keyword-heavy copy; one index.html, local anchor links, a plain variable-driven title, and an SVG favicon are sufficient.
- Do not generate daily uptime values with Math.random, Date.now, or remote data. Preserve the fixed 90-day series, sample reference range, incident chronology, and consistent component-to-incident status mapping in src/content.ts.
- Do not hard-code Fablegrid-specific copy outside the variable defaults and content file. When variables change, rewrite brand references, service descriptions, component names, support details, and incident narratives coherently.
- Do not rely on green, amber, or red alone to communicate state. Preserve text labels, accessible icons, descriptive chart summaries, visible focus states, labeled controls, keyboard-operable accordions and filters, and reduced-motion behavior.
- Do not allow bar tooltips, navigation, status pills, long email addresses, or incident timestamps to create horizontal overflow or console errors at 1440×900 or 390×844.

---
— Prompt by VibeFather · https://vibefather.ai/t/service-status-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
中文参考译文(帮助理解,复制给 AI 时请用上面的英文原版)
# 服务状态页面

完全按照以下描述构建此网站。将 [VARIABLES] 替换为你自己的值;其余内容保持不变。

## 简介
为 [BRAND] 构建一个原创的单页服务状态网站,[BRAND] 是一个为 [AUDIENCE] 虚构的 [SERVICE]。呈现一组连贯的虚构运营数据:整体健康状态、六个组件及其固定的 90 天正常运行时间历史、四条已解决或已完成的事件条目及其带时间戳的更新,以及一个带有诚实静态演示确认的订阅表单。将所有变量驱动的文案、组件记录、每日状态值和事件叙述保留在 src/content.ts 中;当变量变化时重写服务特定的细节,同时保持布局、记录数量和交互模型不变。

- 受众:主要读者是正在检查 [BRAND] 是否可用的 [AUDIENCE],以及需要一份简洁公开事件记录的支持和运营团队。
- 目标:让访客在五秒内了解整体健康状况,比较 90 天内各组件的可靠性,准确查看过去事件的发展过程,并选择本地演示通知偏好,而不暗示发生了真实订阅。
- 语气:冷静、精确、负责任,且沉稳自信。使用平实的运营语言、有用的时间戳和直接的解释;绝不要将页面变成推销话术或制造紧迫感。

## 技术栈
- 框架:Vite 6 + React 19 + TypeScript
- 样式:Tailwind CSS 4
- 库:lucide-react(ISC)、@tailwindcss/vite(MIT)、@fontsource-variable/manrope(OFL)、@fontsource-variable/inter(OFL)、@fontsource/ibm-plex-mono(OFL)
- 构建:`npm run build` → `dist/` 中的静态文件。无后端、无服务器代码、无外部 API。
- 设置:
  - 将 npm 构建脚本设置为 tsc -b && vite build;配置 Vite,使用 base: './'、build.sourcemap: false,以及一个名为 dist 的空 outDir。
  - 使用 @tailwindcss/vite,并在 src/index.css 中使用 @import "tailwindcss";将列出的颜色、字体、间距、阴影和关键帧定义为 CSS 自定义属性和 Tailwind 主题令牌。
  - 在 src/main.tsx 中从各自的 Fontsource 包导入 Manrope Variable、Inter Variable 和 IBM Plex Mono 的 400 与 500 字重,以便每个字体文件都在本地打包。
  - 将所有默认和变量派生的文案、固定的十月样本参考日期、六条组件记录、四条事件记录以及每个 90 天状态序列保留在 src/content.ts 中;切勿将品牌特定文案分散到各个组件中。
  - 为页眉、聚合健康图表、组件行、事件手风琴和订阅表单使用小型 React 组件。仅将 React 状态用于图表检查、事件展开和表单验证或确认;不要添加路由器或全局状态库。
  - 将 90 个每日值表示为在 src/content.ts 中提交的类型化数组,按从最旧到最新排序,并以固定样本日期 10 月 25 日结束。不要使用随机值、当前时间请求或远程数据。

## 变量
- [BRAND] — 品牌名称(默认:"Fablegrid")。一个虚构的产品或公司名称;在页眉、主视觉文案、订阅面板、页脚和文档标题中使用它。
- [SERVICE] — 服务描述(默认:"cloud application platform")。一个描述所报告健康状况之服务的全小写短语。
- [AUDIENCE] — 主要受众(默认:"product engineering teams")。依赖此服务的人群;根据他们改写组件描述和事件用语。
- [SUPPORT_EMAIL] — 支持邮箱(默认:"[email protected]")。与虚构品牌相匹配的支持地址;演示内容请使用保留的 .example 域名。
- [CREDIT] — 在页脚保留一个小型 "Template by VibeFather" 链接,指向 https://vibefather.ai/t/service-status-page(默认:是;删除此行即可移除)

页面与区块(Pages & Sections)下的文案是按默认值撰写的。如果你的取值不同,请为它们重写每一个标题、段落、标签和图片——保持相同的长度、语气和结构。布局、颜色、字体和动效保持所述不变。
将所有文案、图片路径和链接放在一个内容文件中(例如 `src/content.ts`),按区块作为键,以便日后无需改动组件即可替换内容。

## 设计
### 颜色(Colors)
- 画布(Canvas)`#F3F6F2` — 页面背景,带有 3% 墨色不透明度的细微 32 px CSS 网格。
- 表面(Surface)`#FFFFFF` — 组件表格、事件卡片、表单字段和工具提示表面。
- 墨色(Ink)`#13241D` — 主标题、正文强调和深色文本。
- 柔和色(Muted)`#63736B` — 次要文案、时间戳、标签和图表轴文本。
- 线条(Line)`#D8E1DA` — 细线边框、行分隔符和非活动轨道。
- 运行正常(Operational)`#16865A` — 健康状态文本、图标和浅色表面正常运行时间条。
- 运行正常柔和色(Operational Soft)`#E3F4E9` — 整体状态徽章和健康状态药丸背景。
- 性能降级(Degraded)`#C48618` — 性能降级条和琥珀色状态指示器。
- 服务中断(Outage)`#D6574B` — 中断条和错误指示器;始终与文本或图标配对使用。
- 面板(Panel)`#10291F` — 主视觉聚合图表和订阅面板背景。
- 面板文本(Panel Text)`#F2FAF5` — 深色面板上的主要文本。
- 面板柔和色(Panel Muted)`#A8BDB1` — 深色面板上的次要文本和标签。
- 面板条(Panel Bar)`#48D28D` — 深色聚合图表上的健康条。

### 排版
- 展示标题和章节标题:Manrope Variable(OFL),字重 500/600/700
- 正文、导航、控件和运营文案:Inter Variable(OFL),字重 400/500/600
- 正常运行时间值、时间戳、图表标签和紧凑元数据:IBM Plex Mono(OFL),字重 400/500

### 布局与动效
- 间距:使用 8 px 基础节奏。内容容器最大宽度 1180 px,桌面端边距 32 px,移动端边距 20 px。页头高度 72 px。主视觉内边距桌面端顶部 72 px、底部 80 px,移动端顶部 40 px、底部 56 px。主要章节使用桌面端 88 px、移动端 60 px 的垂直内边距。卡片使用桌面端 28 px、移动端 20 px 的内边距;组件行使用 22 px 的垂直间距。正文每行保持在 64 个字符以内。
- 圆角:聚合图表和订阅面板使用 20 px,组件卡片和事件卡片使用 14 px,输入框和按钮使用 10 px,正常运行时间条使用 3 px,状态药丸使用全圆角。边框保持 1 px;阴影谨慎使用,仅在主视觉图表和可见工具提示上使用 0 18 px 50 px rgba(19,36,29,0.10)。
- 动效:初始加载时,主视觉文案和图表在 420 ms 内向上淡入并平移 12 px,错开 80 ms;等待动画期间绝不隐藏核心状态。
- 动效:健康图表条在 320 ms 内从 65% 高度增长到全高,分组小延迟上限为 360 ms;降级和中断条出现时无弹跳。
- 动效:事件更新以 180 ms 的不透明度和 grid-row 过渡展开和折叠,同时将箭头旋转 180 度;保留键盘焦点和 aria-expanded。
- 动效:图表检查工具提示以 120 ms 淡入和 4 px 向上移动显示,裁剪或翻转以确保它们永远不会导致水平溢出。
- 动效:按钮、导航锚点、筛选状态和表单焦点环使用 160 ms 颜色过渡;仅在未请求减少动效时平滑滚动锚点导航。
- 动效:在 prefers-reduced-motion 下,移除入场变换、条形错开、平滑滚动和手风琴动画,同时让每个状态立即可见且可用。
- 图像:不使用照片、生成的位图、人物或装饰性库存插图。首屏视觉锚点是一个丰富的、代码构建的 90 天聚合健康面板,包含 90 个独立条形、精确指标、图例、网格线和检查工具提示。用三个简单的 CSS 状态条构建小型原创 [BRAND] 字形,其他所有地方使用 currentColor Lucide 图标。

## 页面与区块
### [BRAND] 服务状态(`index.html`)
1. **页眉与整体状态主视觉区** — 创建一个纤细的共享页眉,包含一个原创的三横条状态图标、文字标识 '[BRAND] status'、标注为 'Components'、'Incidents' 和 'Subscribe' 的锚点链接,以及一个紧凑的 'All systems operational' 胶囊标签。主视觉区的眉题文字为 'SAMPLE STATUS · UPDATED 2 MIN AGO'。展示一个大的 CheckCircle2 图标、H1 标题 'All systems operational',以及句子 'The latest sample health for [BRAND]'s [SERVICE], built for [AUDIENCE].'。添加两个锚点 CTA:主按钮 'View component history' 和次按钮 'Get incident updates'。在它们下方,显示紧凑的元数据 '6 / 6 components available' 和 '0 active incidents'。相邻的视觉面板标题为 '90-day platform health',以大型等宽字体显示 '99.98%',下方为 'aggregate uptime',并包含恰好 90 根垂直日柱,覆盖固定样本范围 Jul 28–Oct 25。使用 86 根绿色柱,在从零开始的索引 61、82 和 88 处使用琥珀色柱,在索引 73 处使用一根红色柱。添加悬停检查,显示日期、每日状态和样本正常运行时间;在可访问的屏幕外表格中提供相同的每日详情,而不是设置 90 个单独的 Tab 停靠点。以范围标签 'Jul 28' 和 'Oct 25'、三项图例 'Operational'、'Degraded'、'Outage',以及一行页脚文字 '90 days monitored' 和 '4 days with notes' 结束面板。
   布局:将页眉放在 1180 px 容器内,品牌在左、导航居中、状态胶囊在右;在移动端,将品牌和胶囊保留在第一行,并将三个锚点放在第二行水平间隔排列。主视觉区在桌面端使用五列 / 七列网格,间距 56 px。左侧文案垂直居中,H1 为 58 px / 1.04 Manrope,字重 600,字距 -0.04 em。深色图表面板占据右侧七列,内边距 28 px,带有淡淡的内部网格和 152 px 高的柱状区域。柱使用灵活等宽、2 px 间隙和圆角顶部。在低于 800 px 的屏幕上,将文案堆叠在图表上方,间距 32 px,将 H1 缩小至 40 px,保持图表至少 250 px 宽,并通过更窄的间隙保留全部 90 根柱,而不是水平滚动。
   动效:使用指定的主视觉区入场动画和分组柱状生长动画。CTA 和导航获得微妙的颜色和下划线过渡;工具提示仅在指针检查时出现,且从不改变布局。
2. **当前组件** — 标题:'Components'。辅助文案:'Current state and the last 90 days, using fixed sample data.'。添加右对齐图例和标签 '90 days ago / Today'。渲染恰好六个组件行:'Web application',描述为 'Customer-facing application and session delivery',以及 '100.00%';'Public API',描述为 'REST endpoints and authentication',以及 '99.99%';'Developer dashboard',描述为 'Configuration, usage, and team controls',以及 '100.00%';'Background jobs',描述为 'Queues, scheduled work, and retries',以及 '99.96%';'Webhooks',描述为 'Outbound event delivery',以及 '99.92%';'Media delivery',描述为 'Asset processing and edge downloads',以及 '99.98%'。每个当前状态胶囊都显示 'Operational'。每一行都有自己的 90 柱条带:Public API 在索引 82 处为琥珀色,Background jobs 在 61 处,Webhooks 在 73 处为红色,Media delivery 在 88 处为琥珀色,其他所有日柱均为绿色。使用与聚合图表相同的固定 Jul 28–Oct 25 参考日期。包含简洁的逐行可访问摘要,例如 'Public API: 99.99 percent uptime over 90 days; one degraded day; currently operational.'。当变量变化时,重命名并描述组件以适配新的 [SERVICE],同时保留六行和相同的视觉状态分布。
   布局:使用一张白色 14 px 圆角卡片,包含独立行,而不是六张浮动卡片。区块标题和图例共享基线行。在桌面端,每个组件行是一个网格,包含 250 px 的名称和描述列、灵活的日柱列、82 px 右对齐等宽百分比,以及 112 px 右对齐状态胶囊。柱高 30 px,间隙 2 px。行分隔线为 Line,1 px。在移动端,每一行变为一个带内边距的块:第一行是名称和状态胶囊,接下来是描述,然后是全宽柱,最后一行是百分比加 '90-day uptime'。在 390 px 宽度下,绝不截断组件名称或裁剪工具提示。
   动效:行在滚动时不播放动画。正常运行时间条带在行悬停时轻微变亮;单个柱工具提示在 120 ms 内淡入。所有信息在无悬停或无动效时仍然可见。
3. **事件历史** — 标题:'Incident history'。辅助文案:'A clear record of what happened, what changed, and when service recovered.'。提供三个筛选按钮:'All 4'、'Incidents 3' 和 'Maintenance 1',初始选中 All。渲染四条最新在前的条目。第一条,徽章 'Resolved',标题 'Media processing delays',日期 'Oct 22',持续时间 '26 min',受影响组件 'Media delivery',更新为:'11:08 Investigating — We are investigating longer processing queues for uploaded media.';'11:21 Identified — A stalled worker pool has been isolated and pending jobs are moving to healthy capacity.';'11:34 Resolved — Processing times are back to normal and all queued jobs have completed.'。第二条,徽章 'Resolved',标题 'Elevated API latency in the EU region',日期 'Oct 18',持续时间 '38 min',组件 'Public API',更新为:'14:12 Investigating — We are investigating elevated response times for API requests in the EU region.';'14:24 Identified — A saturated cache node has been isolated. Traffic is shifting to healthy capacity.';'14:50 Resolved — Latency has returned to normal. No data loss occurred.'。第三条,徽章 'Resolved',标题 'Webhook delivery interruption',日期 'Oct 9',持续时间 '1 hr 12 min',组件 'Webhooks',更新为:'09:06 Investigating — Some webhook deliveries are failing while event ingestion remains available.';'09:41 Monitoring — Failed events are replaying successfully after we restored the delivery worker.';'10:18 Resolved — The replay is complete and delivery success has returned to normal.'。第四条,徽章 'Completed',标题 'Scheduled database maintenance',日期 'Sep 27',持续时间 '20 min',组件 'Background jobs',更新为:'21:55 Scheduled — Maintenance will begin at 22:00. Background jobs may pause briefly while web requests continue.';'22:00 In progress — The primary database is being updated and queued work is temporarily paused.';'22:20 Completed — Maintenance is complete and all paused jobs have resumed.'。默认展开第一条,折叠其他三条。允许多个条目同时展开,并为变更后的 [SERVICE] 重写事件叙述,不保留不再适用的云特定细节。
   布局:将筛选器放在标题下方的小型分段行中,在移动端自然换行。使用垂直堆叠的白色 14 px 圆角卡片,间距 16 px。每个关闭的页眉左侧显示一个小状态点和徽章,中间是标题和受影响组件,右侧是日期、持续时间和 chevron。展开的更新时间线位于 1 px 分隔线下方,带有垂直线轨、10 px 状态点、等宽时间戳、粗体更新状态和纯文本说明。在移动端,将徽章和日期放在第一行,标题放在第二行,组件和持续时间放在第三行,并将 chevron 右对齐;如果空间低于 360 px,时间线时间戳位于其更新文案上方。筛选会改变可见性,而不留下空白包装器。
   动效:手风琴更新使用 180 ms 展开和 chevron 过渡。筛选变化使用 140 ms 淡入淡出,不进行大规模列表重排或滚动跳转。减少动效的用户获得即时状态变化。
4. **订阅更新** — 创建一个深色面板,眉题为 'STATUS NOTIFICATIONS',标题为 'Know when things change.',文案为 'Choose the sample updates you would receive from [BRAND].'。表单标签为 'Work email',占位符为 '[email protected]',包含一个电子邮件输入框和一个主按钮 'Subscribe to updates'。包含两个已勾选的复选框,标签为 'Incident updates' 和 'Maintenance notices',以及小字行 'Demo form only. Your address is not transmitted or stored.'。验证非空、合理的电子邮件以及至少一种选中的通知类型;在相关控件下方显示具体的行内错误。在有效提交时,将按钮内容替换为对勾和 'Preferences saved locally',然后显示确认信息 'Demo subscription confirmed for this session. No email was sent.'。将输入的地址排除在 localStorage 之外,并提供一个 'Reset preferences' 文本按钮以恢复初始表单。包含一行小型支持信息 'Questions about service health? [SUPPORT_EMAIL]'。
   布局:Panel 色的 20 px 圆角区块采用两栏网格:左侧五栏为说明文案和 Bell 图标,右侧七栏为表单,两者间隔 56 px。输入框为 Surface 色、10 px 圆角、最小高度 48 px,并带有可见的聚焦环;提交按钮使用 Panel Bar 配 Ink 文字。复选框在桌面端排成一行,在窄屏上堆叠。在移动端,将各栏堆叠,间距 28 px,并让按钮占满全宽。错误和成功文本必须预留空间或重新排版而不被裁切。
   动效:仅使用简短的聚焦、悬停、错误和确认过渡。除非请求减少动效,确认勾选在 180 ms 内绘制完成;绝不模拟网络加载延迟。
5. **页脚** — 重复原始的三条横杠字形和 '[BRAND] status'。添加 'Operational communication for [AUDIENCE].' 以及明确说明 'All service names, metrics, and incidents on this page are fictional sample data.'。包含文本链接 'Components'、'Incidents' 和 'Subscribe',分别指向 './index.html#components'、'./index.html#incidents' 和 './index.html#subscribe',以及支持地址 [SUPPORT_EMAIL]。将文档标题设置为 '[BRAND] Service Status',并使用相同的三条横杠字形作为本地生成的 SVG favicon。
   布局:使用顶部边框、32 px 垂直内边距,桌面端为一行,左侧为品牌和示例数据说明,右侧为锚点链接。在移动端,将品牌、说明、链接和支持地址堆叠,间距 16 px。页脚文案保持 Muted 色,元数据使用 12 px IBM Plex Mono。
   动效:无入场动画;仅使用细微的链接颜色过渡。

## 资产
- 图像:不使用位图图像。聚合健康可视化、所有每日正常运行时间条、三栏品牌字形、网格纹理和 SVG favicon 全部使用本地 HTML、CSS、React 和 SVG 渲染;不要调用图像生成器,也不要使用占位图服务。
- 图标:从 lucide-react(ISC)安装并导入 CheckCircle2、ChevronDown、Bell、Mail、Activity、ArrowDownRight、RotateCcw 和 AlertCircle。以 16–20 px 使用 currentColor,装饰性图标上使用 aria-hidden,并用可见文本标签表达含义。
- 字体:通过 @fontsource-variable/manrope(OFL)自托管 Manrope Variable,通过 @fontsource-variable/inter(OFL)自托管 Inter Variable,并通过 @fontsource/ibm-plex-mono(OFL)自托管 IBM Plex Mono 400 和 500。仅从 npm 导入所需文件,并在 ASSETS.md 中列出每个包、作者或项目、源 URL 和许可证。

## 不要做
- 不要向任何服务添加后端、无服务器函数、API 路由、数据库、身份验证、分析、第三方状态源、外部 API 请求或表单提交;所有运营数据都是固定的本地示例数据,订阅交互仅在会话本地生效。
- 不要声称电子邮件、警报、监控、正常运行时间检查或事件更新实际正在运行。绝不要显示虚假的网络加载旋转器、随机刷新健康数据或持久化电子邮件地址。
- 不要使用真实的状态服务提供商或科技公司的名称、徽标、标语、产品文案、实际事件、域名或作为事实呈现的真实正常运行时间数据;每个品牌、指标和事件都必须明确保持为虚构的示例内容。
- 不要复制现有状态页面的精确配色、布局、文案、插图、图标或构图,也不要使用品牌专属吉祥物、自定义字体或徽标集。
- 不要使用照片、AI 生成的位图、库存插图、远程图像、占位图服务、可识别的人物或可识别的品牌资产;精心构建的代码健康面板是视觉锚点。
- 不要从 CDN 加载脚本、样式、字体、图标或资产。仅使用指定的本地 npm 依赖和自托管的 Fontsource 文件,不使用商业性或限制性许可的来源。
- 不要输出源映射、将 src 复制到 dist、使 dist 目录超过 20 MB、使用绝对资产 URL,或要求超过单个 npm run build 命令。
- 不要添加客户端路由、裸目录链接、空 href 属性、SEO 元数据、Open Graph 标签、JSON-LD、站点地图文件或关键词堆砌的文案;一个 index.html、本地锚点链接、一个由变量驱动的纯文本标题和一个 SVG favicon 就足够了。
- 不要使用 Math.random、Date.now 或远程数据生成每日正常运行时间值。在 src/content.ts 中保留固定的 90 天序列、示例参考范围、事件时间线和一致的组件到事件状态映射。
- 不要在变量默认值和内容文件之外硬编码 Fablegrid 专属文案。当变量变化时,连贯地重写品牌引用、服务描述、组件名称、支持详情和事件叙述。
- 不要仅依赖绿色、琥珀色或红色来传达状态。保留文本标签、无障碍图标、描述性图表摘要、可见的焦点状态、带标签的控件、键盘可操作的折叠面板和筛选器,以及减少动态效果的行为。
- 不要让条形图工具提示、导航、状态胶囊、长电子邮件地址或事件时间戳在 1440×900 或 390×844 下造成水平溢出或控制台错误。

---
— Prompt by VibeFather · https://vibefather.ai/t/service-status-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

个人项目可免费使用(CC BY-NC 4.0)。 商业用途需要 Pro.

DESIGN.md

单独的设计规范:配色、字体、间距和动效。可以把这套视觉用到你已有的项目上。

---
name: "Service Status Page"
colors:
  canvas: "#F3F6F2"
  surface: "#FFFFFF"
  ink: "#13241D"
  muted: "#63736B"
  line: "#D8E1DA"
  operational: "#16865A"
  operational_soft: "#E3F4E9"
  degraded: "#C48618"
  outage: "#D6574B"
  panel: "#10291F"
  panel_text: "#F2FAF5"
  panel_muted: "#A8BDB1"
  panel_bar: "#48D28D"
typography:
  display_and_section_headings: { family: "Manrope Variable", weights: [500, 600, 700] }
  body_navigation_controls_and_operational_copy: { family: "Inter Variable", weights: [400, 500, 600] }
  uptime_values_timestamps_chart_labels_and_compact_metadata: { family: "IBM Plex Mono", weights: [400, 500] }
spacing: "Use an 8 px base rhythm. The content container is max-width 1180 px with 32 px desktop gutters and 20 px mobile gutters. Header height is 72 px. Hero padding is 72 px top and 80 px bottom on desktop, 40 px top and 56 px bottom on mobile. Major sections use 88 px desktop and 60 px mobile vertical padding. Cards use 28 px desktop and 20 px mobile padding; component rows use 22 px vertical spacing. Keep body copy measure below 64 characters."
radius: "Use 20 px for the aggregate chart and subscribe panel, 14 px for component and incident cards, 10 px for inputs and buttons, 3 px for uptime bars, and fully rounded status pills. Borders remain 1 px; use shadows sparingly with 0 18 px 50 px rgba(19,36,29,0.10) only on the hero chart and visible tooltip."
---

# Service Status Page — Design System

Apply this design system to an existing project. It describes the look and feel only; for the full site, use prompt.md.

## Colors
- **Canvas** `#F3F6F2` — Page background with a faint 32 px CSS grid at 3 percent ink opacity.
- **Surface** `#FFFFFF` — Component table, incident cards, form fields, and tooltip surfaces.
- **Ink** `#13241D` — Primary headings, body emphasis, and dark text.
- **Muted** `#63736B` — Secondary copy, timestamps, labels, and chart axis text.
- **Line** `#D8E1DA` — Hairline borders, row separators, and inactive tracks.
- **Operational** `#16865A` — Healthy status text, icons, and light-surface uptime bars.
- **Operational Soft** `#E3F4E9` — Overall-state badge and healthy pill backgrounds.
- **Degraded** `#C48618` — Degraded-performance bars and amber status indicators.
- **Outage** `#D6574B` — Outage bars and error indicators; always pair with text or an icon.
- **Panel** `#10291F` — Hero aggregate chart and subscribe panel background.
- **Panel Text** `#F2FAF5` — Primary text on dark panels.
- **Panel Muted** `#A8BDB1` — Secondary text and labels on dark panels.
- **Panel Bar** `#48D28D` — Healthy bars on the dark aggregate chart.

## Typography
- **Display and section headings** — Manrope Variable (OFL), weights 500/600/700. Self-host the font files.
- **Body, navigation, controls, and operational copy** — Inter Variable (OFL), weights 400/500/600. Self-host the font files.
- **Uptime values, timestamps, chart labels, and compact metadata** — IBM Plex Mono (OFL), weights 400/500. Self-host the font files.

## Spacing & shape
- Spacing: Use an 8 px base rhythm. The content container is max-width 1180 px with 32 px desktop gutters and 20 px mobile gutters. Header height is 72 px. Hero padding is 72 px top and 80 px bottom on desktop, 40 px top and 56 px bottom on mobile. Major sections use 88 px desktop and 60 px mobile vertical padding. Cards use 28 px desktop and 20 px mobile padding; component rows use 22 px vertical spacing. Keep body copy measure below 64 characters.
- Radius: Use 20 px for the aggregate chart and subscribe panel, 14 px for component and incident cards, 10 px for inputs and buttons, 3 px for uptime bars, and fully rounded status pills. Borders remain 1 px; use shadows sparingly with 0 18 px 50 px rgba(19,36,29,0.10) only on the hero chart and visible tooltip.

## Motion
- On initial load, fade and translate the hero copy and chart upward by 12 px over 420 ms with an 80 ms stagger; never hide the core status while waiting for animation.
- Grow healthy chart bars from 65 percent to full height over 320 ms with small grouped delays capped at 360 ms; degraded and outage bars appear without bouncing.
- Expand and collapse incident updates with a 180 ms opacity and grid-row transition while rotating the chevron 180 degrees; preserve keyboard focus and aria-expanded.
- Reveal chart inspection tooltips with a 120 ms fade and 4 px upward movement, clipped or flipped so they never cause horizontal overflow.
- Use a 160 ms color transition on buttons, navigation anchors, filter states, and form focus rings; smooth-scroll anchor navigation only when reduced motion is not requested.
- Under prefers-reduced-motion, remove entrance transforms, bar stagger, smooth scrolling, and accordion animation while leaving every state immediately visible and usable.

## Imagery
Use no photographs, generated bitmaps, people, or decorative stock illustrations. The first-screen visual anchor is a rich, code-built 90-day aggregate health panel with 90 individual bars, precise metrics, a legend, grid lines, and inspection tooltips. Build the small original [BRAND] glyph from three simple CSS status bars, and use currentColor Lucide icons everywhere else.

## Tone
Calm, precise, accountable, and quietly confident. Use plain operational language, useful timestamps, and direct explanations; never turn the page into a sales pitch or manufacture urgency.

---
— Prompt by VibeFather · https://vibefather.ai/t/service-status-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

改成你自己的

  • 开发者 API 平台:将 BRAND 设为你的 API 名称,SERVICE 设为你的 API,并将六个组件重写为端点、身份验证和仪表盘可用性。
  • 在线学习平台:将 AUDIENCE 设为学生和讲师,并围绕视频播放、测验和登录问题重写事件更新。
  • 独立 SaaS 创始人:将 SUPPORT_EMAIL 指向你自己的收件箱,并用你真实已解决的故障和维护窗口替换样本事件。
  • 云托管服务商:将 SERVICE 设为云托管,将组件重新标记为计算、存储和网络,并保留 90 天条作为你的正常运行时间记录。

服务状态页:常见问题

服务状态页模板除了提示词还包含什么?

服务状态页模板包含已发布的提示词、一份涵盖颜色、字体、间距和动效的 DESIGN.md,以及变量列表。作为免费模板,提示词和 DESIGN.md 可在 CC BY-NC 4.0 下用于个人非商业用途。商业或客户项目以及演示源代码需要 Pro 会员。

服务状态页可以用于内部产品而不是公开的 SaaS 吗?

服务状态页模板既适用于内部产品,也适用于公共服务。将 BRAND、SERVICE 和 AUDIENCE 变量设置为你的内部平台和团队,并为该受众重写组件描述和事件用语。该页面没有后端或外部 API,因此可以托管在你网络内的任何静态主机上。

怎么用 AI 做一个服务状态页?

复制本页的提示词,或者运行 npx vibefather add service-status-page,把 [BRAND]、[SERVICE]、[AUDIENCE]、[SUPPORT_EMAIL] 换成你自己的内容,再粘贴到 Claude Code、Codex、Cursor 等 AI 编程工具里。在线演示就是用这份提示词原样做出来的。