# voice.md

## Communication Style

### Overall Tone and Personality
Marble's brand voice is **informative, practical, and confidently helpful**. We are a **developer-friendly** and **solution-oriented** brand, prioritizing clarity and efficiency. Our tone is professional yet approachable, never overly formal or stiff. We aim to be transparent and trustworthy, emphasizing simplicity and ease of use in all our communications.

### Key Stylistic Elements and Patterns
*   **Direct and Concise:** We use straightforward language, avoiding unnecessary jargon or fluff. Sentences are typically clear and to the point.
*   **Benefit-Driven:** We highlight the value and practical outcomes for our users, often starting with a key benefit.
*   **Action-Oriented:** We employ strong verbs that encourage action and describe functionality clearly (e.g., "manage," "build," "trigger," "publish").
*   **Structured for Readability:** We make extensive use of headings, subheadings, bullet points, and lists to break down information and enhance scannability.
*   **Technical but Accessible:** While we address technical topics, we strive to explain them in an understandable way, providing context or practical examples.
*   **Emphasis on "Simplicity":** The word "simple" and its synonyms are frequently used to reinforce our core value.

### Vocabulary Preferences and Word Choices
*   **Simplicity:** simple, clean, easy, straightforward, intuitive.
*   **Efficiency & Performance:** fast, instant, real-time, seamless, reliable, quick.
*   **Empowerment:** manage, build, create, publish, unlock, automate, integrate.
*   **Developer-Centric:** headless CMS, API, webhooks, framework, stack, SDK, revalidate, deploy.
*   **Clarity & Guidance:** comprehensive, detailed, guide, learn, understand.

## Content Patterns

### Common Themes and Topics
Our content consistently revolves around:
*   **Integration:** How Marble works with popular frameworks (Next.js, Astro, Framer) and other tools.
*   **Core Functionality:** Explaining and demonstrating content management, media handling, and API usage.
*   **Developer Workflows:** Guides on webhooks, content revalidation, syntax highlighting, and other developer-centric features.
*   **Performance & Efficiency:** Highlighting speed, fast delivery, and streamlined processes.
*   **Product Updates:** Announcing new features and company milestones.
*   **Practical "How-to" Guides:** A dominant format for our blog, offering step-by-step solutions.

### Structural Approaches to Content
*   **Problem/Solution:** Especially in blog posts, we identify a common challenge and provide Marble as the solution.
*   **Feature-Benefit:** Clearly listing features and immediately following with their practical advantages.
*   **Step-by-Step Guidance:** For technical guides, content is broken into logical, easy-to-follow steps.
*   **Q&A Format:** Used for FAQs to directly address common user inquiries.
*   **Visual Elements:** Implied by discussions of styling and media management, suggesting content is designed to be visually appealing.

### Call-to-Action Styles and Patterns
Our CTAs are always clear, direct, and action-oriented. They often appear at the end of sections or after a key benefit.
*   "Read article"
*   "Publish your first post"
*   "Watch Demo"
*   "Start for free"
*   "Upgrade to Hobby"
*   "Get Started"
*   "Sign up"

## Audience Interaction

### How the Brand Addresses Its Audience
We directly address our audience using "you" and "your," fostering a personal and helpful connection. We anticipate their needs as developers, writers, and teams, positioning Marble as the solution to their content management challenges. We speak to their desire for simplicity, efficiency, and powerful tools.

### Level of Formality and Relationship Style
Our relationship with the audience is that of an **expert guide and trusted partner**. We maintain a professional yet approachable demeanor. We are never condescending but always authoritative in our knowledge. We aim to build trust through transparency (e.g., "generous limits," "fair usage policies") and by consistently delivering valuable, actionable information.

### Engagement and Conversation Patterns
Our primary mode of engagement is through providing highly valuable, instructional content that solves real problems. We encourage users to explore our product through clear CTAs and provide avenues for direct interaction via social media (Twitter, Discord) and documentation, though our content itself is largely informative rather than conversational.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication
**Do:**
*   Be clear, concise, and direct.
*   Focus on the practical benefits and how Marble solves user problems.
*   Use action-oriented language and strong verbs.
*   Emphasize simplicity, speed, and developer-friendliness.
*   Break down complex information into digestible, scannable parts.
*   Maintain a helpful, expert, and transparent tone.
*   Address the reader directly using "you" and "your."

**Don't:**
*   Use overly technical jargon without clear explanation.
*   Be vague, ambiguous, or use excessive marketing hype.
*   Sound overly formal, academic, or stiff.
*   Neglect to provide clear and compelling calls to action.
*   Be condescending or assume too much prior technical knowledge without offering guidance.

### Example Phrases and Expressions That Are "On-Brand"
*   "Super simple headless CMS."
*   "Learn how to build a fast Astro blog with Marble."
*   "Everything you need to publish."
*   "Works seamlessly with Next.js, Astro, Nuxt, and more."
*   "Trigger external workflows instantly when your content changes."
*   "A comprehensive guide on adding beautiful, server-rendered syntax highlighting."
*   "Unlock real-time integrations with a reliable, developer-friendly system."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Primarily "how-to" guides, technical deep-dives, product announcements, and company news.
*   **Marketing Pages:** Feature overviews, testimonials, pricing breakdowns, and frequently asked questions (FAQs).
*   **Documentation:** In-depth technical guides and API references (implied).
*   **Social Media Snippets:** Concise updates, announcements, and links to longer content.