Skip to content

Make dark_lang work in MFEs or deprecate it #38626

@kdmccormick

Description

@kdmccormick

Background

The "dark_lang" app is an admin-only feature that lets you preview the site in unsupported languages, like eo (a fake version of "esperanto"). Unfortunately it doesn't seem apply to MFEs. It only manifests legacy frontends, the latter of which are almost all disabled by default.

Furthermore, its interface (at <LMS_ROOT>/update_lang) is a legacy frontend itself, so we'll need to port it to an MFE, or accept that it's an admin-only feature.

For context, we learned of this issue while implementing:

in which we removed the legacy Studio version of the frontend so that we only had only legacy frontend (the LMS one) to deal with.

Tasks

  • Consult with product: Do we want the ability for admins to preview the site in not-yet-supported languages?
    • If no: Deprecate and remove the entire app.
    • If yes:
      • Consult with product: Does it need to be an interface, or is Django admin OK?
        • If Django admin is OK: Deprecate and remove just the UI; keep the app available via Django admin.
        • If we need an interface: Create a ticket to reimplement the UI in an MFE
      • In either case: Create a frontend-base(?) ticket to propagate the preview language setting into frontend apps as an override to the user's language setting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions