-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[META] Moving Kibana off Less and using EUI global CSS scope #19748
Labels
Comments
snide
added
Team:Platform-Design
Team Label for Kibana Design Team. Support the Analyze group of plugins.
Meta
labels
Jun 7, 2018
Kibana packages
Core
UI@cchaos :
Bootstrap
Xpack
|
This was referenced Sep 24, 2018
This was referenced Oct 3, 2018
Note ---DONEWe also need to remove any .LESS file references to removed files in here:
|
This was referenced Oct 5, 2018
Closing this issue. Outside of some hanger on issues, it's complete and would be better served by smaller, clean up issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This will be a meta issue for tracking conversion of Kibana's 307 Less files to Sass.
Primary goals
Why are we doing this?
Staged approach
Because of the size of the changes we should consider staging this out. I could see us doing the following...
After the above is done
Patterns we'll want to follow during conversion
These are simple examples, not meant to be full code methodologies and pathing scenarios.
File organization
Kibana is made up of three major parts: The inherited EUI components, the global Kibana global blob, and individual Kibana plugins.
Kibana global blob would look like this
Then Kibana's core global scope includes/inherits EUI and builds beyond it with it's own global mixins and components in a single css blob. Anything in this file would be considered usable UI for all of Kibana. We'll have better control over the load order and be able to run proper trash tests as we remove code over time.
Plugins would be separated into their own css files (as shown earlier) and loaded only within their plugin scope.
Plugins
Kibana is mostly made up of plugins. We should aim to move all styling to match the below structure.
Sass
Then in the files themseslves
Sections to convert
For an example conversion, along with some tips please look at #20995
Xpack plugins
Kibana OSS
Kibana core + Bootstrap
Kibana core work is blocked by #20859
Kibana core is essentially everything in src/ui/ (which is a lot of files)
KUI
KUI (aka
ui_framework
) should be audited for unused components. Existing, in use ones should import the EUI global scope so that it matches EUI theming as much as possible.The text was updated successfully, but these errors were encountered: