Epic Overview (aka. Goal Summary)

As part of a well localized product, RHDH should look and function well regardless of which supported language is selected. RHDH language support may need to expand to right-to-left languages in the future, and it would be useful to better understand how easy or hard that would be to implement for the first such language, so we have a better idea what the impact and effort might be when there's sufficient customer demand.

Goals (aka. expected user outcomes)

• Assess how well the UI works with right-to-left languages, and better understand what it might take to add these additional languages in the future.

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.

• Investigate how well RHDH works out of the box for these languages, and see where it doesn't work well. 
• Produce a document we can feed into a followup feature where we scope and prioritize any needed product changes.
• If additional work is needed for this to be well supported, create a placeholder followup feature with the document linked that we can scope out with PM.

Out of Scope (Optional)

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

• Making production level changes to the codebase. This is meant to de-risk adding support in the future.
• Product documentation is out of scope here, this is focused on our product UI.