That url is useless. It does not provide direct link to ssr. Read below.
Why we may argue about whether it's important, integration with google search is different then searching on site.
I'll try to explain my workflow.
1) working in jupyter.
2) ctrl+t open new tab ; type kdb ssr ; scan results from top ; click first result ; read doc ; ctrl+w close tab = 2 command shortcuts + 1 list scan + 1 click
3) keeping typing in jupyter with refreshed knowledge
This is about 2 seconds to get to ssr definition. My flow is not interrupted.
with what you suggest i will need to:
- open code.kx.com
(or scan through tabs and find it open) = 1 scan tabs + 1 click OR 1 shortcut + type window title search string (code.kx)
- focus search fild = 1 click
- scan results (no result for SSR) = 1 scan
- click on any link because they all are wrong = 1 click
- scan for ssr (won't do it), instead will type ctrl+f ssr = 1 shortcut + 1 scan for yellow highlight
- click on it = 1 click
While I adore kdb, it's dynamic language, so no any help from IDE, so I use google a lot.
With removal of wiki, i'm out of usable manual.
to make things worse, try searching for "ss" on the site. Compare it to google "kdb ss".
WHAT TO DO:
process your documentation. It seems to be structured enough. Generate partial pages with proper urls without id/anchor, put it in "/funref" directory and let google index it.
Add enough keywords, add "kdb" (because no kdb in url, only kx).
Reformat funref to contain no extra space for novices.
Then compare search hit rate on both funref and current pages, and you'll get what I mean.