Open partiallyordered opened 2 years ago
This is probably best achieved without any per-scheme build. Instead, resources that a scheme might like to customise to brand the portal should exist in the built container image at a pre-determined/documented location. Then, when deployed, these resources should be replaced via volume mount with a scheme's resources to apply their branding. Resources would likely include images and stylesheets. Some modification to the portal might be required to use stylesheets instead of javascript-generated CSS. In the short term, it shouldn't be especially difficult to only replace images to achieve a small degree of branding.
Portal should support branding with the scheme name