Temporary list from engg.

1. 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)
2. 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)
3. Add and improve translation support for Red Hat plugins
   1. Use pluralization feature?
   2. Improve datetime support?
   3. And everything that we missed in 1.8 - tbd.
4. Add and improve translation support for community plugins (if PM wants)
   1. 3scale?
   2. ACR?
   3. JFrog
   4. MCP Chat (initial PR still not merged)
   5. Nexus Repository Manager
   6. ServiceNow
5. Improve plugin author experience with tooling like linter (improve tooling, use eslint rules, make upstream cli contibutions of possible)
6. Automate translation process for the rhdh, rhdh-plugins and overlay repository

Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

<your text here>

• Localizable log in screen to improve the initial experience

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Out of Scope (Optional)

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

<your text here>

Customer Considerations (Optional)

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

<your text here>

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.

<your text here>