We may want to provide the user some link to the library page or its clojars page when we ask him/her if s/he wants to build its documentation. For instance on https://cljdoc.org/d/aoe/aoe/0.1.0-SNAPSHOT, it is difficult to know if I should press that build button if I am not sure what the library does or is.

The open search feature starts to work on my branch. However, the search function from Clojar is really not good, so it makes it less usable than it should be.

I am thinking about ways to run a search function directly in cljdoc: - There is this file which is available. https://github.com/clojars/clojars-web/wiki/Data#list-of-jars-and-versions-in-leiningen-syntax - There is those download stats which can help prioritize the search results which only partially match. https://github.com/clojars/clojars-web/wiki/Data#download-stats - That page also mention a lucene index, maybe worth taking a look at what can be done with it. https://github.com/clojars/clojars-web/wiki/Data#lucene-index-of-maven-artifacts