Skip to content

Remove ambiguous l10n namespace documentation

Miguel Rincon requested to merge doc-namespace-example-improvement into master

What does this MR do?

The namespace localization function is slightly different for frontend and backend, this MR aims to introduce the topic of namespaces without the function name so the concept is more clear.

Frontend and backend specific implementation is explain below as well, so it's less repetitive.

Improvement of !31452 (merged)

Author's checklist (required)

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖

Merge request reports