# voice.md

## Communication Style

### Overall Tone and Personality
Deno's brand voice is **confident, authoritative, and innovative**, directly addressing the needs of modern developers. It's **efficient, practical, and solution-oriented**, positioning Deno as a superior, streamlined alternative. While highly technical, it maintains an approachable professionalism, focusing on clarity and empowerment.

### Key Stylistic Elements and Patterns
*   **Direct & Concise:** We get straight to the point, especially in headlines and feature descriptions. No unnecessary fluff.
*   **Benefit-Oriented:** We emphasize how Deno solves problems and improves workflows, using phrases like "Better, faster JavaScript" and "Everything just works."
*   **Technical Precision:** We use accurate technical terminology (e.g., "runtime," "ESM," "microVMs," "Temporal API") without over-explaining concepts to our target developer audience.
*   **Comparative Language:** We are confident in highlighting Deno's advantages over alternatives (e.g., "Faster than Node; more stable than Bun.").
*   **Lists & Bullet Points:** We frequently use lists to present features, updates, and benefits for maximum readability and scannability.
*   **Code Examples:** We integrate relevant code snippets to demonstrate functionality and ease of use.

### Vocabulary Preferences and Word Choices
*   **Positive & Empowering:** "Better," "faster," "modern," "easy," "secure," "seamless," "built-in," "zero-setup."
*   **Technical & Specific:** "Runtime," "framework," "serverless," "TypeScript," "JavaScript," "ESM," "API," "KV," "microVMs," "agents," "modules," "compiler," "deploy," "sandbox," "subhosting," "security firewall," "durable objects," "View Transitions," "Temporal API."
*   **Action-Oriented Verbs:** "Run," "build," "extend," "introduce," "stabilize," "add," "capture," "persist," "configure," "install."

## Content Patterns

### Common Themes and Topics
Our content consistently revolves around:
*   **Product Updates & New Features:** Announcing new versions, capabilities, and improvements.
*   **Developer Experience:** Highlighting ease of use, built-in tools, and simplified workflows.
*   **Performance & Efficiency:** Showcasing speed and resource optimization.
*   **Compatibility:** Emphasizing Node.js and npm compatibility.
*   **Security:** Addressing secure execution environments and agent firewalls.
*   **How-To Guides:** Practical tutorials for building applications with Deno.

### Structural Approaches to Content
*   **Announcements/Updates:** Start with a bold title (e.g., "Deno 2.9"), followed by a concise summary and a bulleted list of key features/improvements.
*   **Marketing/Landing Pages:** Strong, benefit-driven headlines, followed by clear explanations, feature lists, and often comparative data or code examples.
*   **How-To Guides:** Structured as multi-part series, with clear objectives and step-by-step instructions.
*   **Product Listings:** Categorized lists with short, descriptive taglines for each product/service.

### Call-to-Action Styles and Patterns
Our CTAs are direct, clear, and action-oriented.
*   **Examples:** "Get started," "Learn more," "GitHub," "Docs," "Install Deno."
*   **Placement:** Often prominent on landing pages, embedded within blog posts, or as direct links to documentation or product pages.

## Audience Interaction

### How the Brand Addresses Its Audience
We directly address developers, assuming a foundational level of technical understanding. Our communication focuses on solving their problems and enhancing their productivity. We use "you" implicitly and explicitly when discussing benefits (e.g., "your JavaScript projects," "your Node project").

### Level of Formality and Relationship Style
The relationship is that of an **expert guide and trusted partner**. We maintain a professional yet approachable tone. We are serious about technical excellence and innovation, but avoid being overly stiff or academic. We aim to be helpful and informative, fostering a sense of shared progress.

### Engagement and Conversation Patterns
Our primary mode is informative and instructional. While not overtly conversational in marketing copy, the problem-solution framing ("without the Node problems," "Stop configuring; start building") demonstrates an understanding of the audience's needs. We direct users to community channels (Discord, GitHub) for direct interaction.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**Do's:**
*   Be **clear, concise, and confident**.
*   Focus on **benefits and solutions** for developers.
*   Use **precise technical language** appropriately.
*   Highlight **performance, security, and developer experience**.
*   Employ **lists and bullet points** for readability.
*   Integrate **code examples** where helpful.
*   Maintain a **forward-looking and innovative** stance.

**Don'ts:**
*   Avoid **vague or overly generalized statements**.
*   Steer clear of **excessive marketing jargon or fluff**.
*   Don't be **overly casual or informal**; maintain professionalism.
*   Avoid **unnecessary complexity** in explanations.
*   Do not shy away from **technical details** when relevant.

### Example Phrases and Expressions that are "On-Brand"
*   "Better, faster JavaScript."
*   "Everything just works."
*   "Stop configuring; start building."
*   "Run untrusted code in secure Linux VMs. Built for AI agents."
*   "Easy serverless hosting for your JavaScript projects."
*   "Modern runtime for JavaScript and TypeScript."
*   "Zero-setup TypeScript and npm."
*   "Seamless developer experience."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Product updates, feature announcements, "How To" guides, engineering deep-dives.
*   **Marketing Landing Pages:** Overview of products, core benefits, comparisons.
*   **Product Descriptions:** Concise explanations of individual offerings.
*   **Documentation:** Comprehensive technical guides and API references.
*   **Community Channels:** Discord, GitHub, X (Twitter), YouTube for interaction and support.