Introduction #️⃣

A style guide keeps everyone on the same page. It helps contributors across different languages produce consistent results, makes reviews quicker with fewer rewrites, and even improves AI translation quality by giving it the context it needs to get things right.

---

How to create a style guide #️⃣

1. Open your project in the app.
2. Go to Style guide from the main menu under Context
3. Click Create styleguide and complete the short onboarding.

Configuring the style guide #️⃣

The form is organized into blocks. As you fill them in, your preferences guide AI-assisted translations and help human translators understand your expectations.

Project & Industry #️⃣

Set project context and share sources of truth. This information helps translators, writers, and AI tools understand the purpose, scope, and positioning of the content they’re working on.

Field	Options / Description
Project Type	Mobile, Web, SaaS, Blog, SEO, Company, E-commerce, Game, Marketing, Documentation, User interface, Help center, Social media, Email campaigns, Not specified
Project URLs	Add key links (e.g., Website, Docs, Blog) so translators can reference the right content
Project Description	Briefly explain your product, audience, and key concepts
Industry	Business, Legal, Medical, Healthcare, Education, Finance, Banking, Manufacturing, E-commerce, Gaming, Technology, E-learning, Travel & tourism, Software development, Marketing & advertising, Fashion, Entertainment, Automotive, Real estate, Food & beverage, Telecommunications, Logistics, Agriculture, Not specified
Domain	Academic, Business, General, Legal, Creative, Technical, Scientific
Brand Voice	Corporate, Startup, Playful, Serious, Innovative, Traditional, Luxury, Accessible, Not specified

Language Preferences #️⃣

Tune global style expectations across languages. These settings ensure that all content is consistent, on-brand, and communicates in the right way across different languages and platforms.

Field	Options
Formality	Very formal, Formal, Neutral, Casual, Very casual
Tone	Professional, Authoritative, Emphatic, Direct, Calm, Neutral, Helpful, Friendly, Competitive, Instructional, Emotional, Conversational, Humorous, Inspiring, Urgent, Reassuring
Sentiment	Positive, Negative, Neutral, Context dependent
Preferred Gender	Neutral, Male, Female, Context dependent

Audience Details

Describe who you’re talking to.

• Audience Expertise: Beginner, General, Knowledgeable, Expert
• Audience Education: High school, Undergraduate, Graduate, Professional, Not specified

Advanced Configuration #️⃣

Control how literal or adaptive the output should be and share extra rules.

• Transcreation
  • Disable: Keep close to source
  • If necessary: Allow adaptation when needed for naturalness
  • Enabled: Permit broader cultural adaptation
• URL Handling
  • Keep: Preserve URLs
  • Localize: Adapt links where appropriate
• Accuracy
  • Accurate: Prioritize faithful meaning
  • Balanced: Mix accuracy and fluency
  • Fluent: Optimize for natural, flowing language
• General Instructions
  • This is your custom prompt. Include free-form do’s/don’ts, preferred terminology, examples, and style notes

Best practices #️⃣

You don’t need to fill in everything. Too much context can dilute AI prompts and overwhelm translators. Focus on the few settings that matter for your project, then iterate.

• Start small: Pick 3–5 essentials (e.g., Project Type, Project Description, Formality, Tone, a short General Instructions block)
• Be specific, not exhaustive: Add a handful of do’s/don’ts and 2–3 key terms with examples instead of long essays
• Link to sources: Provide Website/Docs/Help Center URLs instead of duplicating content in the form
• Calibrate strictness: Begin with Accuracy = Accurate and Transcreation = Disable/If necessary; relax later if needed
• Use overrides sparingly: Only add per-language differences where culture or grammar demands it (e.g., higher formality in Japanese)
• Review outcomes: Translate a sample set, inspect results, then adjust tone/formality or instructions based on what you see

---

Language overrides #️⃣

Per-language overrides let you tailor rules for specific locales. Multiple languages can share the same override value via grouped rows.

Replacing base values with overrides #️⃣

For all fields except General Instructions, a language override replaces the base value. Only the override is applied for that language.

• Example: Global Formality = Neutral. Override Formality = Very formal for Japanese. Japanese uses Very formal; other languages use Neutral.
• The UI groups languages that share the same override so you can manage them together.

Language specific instructions #️⃣

Language-specific instructions are appended to the global General Instructions. Both are applied for that language.

• Example: Global instructions define brand terms and voice. German instructions add capitalization rules; Japanese instructions add polite form notes. Each language receives the global part plus its own extra notes.

---

Style guide preview #️⃣

The style guide preview is a compact, read‑only brief generated from your project’s style guide. Think of it as the translator’s cheat sheet: it surfaces only the rules and context that matter, right where translation decisions happen. This helps translators stay aligned on tone, formality, and intent without jumping between screens or guessing.

You can open the preview from two places: directly in the translations table and inside the translate/review interface. Wherever you’re working, the preview sits beside your content so you can double‑check expectations as you translate or review.

The preview is always language‑aware. It shows only the values that apply to the language you’re currently viewing. For example, if your base Formality is Neutral but you set a Very formal override for Japanese, users browsing Japanese will see Very formal in the preview. Users working in other languages will see the base Neutral value. This applies to all overrideable options, so the brief always reflects the exact rules for each locale.

Any time the style guide is updated, the preview highlights the change with a red Updated badge. It’s an at‑a‑glance nudge for translators and reviewers that guidance has changed, so they can adjust their work accordingly.