/
Namespaces
  • Subject to Change
  • Namespaces


    Overview

    Namespaces

    • Namespaces are defined in the next-i18next.config.js configuration file in the application root.

    • Separate localisation namespaces are being used to keep translation keys better organised for

      • logical coherence

      • easier maintenance

      • consistent reusability and minimising duplication

    Namespaces Used

    Namespace

    Purpose & Scope

    Usage

    Configuration Notes

    Namespace

    Purpose & Scope

    Usage

    Configuration Notes

    application

    Phrases used in specific application contexts

     

    default namespace

    common

    Phrases that are reused across and about the user interface

     

    Key scopes restricted to:

    • ui: buttons and other interaction elements

    • nav: sidebar, breadcrumb, page titles

    • link: link hover content

    • a11y: generic accessibility phrases, used by screen readers where existing translation content is not appropriate

    fallback namespace

    validation

    Phrases used in validation interactions for generic and specific workflow operations.

     

     

    glossary

    (not implemented)

    Business vocabulary and phrases that we want to be reused consistently, including context and count variants.

     

     

    References

     

    Operated as a Community Resource by the Open Library Foundation