# Logto Brand Voice Guidelines

This document outlines Logto's communication style, tone, and patterns to ensure consistent and effective brand messaging across all platforms. Our voice is designed to resonate with developers, builders, and technical decision-makers, emphasizing simplicity, efficiency, and reliability in authentication solutions.

### Communication Style

**Overall Tone and Personality**
Logto's tone is **developer-first, practical, and efficient**. We are **confident and authoritative** in our expertise, yet remain **friendly and approachable** with a touch of modern casualness. Our personality is that of a knowledgeable partner who understands developer pain points and offers straightforward, powerful solutions. We are forward-thinking and committed to modern, frictionless experiences.

**Key Stylistic Elements and Patterns**
*   **Concise and Direct:** We use short sentences, punchy phrases, and bullet points to convey information quickly and clearly.
*   **Benefit-Oriented:** We lead with the "why" for our audience, framing features in terms of the problems they solve and the value they deliver.
*   **Problem/Solution Framing:** We acknowledge common developer struggles (e.g., "Tired of duct-taping auth?") and immediately position Logto as the effective solution.
*   **Active Voice & Strong Verbs:** Our language is dynamic and action-oriented, reflecting our product's efficiency.
*   **Parallelism for Impact:** We use repetitive structures to emphasize breadth and completeness (e.g., "From local to cloud. From web to mobile.").
*   **Strategic Use of Emojis:** A celebratory 🎉 or a cool 😎 can add a light, modern touch, especially in headings or feature highlights, without compromising professionalism.

**Vocabulary Preferences and Word Choices**
*   **Technical but Accessible:** We use industry-standard terms (OIDC, OAuth, SAML, RBAC, SSO, MFA, IdP, MAUs, PATs) accurately, but always strive to frame them in simple, benefit-driven language.
*   **Emphasis on Ease & Speed:** Words like "simple," "fast," "quick," "minutes," "frictionless," "out of the box," "obvious."
*   **Emphasis on Reliability & Control:** Words like "proven," "trusted," "secure," "control," "scalable," "compliant."
*   **Emphasis on Developer Focus:** Words like "developer-friendly," "built for devs," "builders," "integration," "open-source."
*   **Avoid unnecessary jargon** or overly academic language.

### Content Patterns

**Common Themes and Topics**
*   The inherent complexity and time-sink of building and maintaining authentication.
*   Logto as the streamlined, modern, and secure solution for auth infrastructure.
*   Specific features: Multi-tenancy, Enterprise SSO, RBAC, MFA, Passwordless, Social Sign-in, M2M, Impersonation, PATs.
*   Benefits for developers and businesses: Saving time, reducing security debt, enabling focus on core product, scalability, reliability, cost-effectiveness.
*   Broad compatibility: Works with any framework, any app, anywhere.
*   Enterprise readiness: Compliance, robust support, advanced features.

**Structural Approaches to Content**
*   **Clear Value Proposition:** Content often starts with a strong headline and a concise summary of Logto's core offering.
*   **Feature/Benefit Sections:** Information is broken down into digestible sections, often with bolded sub-headlines, followed by short descriptions and bullet points.
*   **Problem-Solution Narratives:** We frequently identify a common challenge and then present Logto's feature as the direct answer.
*   **Lists and Grids:** Used for frameworks, protocols, or key benefits to enhance scannability.
*   **Trust Signals:** Inclusion of testimonials, company logos, or statements about reliability.
*   **FAQ Sections:** Directly address common questions, demonstrating transparency and helpfulness.

**Call-to-Action Styles and Patterns**
CTAs are **clear, direct, and benefit-oriented**, designed for low friction.
*   "Get started free"
*   "Contact us"
*   "Learn more"
*   "Check out all frameworks"
They are strategically placed throughout the content, offering clear next steps.

### Audience Interaction

**How the Brand Addresses Its Audience**
We address our audience directly using "you" and "your," fostering a personal connection. We demonstrate empathy for developer pain points and position Logto as a supportive partner that empowers them to build more efficiently.

**Level of Formality and Relationship Style**
Our relationship style is **professional yet highly approachable**. We are experts in our field but communicate without condescension, aiming to be a helpful, collaborative ally to developers. We prioritize clarity and utility over corporate formality.

**Engagement and Conversation Patterns**
*   **Rhetorical Questions:** Used to engage the audience and highlight shared pain points ("Tired of duct-taping auth...?").
*   **Direct Value Statements:** Clearly articulate what Logto provides ("Logto got you covered.").
*   **Focus on User Experience:** Language that emphasizes ease and satisfaction ("Passwordless that feels obvious," "consent flow that doesn’t suck").
*   **Anticipatory:** We anticipate developer needs and provide immediate, relevant solutions.

### Guidelines & Examples

**Do's and Don'ts for Brand Communication**
*   **DO:** Be concise, direct, and action-oriented. Focus on tangible benefits for developers. Use technical terms accurately but explain them simply. Maintain a confident, helpful, and slightly informal tone. Use parallelism for impact.
*   **DON'T:** Be overly verbose, academic, or use corporate jargon that doesn't add value. Sound condescending or overly formal. Overcomplicate simple concepts. Avoid addressing developer pain points directly.

**Example Phrases and Expressions That Are "On-Brand"**
*   "Modern auth infrastructure for developers."
*   "Made simple, fast, and developer-friendly."
*   "For builders who hate rebuilding auth."
*   "Tired of duct-taping auth...? Logto got you covered."
*   "Zero friction."
*   "MFA in minutes."
*   "Enterprise SSO without the enterprise headache."
*   "Consent flow that doesn’t suck."
*   "Troubleshoot like a hero."
*   "No messy sign-ins, just clean access."
*   "Works out of the box."
*   "Grow and scale without security debt."
*   "Focus on shipping, not auth."

**Content Types and Formats the Brand Uses**
*   Website marketing copy (hero sections, feature descriptions, benefit statements)
*   Blog posts (introductions to features, solution-oriented content)
*   Product descriptions (detailed feature breakdowns, use cases, FAQs)
*   Short, punchy headlines and subheadings
*   Bullet points for easy scanning
*   Clear call-to-action buttons
*   Short, descriptive paragraphs
*   Visual aids (UI screenshots, diagrams)