-
Notifications
You must be signed in to change notification settings - Fork 5
A wish: Search bar readily accessible #50
Comments
Hi! Let's see.
I agree it looks arguably weird, thanks for reporting. Now on the search bar.
Yes, but... The docs website is not a search engine like duckduckgo. The main function is to work (primarily read) with docs, not search up things. Search engines are "jump to" pages, you don't need to focus on the content there and the immediate thing you want to do is to jump to the results ASAP. With docs it's a completely different thing: you look something up in the search, which takes like 5 seconds even with 2 excessive clicks, and then read the docs for X minutes (~95% of the time you use the website). That's why especially on small screens you want to see the content you'll read for 95% of the time, not the search bar useless except for mere 5% of the time, obstructing reading the content. No amount of capslock can change this.
To save the space for the menu and have a wide enough search being true. An animation is used to avoid the transition being felt as abrupt and indeed losing the cursor. |
Me disagrees. There are different modes of reading docs. When you start to get to know a topic or a sub-topic, you mostly read indeed. I often find myself jumping from one topic to another: I switch from page to page so frequently, that no-quick-search websites feel hampering. IMHO, docs websites are best described as Search-Read-Repeat-Loop. Not a search engine good (IMHO) examples: Search may not be the main function for a docs website, yet it is a critical and cornerstone function.
May the animation be as brief as a blink of an eye, just linking bar's short and long states, and not obstructing workflow by being long enough to be watchable? |
I think the constructive solution for this would be to have a layout where in the mobile mode the search bar moves to between the logo and the hamburger rather than being hidden in the menu, volunteering to get it done faster is welcome. |
If you hint at me, given my technical level, with me participating you will have to fix more than without me participating, so I would better refrain from offering my antihelp. |
(My personal wish, YMMV)
How any search engine (like duckduckgo) offers a search bar to the user:
you open their webpage, and the search field is right before you, and it is focused straight away and webpage is ready to accept your keyboard input, you start typing immediately without any additional movements.
This is the right way (IMHO).
With https://docs.raku.org/ you fireup the page, the search bar is there waiting for input but it is not focused.
Darn it! Excessive mouse movements and a click or 2 tab presses are needed to focus.
Now take your temporary http://164.90.207.89:10010/
With wide enough screen, the search bar is there, but not focused,
you need excessive mouse movements and a click or 8! tab presses.
With narrow screen, the search bar isn't even displayed, so you need to move that mouse into the corner, then click and, guess what? You get the search bar in the opposite corner of the pane! Your cursor loves to be moved across the screen forth and back! 😄
Please note that with the window size as in the screenshot, there is enough space for the search bar.
Search bar not displayed
(Also please note vertically misaligned
Learn more
button underLanguage Reference & Tutorials
)Search bar in the opposite corner
A keypress like
/
for triggering search might mitigate the issue, yet why hide that poor search bar in the first place?Search bar animation. Why? I come for docs, and want them promptly. With animations I get distracted and they make me wait while animation finishes.
Github search bar like on this page is also expandable, but it is not that bad as it expands left-to-right, and the input cursor stays in place.
With your temporary http://164.90.207.89:10010/ the bar expands right-to-left, and the cursor flies away from the spot where it was which distracts and makes me seek that cursor again.
Recap:
The text was updated successfully, but these errors were encountered: