Documentation feedback #156
Description
Describe the solution you'd like
Based on some customer feedback, it'd be nice to see the documentation have more clarity on configuring Lucene search. Something similar to examples in the Kentico documentation that shows you how to configure search from start to finish. From custom index strategy to rendering results on the front-end site. With the additional optional configurations better explained based on the "minimum" example setup. This will help developers better understand the different components of Lucene Search. As of now, the documentation feels loosely connected.
For example, after setting up a basic search, include optional configuration like a web crawler.
Documentation correction on the page for managing indexes.
Included Path - can be an exact relative path of a web page item, (ex: /path/to/my/page), or a wildcard path (ex: /parent-path/%)
To determine a web page path, select the web page in the website channel page tree, then view the "Current URL" in the Content tab of the web page. The path will be the relative path excluding the domain
In a recent customer call, we determined that using the "Current URL" was incorrect for the path. It is the Tree Path that is more accurate. For example, based on the call, they used something like /my-page-path/% based on the Current URL. But the correct value the worked out was the Tree Path which was /my_page_path/%.
Add a terminology guide page. In addition to the example walkthrough, help users new to working with Lucene by giving them a breakdown of the key words and phrases associated with configuring Lucene search.