# ArcLight Brand Voice Guidelines

This document outlines the core communication style, tone, and patterns for ArcLight, ensuring consistency across all brand touchpoints.

### Communication Style

**Overall Tone and Personality**
ArcLight's voice is **confident, innovative, and empowering**. We speak with the authority of a technical expert, yet remain approachable and focused on the user's creative potential. The tone is direct, precise, and highly functional, conveying a sense of sophisticated simplicity. We aim to inspire users by demystifying complex live production, making them feel like skilled professionals.

**Key Stylistic Elements and Patterns**
*   **Direct and Concise:** We use short, impactful sentences and phrases to deliver information efficiently. Avoid fluff or overly elaborate language.
*   **Benefit-Focused:** Every feature is presented with a clear explanation of its value to the user. The "what" is always followed by the "why it matters to you."
*   **Strategic Emphasis:** Heavy use of **bolding** for key features, benefits, and unique selling propositions. *Italics* are used for core concepts or to add a subtle layer of emphasis.
*   **Analogy and Comparison:** We relate ArcLight to familiar tools (e.g., Keynote, PowerPoint, slide decks) to quickly convey its essence while highlighting its innovative live capabilities.
*   **Quantifiable Claims:** We use numbers and percentages to demonstrate performance, efficiency, and scale, reinforcing our technical prowess.
*   **Action-Oriented Language:** Strong verbs drive the narrative, emphasizing capability and ease of use.

**Vocabulary Preferences and Word Choices**
*   **Technical Precision:** We embrace terms like "Metal," "Swift," "CPU," "GPU," "LUTs," "scopes," "alpha," and "Magic Move," but always in context of user benefit or clear explanation.
*   **User-Centric:** Frequent use of "you" and "your" to directly address the audience and personalize the experience.
*   **Industry-Specific:** Words related to live production, presentation, and design are common (e.g., "slide deck," "live video," "camera," "editor," "transition," "effect," "program," "script," "colorist").
*   **Simple & Direct:** We prefer clear, unambiguous language over jargon where possible, or we explain technical terms concisely.

### Content Patterns

**Common Themes and Topics**
*   Transforming static presentations into dynamic live video.
*   Seamless integration with existing presentation workflows and familiar controls.
*   Unparalleled Mac-native performance and efficiency.
*   The power of AI as a creative co-host and automation tool.
*   Versatility across diverse use cases (events, education, sales, content creation).
*   Making professional-grade features (color grading, transitions, effects) accessible.

**Structural Approaches to Content**
*   **Headline-First:** Content typically begins with a bold, concise headline that immediately communicates the main idea.
*   **Problem/Solution (Implied):** Often, content will subtly highlight the limitations of traditional tools before presenting ArcLight as the modern, intuitive solution.
*   **Feature-Benefit Lists:** Extensive use of bullet points, often with a **bolded feature name** followed by a descriptive benefit or explanation.
*   **Step-by-Step Examples:** Illustrated sequences, such as the "Claude Code" examples, demonstrate functionality and ease of interaction.
*   **Comparative Statements:** Positioning ArcLight distinctly against traditional broadcast or presentation software.

**Call-to-Action Styles and Patterns**
*   **Clear and Direct:** CTAs are straightforward, telling the user exactly what to do.
*   **Benefit-Oriented:** CTAs often include a value proposition, such as pricing or trial information.
*   **Examples:**
    *   `[See it run](#magic-move)`
    *   `Free for 30 days, then $49/year — launch price, locked in.`

### Audience Interaction

**How the Brand Addresses Its Audience**
We address our audience directly using "you" and "your," fostering a personal connection. We speak as an enabler, providing powerful tools that simplify complex tasks.

**Level of Formality and Relationship Style**
The relationship is professional yet approachable. We assume our audience is technically astute or aspiring to be, and we communicate with confidence and clarity, positioning ArcLight as an intelligent partner or "co-host." We aim to build trust through transparent and precise communication.

**Engagement and Conversation Patterns**
Engagement is driven by showcasing possibilities and demonstrating ease of use. We invite users to imagine what they can create, often through evocative language and visual metaphors ("cameras that glide"). The communication is primarily one-way (informative) but designed to elicit a sense of "I can do that!" from the reader.

### Guidelines & Examples

**Do's for Brand Communication**
*   Be direct, clear, and concise.
*   Always highlight user benefits alongside features.
*   Use bolding and italics strategically for maximum impact.
*   Employ analogies to familiar tools to aid understanding.
*   Emphasize ArcLight's Mac-native performance and efficiency.
*   Use action verbs to convey dynamism and capability.
*   Speak directly to the user ("you," "your").

**Don'ts for Brand Communication**
*   Be overly casual, informal, or use slang.
*   Use vague or ambiguous language; be specific.
*   Over-explain basic concepts; assume a reasonable level of tech literacy.
*   Sound generic or mimic the voice of other software brands.
*   Use passive voice when active voice is possible.

**Example Phrases and Expressions That Are "On-Brand"**
*   `Live video, built like a slide deck.`
*   `Cameras that glide.`
*   `Your AI is the co-host.`
*   `Sixteen effects at once. Not a beat missed.`
*   `Look like you hired a colorist.`
*   `Built for the Mac.`
*   `With the controls you already know from Keynote and PowerPoint.`
*   `Every scene is a slide.`

**Content Types and Formats the Brand Uses**
ArcLight's voice is consistently applied across:
*   Blog posts and articles
*   Marketing website copy
*   Product feature descriptions
*   Technical explanations and documentation
*   User interface text (where applicable)
*   Social media updates (adapted for brevity)