Add support for internationalization

Although most i18n is configured client side, if an application may store different versions of content based on language, we could add a reference implementation of handling language-specific content (likely with fallback to default language: `en_US`).