Most of the CSS files are not located in the UI (admincentral). One can bring additional css easily for server side components via annotation. Unfortunatelly, the CSS for the age editor needs to be explicitly injected in the page editor inner frame.
Make the CSS for the variant selector part of personalization module so the changes can be done independently from the UI.
Espen's resource bundle
This is probably "how it should be done"
CSS is parsed and our page-editor.css fails when parsing (all the rules would have to be marked as @external and there are still some parsing errors)
Interfaces can't be overridden by deferred binding?
Based on the GWT public folder (/VAADIN/widgetsets/info.magnolia.widgetset.MagnoliaWidgetSet/page-editor.css).
the page editor css would be moved to the pages module where it belongs
Needs to be pre-compiled
No need to override a method, the custom CSS would be brought by different public folder (/VAADIN/widgetsets/info.magnolia.widgetset.MagnoliaProWidgetSet/page-editor.css)
To not duplicate the original page editor CSS, import the original one and add custom ones:
Does not work since we have MagnoliaWidgetSetPro and the original CSS is not available at runtime. Try to import scss and precompile:
We need to import a SCSS file, since CSS files are not eagerly imported. The results contains wrong paths to magnolia icons (due to the different public URL)