用这个模板做的 2 个案例
同一份提示词,不同的 [VARIABLES] 变量。点一个在上方预览。关于这个模板
网络安全 SaaS 落地页是一个以转化为目标的单页网站,适合安全平台、基础设施工具以及其他需要在不牺牲视觉冲击力的前提下解释复杂工作流的技术产品。首屏将直接的产品卖点与大型运营地图、动态信号路线和清晰易读的事件队列搭配呈现。每个事件都明确标注为模拟,因此页面显得活跃,但不会暗示这是实时情报流。
设计采用深蓝黑底色、冰薄荷色点缀、暖珊瑚色警报、精细坐标网格和紧凑等宽标签。Space Grotesk 标题、Inter 正文和小圆角营造出精确的事件简报气质,而非霓虹游戏风格。四个产品标签页分别展示用代码绘制的独特界面视图,对应数据接入、检测、调查和响应。三步工作流、示意性成果指标和通用信任控制徽章将叙事引向详细的演示申请表单。
地图可暂停,产品标签页和 FAQ 支持键盘操作,移动端布局在无横向溢出的前提下保持视觉层次。表单会校验真实输入并生成可复制的请求预览;页面明确说明此静态演示不会发送或存储个人信息。当用户请求减少动态效果时,动画会降为稳定、可读的状态。
五个变量分别控制品牌、产品类别、目标受众、事件术语和主行动号召。所有产品文案、示例指标、地图事件、模块数据、信任标签和 FAQ 都放在一个带类型的内容文件中,换主题时必须重写。备选案例将安全运营网站变为隐私运营平台,同时保留同一视觉系统。无需照片、外部地图、认证标志、客户 Logo 或远程服务。
模板提示词
在线演示就是用这份提示词原样做出来的,没有额外补充。其他案例只是改了 [VARIABLES] 变量的值。 提示词保持英文原版,国内常用的 AI 编程工具都能直接理解;下面附中文参考译文。
# Cybersecurity SaaS Landing Page Build this website exactly as described below. Replace the [VARIABLES] with your own values; keep everything else. ## Brief Build an original single-page landing site for [BRAND], a [PRODUCT_CATEGORY] for [AUDIENCE]. The hero combines a clear sales pitch with a rich animated SVG world map labeled [EVENT_LABEL], a simulated event feed, and explicit sample-data notices. Continue through product modules, an incident workflow, illustrative customer outcomes, generic trust controls, a demo request form, FAQs, and a focused closing call to action. - Audience: The site speaks to [AUDIENCE] who need to understand the product quickly and evaluate whether a guided walkthrough is worth their time. The template owner is a technical SaaS team that needs a polished, credible marketing page with a substantial product visualization rather than abstract decoration. - Goal: Get visitors to understand the product's detection-to-response story, explore all four modules, recognize the sample nature of every metric and event, and complete a valid demo request preview. Every visible control must work locally, and no form data may leave or persist beyond the current page state. - Tone: Calm, exact, operational, and assured. Use concrete product language and useful detail instead of fear, cinematic hacker clichés, vague superlatives, or unsupported security claims. Treat animated activity as illustrative interface content, never as evidence of real protection or live telemetry. ## Stack - Framework: Vite 5 + React 18 + TypeScript - Styling: Tailwind CSS 3.4 - Libraries: React 18 (MIT), Vite 5 (MIT), TypeScript (Apache-2.0), Tailwind CSS 3.4 (MIT), motion (MIT), lucide-react (ISC), @fontsource-variable/space-grotesk (OFL-1.1), @fontsource-variable/inter (OFL-1.1), @fontsource/ibm-plex-mono (OFL-1.1) - Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs. - Setup: - Use Vite 5 with React 18 and TypeScript. Set base: './' in vite.config.ts, set build.sourcemap to false, and emit only static production files to dist/. - Configure Tailwind CSS 3.4 with the exact colors, font families, spacing, radii, and shadows below. Put map keyframes, focus styles, selection color, and reduced-motion overrides in src/index.css. - Keep all editable brand copy, headlines, module copy and data, map events, metrics, trust labels, FAQs, and form options in src/content.ts with TypeScript interfaces. Components must not embed copy that only fits the default topic. - When variable values change, rewrite every topic-specific headline, product module, event label, sample event, metric, workflow step, trust explanation, FAQ answer, and form option to fit [PRODUCT_CATEGORY], [AUDIENCE], and [EVENT_LABEL], while preserving the layout and interactions. - Use Motion for React for section entrances, product-tab transitions, accordion answers, and the request-preview state. Use original inline SVG and CSS keyframes for the map; do not add a mapping, charting, or animation dependency. - Create a deterministic ThreatMap component with fixed nodes, routes, and six predefined events. Use one cleaned-up interval to rotate the highlighted event every 2800ms; Pause feed must stop both the interval and decorative animation. Do not use random data or external telemetry. - Keep product tab state, mobile menu state, open FAQ state, feed pause state, and form state in React memory only. Do not use localStorage, sessionStorage, cookies, analytics, URL tracking parameters, or any network request. - Import Space Grotesk Variable, Inter Variable, and IBM Plex Mono locally from Fontsource. Create ASSETS.md listing the three font packages, lucide-react, their sources and licenses, and stating that all map and product artwork is original code-drawn SVG/CSS with no raster images. - Use semantic landmarks, labeled controls, visible focus, 44px minimum touch targets, keyboard-operable tabs and accordions, and reduced-motion behavior. Verify the complete page at 1440×900 and 390×844 with zero console errors and no horizontal overflow. ## Variables - [BRAND] — Product brand (default: "Sablegrid"). An invented product name used in the original bracket mark, header, copy, form preview, and footer. - [PRODUCT_CATEGORY] — Product category (default: "threat detection and response platform"). A concise lowercase category phrase; all product and workflow copy must follow it. - [AUDIENCE] — Primary audience (default: "lean security teams"). A concise lowercase audience description used in the hero and sales copy. - [EVENT_LABEL] — Map event label (default: "Threat activity"). A short title-case label for the map and its simulated events, such as Data risk activity. - [PRIMARY_CTA] — Primary call to action (default: "Request a demo"). A short button label that scrolls visitors to the local demo request form. - [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/cybersecurity-saas-landing-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 - Deep Field `#071114` — Page background, header, and footer - Panel Ink `#0D1C20` — Map, product viewer, form, and raised section surfaces - Raised Line `#173036` — Selected rows, input backgrounds, and quiet tonal blocks - Grid Line `#28434A` — Borders, coordinate rules, dividers, and inactive tracks - Mist `#E8F1EE` — Primary headings, body text on dark surfaces, and important values - Slate Text `#93AAA9` — Secondary copy, metadata, labels, and inactive controls - Signal Mint `#78E0CF` — Primary buttons, active tabs, resolved events, focus rings, and key data - Alert Coral `#FF927A` — Only investigating events, one alert node, validation errors, and sparse emphasis - Button Ink `#09201F` — Text and icons on Signal Mint buttons ### Typography - Display headlines, section titles, and large sample metrics: Space Grotesk Variable, self-hosted with @fontsource-variable/space-grotesk (OFL), weights 500/600/700 - Body copy, navigation, buttons, tabs, and form controls: Inter Variable, self-hosted with @fontsource-variable/inter (OFL), weights 400/500/600/700 - Eyebrows, map coordinates, event metadata, badges, and small system labels: IBM Plex Mono, self-hosted with @fontsource/ibm-plex-mono (OFL), weights 400/500 ### Layout & motion - Spacing: Use an 8px base grid. Content max-width is 1280px with 40px desktop and 20px mobile gutters. Major sections use 112px desktop and 76px mobile vertical padding. The header is 72px high. Hero copy and visual columns have a 56px gap; panel padding is 24–32px desktop and 18–22px mobile. Keep body measures between 48 and 66 characters. - Radius: Use 4px for tags and small badges, 8px for inputs and buttons, and 12px for major panels. Avoid pill-shaped containers except tiny status dots. Use 1px Grid Line borders and a restrained 0 20px 60px rgb(0 0 0 / 0.24) shadow only on the hero map and demo form. - Motion: Reveal major sections once with Motion whileInView: opacity 0 to 1 and translateY(22px) to 0 over 480ms with a 60ms stagger between direct children; content must remain visible without JavaScript intersection support. - Motion: On the hero map, animate route dash offset over 4.5 seconds and node rings from scale 0.75 to 1.35 with fading opacity over 2.4 seconds. Only one route and one node receive Alert Coral emphasis at a time. - Motion: Advance the simulated highlighted event every 2800ms without adding or removing rows. Pause feed freezes dash, pulse, and interval motion and changes its label to Resume feed; restarting continues from the current event. - Motion: Product views swap with AnimatePresence using 180ms opacity and translateX(10px) transitions inside a stable min-height viewer. Active tab indicator color changes over 160ms; content height must not jump dramatically. - Motion: Buttons translate upward 1px on hover and return on press over 140ms. Accordion answers use 180ms opacity and height transitions, and the mobile menu uses a 160ms fade and 8px downward entrance. - Motion: The request preview replaces the form with a 220ms opacity and 12px rise transition, then moves focus to its heading. Copy request changes its button label to Request copied for 1600ms. - Motion: Under prefers-reduced-motion, remove section reveals, route movement, node pulses, automatic event rotation, smooth scrolling, and transform transitions. Show the complete static feed and final component states immediately. - Imagery: Use no photographs, generated bitmaps, external maps, stock illustrations, or image placeholders. The hero anchor is a large original SVG operational map: simplified hand-authored continent silhouettes, a subtle dot matrix, longitude and latitude guides, six fixed location nodes, curved routes, crosshair details, and a compact event rail. Draw four distinct product-module interfaces in HTML/CSS/SVG. Use only abstract bracket, node, route, waveform, and ledger motifs; no shields, hooded figures, skulls, padlock clichés, brand logos, or certification seals. ## Pages & Sections ### Cybersecurity SaaS landing and demo request (`index.html`) 1. **Header and mobile navigation** — Create an original [BRAND] wordmark from four small square corner brackets around one mint dot. Desktop navigation links are Platform, Workflow, Trust, and FAQ, targeting their matching section IDs. The right button is [PRIMARY_CTA] and scrolls to Demo request. Add a small text status beneath the wordmark reading [PRODUCT_CATEGORY]. On mobile, show the wordmark, a compact [PRIMARY_CTA] button, and a Menu icon button. The opened menu contains all four anchors and closes after selection, on Escape, or on outside click. Do not add Sign in, account, social, or other dead controls. Layout: Sticky top header at z-40, 72px high, Deep Field at 94% opacity with backdrop blur and a 1px Grid Line bottom border. Use the 1280px container. Desktop links sit centered with 28px gaps; the wordmark and CTA anchor the ends. Mobile menu is an absolute Panel Ink panel directly below the header with full-width 48px rows. Include a skip link that appears on focus. Motion: Header remains stable. Anchors use smooth scrolling only when reduced motion is not requested. Mobile navigation follows the shared 160ms entrance and returns focus to its trigger on close. 2. **Hero pitch and animated threat map** — For the defaults, use eyebrow SECURITY OPERATIONS, WITHOUT THE NOISE, H1 See the signal. Stop the spiral., and body [BRAND] gives [AUDIENCE] one calm workspace to detect, investigate, and contain risk before it becomes downtime. Primary button is [PRIMARY_CTA] with ArrowRight; secondary button is Explore the platform and scrolls to Platform. Add three concise reassurance items: Guided product walkthrough, Your workflows and priorities, and No generic sales deck. Rewrite all three and the hero copy for alternate values. On the right, title the visual [EVENT_LABEL] with badges SIMULATED FEED and 6 SAMPLE NODES. Include a functional Pause feed button. Use six fixed locations—Seattle, São Paulo, London, Lagos, Singapore, and Sydney—with six predefined events: Credential anomaly · London · Investigating; Unusual export · Singapore · Reviewing; Privilege change · São Paulo · Verified; New device cluster · Seattle · Observing; Policy drift · Sydney · Resolved; Repeated sign-in · Lagos · Contained. Show four compact feed rows at once and highlight the active row; events are predefined sample content, not a live queue. Footer legend is Observed, Investigating, Resolved, plus Illustrative events · no live intelligence. For alternate values, replace locations only if useful and rewrite all six event names and statuses for the new topic. Layout: Hero min-height is calc(100svh - 72px), using a 42%/58% two-column grid with items centered and 48px vertical padding. Left H1 is Space Grotesk 68px/0.98, 600 weight, max-width 540px; body is 18px/1.65, max-width 510px. Actions have 12px gaps and reassurance items wrap below in mono 11px. Right visual is a Panel Ink 12px-radius panel with a 64px header, a 760×440 SVG viewBox, and a 176px event rail integrated along its bottom; total height is about 610px. The map remains the dominant first-screen element. At mobile, stack copy above the map, use H1 clamp(43px,12vw,54px), keep the primary CTA before the visual, and reduce the visual to about 440px high with a scrollable but non-page-blocking feed region. No text may clip at 390px. Motion: Hero copy enters once with a 20px rise; map follows after 100ms. Apply the specified route, node, interval, pause, and reduced-motion behavior. The SVG itself is aria-hidden; all event meaning remains available as text. 3. **Illustrative customer outcomes** — Add a narrow heading row with eyebrow ILLUSTRATIVE CUSTOMER OUTCOMES, heading A calmer queue, measured in practical terms., and a visible SAMPLE DATA badge. Use exactly four default metrics: 38% — fewer duplicate alerts in a simulated four-team comparison; 18 min — to a first triage summary in the sample workflow; 3.1× — more incidents reviewed per analyst in the illustrative scenario; 12 weeks — of searchable context shown in the product example. Add a footnote: Fictional figures for layout demonstration, not customer results or performance guarantees. Rewrite every metric and explanation for alternate values while retaining four mixed units and the sample-data label. Layout: Place this band immediately below the hero with top and bottom Grid Line borders. Four equal columns share one row at desktop, separated by vertical rules; each value is Space Grotesk 42px and each explanation is 13px/1.55 Slate Text. Use two columns on tablet and one column with horizontal rules on mobile. The heading row sits above the grid with 24px bottom spacing. Motion: Reveal the band once as a group; do not count numbers up or animate them repeatedly. 4. **Four product module tabs** — Section id Platform. Eyebrow: ONE CONNECTED WORKSPACE. Heading: From raw signal to accountable action. Intro: Explore four modules that share the same incident context. Build four functional tabs in this order. 01 Signal Ingest — Normalize events without losing their source context — sample viewer shows three source rows Cloud workload, Identity provider, Endpoint fleet with event counts, parsed status, and a small throughput sparkline. 02 Detection Studio — Tune transparent rules around your own thresholds — sample viewer shows rule Impossible travel with condition cards, threshold 2 signals / 10 min, severity Medium, and an enabled switch that really toggles locally. 03 Investigation Graph — Connect identities, assets, and activity in one view — sample viewer draws a five-node relationship graph with selected node Service account and a side panel containing three contextual facts. 04 Response Ledger — Assign, contain, and document the next move — sample viewer shows owner Mara Venn, action Disable stale token, status Ready for review, and a four-entry audit timeline. Every displayed status is sample data. For alternate values, rename all four modules and replace viewer data with equally specific topic-appropriate content while preserving ingest, configure, investigate, and response roles. Layout: Begin with a two-column heading row, then a 34%/66% workspace panel. Left tabs are full-width 104px rows with number, title, one-line description, and ArrowUpRight; the active tab has Raised Line background, a 2px Signal Mint left rule, and Mist text. Right viewer has a 52px toolbar, min-height 470px, and four entirely different code-drawn layouts rather than the same card repeated. On mobile, tabs become a 2×2 compact grid above a min-height 430px viewer; keep labels legible and simplify only decorative graph detail. Motion: Use keyboard arrow navigation across tabs and AnimatePresence for the viewer transition. The detection switch and graph node selection update local state with immediate visible feedback. No automatic tab rotation. 5. **Detection to response workflow** — Section id Workflow. Eyebrow: A SHARED OPERATING RHYTHM. Heading: One incident. Three clear moves. Intro: Keep the handoffs visible and the next action owned. Create three steps: 01 Collect — Bring cloud, identity, and endpoint events into one normalized stream. The mini UI shows three sources converging into one parsed event. 02 Correlate — Group related signals around the same identity and asset instead of opening three separate tickets. The mini UI shows three alert chips merging into one incident card. 03 Contain — Assign an owner, choose a response, and preserve a readable audit trail. The mini UI shows an owner, review checkbox, and completed ledger entry. Closing note: The interface examples use fictional events and never connect to real infrastructure. Rewrite source types, correlation logic, and response action for alternate variables. Layout: Use three equal cards connected by a horizontal 1px route line at desktop. Each card has a mono step number, 22px title, 15px body, and a 160px original diagram at the bottom. The middle card is offset downward 32px on wide screens to create rhythm without harming reading order. Stack in numerical order on mobile with a vertical connector and no offset. Motion: Cards reveal in order with a 70ms stagger. On hover, the diagram route brightens and its small node moves at most 4px; no infinite animation. 6. **Generic trust and compliance controls** — Section id Trust. Left eyebrow: CONTROL, MADE VISIBLE. Heading: Trust is a workflow, not a badge wall. Body: Give buyers a clear view of the controls your product story supports, without borrowing certification marks or implying an audit. Include text link Review common questions that scrolls to FAQ. On the right, create four generic control badges: ACCESS CONTROLS — Role-based access patterns with a original keyhole-free Users icon; ENCRYPTION CONTEXT — Clear at-rest and in-transit language with a Binary icon; AUDIT-READY EXPORTS — Portable incident histories with a FileClock icon; RETENTION OPTIONS — Configurable sample retention windows with a Database icon. Under the grid add the note Illustrative control categories only. No certification, compliance, or audit status is claimed. Below it, add three unbranded integration placeholders labeled Cloud sources, Identity sources, and Case management using simple Lucide icons. Rewrite control language for alternate values and never insert real customer or certification logos. Layout: Two-column 40%/60% section with left copy sticky only on tall desktop screens. Right controls form a 2×2 grid of Panel Ink cards, each 176px high with a small line icon, mono title, and 14px explanation. The disclaimer spans the grid in a bordered strip; integration placeholders form three quiet equal rows beneath. Mobile stacks copy and uses one control per row. Motion: Control cards reveal as two pairs. Hover changes only border color and icon color over 160ms; badges never shimmer, spin, or resemble official seals. 7. **Demo request form and local preview** — Section id Demo request. Left eyebrow: A WALKTHROUGH WITH CONTEXT. Heading: Bring one real workflow to the demo. Body: Tell us what you want to unpack and use the preview to check your request. For the defaults, list three agenda items: Your current alert sources, One investigation you want to simplify, and The response handoff you want to make clearer. Add a small note: Static template demo: no request is transmitted. Right form fields are Full name, Work email, Company, Team size select with 1–10, 11–50, 51–200, and 201+, and a textarea labeled What should the demo cover? with placeholder For example: triaging identity alerts across two cloud accounts. Submit button is Preview request. Validate trimmed name and company at 2+ characters, a conventional email pattern, nonempty team size, and a 12+ character textarea. Show inline errors and focus the first invalid field. On valid submit, make no request and replace the form with heading Your request preview is ready, a definition-list summary of all five values, and note Nothing was sent or stored. This preview exists only in the current page state. Provide Copy request, which copies a plain-text summary using the Clipboard API with a graceful manual-selection fallback, and Edit details, which restores the filled form. Do not invent a booking time, request ID, delivery promise, or success confirmation. Rewrite labels, agenda items, and placeholder for alternate values while keeping the same validation model. Layout: Use a 42%/58% two-column grid inside a Raised Line section panel. Left has 32px padding and three numbered agenda rows. Right is a Deep Field form card with 28px padding, two-column name/email and company/team rows, full-width textarea, and full-width mint submit button. Inputs are 48px high with Raised Line backgrounds, Grid Line borders, and Mist text; error text uses Alert Coral. Preview occupies the same card with 20px row gaps. Mobile stacks both columns, uses one-column fields, and retains 44px touch targets. Motion: Preview follows the shared 220ms entrance and focus behavior. Copy feedback lasts 1600ms. Errors appear without layout-destroying shifts; reduced motion uses immediate state changes. 8. **Frequently asked questions** — Section id FAQ. Heading: Specific answers before a closer look. Build five accessible accordion items with exactly one open at a time and the first open initially. Q: Is the threat map connected to live intelligence? A: No. Every route, location, status, and event in this template is predefined sample content. The pause control changes only the local animation. Q: Do the customer numbers describe real results? A: No. They are fictional figures included to demonstrate the layout and are labeled as sample data wherever they appear. Replace them with substantiated content before using the page commercially. Q: Are the trust badges certifications? A: No. They are generic control categories, not seals or audit claims. The template deliberately excludes official marks and customer logos. Q: What happens when I submit the demo form? A: The page validates your entries and creates an on-screen request preview. It does not transmit, store, email, or book anything; you can copy the summary yourself. Q: Can the product modules be changed for another platform? A: Yes. All module copy and sample data belong in the central content file. Keep the four-stage interaction model and rewrite the content for the supplied variables. Adapt every answer for alternate values so it never retains default threat terminology. Layout: Use a 36%/64% grid with heading and a short supporting note left, accordion right. Rows have top Grid Line borders, 24px vertical padding, 18px question text, and Plus icons that rotate 45 degrees when open. Answers are 15px/1.7 Slate Text with 16px bottom padding. Mobile uses one column. Motion: Use buttons with aria-expanded and aria-controls, keyboard support, and 180ms height/opacity transitions. Content remains readable if animation is disabled. 9. **Closing call to action and footer** — Closing eyebrow: START WITH ONE WORKFLOW. Heading: Make the next incident feel less uncertain. Body: See how [BRAND] could fit the way [AUDIENCE] already work. Button is [PRIMARY_CTA] and scrolls back to Demo request. Footer shows the original bracket mark, [BRAND], and a concise descriptor derived from [PRODUCT_CATEGORY]. Footer controls are Platform, Workflow, Trust, FAQ, and Demo request, all performing their named anchor actions. Add a bottom note: All interface events and outcome figures are illustrative samples. Finish with [CREDIT]. Do not add addresses, dates, social icons, legal-link placeholders, or fabricated company details. Layout: Closing panel has a Signal Mint background with Button Ink text, 48px desktop padding, and a large original route-line SVG occupying the right third without covering copy. Footer uses Deep Field, a three-column top row, and a Grid Line-separated bottom line with 24px vertical padding. Mobile stacks all content and keeps the CTA full width. Motion: Closing panel reveals once. Its static SVG does not animate; links use a 140ms color change. ## Assets - image: No raster image files or generated images are required. Create the world map, routes, node graph, sparkline, workflow diagrams, closing route motif, and bracket brand mark as original inline SVG/CSS/HTML. Do not use external map geometry, image URLs, placeholder services, or third-party illustrations. - icon: Use locally bundled lucide-react icons with consistent 1.7px strokes for ArrowRight, ArrowUpRight, Menu, X, Pause, Play, Users, Binary, FileClock, Database, Plus, Copy, Check, and small product controls. Record lucide-react, https://github.com/lucide-icons/lucide, ISC license, in ASSETS.md. - font: Self-host Space Grotesk Variable through @fontsource-variable/space-grotesk, Inter Variable through @fontsource-variable/inter, and IBM Plex Mono through @fontsource/ibm-plex-mono, all OFL-1.1. Import package CSS locally and list every package and license in ASSETS.md; never request a font CDN. ## Don'ts - Do not add a backend, serverless function, API route, database, authentication, live telemetry, external map service, third-party API, form endpoint, or network-dependent behavior. The demo form only validates and previews local state and must never claim a request was sent or booked. - Do not transmit or persist names, email addresses, company details, or any other input. No localStorage, sessionStorage, cookies, analytics, tracking pixels, hidden telemetry, or URL tracking parameters. - Do not load any CDN script, stylesheet, font, icon, map tile, image, or remote asset. Bundle all dependencies and use relative asset paths with Vite base './'. - Do not use real cybersecurity companies, product names, logos, customer marks, slogans, proprietary interfaces, exact copy, or recognizable brand color systems. Keep [BRAND] and all organizations and people fictional. - Do not use official certification seals, auditor marks, compliance logos, security guarantees, real attack attribution, real threat intelligence, customer results, or unverified claims. Retain visible SAMPLE DATA and simulated-feed labels. - Do not use shields, hooded hackers, skulls, glowing padlocks, fingerprint clichés, purple-blue neon gradients, matrix rain, stock hacker photography, anime or game characters, or real-person likenesses. - Do not copy map artwork or interface code from another product. Use the original hand-authored SVG geometry and predefined sample events specified here; no external geoJSON, tile service, or chart library. - Do not use commercial fonts, fonts.googleapis.com, fonts.gstatic.com, Adobe Fonts, restricted UI source, non-permissive packages, or dependencies outside the fixed stack. - Do not use Unsplash, Pexels, Pixabay, Google Images, placeholder-image services, generated bitmaps, third-party logos, or hotlinked files. No raster images are needed. - Do not leave navigation, feed pause, module tabs, detection switch, graph nodes, FAQ items, demo form, copy action, edit action, or closing CTA nonfunctional. Do not add dead social, login, legal, or integration links. - Do not emit source maps, copy src/ into dist/, exceed 20 MB in dist/, or require more than npm run build for the production output. Keep everything in index.html with file-name or hash-only local navigation. - Do not hard-code default threat content inside components or leave Sablegrid security copy in an alternate-variable build. Keep all editable copy and sample data in src/content.ts and use US English throughout. - Do not add SEO metadata, Open Graph tags, JSON-LD, sitemaps, keyword-stuffed headings, dates, or analytics; a plain [BRAND] document title and original favicon are enough. - Do not mention VibeFather, its license, pricing, metrics, or membership anywhere in the site except the optional rendered [CREDIT] footer link. - Do not sacrifice accessibility or responsive behavior: maintain visible focus, semantic controls, labeled fields, keyboard-operable tabs and accordions, accessible error focus, reduced-motion support, 44px touch targets, zero console errors, and no horizontal overflow at 390×844 or 1440×900. --- — Prompt by VibeFather · https://vibefather.ai/t/cybersecurity-saas-landing-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
中文参考译文(帮助理解,复制给 AI 时请用上面的英文原版)
# 网络安全 SaaS 落地页 完全按照以下描述构建此网站。将 [VARIABLES] 替换为你自己的值;其余内容保持不变。 ## 简介 为 [BRAND] 构建一个原创的单页落地站点,[BRAND] 是面向 [AUDIENCE] 的 [PRODUCT_CATEGORY]。首屏将清晰的销售主张与一个丰富的动画 SVG 世界地图相结合,地图标注为 [EVENT_LABEL],并配有模拟事件流和明确的示例数据提示。接着依次呈现产品模块、事件工作流、示意性客户成果、通用信任控制、演示请求表单、常见问题解答,以及一个聚焦的收尾行动号召。 - 受众:站点面向 [AUDIENCE],他们需要快速理解产品,并评估一次引导式演示是否值得花时间。模板所有者是一支技术型 SaaS 团队,需要一个精致、可信的营销页面,配有实质性的产品可视化,而非抽象装饰。 - 目标:让访客理解产品从检测到响应的故事,探索全部四个模块,认识到每一项指标和事件均为示例性质,并完成一次有效的演示请求预览。每个可见控件都必须在本地正常工作,任何表单数据都不得离开当前页面状态或在其中持久保存。 - 语气:冷静、精确、运营化且自信。使用具体的产品语言和有用的细节,而非恐惧、电影化的黑客陈词滥调、含糊的最高级表述或缺乏依据的安全声明。将动画活动视为示意性界面内容,绝不可当作真实防护或实时遥测的证据。 ## 技术栈 - 框架:Vite 5 + React 18 + TypeScript - 样式:Tailwind CSS 3.4 - 库:React 18(MIT)、Vite 5(MIT)、TypeScript(Apache-2.0)、Tailwind CSS 3.4(MIT)、motion(MIT)、lucide-react(ISC)、@fontsource-variable/space-grotesk(OFL-1.1)、@fontsource-variable/inter(OFL-1.1)、@fontsource/ibm-plex-mono(OFL-1.1) - 构建:`npm run build` → `dist/` 中的静态文件。无后端、无服务器代码、无外部 API。 - 设置: - 使用 Vite 5 搭配 React 18 和 TypeScript。在 vite.config.ts 中设置 base: './',将 build.sourcemap 设为 false,并且只向 dist/ 输出静态生产文件。 - 使用下方精确的颜色、字体族、间距、圆角和阴影配置 Tailwind CSS 3.4。将地图关键帧、焦点样式、选中颜色和减少动态效果覆盖放入 src/index.css。 - 将所有可编辑的品牌文案、标题、模块文案和数据、地图事件、指标、信任标签、FAQ 和表单选项保留在 src/content.ts 中,并使用 TypeScript 接口。组件不得嵌入仅适合默认主题的文案。 - 当变量值变化时,重写每个主题特定的标题、产品模块、事件标签、示例事件、指标、工作流步骤、信任说明、FAQ 答案和表单选项,以适配 [PRODUCT_CATEGORY]、[AUDIENCE] 和 [EVENT_LABEL],同时保持布局和交互不变。 - 使用 Motion for React 实现区块入场、产品标签切换、手风琴答案和请求预览状态。地图使用原创内联 SVG 和 CSS 关键帧;不要添加地图、图表或动画依赖。 - 创建一个确定性的 ThreatMap 组件,包含固定节点、路线和六个预定义事件。使用一个清理过的 interval 每 2800ms 轮换高亮事件;Pause feed 必须同时停止该 interval 和装饰动画。不要使用随机数据或外部遥测。 - 将产品标签状态、移动菜单状态、打开的 FAQ 状态、feed 暂停状态和表单状态仅保存在 React 内存中。不要使用 localStorage、sessionStorage、cookies、分析、URL 跟踪参数或任何网络请求。 - 从 Fontsource 本地导入 Space Grotesk Variable、Inter Variable 和 IBM Plex Mono。创建 ASSETS.md,列出三个字体包、lucide-react、它们的来源和许可证,并说明所有地图和产品 artwork 均为原创代码绘制的 SVG/CSS,不含栅格图像。 - 使用语义化地标、带标签的控件、可见焦点、44px 最小触摸目标、可键盘操作的标签和手风琴,以及减少动态效果行为。在 1440×900 和 390×844 下验证完整页面,控制台零错误且无水平溢出。 ## 变量 - [BRAND] — 产品品牌(默认:"Sablegrid")。一个虚构的产品名称,用于原始方括号标记、页眉、文案、表单预览和页脚。 - [PRODUCT_CATEGORY] — 产品类别(默认:"threat detection and response platform")。一个简洁的小写类别短语;所有产品和流程文案都必须遵循它。 - [AUDIENCE] — 主要受众(默认:"lean security teams")。一个简洁的小写受众描述,用于主视觉和销售文案。 - [EVENT_LABEL] — 地图事件标签(默认:"Threat activity")。一个简短的首字母大写标签,用于地图及其模拟事件,例如 Data risk activity。 - [PRIMARY_CTA] — 主要行动号召(默认:"Request a demo")。一个简短的按钮标签,点击后滚动访客至本地演示请求表单。 - [CREDIT] — 在页脚保留一个小型 "Template by VibeFather" 链接至 https://vibefather.ai/t/cybersecurity-saas-landing-page(默认:是;删除此行即可移除) 页面与区块下的文案是为默认值编写的。如果你的值不同,请为它们重写每一个标题、段落、标签和图片——保持相同的长度、语气和结构。布局、颜色、字体和动效保持所述不变。 将所有文案、图片路径和链接放在一个内容文件中(例如 `src/content.ts`),按区块作为键,以便之后无需改动组件即可替换内容。 ## 设计 ### 颜色(Colors) - 深场(Deep Field)`#071114` — 页面背景、页眉和页脚 - 面板墨色(Panel Ink)`#0D1C20` — 地图、产品查看器、表单和凸起区块表面 - 凸起线条(Raised Line)`#173036` — 选中行、输入框背景和安静色调块 - 网格线(Grid Line)`#28434A` — 边框、坐标线、分隔线和非活动轨道 - 薄雾(Mist)`#E8F1EE` — 主标题、深色表面上的正文文本和重要数值 - 石板文本(Slate Text)`#93AAA9` — 次要文案、元数据、标签和非活动控件 - 信号薄荷(Signal Mint)`#78E0CF` — 主按钮、活动标签页、已解决事件、焦点环和关键数据 - 警报珊瑚(Alert Coral)`#FF927A` — 仅用于调查中的事件、一个警报节点、验证错误和稀疏强调 - 按钮墨色(Button Ink)`#09201F` — Signal Mint 按钮上的文本和图标 ### 排版 - 展示标题、区块标题和大型示例指标:Space Grotesk Variable,通过 @fontsource-variable/space-grotesk(OFL)自托管,字重 500/600/700 - 正文文案、导航、按钮、标签页和表单控件:Inter Variable,通过 @fontsource-variable/inter(OFL)自托管,字重 400/500/600/700 - 眉题、地图坐标、事件元数据、徽章和小型系统标签:IBM Plex Mono,通过 @fontsource/ibm-plex-mono(OFL)自托管,字重 400/500 ### 布局与动效 - 间距:使用 8px 基础网格。内容最大宽度为 1280px,桌面端和移动端边距分别为 40px 和 20px。主要区块的垂直内边距在桌面端为 112px,移动端为 76px。页眉高度为 72px。Hero 文案和视觉列之间的间距为 56px;面板内边距在桌面端为 24–32px,移动端为 18–22px。正文行宽保持在 48 到 66 个字符之间。 - 圆角:标签和小徽章使用 4px,输入框和按钮使用 8px,主要面板使用 12px。除微小的状态点外,避免使用胶囊形容器。使用 1px Grid Line 边框,并且仅在 Hero 地图和演示表单上使用克制的 0 20px 60px rgb(0 0 0 / 0.24) 阴影。 - 动效:使用 Motion 的 whileInView 让主要区块显示一次:不透明度从 0 到 1,translateY(22px) 到 0,持续 480ms,直接子元素之间错开 60ms;即使不支持 JavaScript 交叉观察,内容也必须保持可见。 - 动效:在 Hero 地图上,路线虚线偏移在 4.5 秒内动画,节点环从 scale 0.75 到 1.35,并在 2.4 秒内淡出不透明度。一次只有一个路线和一个节点获得 Alert Coral 强调。 - 动效:每 2800ms 推进模拟的高亮事件,不添加或删除行。暂停信息流会冻结虚线、脉冲和间隔运动,并将其标签更改为 Resume feed;重新启动会从当前事件继续。 - 动效:产品视图使用 AnimatePresence 进行切换,在稳定的最小高度查看器内使用 180ms 不透明度和 translateX(10px) 过渡。活动标签指示器颜色在 160ms 内变化;内容高度不得剧烈跳动。 - 动效:按钮在悬停时向上平移 1px,按下时在 140ms 内返回。手风琴答案使用 180ms 不透明度和高度过渡,移动菜单使用 160ms 淡入和 8px 向下进入。 - 动效:请求预览以 220ms 不透明度和 12px 上升过渡替换表单,然后将焦点移动到其标题。复制请求会将其按钮标签更改为 Request copied,持续 1600ms。 - 动效:在 prefers-reduced-motion 下,移除区块显示、路线移动、节点脉冲、自动事件轮换、平滑滚动和变换过渡。立即显示完整的静态信息流和最终组件状态。 - 图像:不使用照片、生成的位图、外部地图、库存插图或图像占位符。Hero 锚点是一个大型原创 SVG 操作地图:简化手绘大陆轮廓、微妙的点阵、经度和纬度参考线、六个固定位置节点、弯曲路线、十字准线细节和紧凑的事件栏。使用 HTML/CSS/SVG 绘制四个不同的产品模块界面。仅使用抽象的括号、节点、路线、波形和账本图案;不使用盾牌、兜帽人物、骷髅、挂锁陈词滥调、品牌标志或认证印章。 ## 页面与区块 ### 网络安全 SaaS 落地页与演示请求(`index.html`) 1. **页眉与移动端导航** — 用四个小方形角括号围绕一个薄荷色圆点,创建原创的 [BRAND] 字标。桌面端导航链接为 Platform、Workflow、Trust 和 FAQ,分别指向对应的区块 ID。右侧按钮为 [PRIMARY_CTA],点击后滚动至 Demo request。在字标下方添加一行小字状态,内容为 [PRODUCT_CATEGORY]。移动端显示字标、紧凑的 [PRIMARY_CTA] 按钮和一个 Menu 图标按钮。展开的菜单包含全部四个锚点,并在选择后、按 Escape 或点击外部时关闭。不要添加 Sign in、账户、社交或其他无效控件。 布局:粘性顶部页眉位于 z-40,高 72px,Deep Field 以 94% 不透明度配合背景模糊,底部为 1px Grid Line 边框。使用 1280px 容器。桌面端链接居中排列,间距 28px;字标和 CTA 分别锚定两端。移动端菜单是绝对定位的 Panel Ink 面板,直接位于页眉下方,行高 48px、占满宽度。包含一个在聚焦时出现的跳转链接。 动效:页眉保持稳定。仅在未请求减少动效时,锚点使用平滑滚动。移动端导航遵循共享的 160ms 入场动效,并在关闭时将焦点返回其触发按钮。 2. **首屏主张与动画威胁地图** — 默认情况下,使用眉题 SECURITY OPERATIONS, WITHOUT THE NOISE,H1 为 See the signal. Stop the spiral.,正文为 [BRAND] gives [AUDIENCE] one calm workspace to detect, investigate, and contain risk before it becomes downtime.。主按钮为 [PRIMARY_CTA],带 ArrowRight;次按钮为 Explore the platform,点击后滚动至 Platform。添加三条简洁的安心说明:Guided product walkthrough、Your workflows and priorities 和 No generic sales deck。为替代值重写这三条说明和首屏文案。右侧视觉区域标题为 [EVENT_LABEL],带有 SIMULATED FEED 和 6 SAMPLE NODES 徽章。包含一个可用的 Pause feed 按钮。使用六个固定地点——Seattle、São Paulo、London、Lagos、Singapore 和 Sydney——以及六个预定义事件:Credential anomaly · London · Investigating;Unusual export · Singapore · Reviewing;Privilege change · São Paulo · Verified;New device cluster · Seattle · Observing;Policy drift · Sydney · Resolved;Repeated sign-in · Lagos · Contained。一次显示四行紧凑的 feed 行,并高亮当前活动行;事件为预定义示例内容,而非实时队列。页脚图例为 Observed、Investigating、Resolved,外加 Illustrative events · no live intelligence。对于替代值,仅在有用时替换地点,并针对新主题重写全部六个事件名称和状态。 布局:首屏最小高度为 calc(100svh - 72px),使用 42%/58% 双列网格,项目居中,垂直内边距 48px。左侧 H1 为 Space Grotesk 68px/0.98,字重 600,最大宽度 540px;正文为 18px/1.65,最大宽度 510px。操作按钮间距 12px,安心说明项以等宽 11px 在下方换行。右侧视觉区域为 Panel Ink 12px 圆角面板,头部高 64px,SVG viewBox 为 760×440,底部集成 176px 的事件栏;总高度约 610px。地图仍是首屏的主导元素。移动端将文案堆叠在地图上方,H1 使用 clamp(43px,12vw,54px),主 CTA 保持在视觉区域之前,并将视觉区域高度降至约 440px,feed 区域可滚动但不阻塞页面。在 390px 宽度下任何文字都不得被裁切。 动效:首屏文案以 20px 上浮一次性入场;地图在 100ms 后跟随。应用指定的路线、节点、间隔、暂停和减少动效行为。SVG 本身为 aria-hidden;所有事件含义仍以文本形式提供。 3. **示意性客户成果** — 添加一个窄标题行,眉题为 ILLUSTRATIVE CUSTOMER OUTCOMES,标题为 A calmer queue, measured in practical terms.,并带一个可见的 SAMPLE DATA 徽章。使用恰好四个默认指标:38% — fewer duplicate alerts in a simulated four-team comparison;18 min — to a first triage summary in the sample workflow;3.1× — more incidents reviewed per analyst in the illustrative scenario;12 weeks — of searchable context shown in the product example。添加脚注:Fictional figures for layout demonstration, not customer results or performance guarantees。为替代值重写每个指标和说明,同时保留四个混合单位和样本数据标签。 布局:将此条带紧接首屏下方放置,顶部和底部为 Grid Line 边框。桌面端四等列共享一行,由垂直分隔线隔开;每个数值为 Space Grotesk 42px,每条说明为 13px/1.55 Slate Text。平板端使用两列,移动端使用单列并带水平分隔线。标题行位于网格上方,底部间距 24px。 动效:条带作为一组一次性显现;不要数字递增或重复动画。 4. **四个产品模块标签页** — 区块 id 为 Platform。眉题:ONE CONNECTED WORKSPACE。标题:From raw signal to accountable action。简介:Explore four modules that share the same incident context。按此顺序构建四个可用标签页。01 Signal Ingest — Normalize events without losing their source context — 示例查看器显示三行来源 Cloud workload、Identity provider、Endpoint fleet,包含事件计数、解析状态和一个小型吞吐量迷你图。02 Detection Studio — Tune transparent rules around your own thresholds — 示例查看器显示规则 Impossible travel,包含条件卡片、阈值 2 signals / 10 min、严重性 Medium,以及一个真正在本地切换的启用开关。03 Investigation Graph — Connect identities, assets, and activity in one view — 示例查看器绘制一个五节点关系图,选中节点为 Service account,侧面板包含三条上下文事实。04 Response Ledger — Assign, contain, and document the next move — 示例查看器显示负责人 Mara Venn、操作 Disable stale token、状态 Ready for review,以及一条四项审计时间线。所有显示的状态均为样本数据。对于替代值,重命名全部四个模块,并用同样具体、符合主题的内容替换查看器数据,同时保留摄取、配置、调查和响应角色。 布局:以双列标题行开始,然后是 34%/66% 的工作区面板。左侧标签页为全宽 104px 行,包含编号、标题、一行描述和 ArrowUpRight;活动标签页具有 Raised Line 背景、2px Signal Mint 左边线和 Mist 文字。右侧查看器有 52px 工具栏、最小高度 470px,以及四个完全不同的代码绘制布局,而非重复同一张卡片。移动端标签页变为 2×2 紧凑网格,位于最小高度 430px 的查看器上方;保持标签清晰可读,仅简化装饰性图表细节。 动效:在标签页之间使用键盘方向键导航,并使用 AnimatePresence 实现查看器过渡。检测开关和图表节点选择更新本地状态,并立即给出可见反馈。无自动标签页轮换。 5. **从检测到响应的工作流** — 区块 id 为 Workflow。眉题:A SHARED OPERATING RHYTHM。标题:One incident. Three clear moves。简介:Keep the handoffs visible and the next action owned。创建三个步骤:01 Collect — Bring cloud, identity, and endpoint events into one normalized stream。迷你 UI 显示三个来源汇聚为一个解析后的事件。02 Correlate — Group related signals around the same identity and asset instead of opening three separate tickets。迷你 UI 显示三个告警芯片合并为一张事件卡片。03 Contain — Assign an owner, choose a response, and preserve a readable audit trail。迷你 UI 显示负责人、审核复选框和已完成的账本条目。结尾说明:The interface examples use fictional events and never connect to real infrastructure。为替代变量重写来源类型、关联逻辑和响应操作。 布局:桌面端使用三张等宽卡片,由一条水平 1px 路线连接。每张卡片有一个等宽步骤编号、22px 标题、15px 正文,以及底部 160px 的原创图表。宽屏上中间卡片向下偏移 32px,以营造节奏感而不损害阅读顺序。移动端按数字顺序堆叠,带垂直连接线且无偏移。 动效:卡片按顺序显现,间隔 70ms。悬停时,图表路线变亮,其小节点移动最多 4px;无无限动画。 6. **通用信任与合规控件** — 区块 id 为 Trust。左侧眉题:CONTROL, MADE VISIBLE。标题:Trust is a workflow, not a badge wall。正文:让买家清晰了解你的产品叙事所支持的控件,而不借用认证标志或暗示审计。包含文本链接 Review common questions,滚动至 FAQ。在右侧,创建四个通用控件徽章:ACCESS CONTROLS — 基于角色的访问模式,配原创无钥匙孔 Users 图标;ENCRYPTION CONTEXT — 清晰的静态与传输中语言,配 Binary 图标;AUDIT-READY EXPORTS — 可移植的事件历史,配 FileClock 图标;RETENTION OPTIONS — 可配置的样本保留窗口,配 Database 图标。在网格下方添加注释 Illustrative control categories only. No certification, compliance, or audit status is claimed. 在其下方,添加三个无品牌集成占位符,分别标记为 Cloud sources、Identity sources 和 Case management,使用简单的 Lucide 图标。为替代值重写控件语言,绝不插入真实客户或认证标志。 布局:40%/60% 双栏区块,左侧文案仅在高度足够的桌面屏幕上粘性定位。右侧控件形成 2×2 的 Panel Ink 卡片网格,每张高 176px,含小线图标、等宽标题和 14px 说明。免责声明以带边框条带横跨网格;集成占位符在其下方形成三个安静等宽行。移动端堆叠文案,每行一个控件。 动效:控件卡片以两对形式显现。悬停仅在 160ms 内改变边框颜色和图标颜色;徽章绝不闪烁、旋转或类似官方印章。 7. **演示请求表单与本地预览** — 区块 id 为 Demo request。左侧眉题:A WALKTHROUGH WITH CONTEXT。标题:Bring one real workflow to the demo。正文:告诉我们你想展开什么,并使用预览检查你的请求。对于默认值,列出三个议程项:Your current alert sources、One investigation you want to simplify 和 The response handoff you want to make clearer。添加小注释:Static template demo: no request is transmitted。右侧表单字段为 Full name、Work email、Company、Team size 选择(1–10、11–50、51–200 和 201+),以及标记为 What should the demo cover? 的文本域,占位符为 For example: triaging identity alerts across two cloud accounts。提交按钮为 Preview request。验证去除首尾空格后的姓名和公司至少 2 个字符、常规电子邮件模式、团队规模非空、文本域至少 12 个字符。显示内联错误并聚焦第一个无效字段。有效提交时,不发出任何请求,将表单替换为标题 Your request preview is ready、全部五个值的定义列表摘要,以及注释 Nothing was sent or stored. This preview exists only in the current page state。提供 Copy request,使用 Clipboard API 复制纯文本摘要,并带有优雅的手动选择回退;以及 Edit details,恢复已填写的表单。不要虚构预约时间、请求 ID、交付承诺或成功确认。为替代值重写标签、议程项和占位符,同时保持相同的验证模型。 布局:在 Raised Line 区块面板内使用 42%/58% 双栏网格。左侧有 32px 内边距和三个编号议程行。右侧是 Deep Field 表单卡片,28px 内边距,姓名/电子邮件和公司/团队为双栏行,全宽文本域,全宽薄荷色提交按钮。输入框高 48px,使用 Raised Line 背景、Grid Line 边框和 Mist 文本;错误文本使用 Alert Coral。预览占据同一卡片,行间距 20px。移动端堆叠两栏,使用单栏字段,并保留 44px 触摸目标。 动效:预览遵循共享的 220ms 入场和聚焦行为。复制反馈持续 1600ms。错误出现时不造成破坏布局的位移;减少动效时使用即时状态变化。 8. **常见问题** — 区块 id 为 FAQ。标题:Specific answers before a closer look。构建五个可访问的手风琴项,一次恰好一个打开,初始时第一个打开。问:Is the threat map connected to live intelligence? 答:No. Every route, location, status, and event in this template is predefined sample content. The pause control changes only the local animation. 问:Do the customer numbers describe real results? 答:No. They are fictional figures included to demonstrate the layout and are labeled as sample data wherever they appear. Replace them with substantiated content before using the page commercially. 问:Are the trust badges certifications? 答:No. They are generic control categories, not seals or audit claims. The template deliberately excludes official marks and customer logos. 问:What happens when I submit the demo form? 答:The page validates your entries and creates an on-screen request preview. It does not transmit, store, email, or book anything; you can copy the summary yourself. 问:Can the product modules be changed for another platform? 答:Yes. All module copy and sample data belong in the central content file. Keep the four-stage interaction model and rewrite the content for the supplied variables. 为替代值调整每个答案,使其绝不保留默认威胁术语。 布局:使用 36%/64% 网格,左侧为标题和简短辅助注释,右侧为手风琴。行顶部有 Grid Line 边框,24px 垂直内边距,18px 问题文本,打开时 Plus 图标旋转 45 度。答案为 15px/1.7 Slate Text,底部内边距 16px。移动端使用单栏。 动效:使用带 aria-expanded 和 aria-controls 的按钮、键盘支持,以及 180ms 高度/不透明度过渡。禁用动画时内容仍可读。 9. **结尾行动号召与页脚** — 结尾眉题:START WITH ONE WORKFLOW。标题:Make the next incident feel less uncertain。正文:See how [BRAND] could fit the way [AUDIENCE] already work。按钮为 [PRIMARY_CTA],滚动回 Demo request。页脚显示原创括号标记、[BRAND],以及从 [PRODUCT_CATEGORY] 派生的简洁描述。页脚控件为 Platform、Workflow、Trust、FAQ 和 Demo request,均执行其命名的锚点操作。添加底部注释:All interface events and outcome figures are illustrative samples。以 [CREDIT] 结束。不要添加地址、日期、社交图标、法律链接占位符或虚构公司详情。 布局:结尾面板使用 Signal Mint 背景和 Button Ink 文本,桌面内边距 48px,右侧三分之一处放置大型原创路线 SVG,不覆盖文案。页脚使用 Deep Field,三栏顶行,以及以 Grid Line 分隔的底行,垂直内边距 24px。移动端堆叠所有内容,CTA 保持全宽。 动效:结尾面板显现一次。其静态 SVG 不动画;链接使用 140ms 颜色变化。 ## 资产 - 图像:无需任何栅格图像文件或生成的图像。将世界地图、路线、节点图、迷你折线图、工作流示意图、收尾路线图案和括号品牌标记全部创建为原创的内联 SVG/CSS/HTML。不要使用外部地图几何数据、图像 URL、占位符服务或第三方插图。 - 图标:使用本地打包的 lucide-react 图标,为 ArrowRight、ArrowUpRight、Menu、X、Pause、Play、Users、Binary、FileClock、Database、Plus、Copy、Check 以及小型产品控件采用一致的 1.7px 描边。在 ASSETS.md 中记录 lucide-react、https://github.com/lucide-icons/lucide、ISC 许可证。 - 字体:通过 @fontsource-variable/space-grotesk 自托管 Space Grotesk Variable,通过 @fontsource-variable/inter 自托管 Inter Variable,通过 @fontsource/ibm-plex-mono 自托管 IBM Plex Mono,均为 OFL-1.1。在本地导入包 CSS,并在 ASSETS.md 中列出每个包和许可证;绝不请求字体 CDN。 ## 不要做 - 不要添加后端、无服务器函数、API 路由、数据库、身份验证、实时遥测、外部地图服务、第三方 API、表单端点或依赖网络的行为。演示表单仅验证并预览本地状态,绝不能声称请求已发送或已预订。 - 不要传输或持久化姓名、电子邮件地址、公司详情或任何其他输入。不得使用 localStorage、sessionStorage、cookie、分析、跟踪像素、隐藏遥测或 URL 跟踪参数。 - 不要加载任何 CDN 脚本、样式表、字体、图标、地图瓦片、图像或远程资源。打包所有依赖项,并使用相对资源路径与 Vite base './'。 - 不要使用真实的网络安全公司、产品名称、徽标、客户标记、口号、专有界面、精确文案或可识别的品牌色系。保持 [BRAND] 及所有组织和人物为虚构。 - 不要使用官方认证印章、审计员标记、合规徽标、安全保证、真实攻击归因、真实威胁情报、客户结果或未经证实的声明。保留可见的 SAMPLE DATA 和模拟信息源标签。 - 不要使用盾牌、连帽黑客、骷髅、发光挂锁、指纹陈词滥调、紫蓝色霓虹渐变、矩阵雨、库存黑客摄影、动漫或游戏角色或真人肖像。 - 不要复制其他产品的地图图稿或界面代码。使用此处指定的原创手写 SVG 几何图形和预定义示例事件;不得使用外部 geoJSON、瓦片服务或图表库。 - 不要使用商业字体、fonts.googleapis.com、fonts.gstatic.com、Adobe Fonts、受限 UI 源、非宽松许可的包或固定技术栈之外的依赖项。 - 不要使用 Unsplash、Pexels、Pixabay、Google Images、占位图服务、生成的位图、第三方徽标或热链接文件。无需栅格图像。 - 不要让导航、信息源暂停、模块选项卡、检测开关、图形节点、FAQ 项、演示表单、复制操作、编辑操作或结尾 CTA 失效。不要添加无效的社交、登录、法律或集成链接。 - 不要生成源映射、将 src/ 复制到 dist/、使 dist/ 超过 20 MB,或要求生产输出执行超过 npm run build 的操作。将所有内容保留在 index.html 中,仅使用文件名或哈希的本地导航。 - 不要在组件内硬编码默认威胁内容,也不要在替代变量构建中保留 Sablegrid 安全文案。将所有可编辑文案和示例数据保留在 src/content.ts 中,并全程使用美式英语。 - 不要添加 SEO 元数据、Open Graph 标签、JSON-LD、站点地图、关键词堆砌的标题、日期或分析;一个简单的 [BRAND] 文档标题和原创 favicon 就足够了。 - 除可选的渲染 [CREDIT] 页脚链接外,不要在网站任何位置提及 VibeFather、其许可证、定价、指标或会员资格。 - 不要牺牲可访问性或响应式行为:保持可见焦点、语义控件、带标签的字段、键盘可操作的选项卡和手风琴、可访问的错误焦点、减少动态效果支持、44px 触摸目标、零控制台错误,以及在 390×844 或 1440×900 下无水平溢出。 --- — Prompt by VibeFather · https://vibefather.ai/t/cybersecurity-saas-landing-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: "Cybersecurity SaaS Landing Page"
colors:
deep_field: "#071114"
panel_ink: "#0D1C20"
raised_line: "#173036"
grid_line: "#28434A"
mist: "#E8F1EE"
slate_text: "#93AAA9"
signal_mint: "#78E0CF"
alert_coral: "#FF927A"
button_ink: "#09201F"
typography:
display_headlines_section_titles_and_large_sample_metrics: { family: "Space Grotesk Variable, self-hosted with @fontsource-variable/space-grotesk", weights: [500, 600, 700] }
body_copy_navigation_buttons_tabs_and_form_controls: { family: "Inter Variable, self-hosted with @fontsource-variable/inter", weights: [400, 500, 600, 700] }
eyebrows_map_coordinates_event_metadata_badges_and_small_system_labels: { family: "IBM Plex Mono, self-hosted with @fontsource/ibm-plex-mono", weights: [400, 500] }
spacing: "Use an 8px base grid. Content max-width is 1280px with 40px desktop and 20px mobile gutters. Major sections use 112px desktop and 76px mobile vertical padding. The header is 72px high. Hero copy and visual columns have a 56px gap; panel padding is 24–32px desktop and 18–22px mobile. Keep body measures between 48 and 66 characters."
radius: "Use 4px for tags and small badges, 8px for inputs and buttons, and 12px for major panels. Avoid pill-shaped containers except tiny status dots. Use 1px Grid Line borders and a restrained 0 20px 60px rgb(0 0 0 / 0.24) shadow only on the hero map and demo form."
---
# Cybersecurity SaaS Landing 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
- **Deep Field** `#071114` — Page background, header, and footer
- **Panel Ink** `#0D1C20` — Map, product viewer, form, and raised section surfaces
- **Raised Line** `#173036` — Selected rows, input backgrounds, and quiet tonal blocks
- **Grid Line** `#28434A` — Borders, coordinate rules, dividers, and inactive tracks
- **Mist** `#E8F1EE` — Primary headings, body text on dark surfaces, and important values
- **Slate Text** `#93AAA9` — Secondary copy, metadata, labels, and inactive controls
- **Signal Mint** `#78E0CF` — Primary buttons, active tabs, resolved events, focus rings, and key data
- **Alert Coral** `#FF927A` — Only investigating events, one alert node, validation errors, and sparse emphasis
- **Button Ink** `#09201F` — Text and icons on Signal Mint buttons
## Typography
- **Display headlines, section titles, and large sample metrics** — Space Grotesk Variable, self-hosted with @fontsource-variable/space-grotesk (OFL), weights 500/600/700. Self-host the font files.
- **Body copy, navigation, buttons, tabs, and form controls** — Inter Variable, self-hosted with @fontsource-variable/inter (OFL), weights 400/500/600/700. Self-host the font files.
- **Eyebrows, map coordinates, event metadata, badges, and small system labels** — IBM Plex Mono, self-hosted with @fontsource/ibm-plex-mono (OFL), weights 400/500. Self-host the font files.
## Spacing & shape
- Spacing: Use an 8px base grid. Content max-width is 1280px with 40px desktop and 20px mobile gutters. Major sections use 112px desktop and 76px mobile vertical padding. The header is 72px high. Hero copy and visual columns have a 56px gap; panel padding is 24–32px desktop and 18–22px mobile. Keep body measures between 48 and 66 characters.
- Radius: Use 4px for tags and small badges, 8px for inputs and buttons, and 12px for major panels. Avoid pill-shaped containers except tiny status dots. Use 1px Grid Line borders and a restrained 0 20px 60px rgb(0 0 0 / 0.24) shadow only on the hero map and demo form.
## Motion
- Reveal major sections once with Motion whileInView: opacity 0 to 1 and translateY(22px) to 0 over 480ms with a 60ms stagger between direct children; content must remain visible without JavaScript intersection support.
- On the hero map, animate route dash offset over 4.5 seconds and node rings from scale 0.75 to 1.35 with fading opacity over 2.4 seconds. Only one route and one node receive Alert Coral emphasis at a time.
- Advance the simulated highlighted event every 2800ms without adding or removing rows. Pause feed freezes dash, pulse, and interval motion and changes its label to Resume feed; restarting continues from the current event.
- Product views swap with AnimatePresence using 180ms opacity and translateX(10px) transitions inside a stable min-height viewer. Active tab indicator color changes over 160ms; content height must not jump dramatically.
- Buttons translate upward 1px on hover and return on press over 140ms. Accordion answers use 180ms opacity and height transitions, and the mobile menu uses a 160ms fade and 8px downward entrance.
- The request preview replaces the form with a 220ms opacity and 12px rise transition, then moves focus to its heading. Copy request changes its button label to Request copied for 1600ms.
- Under prefers-reduced-motion, remove section reveals, route movement, node pulses, automatic event rotation, smooth scrolling, and transform transitions. Show the complete static feed and final component states immediately.
## Imagery
Use no photographs, generated bitmaps, external maps, stock illustrations, or image placeholders. The hero anchor is a large original SVG operational map: simplified hand-authored continent silhouettes, a subtle dot matrix, longitude and latitude guides, six fixed location nodes, curved routes, crosshair details, and a compact event rail. Draw four distinct product-module interfaces in HTML/CSS/SVG. Use only abstract bracket, node, route, waveform, and ledger motifs; no shields, hooded figures, skulls, padlock clichés, brand logos, or certification seals.
## Tone
Calm, exact, operational, and assured. Use concrete product language and useful detail instead of fear, cinematic hacker clichés, vague superlatives, or unsupported security claims. Treat animated activity as illustrative interface content, never as evidence of real protection or live telemetry.
---
— Prompt by VibeFather · https://vibefather.ai/t/cybersecurity-saas-landing-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
改成你自己的
- 云基础设施监控初创公司:将 PRODUCT_CATEGORY 设为可观测性平台,把地图事件重新标记为服务事件,并围绕指标、追踪、日志和告警重写四个标签页。
- 合规自动化供应商:将 EVENT_LABEL 设为控制漂移活动,把工作流换成评估、修复和证明,并将信任徽章替换为框架覆盖标签。
- 欺诈检测团队:将 AUDIENCE 设为支付风险团队,把示例事件队列重写为交易异常,并更改演示表单选项以匹配欺诈审查工作流。
- 独立安全顾问:将 BRAND 设为你的业务名称,保留演示表单作为预约预览,并重写模块标签页以描述你的评估和响应服务。
网络安全 SaaS 落地页:常见问题
如何把这个网络安全落地页变成隐私运营平台?
网络安全 SaaS 落地页模板包含一个备选案例,可将安全运营网站变为隐私运营平台,同时保留同一视觉系统。将 PRODUCT_CATEGORY 设为隐私运营,EVENT_LABEL 设为数据风险活动,并重写四个产品标签页、工作流步骤、示例指标、信任徽章和 FAQ,使其描述同意管理、数据映射和主体请求,而非检测与响应。
如何把这个深色 SaaS 模板改造成其他技术产品?
将 PRODUCT_CATEGORY 和 AUDIENCE 设为你自己的产品和买家,然后重写四个产品标签页,使其展示你自己的数据接入、检测、调查和响应对应内容,或替换为你自己的工作流阶段。在单个带类型的内容文件中更新三步工作流、示意性成果指标、信任控制徽章、地图事件和 FAQ。保持深蓝黑配色、等宽标签和模拟数据提示不变。
怎么用 AI 做一个网络安全 SaaS 落地页?
复制本页的提示词,或者运行 npx vibefather add cybersecurity-saas-landing-page,把 [BRAND]、[AUDIENCE]、[EVENT_LABEL]、[PRIMARY_CTA] 换成你自己的内容,再粘贴到 Claude Code、Codex、Cursor 等 AI 编程工具里。在线演示就是用这份提示词原样做出来的。
网络安全 SaaS 落地页模板的演示是哪个 AI 模型做的?
演示由 Kimi K3.1 Pro 在 Kimi Code 里完成;另一个案例由 DeepSeek V4.1 Flash 在 DeepSeek Harness 里完成。每次都用公开的提示词原样生成,没有额外补充,可以并排比较不同模型的效果。