返回提示词目录第 1514 页

制定多语言内容运营方案

结合受众证据与团队产能,为各语言规划渠道、内容处理方式、审核流程、发布频率和效果评估。

完整提示词

<context>
You help a creator, brand, nonprofit or public body plan content for audiences who speak different languages. Teams usually get this wrong in one of three ways: translating everything word for word into every language and burning out; publishing a token translation that is never updated; or mixing languages in one feed so no one is served well. Experienced multilingual teams decide per language from audience evidence and capacity, then choose a treatment per content type: translate (factual, stable material such as service information or help pages), transcreate (campaigns, hooks, humour, idioms, cultural references), create natively (community, news and trend content where a native speaker leads), or summarise and link. Channel structure matters: separate accounts or editions per language versus one account with captions or alternate posts. Machine translation can draft, but a fluent human reviewer is needed for anything public, sensitive or legal, and for some audiences a plain-language summary in their language serves better than a full translation. Script direction, fonts, captions and alt text also need checking per language.

Organisation and audience: {{audience}}
Current content and channels: {{current_content}}
Languages being considered and who on the team speaks them: {{languages}}
{{#capacity}}Capacity and budget: {{capacity}}{{/capacity}}
</context>

<task>
1. For each language, weigh audience evidence (what the data or community contact shows), the goal it serves and the capacity to sustain it; recommend start now, start later or not yet, with reasons. If audience evidence is missing, say what to collect.
2. Choose a channel structure per language (separate account or edition, same account with alternates, captions or subtitles only, website language versions) and explain the trade-offs.
3. Build a treatment matrix by content type: translate, transcreate, create natively, summarise and link, or English or source language only.
4. Set the workflow: who drafts, whether machine translation is used for drafts, who reviews for fluency, accuracy and cultural fit, and sign-off for sensitive, legal, health or safety content.
5. Set a cadence per language that the reviewers can sustain, and what happens when a reviewer is unavailable.
6. List the production checks: glossary and voice notes per language, captions and alt text, right-to-left layout or special scripts, dates, numbers and units, names and forms of address.
7. Define how to measure each language separately and when to review the decision.
</task>

<constraints>
- Do not invent audience figures, language statistics or translation costs; use what is given and mark gaps as [X].
- Never recommend publishing machine translation without fluent human review for public-facing content.
- Do not treat a language as one culture; note regional variants that matter for the audience given.
- Keep the plan within the stated capacity; it is better to serve two languages well than five badly.
</constraints>

<output_format>
## Language decisions
Table: Language | Audience evidence | Goal served | Capacity | Decision.
## Channel structure
## Treatment by content type
Table: Content type | Treatment | Why.
## Workflow and review
## Cadence
## Production checks
A checklist.
## Measuring and review
</output_format>

可替换内容

  • {{audience}}
  • {{current_content}}
  • {{languages}}
  • {{#capacity}}
  • {{capacity}}
  • {{/capacity}}
  • [X]

分类与标签

内容创作、多语言运营、内容策略、渠道规划

前往 AI 图片创作