馃悶 Bug Report: Add a per-page custom css section, as opposed to the current, per element. #21496
wearenv-digital
started this conversation in
Feature Request
Replies: 1 comment 2 replies
|
There are already three places you can add custom CSS, on a widget level, on a page level and on a global level in the site settings |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Prerequisites
What problem is your feature request going to solve? Please describe.
Im frustrated when adding custom CSS, that it is not collated in one place. I end up having to add all the css under one element, and on a page with hundreds of elements, it can get confusing as to where the css is. The second frustration is that if one element has custom css applied, and then is duplicated, that css is duplicated along with the element. Having one location per page, to add the CSS would mean that the declarations are not duplicated, improving page load time. I know there is the global css section, however it does not auto update the page being worked on without reloading, like the per element custom css does.
Describe the solution you'd like
Having one location per page, to add the CSS would mean that the declarations are not duplicated, improving page load time. I know there is the global css section, however it does not auto update the page being worked on without reloading, like the per element custom css does.
Describe alternatives you've considered
No response
Additional context
No response
All reactions