# Heroku Brand Voice Guidelines

This document outlines the Heroku brand's communication style, tone, and patterns to ensure consistent and effective messaging across all content.

### Communication Style

-   **Overall Tone and Personality:** Heroku's voice is **professional, empowering, and knowledgeable**, with an underlying current of helpfulness and enthusiasm for developer innovation. We are a trusted guide, not just a vendor. We aim to be clear, concise, and direct, avoiding excessive formality while maintaining authority in our domain.
-   **Key Stylistic Elements and Patterns:**
    -   **Benefit-Oriented:** We consistently frame our offerings in terms of how they benefit the user, focusing on efficiency, productivity, and enabling creation.
    -   **Direct Address:** We speak directly to our audience using "you" and "your" to foster a personal connection and highlight relevance.
    -   **Action-Oriented Language:** We use strong, active verbs to convey capability and drive.
    -   **Clarity and Conciseness:** Sentences are typically straightforward and to the point, designed for easy comprehension by a technical audience.
    -   **Strategic Use of Technical Jargon:** We embrace appropriate technical terms (PaaS, CLI, polyglot, container system) as our audience is technical, but always ensure they are used in context and contribute to clarity.
-   **Vocabulary Preferences and Word Choices:**
    -   **Preferred:** `effortless`, `simplify`, `accelerate`, `optimize`, `powerful`, `robust`, `innovative`, `enhance`, `scalable`, `reliable`, `modern`, `intelligent`, `managed`, `ecosystem`, `workflow`.
    -   **Avoid:** Overly academic, overly casual slang, vague adjectives, buzzwords without clear meaning.

### Content Patterns

-   **Common Themes and Topics:** Our content consistently revolves around developer experience, app deployment and scaling, managed data and AI services, the Heroku ecosystem (add-ons, buildpacks), productivity, innovation, and customer success stories across various industries and languages.
-   **Structural Approaches to Content:**
    -   **Problem/Solution:** Often introduces a developer challenge and positions Heroku as the elegant solution.
    -   **Benefit-First:** Leads with the value proposition before detailing features.
    -   **Scannable Formats:** Utilizes clear headings, subheadings, bulleted lists, and short paragraphs to make complex information digestible.
    -   **Educational/Informative:** Blog posts often provide practical tips, guides, or insights (e.g., CLI commands).
-   **Call-to-Action Styles and Patterns:**
    -   **Direct and Imperative:** Clear instructions on the next step.
    -   **Benefit-Driven:** CTAs often highlight what the user will gain by taking action.
    -   **Prominent Placement:** CTAs are typically bolded, buttonized, or strategically placed for high visibility.
    -   **Examples:** "Sign Up Now!", "Build Your Next Big Thing on Heroku.", "Discover Heroku’s PaaS...", "Dive into our comprehensive documentation."

### Audience Interaction

-   **How the Brand Addresses its Audience:** We address our audience as capable, intelligent developers and business leaders who are focused on building and innovating. We position ourselves as a partner that empowers them to achieve their goals by handling the underlying infrastructure.
-   **Level of Formality and Relationship Style:** The relationship is professional and respectful, yet approachable and supportive. It's akin to a peer-to-peer relationship where Heroku shares expertise and tools to help the developer succeed. We avoid overly stiff corporate language or overly casual, unprofessional slang.
-   **Engagement and Conversation Patterns:** Engagement is primarily through providing valuable information, practical solutions, and tools that directly address developer needs. While not conversational in a social media sense, the content is designed to anticipate questions and provide clear answers, fostering a sense of helpful dialogue.

### Guidelines & Examples

**Do's:**
-   **Focus on the "why":** Always explain the benefit before or alongside the feature.
-   **Be empowering:** Use language that suggests ease, capability, and potential.
-   **Maintain clarity:** Use straightforward sentences and avoid ambiguity.
-   **Use active voice:** Keep sentences dynamic and direct.
-   **Embrace technical accuracy:** Use industry-standard terms correctly and confidently.
-   **Structure for readability:** Utilize lists, bolding, and clear headings.

**Don'ts:**
-   **Don't be overly casual or unprofessional:** Avoid slang, emojis, or overly informal language.
-   **Don't be vague:** Provide concrete examples or clear descriptions.
-   **Don't use jargon for jargon's sake:** Ensure technical terms serve a purpose and are understood by the target audience.
-   **Don't sound condescending or overly academic:** Maintain a helpful, peer-like tone.
-   **Don't over-promise or exaggerate:** Be authentic and realistic about capabilities.

**Example Phrases and Expressions:**
-   "Build Your Next Big Thing on Heroku."
-   "Focus on building apps, not infrastructure."
-   "Designed for effortless app deployment and scaling."
-   "Simplify your data management with Heroku’s fully managed cloud databases."
-   "Accelerate your app development with our ecosystem of add-ons, integrations, and buildpacks."
-   "Optimize your workflow and instantly upgrade your daily productivity."
-   "Benefit from a meticulously designed developer experience."

**Content Types and Formats the Brand Uses:**
-   Blog Posts (technical guides, product updates, thought leadership)
-   Marketing Copy (website pages, landing pages, ad copy)
-   Product Descriptions (feature overviews, capability highlights)
-   Documentation (Dev Center guides, API references)
-   Customer Stories / Case Studies