# voice.md

## Communication Style

-   **Overall tone and personality:** Confident, authoritative, expert, and highly technical, yet practical and problem-solving. We aim to be a trusted resource for developers and engineers, providing clear, direct, and actionable insights. We are serious about performance and reliability, but approachable in our explanations.
-   **Key stylistic elements and patterns:**
    -   **Direct and Concise:** Get straight to the point, especially in headlines and introductions.
    -   **Problem/Solution Framing:** Often introduce a common technical challenge before presenting our solution or insight.
    -   **Benefit-Oriented (Marketing):** Clearly articulate the advantages and outcomes for the user (e.g., "unlimited IOPS," "protect your database").
    -   **Technical Precision:** Embrace and correctly use industry-specific jargon. Avoid oversimplification that sacrifices accuracy.
    -   **Strong Adjectives & Superlatives (Marketing):** Use words like "fastest," "most scalable," "blazing fast" to emphasize our capabilities.
    -   **Proprietary Naming:** Use trademarks like "Database Traffic Control™" consistently.
    -   **Intriguing Hooks:** Sometimes use slightly provocative or counter-intuitive titles (e.g., "High memory usage in Postgres is good, actually") to grab attention.
-   **Vocabulary preferences and word choices:**
    -   **Technical:** Postgres, Vitess, query, traffic, database, scaling, sharding, IOPS, NVMe, degradation, latency, connections, workloads, tuples, vacuum, CLI, API.
    -   **Performance & Scalability:** fastest, scalable, blazing fast, unlimited, high-churn, real-time, protect, optimize, enhance, healthy, efficient, robust, resilient.
    -   **Problem/Solution:** degrade, overwhelm, outage, protect, control, manage, keep on track, patterns, insights, prevent, mitigate.
    -   **Action-oriented:** Introducing, learn, enforce, provision, manage, compare, require, cover, deliver, unlock, powers.

## Content Patterns

-   **Common themes and topics:**
    -   **Database Performance & Scalability:** Deep dives into achieving and maintaining high performance and horizontal scaling with Postgres and Vitess.
    -   **Reliability & Resilience:** Strategies for preventing outages, graceful degradation, and protecting databases from issues like runaway queries.
    -   **Database Management & Optimization:** Best practices, tools, and features for managing and optimizing database health (e.g., Query Insights, Traffic Control, connection management).
    -   **Product & Feature Announcements:** Introductions and explanations of new PlanetScale capabilities.
    -   **Engineering Deep Dives:** "Behind the scenes" looks at how our technology works.
    -   **Tutorials & How-to Guides:** Practical instructions for using PlanetScale and related technologies.
    -   **Partnerships & Integrations:** Showcasing collaborations with other developer tools and platforms.
-   **Structural approaches to content:**
    -   **Blog Posts:** Begin with a compelling title, often followed by a concise summary. Content typically presents a problem, explains the underlying mechanics, and offers solutions or insights. Categorized for easy navigation.
    -   **Marketing Pages:** Start with a bold, benefit-driven headline, followed by clear value propositions. Incorporate social proof (testimonials, case studies) and technical explanations (e.g., architecture diagrams for Vitess).
    -   **Introductions:** New features or products are typically introduced with "Introducing [Feature Name]: [Benefit/Description]."
-   **Call-to-action styles and patterns:**
    -   **Clear and Imperative:** CTAs are direct and action-oriented.
    -   **Examples:** "Learn more," "Log in," "Get started," "Get in touch," "Read case study," "Read blog post," "Sign up."
    -   **Strategic Placement:** CTAs are prominently featured in navigation, hero sections, and at the end of content sections.

## Audience Interaction

-   **How the brand addresses its audience:** We address our audience as fellow technical professionals – developers, engineers, database administrators, and CTOs. We speak directly to "you" as someone who understands and values deep technical explanations and solutions to complex database challenges.
-   **Level of formality and relationship style:** Professional and expert. We aim to be a trusted advisor and solution provider, fostering a relationship built on technical competence and reliability. While not overly formal, we maintain a tone of authority and respect for our audience's intelligence.
-   **Engagement and conversation patterns:** Our primary mode of engagement is through informative and educational content. We provide answers, solutions, and insights. We encourage further exploration through links to documentation, other blog posts, and direct contact. Social media engagement (e.g., author X handles) suggests a willingness for direct conversation on relevant platforms.

## Guidelines & Examples

-   **Do's for brand communication:**
    -   **Be technically accurate and precise.** Our audience values expertise.
    -   **Focus on the "why" and "how":** Explain the problem, the solution, and how it works.
    -   **Emphasize performance, scalability, and reliability.** These are our core strengths.
    -   **Use strong, confident language.** We are leaders in our field.
    -   **Leverage real-world scenarios and examples** where possible.
    -   **Maintain a consistent tone** across all content types.
-   **Don'ts for brand communication:**
    -   **Avoid jargon for jargon's sake.** Use technical terms correctly and where they add clarity.
    -   **Don't be vague or make unsubstantiated claims.** Back up claims with evidence or explanation.
    -   **Don't use overly casual or informal language** that detracts from our expert image.
    -   **Don't shy away from complex topics.** Our audience expects depth.
-   **Example phrases and expressions that are "on-brand":**
    -   "Introducing Database Traffic Control™: resource budgets for your Postgres query traffic."
    -   "The world’s fastest and most scalable cloud databases."
    -   "Our blazing fast NVMe drives unlock unlimited IOPS."
    -   "Dead tuples from high-churn job queues can silently degrade your Postgres database when vacuum falls behind."
    -   "Not all traffic is created equal. When a database is overwhelmed, you want the important queries to keep executing."
    -   "PlanetScale for Postgres is now generally available."
    -   "Learn how Traffic Control enforces real-time limits on Postgres queries."
-   **Content types and formats the brand uses:**
    -   Blog posts (Engineering deep dives, Product announcements, Tutorials, Company news, Vitess-specific content)
    -   Marketing landing pages
    -   Case studies
    -   Documentation
    -   Pricing pages
    -   Testimonials/Quotes
    -   Social media snippets (often linking to longer content)