-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove CSS settings from app-settings #17235
Comments
These options are used by the these helpers that are used everywhere Line 8 in 411cbf1
OrchardCore/src/OrchardCore/OrchardCore.DisplayManagement/Html/CssOrchardHelperExtensions.cs Line 8 in 411cbf1
These configuration can be configured by any theme that is derived by TheAdmin theme to enable styling and small customization. Until we reusable components in TheAdmin theme that allows one to override the look and feel of TheAdmin theme, these should be be removed. For example, I have an admin theme that places the labels on the same line as the input. I am able to do this now using these options. Here is an example This is possible by adding the following
What I suggest to do, is add theme settings UI to expose these options. The Themes UI is now shape base and you can add a settings button next to each theme where one can configure these values from the UI. In my project, I have this settings for each theme. currently, this allows me to inject css code in the theme. But you can use the same thing to expose these settings. |
From a UI/UX perspective coding CSS classes is hard, it would be nice to let the HTML control everything. I still remember one of my friends 3 or 4 years ago when he told me, why the framework is tightly coupled on Bootstrap, this will limit the possibility of extending or changing the UI framework in the future |
I agree. That's when having some sort of components design would be great. Until then, these options should stay to allow customizing our tightly couple theme. |
I created a prototype long time ago, hopefully one day I will demo it |
If this is the only issue, I believe there are ways to fix it, like @MikeAlhayek suggested by code. Or load other config files, splitting the config (is that possible?, something to add?) |
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues). This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here. |
Current setting works for small org where few dev manaenge the app. But in SME or LE, have separation of duties, some organizations have app support team they manage infrastructure and app configuration- but they are not admin or owner of the application. Designer who can control such css- do not have access to change such configuration on infra. |
Today the CSS classes are defined in app-settings as following, this makes app-settings noisy - The purpose of app setting to be limited to application and feature configuration - that managed by configuration management and not for UX/UI management
Like Zone, we don't provide Zones configuration in app-settings, instead we provide UI to manage zones
Similarly we should not have CSS settings in app settings -instead, theme should provide custom UI to manage such settings needed for the theme that is only applicable to that theme.
Possible options
The text was updated successfully, but these errors were encountered: