# CloudPulse Brand Guidelines

## Brand Identity

**Product Name:** CloudPulse
**Tagline:** "Monitor smarter, respond faster."
**Domain:** cloudpulse.io

## Voice & Tone

- **Confident but not arrogant.** We know our product is excellent — we let results speak.
- **Technical but accessible.** Engineers are our audience, but clarity beats jargon.
- **Action-oriented.** Every sentence should move the reader toward a decision.
- **Concise.** Short sentences. No filler. Every word earns its place.
- **Human.** We solve real problems for real teams. Avoid corporate-speak.

### Writing Rules

1. Use active voice ("CloudPulse detects anomalies" not "Anomalies are detected").
2. Lead with benefits, follow with features.
3. Numbers over adjectives ("99.9% uptime" not "incredibly reliable").
4. Address the reader as "you" / "your team".
5. Avoid superlatives unless backed by data.

## Color Palette

| Role      | Name         | Hex     | Usage                                          |
| --------- | ------------ | ------- | ---------------------------------------------- |
| Primary   | Pulse Blue   | #2563EB | CTAs, links, primary buttons, key icons        |
| Secondary | Vivid Violet | #7C3AED | Gradients, accents, premium tier badges        |
| Accent    | Signal Green | #10B981 | Success states, uptime indicators, check marks |
| Dark      | Slate Dark   | #1E293B | Body text, headings, dark backgrounds          |
| Light     | Cloud White  | #F8FAFC | Page backgrounds, card surfaces                |

### Gradient

Primary gradient: `linear-gradient(135deg, #2563EB, #7C3AED)` — used for hero backgrounds, featured elements, and hover states.

## Typography

- **Headings:** System sans-serif stack: `-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif`
- **Body:** Same stack, regular weight.
- **Monospace (code/metrics):** `"SF Mono", "Cascadia Code", "Fira Code", Consolas, monospace`
- **Scale:** 16px base. Headings: h1=3rem, h2=2.25rem, h3=1.5rem, h4=1.25rem.
- **Line height:** 1.6 for body, 1.2 for headings.
- **Font weights:** 400 (body), 600 (subheadings), 700 (headings).

## Naming Conventions

- Always write "CloudPulse" as one word, capital C and P.
- Feature names use Title Case: "Anomaly Detection", "Incident Timeline".
- Never abbreviate the product name (no "CP" or "CPulse").
- Use "dashboard" (lowercase) for the UI, "Dashboard" when referring to the named product feature.

## Iconography

- Use CSS/SVG shapes only — no external image files.
- Prefer simple geometric forms (circles, rounded rectangles, pulse lines).
- Icon color follows the nearest semantic context (blue for actions, green for success, violet for premium).

## Spacing & Layout

- Section padding: 5rem vertical on desktop, 3rem on mobile.
- Max content width: 1200px, centered.
- Card border-radius: 12px.
- Consistent 1.5rem–2rem gaps between elements.
