# Improving findability with UX patterns

**URL:** <https://discuss.elastic.co/t/improving-findability-with-ux-patterns/43502>\
**Category:** Kibana\
**Created:** [March 4, 2016, 11:19am UTC](https://discuss.elastic.co/t/improving-findability-with-ux-patterns/43502 "2016-03-04T11:19:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjornte](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bjornte/32/8273_2.png) [@bjornte](https://discuss.elastic.co/u/bjornte)\
**Post date:** [March 4, 2016, 11:19am UTC](https://discuss.elastic.co/t/improving-findability-with-ux-patterns/43502/1 "2016-03-04T11:19:56Z")

</div>

I'm interested in your opinions regarding a findability-focused, UX-oriented pattern library.

When developing enterprise search solutions over the last 10 years, my experience has consistently been that UX-driven features that are crucial to findability rarely make it into the actual services. Consequently, the services often suffer from findability of 20% or less in the «unstructured data behind the firewall» scenario.

To remedy, I’m wondering if there’s interest in a findability-focused, UX-oriented repository for teams building enterprise search solutions. I have made a start here:

> **[bjornte/UX-patterns-for-findability](https://github.com/bjornte/UX-patterns-for-findability/)**
>
> UX-patterns-for-findability - At first a single template for a search engine result page (SERP). Over time hopefully a library?

It contains elements like this (a disambiguation strategy sometimes called a [OneBox](http://searchengineland.com/meet-the-google-onebox-plus-box-direct-answers-the-10-pack-26706)):

![disambiguation result illustration](https://raw.githubusercontent.com/bjornte/UX-patterns-for-findability/master/disambiguation-result-illustration.png)

All of the described concepts would benefit from support from the core technical search service. I therefore have some open questions: Are there some technically inclined committers who see the value of supporting these UX concepts with reusable code? More in general, do you have opinions on how to best create a repository that will be valuable to the community?

Please let me know if I can clarify my request in any way. Everyone are welcome to make commits also to the UX part of the repository. Thanks in advance for any and all interest.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 2:00pm UTC](https://discuss.elastic.co/t/improving-findability-with-ux-patterns/43502/2 "2017-07-06T14:00:15Z")

</div>