# Banatie Brand Guidelines

## Brand Voice

Banatie speaks as a **developer tool built by developers**. We understand the workflow problems because we've lived them.

### Core Characteristics

1. **Technical but Accessible**
   - Use technical terms freely (API, CDN, endpoint)
   - But explain complex concepts when introducing them
   - Never condescending, never oversimplified

2. **Problem-Focused**
   - Lead with the problem, not the feature
   - "Tired of leaving your IDE to generate images?" > "Introducing our MCP integration!"
   - Show you understand the pain

3. **Honest and Direct**
   - Don't oversell
   - Acknowledge limitations openly
   - "We're not the cheapest, but we save you time"

4. **Developer-to-Developer**
   - Write like talking to a colleague
   - Use "you" and "we"
   - Share real experiences and learnings

## Brand Personality

- **Confident** but not arrogant
- **Helpful** but not pushy
- **Technical** but not intimidating
- **Modern** but not trendy for trend's sake

## Visual Brand

### Colors
- Primary: `#6366F1` (Indigo/Purple)
- Secondary: `#22D3EE` (Cyan)
- Background: `#0F172A` (Dark Slate)
- Text: `#F8FAFC` (Light) / `#1E293B` (Dark mode text)

### Image Style
- Modern, clean, geometric
- Abstract tech imagery
- Avoid: clipart, stock photos, busy compositions
- Avoid: text in images, hands, faces (AI artifacts)

### Logo Usage
- Use the Banatie wordmark
- Maintain clear space
- Don't distort or recolor

## Tone by Context

### Technical Documentation
- Precise and clear
- Code examples first
- Step-by-step instructions
- Minimal marketing language

### Blog Posts
- More conversational
- Personal experiences welcome
- Problem → Solution structure
- Clear takeaways

### Social Media
- Concise and punchy
- One key message per post
- Technical tips work well
- Avoid corporate speak

### Error Messages / UI
- Helpful, not cryptic
- Suggest solutions
- "Image generation failed. Try simplifying your prompt." > "Error 500"

## Words to Use

- "workflow" (not "process")
- "generate" (not "create" for AI images)
- "integrate" (not "connect")
- "developers" (not "users")
- "production-ready" (not "high-quality")

## Words to Avoid

- "Revolutionary" / "Game-changing"
- "Seamless" (overused)
- "Best-in-class"
- "Leverage" (corporate speak)
- "Utilize" (just say "use")
- "In today's digital landscape..."

## Content Structure

### Blog Posts
1. Hook with the problem (1-2 paragraphs)
2. Promise the solution (1 paragraph)
3. Deliver value (main content)
4. Practical example with code
5. Clear next step / CTA

### Tutorials
1. What you'll build/learn
2. Prerequisites
3. Step-by-step with code
4. Explanation of why, not just how
5. Complete working example
6. Next steps / related content

## Call-to-Action Guidelines

- Clear and specific
- "Try Banatie free" > "Get started"
- "See the API docs" > "Learn more"
- One primary CTA per piece