Product releases bring marketing, support and technical content together. Keep regional wording and release versions aligned with the work your team needs to publish.
Discuss your projectA clear brief makes it easier to discuss scope before production begins. You do not need every file on day one, but the audience, purpose and working source should be clear.
Read guideSelecting a language region helps shape terminology, spelling, tone and formatting. A regional label is useful only when the content and review process support it.
Read guideA translated file is only as current as its source. Simple version discipline helps teams avoid reviewing or publishing the wrong document.
Read guideService scope, availability, responsibilities, fees and delivery arrangements are confirmed for each project before work begins.
