7 ways to search for a camelCased parameter in your docs
Technical documentation contains word patterns like camelCase that give traditional search engines a headache. See how Algolia makes camelCase parameters searchable by 7 different types of queries. Given at API Days Paris 2016.
https://www.dropbox.com/s/ipty10vd9c7u4jv/Screenshot%202016-12-13%2012.01.04.png?d l=0 DOCUMENTATION SEARCH Do your docs have a search? Search the docs... Get community.algolia.com/DocSearch, used by:
DOCUMENTATION SEARCH 7 common queries for this parameter 1. `crossOriginLoading` 2. `cross Origin Loading` 3. `Origin` 4. `OriginLoading` 5. `Origin cross` 6. `Origin Loading` 7. `OriginLoad` Note: all uppercase/lowercase characters are treated the same
DOCUMENTATION SEARCH Fix #1: Uncamelizing Split word into parts by capital letter `crossOriginLoading` => `cross Origin Loading` Caution: Don’t split “API” into “A P I”
DOCUMENTATION SEARCH camelCased Query #6 (later words) OriginLoading| MOSTLY OK! `OriginLoading` is a 1-typo match for `Origin Loading` 1 typo: it will appear in results but potentially lower ranking.
DOCUMENTATION SEARCH Back to camelCased Query #1 crossOriginLoading| FIXED! \o/ Synonym matches `cross Origin Loading` Results show `crossOriginLoading` w/ no spaces, spaces are replaced by invisible unicode character \u2063
DOCUMENTATION SEARCH camelCased Query #7 (later term partial) OriginLoad| FIXED! \o/ `OriginLoad` will prefix-match synonym `OriginLoading` thereby becoming `Origin Loading` and a 2-word match of `cross Origin Loading`