Better handling of links in documentation, against documentation changes

[evnchn]

With reference to #904 (comment)

The following approaches could be valid. It may or may not be good to do both. Let's assess.

1. If we can't find the paragraph in https://nicegui.io/documentation#clear_containers, should we invoke a side-wide search and redirect on found, instead of leaving users on the main documentation page?
2. Instead of sharing https://nicegui.io/documentation/section_page_layout#clear_containers, can we share a link which does a site-wide search (thinking maybe https://nicegui.io/documentation/search/clear_containers?)

[falkoschindler]

Hi @evnchn,

Showing the search dialog as a fallback is a great idea. Some thoughts about it:

• Before starting to work on this feature, we should wait for PR Introduce ui.sub_pages to allow implementing single page applications (SPAs) #4821 getting merged which changes some inner workings of the documentation.
• Somewhere around here we could open and pre-fill the search dialog instead of raising a 404 exception.
• Additionally, supporting a query parameter ?s=... would allow adding site search shortcuts for nicegui.io in your browser. This way you could type "nicegui<space>button<enter>" and you would automatically get the search results for "button".