microsoft / microsoft/AzureTRE

Support for skinning/customising the UI

Open
#4,299 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
Python
Stars
235
Forks
192
Avg merge
1d 23h
Merged PRs (30d)
13

Description

We'd like to add an NHS logo to the UI for our SDE, maybe skin the site to fit our branding, add custom links to documentation relating to our environment, make some local customisations etc. This comes down to two things:

  1. Skinning. How can we change the appearance of the site without having to patch our fixes into the UI code whenever we update from upstream?
  2. Customisation. What's the current development procedure for enhancing or customising the UI? I've seen the documentation, but it's not clear from that if there's any support for debugging the React code without building a full deployment, which is a) slow, and b) hard to debug because the code is minified. Is there anything to make debugging easier and faster?

Many of our tweaks will be site-specific, not something that should be contributed back to the upstream codebase. It would be great if that could be supported by a clean separation of 'core' and 'custom' UI features.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the UI development documentation linked in the issue and the existing React development procedure. Clarify the supported approach for skinning, site-specific links and customizations, and faster unminified debugging; done should be a cleanly separated customization path that avoids patching upstream UI code.

Written by the indexing model from the issue text.

Assessment

Tech stack
react
Domain
developer-experience, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.