Eui: Elastic UI but for VueJS

Created on 17 Feb 2020  路  3Comments  路  Source: elastic/eui

Hi team,

Just wondering what do you think about creating a new library based on this one but using VueJS instead. I've been playing with your theme styles on top of some Vue components and they look pretty nice. There are some good UI frameworks out there with version in both ReactJs and VueJs, eg: ElementUI so I was thinking that maybe I can start working on a new EUI version but delivering VueJs components.

Do you think it's a good idea? Am I able to do that by maintaining your trademark right?

Most helpful comment

@chandlerprall Thank you so much for answering so quickly. I just sent an e-mail to the e-mail address you've provided :+1:

I've been working with the Elastic Search stack for a while, and IMHO, EUI it's one of the cleanest frameworks out there. I fell in love with Kibana UI at first sight :)

As I mentioned, I've been trying to create my own components using your CSS layer. I tried to maintain the same props and signatures that the React implementation has at this moment.

I'm aware that creating such a library takes some time and effort to maintain, but I was thinking that if the community really likes the idea, they'll probably jump and contribute with the open-source project.

Anyway, let's wait for the answer from the license team side, and then we can decide if we can move forward with the implementation or not.

Again, thank you so much!

All 3 comments

Thanks for the interest, and the compliment on Elastic UI!

First, some thoughts on the non-legal side of things:

  • We are planning (#1656) to move to some sort of CSS-in-JS solution at some point this year. This will be likely be Emotion. I do not know the CSS-in-JS landscape for Vue, but a quick google search shows it may be straight forward to use those together?
  • Maintainability may be tough; we move pretty fast and I imagine mirroring even a subset of our changelog would take time. Further, we do not consider [most] style changes to be breaking which may cause other issues.

As for the legal, I'll add some thoughts below with the caveats:

  • I am not a lawyer, this is not legal advice
  • If you go down this route please reach out to [email protected] as they will be able to help navigate any trademark issues

As our CSS styles (and the rest of the codebase) are licensed under the Apache 2.0 they can be included, modified, and redistributed within other projects, as long as attribution (as determined by the license) is maintained.

The license explicitly does not grant permission to use our trademarks, etc. How to best indicate a new, separate library is "Elastic UI but for Vue" is an interesting question. Again, I strongly recommend contacting [email protected] in this area.

@chandlerprall Thank you so much for answering so quickly. I just sent an e-mail to the e-mail address you've provided :+1:

I've been working with the Elastic Search stack for a while, and IMHO, EUI it's one of the cleanest frameworks out there. I fell in love with Kibana UI at first sight :)

As I mentioned, I've been trying to create my own components using your CSS layer. I tried to maintain the same props and signatures that the React implementation has at this moment.

I'm aware that creating such a library takes some time and effort to maintain, but I was thinking that if the community really likes the idea, they'll probably jump and contribute with the open-source project.

Anyway, let's wait for the answer from the license team side, and then we can decide if we can move forward with the implementation or not.

Again, thank you so much!

Closing this as #3572 has more relevant information regarding licensing.

Feel free to repoen if new information becomes available.

Was this page helpful?
0 / 5 - 0 ratings