Voice & Tone Guidelines

How we speak to our community. This document defines the personality behind InkWell's content, ensuring every word feels authentic, insightful, and intentionally crafted.

v2.1 · Updated Dec 2024

Our Core Voice

InkWell's voice remains consistent across all channels. We are never salesy, never condescending, and always human.

🎯 Authentic

We speak honestly about complexity. We acknowledge nuance, admit when we're learning, and avoid corporate jargon or empty hype.

🧠 Insightful

Every piece of content aims to teach, reframe, or inspire action. We prioritize depth over virality and substance over trends.

💬 Conversational

We write like we're talking to a smart friend. Active voice, clear sentences, and approachable phrasing keep readers engaged.

🚀 Empowering

We equip readers with frameworks, not just facts. Our tone encourages experimentation, curiosity, and continuous growth.

💡 Key Principle

Voice is who we are. It stays consistent. Tone is how we adapt to context, audience, and format.

Contextual Tone Shifts

While our core voice never changes, we adjust tone to match the medium and reader intent.

Channel	Primary Tone	Pacing & Style	Example
Blog Articles	Thoughtful & Structured	Measured pacing, clear hierarchy, deep dives	"Let's unpack why this matters, and what it means for your workflow..."
Weekly Newsletter	Warm & Curated	Conversational opener, scannable highlights, personal sign-off	"Three things caught my eye this week. The second one might save you hours..."
Social & Threads	Punchy & Engaging	Short sentences, hooks, questions, minimal fluff	"Stop overcomplicating your onboarding. Here's the 3-step framework that actually works. 👇"
Docs & Support	Clear & Direct	Step-by-step, imperative verbs, zero ambiguity	"Navigate to Settings → Workspace. Toggle 'Enable Auto-Save'. Your progress is now preserved locally."

Writing & Formatting Rules

Consistency builds trust. Follow these structural and stylistic standards for all published content.

✅ Do

Use active voice: The editor approved the draft instead of The draft was approved

Keep paragraphs under 4 lines for digital readability

Write headings as mini-summaries, not clickbait

Use Oxford commas and American English spelling

Cite sources with clickable, descriptive anchor text

❌ Don't

Use corporate buzzwords: synergy, leverage, paradigm shift

Rely on exclamation marks or all-caps for emphasis

Write longer than 15 words without a natural pause

Use "you guys" or assume gender/role

Nest more than 2 levels of bullet points

📐 Structural Standards

Every blog post must include: a 1-sentence hook, H2/H3 hierarchy, 1 key takeaway box, and a clear next-step CTA. Meta descriptions stay under 155 characters.

Examples in Action

See how our voice translates from draft to published content.

❌ Before (Off-Voice)

We are excited to announce the revolutionary deployment of our cutting-edge platform that will synergize your workflow and leverage maximum efficiency for optimal outcomes. Utilize the tool today to unlock unprecedented productivity.

✅ After (On-Voice)

We built this platform to remove friction from your daily workflow. Instead of chasing efficiency, you'll finally have space to focus on the work that matters. Try the beta and tell us what breaks first.

❌ Before (Unclear)

Users should probably make sure they're using the latest version because older versions might have some issues with the new API endpoints and that could cause errors.

✅ After (Direct)

Update to v3.2+ before calling the new endpoints. Older versions will return 401 errors. Run npm install @inkwell/core@latest to upgrade.

⚠️ Review Checklist

Before publishing, ask: "Would a smart peer nod at this?" If it sounds like a press release, rewrite it. If it reads like a conversation, publish it.