Issue #3047719 by agrochal, shimpy, Manav, jhodgdon, hash6, Sarahphp1,...

Issue #3047719 by agrochal, shimpy, Manav, jhodgdon, hash6, Sarahphp1, batigolix, alonaoneill, ketansevekari, EricRubino, rkoller: Convert search module hook_help() to topic(s)

(cherry picked from commit c4ae3cf4)

core/modules/help_topics/help_topics/help.help_topic_search.html.twig

 ---
 label: 'Configuring help search'
-top_level: true
 related:
   - block.place
   - system.cache
   - core.cron
+  - search.overview
 ---
 {% set extend_url = render_var(url('system.modules_list')) %}
 {% set help_url = render_var(url('help.main')) %}

core/modules/help_topics/help_topics/search.configuring.html.twig

+---
+label: 'Configuring search pages'
+related:
+  - search.overview
+  - search.index
+---
+{% set search_settings = render_var(url('entity.search_page.collection')) %}
+{% set index_topic = render_var(url('help.help_topic', {'id': 'search.index'})) %}
+<h2>{% trans %}Goal{% endtrans %}</h2>
+<p>{% trans %}Configure one or more search pages.{% endtrans %}</p>
+<h2>{% trans %}Steps{% endtrans %}</h2>
+<ol>
+  <li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Search and Metadata</em> &gt; <a href="{{ search_settings }}"><em>Search pages</em></a>.{% endtrans %}</li>
+  <li>{% trans %}Scroll down to the <em>Search pages</em> section. You will see a list of the already-configured search pages on your site.{% endtrans %}</li>
+  <li>{% trans %}To configure an existing search page, click <em>Edit</em>. Or, to add a new search page, select the <em>Search page type</em> and click <em>Add search page</em>.{% endtrans %}</li>
+  <li>{% trans %}Enter the desired <em>Label</em> name and URL <em>Path</em> for the search page.{% endtrans %}</li>
+  <li>{% trans %}For <em>Content</em> search pages, select the desired level of influence in ranking search results of the available <em>Content ranking</em> factors.{% endtrans %}</li>
+  <li>{% trans %}Click <em>Save</em>. You will be returned to the <em>Search pages</em> page.{% endtrans %}</li>
+  <li>{% trans %}Verify that the correct search page is listed as <em>Default</em> in the <em>Status</em> column. If not, click <em>Set as default</em> in the <em>Operations</em> list for the correct search page.{% endtrans %}</li>
+  <li>{% trans %}Optionally, disable or delete any search pages that you do not want to have available on the site (disabling is temporary, while deleting is permanent).{% endtrans %}</li>
+  <li>{% trans %}Follow the steps in <a href="{{ index_topic }}">Managing the search index</a> to make sure that the search index is updated.{% endtrans %}</li>
+</ol>

core/modules/help_topics/help_topics/search.index.html.twig

+---
+label: 'Managing the search index'
+related:
+  - search.overview
+  - search.configuring
+---
+{% set cron_topic = render_var(url('help.help_topic', {'id': 'core.cron'})) %}
+{% set search_settings = render_var(url('entity.search_page.collection')) %}
+<h2>{% trans %}Goal{% endtrans %}</h2>
+<p>{% trans %}Manage the search index, and make sure that the site is fully indexed for searching.{% endtrans %}</p>
+<h2>{% trans %}What is the search index?{% endtrans %}</h2>
+<p>{% trans %}The <em>Content</em> and <em>Help</em> search types provided by the core software pre-index their content and store the results in several database tables that are collectively called the <em>search index</em>. The process of indexing renders the content and breaks it up into words, which can then be matched more efficiently with keyword queries when users perform searches. Search indexing happens during cron runs; see <a href="{{ cron_topic }}">Running and configuring cron</a> for more information about cron.{% endtrans %}</p>
+<h2>{% trans %}Steps{% endtrans %}</h2>
+<ol>
+<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Search and Metadata</em> &gt; <a href="{{ search_settings }}"><em>Search pages</em></a>.{% endtrans %}</li>
+<li>{% trans %}Under <em>Indexing throttle</em>, select the <em>Number of items to index per cron run</em>. A smaller number will make cron faster and reduce the possibility of timeout; a larger number will make sure more of your site is indexed in fewer cron runs.{% endtrans %}</li>
+<li>{% trans %}Under <em>Default indexing settings</em>, enter the desired <em>Minimum word length to index</em>. Words smaller than this length will be dropped from both keywords when searching and content when indexing.{% endtrans %}</li>
+<li>{% trans %}If your site uses Chinese, Japanese, or Korean languages, optionally check <em>Simple CJK handling</em> under <em>Default indexing settings</em> to provide some support for these languages.{% endtrans %}</li>
+<li>{% trans %}Click <em>Save configuration</em>, and you should be returned to the <em>Search pages</em> page.{% endtrans %}</li>
+<li>{% trans %}Click <em>Re-index site</em> if you have changed the indexing configuration, or later on, if you believe that the search index has been corrupted.{% endtrans %}</li>
+<li>{% trans %}Follow the steps in <a href="{{ cron_topic }}">Running and configuring cron</a> to make sure a cron task has been configured.{% endtrans %}</li>
+<li>{% trans %}After waiting for cron to run several times, verify that the content has been fully indexed for searching. The overall status is listed under <em>Indexing progress</em>, and the status for each search page is shown in the <em>Indexing progress</em> column of the <em>Search pages</em> section.{% endtrans %}</li>
+</ol>

