-
Notifications
You must be signed in to change notification settings - Fork 918
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
[Discuss] Strategies for auditing OUI usage #3803
Comments
Love the proposal. |
@andreymyssak @SergeyMyssak @curq - Now that you've audited some of the plugins, anything else we need to capture here, or should we close this discussion and make any subsequent template updates in #3945? |
@joshuarrrr I think it is okay to close this discussion and move to the #3945, where we can continue any future discussions and make further updates to templates as needed. |
I think this issue can be closed. Plugins with Sass have had issues created for them (ex #4076), with related info put into each individual issue. I'm about to create similar issues for core services. I'm also going to make a meta issue to track everything |
As part of our efforts to provide a more cohesive experience across interfaces and components, we've committed to building out, expanding, and improving OUI. But to maximize the benefits of the work in OUI, it's important that OpenSearch Dashboards is actually consuming, implementing, and using the existing OUI components correctly and comprehensively.
Anecdotally, we know there are many gaps today, where Dashboards components and apps are either not using OUI components at all, using them incorrectly, or extending them through hacks and overrides. The goal of this issue is to determine strategies for finding, understanding, and fixing these antipatterns. In an ideal world, there would be a complete separation of responsibility between OUI and OpenSearch dashboards, with OUI responsible for all the components and styles that implement the OpenSearch Design System. As we dig deeper into the gaps, we may discover that's not a reasonable or desirable goal, but it's a useful framework to start with.
The text was updated successfully, but these errors were encountered: