Feature Overview (aka. Goal Summary)

Improve (add missing translations) for Backstage Core plugins like Catalog and Notifications.

Automate translations for plugins that are build with the overlay repository.

Goals (aka. expected user outcomes)

1. Add and extend translation support in core backstage plugins
   1. Backstage catalog improvements (like adding support for "Links", and other card labels)
   2. Backstage notifications plugin (completely new)
   3. Backstage core components Header should set an localizable title (uses just app.title configuration now)
2. Automate translation process for the rhdh, rhdh-plugins and overlay repository
3. Localizable log in screen to improve the initial experience (if not done already)
4. Add and improve translation support for rhdh-plugins
   1. Use pluralization feature
   2. Improve datetime support
   3. And everything that we missed in 1.8 - tbd.
5. Add and improve translation support for backstage/community-plugins contributed by Red Hat
   1. 3scale
   2. ACR
   3. JFrog
   4. MCP Chat?
   5. Nexus Repository Manager
   6. ServiceNow
6. Stretch goal: Improve plugin author experience with tooling (eslint)
7. Stretch goal: Help Backstage team to remove the experimental badge from the translation feature
   1. Add mocks for translationApi and appLanguageApi into backstage/test-utils
   2. Add Trans into backstage core
   3. Add LocalDateTime component into backstage core?
   4. Fix the need of defining our own types for useTranslation (if not already fixed)

Requirements (aka. Acceptance Criteria):

1. Core backstage plugins like catalog and notifications are fully translated (translation support and translations to French)
2. Overlay repository builds (OCI container images) contains translations

Out of Scope (Optional)

High-level list of items that are out of scope.

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.