Open timheuer opened 2 months ago
@leslierichardson95 - lets discuss details/timeframe etc.
@timheuer - With all due respect, NO. The dashboard is not intended as a component that others can take, rebrand and use in different places. We will have extensibility for adding more modules.
Once you have people adding their own CSS, the opportunity for conflicts, especially during ongoing development is not worth the risk.
Let’s not close things without a discussion and have PM participate (as noted from Kay).
Consider exposing a small set of properties via CSS that could enable 'branding' of the Aspire Dashboard a bit more.
An example of this is the HealthChecksUI, that comes with a default experience:![image](https://github.com/dotnet/aspire/assets/4821/821ad07f-c252-4166-90fe-25024ebff75d)
But with providing a branding CSS file can be customized:![image](https://github.com/dotnet/aspire/assets/4821/f466ec6a-babe-44ac-b8bb-b174de7b76ab)
Exposing a small set of branding UI properties via environment variables and or mapping a CSS file for the Dashboard would enable those who are desiring a branded experience (maybe using hosted container image) a simple way rather than rebuild the source itself with adjustments.
Example methods HealthChecksUI uses:
Recommended customizations: