Skip to content

Reduce institution-specific customization pain points #1628

Open
@clpetersonucf

Description

@clpetersonucf

Our work with other institutions has identified a number of pain points associated with overriding or customizing various pages. While this was originally easier, the combination of dockerization and react UI rendering makes inserting overrides more difficult.

Currently, overrides must be managed in one of two ways:

  • Forking the repo, creating custom variations of files, and then publishing your own docker image(s).
  • Implementing a custom theme package via compose and then redoing the above.
  • Overriding specific files via volume mounts.

Both are potentially prohibitively complex for institutions that just want to change a few strings here and there. Ideally these values could be configured more easily and then loaded into the application as overrides for specific locations.

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