I have shipped search functionality on Web Platform Daily (WPD). This is a subscriber feature and it’s currently in alpha. If you encounter bugs, please report them (create an issue in this repo).
This feature enables you to perform searches on the entire WPD dataset (~600 releases). You execute a search term and the entries that contain that string (exact match) are displayed.
I have enhanced the search functionality with the following operators:
svg and icon... user:chris
Finds all entries that contain the word “svg” and a word that starts with “icon” (the ... is used to match both “icon” and “icons”), and that have been posted by a user whose Twitter handle contains “chris” (the search obviously targets Chris Coyier).
300ms or 350ms
Finds entries containing either one of those; useful for finding all the entries about the tap delay.
aria or accessib... in:demos
Finds all demos that contain either “aria”, or “accessible”/“accessibility”/etc.
csp and report...
Find entries containing “csp” and “report”/“reporting”/etc.; so all entries related to CSP reporting.
Finds all entries about ES6 that have been published on the Mozilla Hacks website.
In my browser (Firefox 42.0 on OS X 10.11.1), pressing / actually open the browser’s built-in quick search feature (like it’s supposed to do). It seems that, in this case, the script is not able to catch the keystroke or to prevent the browser’s default behaviour.
I love this feature, but I had to look up the link to this issue to find the shortcut (I kept trying "t" a la github's file finder). Any chance you'd be open to changing the key-binding?
This is really nice... perhaps you can put the possible filters/sections at the top of the page, right now I need to scroll first to see what the sections are so I can use them as filters.. having a key handler is all for fast access, if I then have to remember the filters... I'm kind of wasting time scrolling. Plus, the sections could also serve as a filter for the content below, jumping to it or something like that.
But in any case, I like how simple everything is.
@rolfnl Yeah, I should probably show a tooltip with the possible values for the in: filter. I haven’t defined the new UI yet, but there will definitely be a handy box explaining how to use the search in more detail. Not sure what you mean by that last sentence.