String resource management is currently not uniform across the codebase. Some user-facing strings are stored in resources and retrieved via Strings , while other strings, including exception messages, are hardcoded directly in the code.
We need to review existing hardcoded strings and move user-facing strings to shared resources. This includes exception messages, validation messages, and other messages that may be displayed to users or returned through APIs.
Strings that are purely technical, such as log messages, configuration keys, protocol values, route names, constants, or internal diagnostics, should remain in code unless there is a clear reason to localize them.
For string retrieval, we should use the same approach as Origam.Server , namely IStringLocalizer<SharedResources> . Existing usages of Strings should be reviewed and migrated to this approach where appropriate, so the codebase has a single preferred localization pattern.