Strategies to improve search capabilities on MIxS documentation site

[sujaypatil96]

Trying out different search configuration options provided by mkdocs: https://www.mkdocs.org/user-guide/configuration/#search

[sujaypatil96]

To see if we need to enforce a minimum length for search query/string: https://www.mkdocs.org/user-guide/configuration/#min_search_length look through the schema and calculate a distribution of the lengths of all slots and classes in the schema.

Note: ph might be the only 2-character term.

[sujaypatil96]

Should we add parantheses as a splitting character: https://www.mkdocs.org/user-guide/configuration/#separator

[sujaypatil96]

The configurability options provided by the mkdocs framework for the search plugin are:

Option	Action	Modified/default
separator	modified to '[\s\-\:\(\)]+'	modified
min_search_length	using default 3-character minimum	default
indexing	full	default
pre_build_index	disabled	default
lang	default	default

• For the separator, we have added in :, ( and ) as additional word separators because these delimiters are used on page titles
• For min_search_length, we are sticking to the default minimum character limit of 3
  • The only term (slot) with length less than 3 is ph, and there are no checklists, extensions or combinations (classes) with length less than 3
• For indexing, we will stick to the default full page indexing because there is useful content in the descriptions, etc. that people might want to search on