Use case #0: Introduction

[lecoqlibre]

The next use cases describe how to use this plugin to translate a WordPress website using Weblate.

Weblate works with components inside projects hosted on an instance. Naturally these Weblate objects are integrated into the plugin as particular WordPress objects pointing to the corresponding Weblate object such as:

• WP instance ==========> Weblate instance
  • WP project ========> Weblate project
    • WP component => Weblate component

These particular WP objects are used to make the link between WordPress and Weblate. This allows the regular WP objects like post, page and others to be translated. Indeed, the WP instance, project and component are used to track the location of translations within Weblate.

Any regular WP object to translate is then associated with a WP component that knows where to find the translations when the time has come.

[nijel]

Weblate will have additional level(s) of structuring content in the future, the naming is still unclear, though. But you can expect there will be an additional optional layer between what is currently called a project and a component. See WeblateOrg/weblate#263 or WeblateOrg/weblate#3299

[lecoqlibre]

OK, great to know. Maybe the thing is to make a project recursive so a project can contain a project. If that kind a tree structure is used, the UI of the plugin could still be a top-down list but should be ideally a real tree with a + to open underlying structure.