Translation Editorial

Translation and Editorial

Navigation: Skill index

Overview

Convert technical inputs into understandable application content:

• without jargon,
• with a clear practical effect,
• with 7-day action.

Skill is responsible for the signal -> message map -> card/post -> editorial QA phase.

Workflow

1) Pick Audience

Assign primary audience:

• entrepreneur
• operator
• specialist

If the audience is mixed, select one primary and specify secondary.

2) Build Message Map

For each signal / case, fix 5 reference points:

• What happened (fact)
• What does it change in work (mechanics of effect)
• For whom it is useful / risky
• What to do in 7 days
• What not to do

3) Produce Artifacts

Use the templates from card-templates.

Minimum:

• Short card (for digest)
• Blog block (expanded paragraph)

4) Editorial QA

Run the checklist out editorial-checklist.

If there is a complicated term, add a short explanation at the practice level.

Output

Return 2 blocks:

1. Digest Card
2. Blog Paragraph

For each block, indicate:

• primary audience
• actionable

Quality Gates

• The main idea is clear from the first 2 sentences.
• There is no objectless revolution/breakthrough evaluation without mechanics.
• There is a specific step for 7 days.
• There's a "what not to do" block.
• There is no internal contradiction with the original signal.

Anti-Patterns

• Do not retell changelog instead of applied meaning.
• Don't write "for everyone."
• Do not publish without a specific next step.
• Do not inflate the format: one card = one central thought.

References

• card-templates
• editorial-checklist