Skip to content

Configure Published Documentation Languages

page
3 min readUpdated

Configure the languages available to your documentation audiences before you share or publish documentation. This helps readers access published content in the language that best fits their needs.

Overview

Atloria supports 24+ languages for documentation. Language configuration determines which language options are available when documentation is presented to your audiences and when they open your published documentation.

You typically configure languages during the publishing setup process, after your documentation has been generated or imported and before you direct readers to the published site. This keeps your published documentation aligned with the regions, teams, and customers you support.

Language availability is part of the broader publishing experience. After configuration, you can use View Published Docs or 🌐 View Published Docs to review the reader-facing documentation and confirm that the intended language options are available.

📷 Screenshot pending: Language configuration area showing the supported documentation languages and publishing controls.

Prerequisites

Before you begin, make sure you have:

  • Access to the documentation project you want to publish.
  • Documentation that has been generated using Generate Documentation →, or content that has been added through Or import existing documentation.
  • Access to the publishing configuration area.
  • A list of the languages your documentation audiences require.
  • A published documentation destination to review after configuration.

Step-by-Step Instructions

  1. Open the documentation project that you want to configure for publishing.

  2. Go to the publishing area by selecting Publishing.

  3. Select Configure → to open the available publishing configuration options.

  4. Locate the language information by selecting see the 24+ languages we support.

  5. Review the supported languages and identify the languages needed by your intended documentation audiences.

  6. Enable or configure the languages that you want to make available for published documentation.

  7. Confirm that the language configuration matches the audience or audiences that will use the documentation.

  8. Return to the publishing area when you have finished configuring languages.

  9. Check the publishing state shown under 3. Published Status.

  10. Publish the documentation when the publishing status and configured languages are ready for readers.

  11. Select View Published Docs to open the published documentation.

  12. If available in your workspace, select 🌐 View Published Docs to review the public documentation experience.

  13. Verify that readers can access the published documentation in the languages you configured.

📷 Screenshot pending: Published documentation view used to verify the configured audience languages.

Tips and Best Practices

  • Configure languages before promoting the published documentation link to customers or internal teams. This avoids directing readers to a site before the expected language experience is ready.

  • Start with the languages required by your largest or most important audiences. You can review the 24+ supported languages through see the 24+ languages we support when planning future expansion.

  • Review your documentation content before publishing. If you are still preparing content, use Generate Documentation → to create documentation from your code, or select Or import existing documentation when you already have material to bring into Atloria.

  • Use View Published Docs after publishing rather than relying only on the configuration screen. The published view is the best place to confirm the reader-facing result.

  • Keep language choices consistent with your documentation audience strategy. For example, configure the same language expectations across related published documentation so readers have a predictable experience.

  • Recheck language availability whenever you make major publishing changes, update documentation structure, or create documentation for a new audience.

Troubleshooting

You cannot find language options

Select Publishing, then choose Configure →. Look for see the 24+ languages we support to review the available language options. If you still cannot access configuration controls, verify that you have access to the documentation project and its publishing settings.

The published site does not show the language experience you expected

Open View Published Docs or 🌐 View Published Docs and review the published reader experience. Return to Publishing and confirm that the intended languages were configured before publishing. Republish the documentation if your workspace requires publishing changes to be applied again.

Documentation is not ready to publish

Check 3. Published Status to understand the current publishing state. If content has not yet been created, select Generate Documentation →. If you have existing content, select Or import existing documentation before completing language configuration and publishing.

Was this page helpful?

Download as PDF
Configure Published Documentation Languages — Atloria (self dogfood)