-
Notifications
You must be signed in to change notification settings - Fork 26
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
Search bar on the juju.is is missing #435
Comments
Please see this reply: #442 (comment) |
@Lukewh that does not answer the query. if we have this search on SDK and OLM, cannot we bring it to the main page? UPD: there is no indent to search charms. Idea is that once you open juju.is you can immediately search docs without extra clicks |
“The main page” is ambiguous here. Do you mean https://juju.is or https://juju.is/docs? |
@Lukewh |
So, the linked comment does answer the query, when we add the unified search in the navigation, it will be possible to search docs from any page on juju.is and charmhub.io, including the homepage. |
@Lukewh ok, it depends. If unified search is something that is coming soon, then we are good if there is no timeline on it, then at least copy pasting the search bar from https://juju.is/docs to https://juju.is/ will resolve the issue. Then at least docs would be searchable from everywhere |
It's not a simple copy-paste solution, we have user experience and design to consider. If we simply copy and pasted every idea everyone had, we'd be in a poor place. We have guidelines and processes to follow in design, just as we do with code. |
@Lukewh well, I agree. However, what would be the solution for now? (because now we force every user to do extra clicks to reach search) |
As stated in the comment, it's on our roadmap for next cycle. |
@Lukewh |
Hello,
currently we are missing a search bar on the main page of the juju.is website.
Existing workflow is confusing:
Proposal:
add search bar on the main page. Then people can search through the whole material (which is anyway already done) with less confusing clicks.
I hope that implementation is simple, since there is no need in backend changes. Same search, just place a component on the main page.
The text was updated successfully, but these errors were encountered: