From b7cf066d1831e3baf15f454c0115fec5734f8157 Mon Sep 17 00:00:00 2001 From: weru <fromweru@gmail.com> Date: Mon, 07 Dec 2020 13:17:44 +0000 Subject: [PATCH] edit page --- exampleSite/content/docs/compose/search.md | 12 ++++++++++-- 1 files changed, 10 insertions(+), 2 deletions(-) diff --git a/exampleSite/content/docs/compose/search.md b/exampleSite/content/docs/compose/search.md index 8c76cb5..d52e042 100644 --- a/exampleSite/content/docs/compose/search.md +++ b/exampleSite/content/docs/compose/search.md @@ -12,7 +12,7 @@ ### 2. Live search -This behaviour will be obvious as the user types a search query on the search field. All search queries, will yield a list of `quick links` or a simple `no matches found`. Else, the user will be prompted to continue typing. +This behaviour will be obvious as the user types a search query on the search field. All `valid search queries`, will yield a list of `quick links` or a simple `no matches found`. Else, the user will be prompted to continue typing. > Please note that the results under quick links will be a truncated list of the most relevant results. Only a maximum of 8 items will be returned. This number is pragmatic at best if not arbitrary. On the search page, the number is set to 12. @@ -29,4 +29,12 @@ I think the other 3 are not only related, but can be for the most part be achieved using the good old-fashioned CTRL/CMD + F. (1) multilingual sites -(2) blog/events sections that are separate from the docs section --> \ No newline at end of file +(2) blog/events sections that are separate from the docs section --> + +### What is a valid search query + +A valid search query must be long enough. If the search query can be cast as a float, then it only need contain one or more characters. + +Else the search query must be at least 2 characters long. + +<!-- This behaviour will change. --> \ No newline at end of file -- Gitblit v1.10.0