core/modules/help_topics/help_topics/search.overview.html.twig

+---
+label: 'Configuring site search'
+top_level: true
+related:
+  - user.permissions
+  - block.place
+---
+{% set search_url = render_var(url('search.view')) %}
+{% set user_topic = render_var(url('help.help_topic', {'id': 'user.overview'})) %}
+<h2>{% trans %}What are search pages?{% endtrans %}</h2>
+<p>{% trans %}The core Search module organizes site search into <em>pages</em>. Each page allows users to search a particular type of content with a particular configuration. The configuration includes specifying a URL that starts with <em>search</em>, a name for the page, and additional options for some search page types.{% endtrans %}</p>
+<p>{% trans %}When users visit the main <a href={{ search_url }}>Search page</a>, they will see the configured search pages that they have access to. Each search page has a search form on it, and the page will display search results after the user enters keywords into the form and clicks the search button.{% endtrans %}</p>
+<h2>{% trans %}What modules provide site search?{% endtrans %}</h2>
+<p>{% trans %}The core Search module provides the ability to configure search pages; search page types are provided by both core and contributed modules. The core modules that provide search page types are:{% endtrans %}</p>
+<ul>
+  <li>{% trans %}The Node module, for searching content pages{% endtrans %}</li>
+  <li>{% trans %}The User module, for searching user profiles{% endtrans %}</li>
+  <li>{% trans %}The Help module, for searching help topics{% endtrans %}</li>
+</ul>
+<p>{% trans %}As an alternative to the core Search module's system of search pages, you can use contributed modules to provide site search. For example, the <a href="https://www.drupal.org/project/apachesolr">Apache Solr</a> and <a href="https://www.drupal.org/project/sphinx">Sphinx</a> contributed modules use third-party technology to provide site search.{% endtrans %}</p>
+<h2>{% trans %}What are the limitations of the core Search module?{% endtrans %}</h2>
+<p>{% trans %}There are two main limitations of the core Search module. First, it is not appropriate for very large sites -- if you have a large site, look into other search technologies like Apache Solr. Second, the Node search page type only supports exact keyword matching, which is not the behavior that most users will expect. You can improve this by installing a language-specific stemming module for your language (such as <a href="https://www.drupal.org/project/porterstemmer">Porter Stemmer</a> for American English), which makes it so that, for example, a search for the word walk would match pages containing the words walk, walking, and walked.{% endtrans %}</p>
+<h2>{% trans %}What are the search permissions?{% endtrans %}</h2>
+<ul>
+<li>{% trans %}Users with <em>Use search</em> permission can use the <em>Search form</em> block and <em>Search</em> page; this permission is required for any search configured in the core Search module.{% endtrans %}</li>
+<li>{% trans %}In addition to <em>Use search</em>, <em>View user information</em> permission is needed for searching users.{% endtrans %}</li>
+<li>{% trans %}In addition to <em>Use search</em>, <em>View published content</em> permission is needed for searching content.{% endtrans %}</li>
+<li>{% trans %}Users with <em>Use advanced search</em> permission can use more complex search filtering when performing content searches.{% endtrans %}</li>
+</ul>
+<h2>{% trans %}Configuring site search overview{% endtrans %}</h2>
+<p>{% trans %}In order to configure site search using the core Search module, you will need to configure one or more search pages. You will also need to verify or alter permissions so that the desired user roles can search the site (see <a href="{{ user_topic }}">Managing user accounts and site visitors</a> for more information about roles and permissions). For content search, you will also need to make sure that the search index is configured and that the site is fully indexed. Finally, you may wish to place the <em>Search form</em> block on pages of your site, or add the search page to a navigation menu, to give users easy access to search. See the related topics listed below for specific tasks.{% endtrans %}</p>
+<h2>{% trans %}Additional resources{% endtrans %}</h2>
+<ul>
+  <li>{% trans %}<a href="https://www.drupal.org/documentation/modules/search">Online documentation for the Search module</a>{% endtrans %}</li>
+</ul>