@@ -25,14 +25,14 @@ function book_help($route_name, RouteMatchInterface $route_match) {
switch($route_name){
case'help.page.book':
$output='<h3>'.t('About').'</h3>';
$output.='<p>'.t('The Book module is used for creating structured, multi-page content, such as site resource guides, manuals, and wikis. It allows you to create content that has chapters, sections, subsections, or any similarly-tiered structure. Enabling the module creates a new content type <em>Book page</em>. For more information, see the <a href=":book">online documentation for the Book module</a>.',[':book'=>'https://www.drupal.org/documentation/modules/book']).'</p>';
$output.='<p>'.t('The Book module is used for creating structured, multi-page content, such as site resource guides, manuals, and wikis. It allows you to create content that has chapters, sections, subsections, or any similarly-tiered structure. Installing the module creates a new content type <em>Book page</em>. For more information, see the <a href=":book">online documentation for the Book module</a>.',[':book'=>'https://www.drupal.org/documentation/modules/book']).'</p>';
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Adding and managing book content').'</dt>';
$output.='<dd>'.t('Books have a hierarchical structure, called a <em>book outline</em>. Each book outline can have nested pages up to nine levels deep. Multiple content types can be configured to behave as a book outline. From the content edit form, it is possible to add a page to a book outline or create a new book.').'</dd>';
$output.='<dd>'.t('You can assign separate permissions for <em>creating new books</em> as well as <em>creating</em>, <em>editing</em> and <em>deleting</em> book content. Users with the <em>Administer book outlines</em> permission can add <em>any</em> type of content to a book by selecting the appropriate book outline while editing the content. They can also view a list of all books, and edit and rearrange section titles on the <a href=":admin-book">Book list page</a>.',[':admin-book'=>Url::fromRoute('book.admin')->toString()]).'</dd>';
$output.='<dt>'.t('Configuring content types for books').'</dt>';
$output.='<dd>'.t('The <em>Book page</em> content type is the initial content type enabled for book outlines. On the <a href=":admin-settings">Book settings page</a> you can configure content types that can used in book outlines.',[':admin-settings'=>Url::fromRoute('book.settings')->toString()]).'</dd>';
$output.='<dd>'.t('The <em>Book page</em> content type is the initial content type installed for book outlines. On the <a href=":admin-settings">Book settings page</a> you can configure content types that can used in book outlines.',[':admin-settings'=>Url::fromRoute('book.settings')->toString()]).'</dd>';
$output.='<dd>'.t('Users with the <em>Add content and child pages to books</em> permission will see a link to <em>Add child page</em> when viewing a content item that is part of a book outline. This link will allow users to create a new content item of the content type you select on the <a href=":admin-settings">Book settings page</a>. By default this is the <em>Book page</em> content type.',[':admin-settings'=>Url::fromRoute('book.settings')->toString()]).'</dd>';
$output.='<dt>'.t('Book navigation').'</dt>';
$output.='<dd>'.t("Book pages have a default book-specific navigation block. This navigation block contains links that lead to the previous and next pages in the book, and to the level above the current page in the book's structure. This block can be enabled on the <a href=':admin-block'>Blocks layout page</a>. For book pages to show up in the book navigation, they must be added to a book outline.",[':admin-block'=>(\Drupal::moduleHandler()->moduleExists('block'))?Url::fromRoute('block.admin_display')->toString():'#']).'</dd>';
@@ -38,7 +38,7 @@ function ckeditor5_help($route_name, RouteMatchInterface $route_match) {
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Enabling CKEditor 5 for individual text formats').'</dt>';
$output.='<dd>'.t('CKEditor 5 has to be enabled and configured separately for individual text formats from the <a href=":formats">Text formats and editors page</a> because the filter settings for each text format can be different. For more information, see the <a href=":text_editor">Text Editor help page</a> and <a href=":filter">Filter help page</a>.',[':formats'=>Url::fromRoute('filter.admin_overview')->toString(),':text_editor'=>Url::fromRoute('help.page',['name'=>'editor'])->toString(),':filter'=>Url::fromRoute('help.page',['name'=>'filter'])->toString()]).'</dd>';
$output.='<dd>'.t('CKEditor 5 has to be installed and configured separately for individual text formats from the <a href=":formats">Text formats and editors page</a> because the filter settings for each text format can be different. For more information, see the <a href=":text_editor">Text Editor help page</a> and <a href=":filter">Filter help page</a>.',[':formats'=>Url::fromRoute('filter.admin_overview')->toString(),':text_editor'=>Url::fromRoute('help.page',['name'=>'editor'])->toString(),':filter'=>Url::fromRoute('help.page',['name'=>'filter'])->toString()]).'</dd>';
$output.='<dt>'.t('Configuring the toolbar').'</dt>';
$output.='<dd>'.t('When CKEditor 5 is chosen from the <em>Text editor</em> drop-down menu, its toolbar configuration is displayed. You can add and remove buttons from the <em>Active toolbar</em> by dragging and dropping them. Separators and rows can be added to organize the buttons.').'</dd>';
$output.='<dt>'.t('Filtering HTML content').'</dt>';
@@ -51,9 +51,9 @@ function comment_help($route_name, RouteMatchInterface $route_match) {
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Enabling commenting').'</dt>';
$output.='<dd>'.t('Comment functionality can be enabled for any entity sub-type (for example, a <a href=":content-type">content type</a>) by adding a <em>Comments</em> field on its <em>Manage fields page</em>. Adding or removing commenting for an entity through the user interface requires the <a href=":field_ui">Field UI</a> module to be enabled, even though the commenting functionality works without it. For more information on fields and entities, see the <a href=":field">Field module help page</a>.',[':content-type'=>(\Drupal::moduleHandler()->moduleExists('node'))?Url::fromRoute('entity.node_type.collection')->toString():'#',':field'=>Url::fromRoute('help.page',['name'=>'field'])->toString(),':field_ui'=>(\Drupal::moduleHandler()->moduleExists('field_ui'))?Url::fromRoute('help.page',['name'=>'field_ui'])->toString():'#']).'</dd>';
$output.='<dd>'.t('Comment functionality can be enabled for any entity sub-type (for example, a <a href=":content-type">content type</a>) by adding a <em>Comments</em> field on its <em>Manage fields page</em>. Adding or removing commenting for an entity through the user interface requires the <a href=":field_ui">Field UI</a> module to be installed, even though the commenting functionality works without it. For more information on fields and entities, see the <a href=":field">Field module help page</a>.',[':content-type'=>(\Drupal::moduleHandler()->moduleExists('node'))?Url::fromRoute('entity.node_type.collection')->toString():'#',':field'=>Url::fromRoute('help.page',['name'=>'field'])->toString(),':field_ui'=>(\Drupal::moduleHandler()->moduleExists('field_ui'))?Url::fromRoute('help.page',['name'=>'field_ui'])->toString():'#']).'</dd>';
$output.='<dd>'.t('Commenting settings can be configured by editing the <em>Comments</em> field on the <em>Manage fields page</em> of an entity type if the <em>Field UI module</em> is enabled. Configuration includes the label of the comments field, the number of comments to be displayed, and whether they are shown in threaded list. Commenting can be configured as: <em>Open</em> to allow new comments, <em>Closed</em> to view existing comments, but prevent new comments, or <em>Hidden</em> to hide existing comments and prevent new comments. Changing this configuration for an entity type will not change existing entity items.').'</dd>';
$output.='<dd>'.t('Commenting settings can be configured by editing the <em>Comments</em> field on the <em>Manage fields page</em> of an entity type if the <em>Field UI module</em> is installed. Configuration includes the label of the comments field, the number of comments to be displayed, and whether they are shown in threaded list. Commenting can be configured as: <em>Open</em> to allow new comments, <em>Closed</em> to view existing comments, but prevent new comments, or <em>Hidden</em> to hide existing comments and prevent new comments. Changing this configuration for an entity type will not change existing entity items.').'</dd>';
$output.='<dd>'.t('Users with the appropriate permissions can override the default commenting settings of an entity type when they create an item of that type.').'</dd>';
$output.='<li>'.t('Hovering over the area of interest will temporarily make the contextual links button visible (which looks like a pencil in most themes, and is normally displayed in the upper right corner of the area). The icon typically looks like this: @picture',['@picture'=>$sample_picture]).'</li>';
$output.='<li>'.t('If you have the <a href=":toolbar">Toolbar module</a> enabled, clicking the contextual links button in the toolbar (which looks like a pencil) will make all contextual links buttons on the page visible. Clicking this button again will toggle them to invisible.',[':toolbar'=>(\Drupal::moduleHandler()->moduleExists('toolbar'))?Url::fromRoute('help.page',['name'=>'toolbar'])->toString():'#']).'</li>';
$output.='<li>'.t('If you have the <a href=":toolbar">Toolbar module</a> installed, clicking the contextual links button in the toolbar (which looks like a pencil) will make all contextual links buttons on the page visible. Clicking this button again will toggle them to invisible.',[':toolbar'=>(\Drupal::moduleHandler()->moduleExists('toolbar'))?Url::fromRoute('help.page',['name'=>'toolbar'])->toString():'#']).'</li>';
$output.='</ol>';
$output.=t('Once the contextual links button for the area of interest is visible, click the button to display the links.');
@@ -89,7 +89,7 @@ function field_help($route_name, RouteMatchInterface $route_match) {
$output.='<h3>'.t('Uses').'</h3>';
$output.='<dl>';
$output.='<dt>'.t('Enabling field types, widgets, and formatters').'</dt>';
$output.='<dd>'.t('The Field module provides the infrastructure for fields; the field types, formatters, and widgets are provided by Drupal core or additional modules. Some of the modules are required; the optional modules can be enabled from the <a href=":modules">Extend administration page</a>. Additional fields, formatters, and widgets may be provided by contributed modules, which you can find in the <a href=":contrib">contributed module section of Drupal.org</a>.',[':modules'=>Url::fromRoute('system.modules_list')->toString(),':contrib'=>'https://www.drupal.org/project/modules']).'</dd>';
$output.='<dd>'.t('The Field module provides the infrastructure for fields; the field types, formatters, and widgets are provided by Drupal core or additional modules. Some of the modules are required; the optional modules can be installed from the <a href=":modules">Extend administration page</a>. Additional fields, formatters, and widgets may be provided by contributed modules, which you can find in the <a href=":contrib">contributed module section of Drupal.org</a>.',[':modules'=>Url::fromRoute('system.modules_list')->toString(),':contrib'=>'https://www.drupal.org/project/modules']).'</dd>';
$output.='<h3>'.t('Field, widget, and formatter information').'</h3>';
@@ -122,7 +122,7 @@ function field_help($route_name, RouteMatchInterface $route_match) {
}
if($items){
$output.='<dt>'.t('Provided by modules').'</dt>';
$output.='<dd>'.t('Here is a list of the currently enabled field, formatter, and widget modules:');
$output.='<dd>'.t('Here is a list of the currently installed field, formatter, and widget modules:');