Brand guidelines.
Everything to build a Taifoon-consistent announcement by hand — colors, type, layout rules, and the logo/font files themselves. Prefer not to do this manually? Generate one instead →
[ downloads ]
[ color palette ]
85–90% of every surface. Background, cards.
Subtle depth behind Black where needed.
Primary text, headlines, data values.
Accent — CTAs, labels, interactive states.
Secondary accent — status dots, live data.
Tertiary accent — infra, depth hints.
[ typography ]
The quick brown fox jumps over the lazy dog.
0x4f2a…9c1e · 41 chains · 97 proofs/sec
Headlines run light-weight (300) with tight tracking. Section labels and data values run monospace, uppercase, wide letter-spacing (0.20–0.25em).
[ layout ]
[ content rules ]
- No emojis — use inline geometric icons instead.
- No rounded corners, anywhere. border-radius: 0.
- Monospace for data — chain names, hashes, block numbers, prices, latencies.
- Blue for anything interactive — links, CTAs, active states, section labels.
- Teal for status — live indicators, health dots.
- Silver gradient for headlines, light font weight.
- Uppercase monospace for labels — small, wide letter-spacing.
[ writing an announcement by hand ]
1. Lead with a fact, not an adjective. "Live" beats "revolutionary." Every number you publish should be a URL someone else can hit and get the same answer.
2. Two voices, one post each.A short line in your own voice, and a short line in Taifoon's — both under 280 characters, both linking to the same place.
3. One graphic, 1200×630. Black background, your accent color as the only warm note, three facts along the bottom edge.
4. Say what's verifiable, not what's planned.If a number isn't live yet, don't publish it yet.
Prefer not to assemble this by hand? /claim/new runs this exact rubric for you — fill in a few facts, get the graphic, both posts, and the press body generated and published automatically.