What problem does it solve?
Writing style drift across Liftosaur's public content erodes clarity and trust. This guide provides a practical, human-friendly framework to keep program descriptions, technique pages, FAQs, blog posts, and release notes consistent in tone, terminology, and formatting.
Core Features & Use Cases
- Voice & Tone: Write like a knowledgeable training partner, using first-person perspective for the developer voice and addressing the reader directly.
- Plain Language & Clarity: Favor simple, concrete words and avoid unnecessary jargon.
- Core Principles: Be direct and specific; use concrete numbers; avoid padding and filler.
- Sentence Rhythm & Readability: Vary sentence length and use natural fragments where appropriate to aid skimming.
- Conversational Patterns: Use dashes for asides, discovery language, and direct reassurance to keep tone approachable.
- Problem-Solution Framing: Lead with the user's problem, then describe the solution.
- Specificity & Examples: Provide concrete, real-world examples rather than vague claims.
- Explanations & FAQ Style: Keep explanations concise and rephrase main points for quick scanning.
- Whatsnew & Changelog Style: Lead with changes and explain user impact in bullet points where relevant.
Quick Start
Review a draft and rewrite it using this guide before publishing.
