You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how feasible this would be, given the nature of how the pages are generated, but it would help with usability if I didn't have to manually check every page to see what a %W() is, for example.
The text was updated successfully, but these errors were encountered:
Yes, that's a long-anticipated thing, but how to implement is a bit of question.
Technically, there are solutions for the static sites (they just render the search index into JSON file and load it onto search page, and process search with JS on a client-side), so it is not a big of a problem.
But conceptually, WHAT should be put in a search index, IS a problem. Because if it is "every word in a text", then probably google term site:rubyreferences.github.io/rubyref is good enough. So, the task is not to "index it to be searchable", but to create a proper index of terms, which is either a tedious manual work or some inventive automation I haven't decided on yet :)
Sorry about the inactivity, but you do have a very good point. I'll use the Google method for now and we'll see if someone has a good idea for this eventually.
But conceptually, WHAT should be put in a search index, IS a problem. Because if it is "every word in a text", then probably google term site:rubyreferences.github.io/rubyref
maybe add a search bar that does that on form submission?
I'm not sure how feasible this would be, given the nature of how the pages are generated, but it would help with usability if I didn't have to manually check every page to see what a
%W()
is, for example.The text was updated successfully, but these errors were encountered: