# voice.md

## Communication Style

### Overall Tone and Personality
Lingo.dev's communication is **authoritative, precise, and highly technical**, yet always **solution-oriented and confident**. We speak as experts in localization engineering, providing clear, data-backed insights and demonstrating deep understanding of complex problems. The tone is professional but not overly formal, focusing on clarity, innovation, and measurable impact for developers and enterprises.

### Key Stylistic Elements and Patterns
*   **Direct and Concise:** We get straight to the point, often using short, impactful sentences and phrases.
*   **Problem/Solution Framing:** Content frequently identifies a technical challenge and immediately presents Lingo.dev as the elegant, engineering-driven solution.
*   **Data-Driven Claims:** We back up statements with quantifiable results and percentages (e.g., "reduces LLM terminology errors 17-45%").
*   **Technical Jargon (Used Appropriately):** We embrace industry-specific terms like "LLM," "API," "webhook," "retrieval augmented localization," and "stateful engines," assuming a technically proficient audience.
*   **Emphasis on Automation & Efficiency:** Highlighting how Lingo.dev streamlines complex workflows and delivers "localization infrastructure."
*   **Structured Information:** We frequently use numbered lists, bullet points, and clear headings to break down complex processes and features.

### Vocabulary Preferences and Word Choices
*   **Engineering & Technology:** `infrastructure`, `architecture`, `platform`, `engine`, `API`, `LLM`, `models`, `algorithms`, `webhook`, `embeddings`, `compiler`, `CLI`, `GitHub Action`, `stateful`.
*   **Precision & Quality:** `refinement`, `enrichment`, `scoring`, `qualified`, `verified`, `enforcement`, `accurate`, `consistent`, `holistic`, `robust`.
*   **Scale & Efficiency:** `at scale`, `linear`, `automated`, `encapsulated`, `orchestrated`, `seamless`, `multi-tenant`.
*   **Action-Oriented Verbs:** `build`, `create`, `reduce`, `ship`, `monetize`, `integrate`, `configure`, `track`, `route`, `encapsulate`.
*   **Benefit-Driven Adjectives:** `professional`, `fast-growing`, `isolated`, `natural`, `effortless`, `intelligent`.

## Content Patterns

### Common Themes and Topics
*   **Localization Engineering:** The core focus, often discussing the technical challenges and innovative solutions.
*   **AI/LLM in Translation:** How cutting-edge AI is integrated to improve quality and efficiency.
*   **API-First Approach:** Emphasizing the programmatic control and flexibility Lingo.dev offers.
*   **Quality & Accuracy:** Detailed explanations of how translation quality is measured, enforced, and verified.
*   **Developer Experience:** Highlighting ease of integration and developer-centric tools.
*   **Scalability & Enterprise Solutions:** Addressing the needs of large, global platforms and companies.

### Structural Approaches to Content
*   **Benefit-Oriented Headlines:** Content often starts with a clear benefit or problem statement.
*   **Sequential Explanations:** Complex processes are broken down into logical, numbered steps (e.g., "What Happens Inside A Localization Engine").
*   **Feature-Benefit Pairing:** Each feature is typically presented with its direct advantage for the user.
*   **Testimonial Integration:** Quotes from industry leaders and customers are strategically placed to build credibility.

### Call-to-Action Styles and Patterns
CTAs are **direct, clear, and action-oriented**, guiding the user to the next logical step.
*   `Read the API Docs`
*   `Talk to a Localization Expert`
*   `View open roles`
*   `Sign in / Sign up`
*   `Read article`

## Audience Interaction

### How the Brand Addresses its Audience
We address our audience as **fellow engineers, technical leaders, and product managers** who appreciate robust, scalable, and intelligent solutions. We speak directly to their technical needs and pain points, positioning Lingo.dev as a trusted partner and an essential piece of their infrastructure.

### Level of Formality and Relationship Style
The relationship is **professional and expert-to-expert**. While not overly stiff, we maintain a respectful distance, focusing on conveying information and demonstrating competence rather than engaging in casual banter. We aim to be seen as an indispensable tool, not a friendly chat partner.

### Engagement and Conversation Patterns
Engagement is primarily driven by **demonstrating superior technical solutions and quantifiable results**. We inform and empower, rather than initiating casual conversations. Testimonials serve as social proof, validating our claims through the voice of respected peers.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication
**DO:**
*   **Be precise and technical:** Use accurate terminology.
*   **Focus on measurable benefits:** Quantify impact whenever possible.
*   **Demonstrate expertise:** Speak with authority and deep understanding.
*   **Be direct and concise:** Avoid fluff and unnecessary words.
*   **Highlight innovation:** Emphasize how Lingo.dev pushes boundaries.
*   **Use problem/solution framing:** Clearly articulate challenges and our answers.

**DON'T:**
*   **Be vague or ambiguous:** Avoid generalizations.
*   **Use overly casual language or slang:** Maintain a professional tone.
*   **Make unsubstantiated claims:** Always back up statements with facts or logic.
*   **Overly anthropomorphize the product:** Lingo.dev is powerful infrastructure, not a playful assistant.
*   **Be overly conversational or chatty:** Focus on delivering value and information.

### Example Phrases and Expressions
*   "Professional localization - source refinement, glossary enrichment, quality scoring, and optional human review - encapsulated behind a single POST."
*   "Retrieval Augmented Localization Cuts LLM Terminology Errors 17-45%."
*   "Quality you can measure, not just hope for."
*   "Integrate in Minutes."
*   "Professional Localization, Delivered As Infrastructure."
*   "Prevents the garbage-in / garbage-out problem at the source."
*   "Their content, their voice - at any scale."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Research findings, product announcements, technical deep-dives.
*   **Marketing Landing Pages:** Feature overviews, benefit highlights, use cases.
*   **API Documentation & Guides:** Technical specifications, implementation instructions.
*   **Case Studies/Testimonials:** Real-world applications and success stories.
*   **Career Pages:** Attracting top engineering talent.