Skip to content

Make page header customizable

What does this MR do?

By adding a new entry header in our application configuration, we can now have a customizable brand name and instead of Student Information System / Universis , an institute can customize it to its needs. It can be available in more than one locale.

The header field in the application settings accepts an array of objects with the following structure:

"header": [
          {
            "additionalType": "Header",
            "body": "",
            "abbr": "",
            "inLanguage": "en"
          }
...
        ]

If any of the body/abbr is empty/whitespace , the layout fallbacks to the default Student Information System/Universis header based on the screen-size

Related issues and links

Fix #218 (closed)

Other relevant links

Developer Checklist

  • I have successfully run the code of this merge request locally

  • I have verified locally that my changes work for all necessary screen sizes

  • I have tried out the changes of this MR with different users to identify bugs

  • Coding is in progress, and I have marked the MR as WIP

  • Coding is completed and the MR is ready for review

  • My branch is up-to-date with the upstream master branch

  • My MR follows the contribution guidelines

  • I have added a comment with screenshots of the code running locally

Tech review Checklist

Have you verified that what is supposed to happen, actually does, and what is not supposed to happen, indeed does not?

  • The MR accurately describes the changes and has a relevant title/description
  • The MR does what it is supposed to according to its title, description and related issues/links
  • I have successfully run the changes locally, and tried the new code

Overall review Checklist

  • The MR references related issues/MRs
  • The MR provides links to screens and screenshots
  • The commits of the MR describe the changes, have proper wording, and follow the guidelines
  • I have successfully run the changes locally, and tried the new code
  • The MR is ready for merge (rebased, commit squashed if needed, etc)

Merge request reports