Comment by cjcenizal

Thank you! As snide mentions a few threads up, we built a documentation website for the library from day 1, which I think helped folks a lot. I'm not a fan of Storybook -- I prefer docs to present components in realistic situations, and to have code snippets live-side-by-side so someone can say "Hey this is exactly what I need" and copy and paste it into their codebase. For example, form docs should have an example of a complete form with validation, accessibility attributes, help text, and so on. This way the docs act as both an advertisement and as a resource.

Regarding tools, I recall a bunch of stuff. YMMV:

* A presentation to the wider team on the goals of the library.

* GitHub issues outlining technical design of the library -- this was useful for getting buy-in from tech leads.

* One of the consuming developers gave a presentation on how she had implemented a UI using EUI.

I think it just comes down to repetition and, as snide alluded, positioning yourself as a servant instead of an authority. Keep beating the drum, share success stories, and demonstrate that you're responsive to the feedback you're heading from the folks downstream. Good luck!