diff --git a/core/modules/help_topics/help_topics/aggregator.overview.html.twig b/core/modules/help_topics/help_topics/aggregator.overview.html.twig
index 62ae608deeaa352861f704f8cd9625dde6a7cf4d..8952662cf1d14b3592b8391f188ee8603fca1aa3 100644
--- a/core/modules/help_topics/help_topics/aggregator.overview.html.twig
+++ b/core/modules/help_topics/help_topics/aggregator.overview.html.twig
@@ -4,18 +4,18 @@ top_level: true
related:
- block.place
---
-{% set create_topic = render_var(url('help.help_topic', {'id': 'aggregator.creating'})) %}
-{% set config_topic = render_var(url('help.help_topic', {'id': 'aggregator.managing'})) %}
+{% set creating_topic = render_var(help_topic_link('aggregator.creating')) %}
+{% set managing_topic = render_var(help_topic_link('aggregator.managing')) %}
<h2>{% trans %}What is a feed?{% endtrans %}</h2>
<p>{% trans %}A feed is syndicated content data provided by a source outside of your website, which is imported into your website.{% endtrans %}</p>
<h2>{% trans %}What is OPML?{% endtrans %}</h2>
<p>{% trans %}OPML (Outline Processor Markup Language) is a specification for making hierarchical lists, which is commonly used for lists of feeds.{% endtrans %}</p>
<h2>{% trans %}What are the options for updating feed items?{% endtrans %}</h2>
-<p>{% trans %}Feeds are <em>updated</em> (new items imported) each time your site's cron task runs, if the selected <em>Update interval</em> for the feed has passed. You can also update feeds manually; see <a href="{{ config_topic }}">Managing and configuring an existing feed</a> for details.{% endtrans %}</p>
+<p>{% trans %}Feeds are <em>updated</em> (new items imported) each time your site's cron task runs, if the selected <em>Update interval</em> for the feed has passed. You can also update feeds manually; see {{ managing_topic }} for details.{% endtrans %}</p>
<h2>{% trans %}What are the options for displaying feeds?{% endtrans %}</h2>
<p>{% trans %}Using the core Aggregator, Views, Views UI, and Block modules, you can display feed data in your site in various ways (see related topics for more information):{% endtrans %}</p>
<ul>
- <li>{% trans %}After creating and updating a feed, view the feed page provided by the core Aggregator module, which displays recent imported items; see <a href="{{ create_topic }}">Creating a feed</a> for details.{% endtrans %}</li>
+ <li>{% trans %}After creating and updating a feed, view the feed page provided by the core Aggregator module, which displays recent imported items; see {{ creating_topic }} for details.{% endtrans %}</li>
<li>{% trans %}Place the <em>Aggregator feed</em> block in a region of your theme; each block you place lists the most recent items from one feed.{% endtrans %}</li>
<li>{% trans %}Create a custom view that shows either <em>Aggregator feed</em> (feeds) or <em>Aggregator feed item</em> (items from feeds).{% endtrans %}</li>
</ul>
diff --git a/core/modules/help_topics/help_topics/book.about.html.twig b/core/modules/help_topics/help_topics/book.about.html.twig
index 86e9b3ca2f8d2df162fc01cf5cff1adae58d762f..58c6d7ef0b87f703e08ffd867b936428b5abc038 100644
--- a/core/modules/help_topics/help_topics/book.about.html.twig
+++ b/core/modules/help_topics/help_topics/book.about.html.twig
@@ -2,11 +2,11 @@
label: 'Managing books'
top_level: true
---
-{% set user_topic = render_var(url('help.help_topic', {'id': 'user.overview'})) %}
+{% set user_overview_topic = render_var(help_topic_link('user.overview')) %}
<h2>{% trans %}What is a book?{% endtrans %}</h2>
<p>{% trans %}A book is a structured group of content pages, arranged in a hierarchical structure called a <em>book outline</em>. A book hierarchy can be up to nine levels deep, and a book can include <em>Book page</em> content items or other content items. Every book has a default book-specific navigation block, which 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.{% endtrans %}</p>
<h2>{% trans %}What are the permissions for books?{% endtrans %}</h2>
-<p>{% trans %}The following permissions are needed to create and manage books; see <a href="{{ user_topic }}">Managing user accounts and site visitors</a> and its related topics for more about permissions.{% endtrans %}</p>
+<p>{% trans %}The following permissions are needed to create and manage books; see {{ user_overview_topic }} and its related topics for more about permissions.{% endtrans %}</p>
<dl>
<dt>{% trans %}Create new books{% endtrans %}</dt>
<dd>{% trans %}Allows users to add new books to the site.{% endtrans %}</dd>
diff --git a/core/modules/help_topics/help_topics/book.adding.html.twig b/core/modules/help_topics/help_topics/book.adding.html.twig
index 8100782d9bfdc031e7f94ed8f24b3781d77e9583..84e17b6ddbcbb2aa6bb3a23dea08888d65594e05 100644
--- a/core/modules/help_topics/help_topics/book.adding.html.twig
+++ b/core/modules/help_topics/help_topics/book.adding.html.twig
@@ -7,12 +7,12 @@ related:
- book.organizing
---
{% set node_add = render_var(url('node.add_page')) %}
-{% set config = render_var(url('help.help_topic', {'id': 'book.configuring'})) %}
+{% set configuring_topic = render_var(help_topic_link('book.configuring')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Add a page to an existing book.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
- <li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Content</em> > <a href="{{ node_add }}"><em>Add content</em></a> > <em>Book page</em>. If you have configured additional content types that can be added to books, you can substitute a different content type for <em>Book page</em> (see the <a href="{{ config }}">Configuring books</a> topic for more information).{% endtrans %}</li>
+ <li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Content</em> > <a href="{{ node_add }}"><em>Add content</em></a> > <em>Book page</em>. If you have configured additional content types that can be added to books, you can substitute a different content type for <em>Book page</em>; see {{ configuring_topic }} for more information.{% endtrans %}</li>
<li>{% trans %}Enter a title for the page and some text for the body of the page.{% endtrans %}</li>
<li>{% trans %}In the vertical tabs area, click <em>Book Outline</em>. Select the book you want to add the page to in the <em>Book</em> select list. If you want to insert this page into the book hierarchy, also select the desired parent page in the <em>Parent item</em> select list.{% endtrans %}</li>
<li>{% trans %}Select the desired weight for the page in the <em>Weight</em> select list (pages with the same parent item are ordered from lowest to highest weight).{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/config.export_full.html.twig b/core/modules/help_topics/help_topics/config.export_full.html.twig
index 03213128e17fe56aaa7ab42cebb5e88e92f3f62a..cc8f0b772d146bc5a9d20c0670e7e67c1f5ea0a6 100644
--- a/core/modules/help_topics/help_topics/config.export_full.html.twig
+++ b/core/modules/help_topics/help_topics/config.export_full.html.twig
@@ -7,9 +7,9 @@ related:
- config.import_single
---
{% set export = render_var(url('config.export_full')) %}
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Create and download an archive containing all your site's configuration, exported as YAML files. See <a href="{{ config_overview }}">Managing and deploying configuration</a> for more information about configuration.{% endtrans %}</p>
+<p>{% trans %}Create and download an archive containing all your site's configuration, exported as YAML files. See {{ config_overview_topic }} for more information about configuration.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>Configuration synchronization</em> > <a href="{{ export }}"><em>Export</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/config.export_single.html.twig b/core/modules/help_topics/help_topics/config.export_single.html.twig
index 8a1cf57f3b280dfaedd8af5a091206df3ab3fa9a..290197a3c88d6eecb5b2ae1de04ea52a3dc93d26 100644
--- a/core/modules/help_topics/help_topics/config.export_single.html.twig
+++ b/core/modules/help_topics/help_topics/config.export_single.html.twig
@@ -7,9 +7,9 @@ related:
- config.import_single
---
{% set single_export = render_var(url('config.export_single')) %}
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Export a single configuration item to a file. See <a href="{{ config_overview }}">Managing and deploying configuration</a> for more information about configuration.{% endtrans %}</p>
+<p>{% trans %}Export a single configuration item to a file. See {{ config_overview_topic }} for more information about configuration.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>Configuration synchronization</em> > <em>Export</em> > <em><a href="{{ single_export }}">Single item</a></em>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/config.import_full.html.twig b/core/modules/help_topics/help_topics/config.import_full.html.twig
index a083d79dd2b6501cf27a87098401c3d003fd9e02..302de56db290052a1efec2a5641e157ebce0af80 100644
--- a/core/modules/help_topics/help_topics/config.import_full.html.twig
+++ b/core/modules/help_topics/help_topics/config.import_full.html.twig
@@ -7,10 +7,10 @@ related:
- config.export_single
---
{% set import_page = render_var(url('config.import_full')) %}
-{% set export_full = render_var(url('help.help_topic', {'id': 'config.export_full'})) %}
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
+{% set export_full_topic = render_var(help_topic_link('config.export_full')) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Import the complete configuration of your site from an archive file, such as one that was previously exported (see <a href="{{ export_full }}">Exporting your complete site configuration</a>). See <a href="{{ config_overview }}">Managing and deploying configuration</a> for more information about configuration.{% endtrans %}</p>
+<p>{% trans %}Import the complete configuration of your site from an archive file, such as one that was previously exported (see {{ export_full_topic }}). See {{ config_overview_topic }} for more information about configuration.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>Configuration synchronization</em> > <em><a href="{{ import_page }}">Import</a></em>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/config.import_single.html.twig b/core/modules/help_topics/help_topics/config.import_single.html.twig
index c1e40fe58d74205fe8c0876fc62a856c11c79dd2..0593963c86204ba84801ec647524151f16c56150 100644
--- a/core/modules/help_topics/help_topics/config.import_single.html.twig
+++ b/core/modules/help_topics/help_topics/config.import_single.html.twig
@@ -7,10 +7,10 @@ related:
- config.export_single
---
{% set single_import = render_var(url('config.import_single')) %}
-{% set single_export = render_var(url('help.help_topic', {'id': 'config.export_single'})) %}
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
+{% set export_single_topic = render_var(help_topic_link('config.export_single')) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Import a single configuration item in YAML format, such as one that was previously exported (see <a href="{{ single_export }}">Exporting a single configuration item</a>). See <a href="{{ config_overview }}">Managing and deploying configuration</a> for more information about configuration.{% endtrans %}</p>
+<p>{% trans %}Import a single configuration item in YAML format, such as one that was previously exported (see {{ export_single_topic }}). See {{ config_overview_topic }} for more information about configuration.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em>Configuration synchronization</em> > <em>Import</em> > <a href="{{ single_import }}"><em>Single item</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/config_translation.overview.html.twig b/core/modules/help_topics/help_topics/config_translation.overview.html.twig
index 687951a1c78c0a389744628fcdb5ed15f677b88b..1d899e1e47fad639eaf6c4fa86f21d0fb4554e50 100644
--- a/core/modules/help_topics/help_topics/config_translation.overview.html.twig
+++ b/core/modules/help_topics/help_topics/config_translation.overview.html.twig
@@ -6,14 +6,14 @@ related:
- language.add
---
{% set config_translation = render_var(url('config_translation.mapper_list'))%}
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
-{% set language_add = render_var(url('help.help_topic', {'id': 'language.add'})) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
+{% set language_add_topic = render_var(help_topic_link('language.add')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Translate your site configuration to another language. See <a href="{{ language_add }}">Adding a language</a> if you need to add a new language.{% endtrans %}</p>
+<p>{% trans %}Translate your site configuration to another language. See {{ language_add_topic }} if you need to add a new language.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Regional and language</em> > <a href="{{ config_translation }}"><em>Configuration translation</em></a>.{% endtrans %}</li>
- <li>{% trans %}Find either the configuration entity type or the simple configuration item that you want to translate in the <em>Label</em> column of the list. Click <em>List</em> under <em>Operations</em> for a configuration entity, or <em>Translate</em> for simple configuration. (See <a href="{{ config_overview }}">Managing and deploying configuration</a> to learn more about types of configuration and configuration entities.){% endtrans %}</li>
+ <li>{% trans %}Find either the configuration entity type or the simple configuration item that you want to translate in the <em>Label</em> column of the list. Click <em>List</em> under <em>Operations</em> for a configuration entity, or <em>Translate</em> for simple configuration. (See {{ config_overview_topic }} to learn more about types of configuration and configuration entities.){% endtrans %}</li>
<li>{% trans %}For configuration entities, find the specific entity that you want to translate on the next page, and click <em>Translate</em> under <em>Operations</em>.{% endtrans %}</li>
<li>{% trans %}Enter translations for the translatable text fields for the configuration item, and save.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/contact.configuring_personal.html.twig b/core/modules/help_topics/help_topics/contact.configuring_personal.html.twig
index 252ab27492bcbc538a5f12c6fe86096829c3c8bf..34d5f3ab471c006546f6f3b91c381690b844a415 100644
--- a/core/modules/help_topics/help_topics/contact.configuring_personal.html.twig
+++ b/core/modules/help_topics/help_topics/contact.configuring_personal.html.twig
@@ -6,7 +6,7 @@ related:
---
{% set config_url = render_var(url('entity.user.admin_form')) %}
{% set permission_url = render_var(url('user.admin_permissions')) %}
-{% set add_fields = render_var(url('help.help_topic', {'id': 'contact.adding_fields'})) %}
+{% set adding_fields_topic = render_var(help_topic_link('contact.adding_fields')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Configure personal contact forms for registered users on the website.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -17,5 +17,5 @@ related:
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>People</em> > <a href="{{ permission_url }}"><em>Permissions</em></a>.{% endtrans %}</li>
<li>{% trans %}Verify that permissions are correct for your site's roles, including the generic <em>Anonymous user</em> and <em>Authenticated user</em>. In order to use personal contact forms, users need both <em>View user information</em> (in the <em>User</em> section, which enables them to view user profiles) and <em>Use users' personal contact forms</em> (in the <em>Contact</em> section, which enables them to use contact forms if they can view user profiles).{% endtrans %}</li>
<li>{% trans %}Click <em>Save permissions</em>.{% endtrans %}</li>
- <li>{% trans %}The contact form will always have <em>Subject</em> and <em>Message</em> fields. If you want to add more fields, follow the steps in <a href="{{ add_fields }}">Managing the fields of contact forms</a>.{% endtrans %}</li>
+ <li>{% trans %}The contact form will always have <em>Subject</em> and <em>Message</em> fields. If you want to add more fields, follow the steps in {{ adding_fields_topic }}.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/contact.creating.html.twig b/core/modules/help_topics/help_topics/contact.creating.html.twig
index b837b4fc988976fa2ae90df567a8aca8ff879856..e4e990d256efc38f8b959dfd5361614b704718dd 100644
--- a/core/modules/help_topics/help_topics/contact.creating.html.twig
+++ b/core/modules/help_topics/help_topics/contact.creating.html.twig
@@ -6,7 +6,7 @@ related:
- contact.setting_default
---
{% set contact_url = render_var(url('entity.contact_form.collection')) %}
-{% set add_fields = render_var(url('help.help_topic', {'id': 'contact.adding_fields'})) %}
+{% set adding_fields_topic = render_var(help_topic_link('contact.adding_fields')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Create a new site-wide contact form.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -15,5 +15,5 @@ related:
<li>{% trans %}Click <em>Add contact form</em>.{% endtrans %}</li>
<li>{% trans %}Fill in the <em>Label</em> (title) for the form, <em>Recipients</em>, and optionally the other settings.{% endtrans %}</li>
<li>{% trans %}Click <em>Save</em>. You should see your new contact form in the table, along with a link to view it.{% endtrans %}</li>
- <li>{% trans %}The contact form will always have <em>Subject</em> and <em>Message</em> fields. If you want to add more fields, follow the steps in <a href="{{ add_fields }}">Managing the fields of contact forms</a>.{% endtrans %}</li>
+ <li>{% trans %}The contact form will always have <em>Subject</em> and <em>Message</em> fields. If you want to add more fields, follow the steps in {{ adding_fields_topic }}.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/content_moderation.changing_states.html.twig b/core/modules/help_topics/help_topics/content_moderation.changing_states.html.twig
index c368225f54fa0b0443f1118662a0a79d26ce34a5..d8dcc03df378226069671f8fd7b3c84569c8b543 100644
--- a/core/modules/help_topics/help_topics/content_moderation.changing_states.html.twig
+++ b/core/modules/help_topics/help_topics/content_moderation.changing_states.html.twig
@@ -5,12 +5,12 @@ related:
- content_moderation.configuring_workflows
- core.content_structure
---
-{% set workflow_topic = render_var(url('help.help_topic', {'id': 'workflows.overview'})) %}
-{% set entity_topic = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set workflows_overview_topic = render_var(help_topic_link('workflows.overview')) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
{% set content_moderation_permissions = render_var(url('user.admin_permissions', {}, {'fragment': 'module-content_moderation'})) %}
{% set content = render_var(url('system.admin_content')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Change the workflow state of a particular entity. See <a href="{{ workflow_topic }}">Managing content moderation workflows</a> for an overview of workflows, and <a href="{{ entity_topic }}">Managing content structure</a> for an overview of content entities.{% endtrans %}</p>
+<p>{% trans %}Change the workflow state of a particular entity. See {{ workflows_overview_topic }} for an overview of workflows, and {{ content_structure_topic }} for an overview of content entities.{% endtrans %}</p>
<h2>{% trans %}Who can change workflow states?{% endtrans %}</h2>
<p>{% trans %}Users with the <a href="{{ content_moderation_permissions }}">content moderation permissions</a> can change workflow states. There are separate permissions for each transition.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
diff --git a/core/modules/help_topics/help_topics/content_moderation.configuring_workflows.html.twig b/core/modules/help_topics/help_topics/content_moderation.configuring_workflows.html.twig
index 881630a59b966539022fc715abb0ffd6c0f6c2d9..35f3bce72f44220dab6b85a7d5131a8229c34566 100644
--- a/core/modules/help_topics/help_topics/content_moderation.configuring_workflows.html.twig
+++ b/core/modules/help_topics/help_topics/content_moderation.configuring_workflows.html.twig
@@ -6,15 +6,15 @@ related:
- core.content_structure
- views_ui.create
---
-{% set entities_topic = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
-{% set user_topic = render_var(url('help.help_topic', {'id': 'user.overview'})) %}
-{% set permissions_topic = render_var(url('help.help_topic', {'id': 'user.permissions'})) %}
-{% set workflows_overview = render_var(url('help.help_topic', {'id': 'workflows.overview'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
+{% set user_overview_topic = render_var(help_topic_link('user.overview')) %}
+{% set user_permissions_topic = render_var(help_topic_link('user.permissions')) %}
+{% set workflows_overview_topic = render_var(help_topic_link('workflows.overview')) %}
{% set content_moderation_permissions = render_var(url('user.admin_permissions', {}, {'fragment': 'module-content_moderation'})) %}
{% set workflows_permissions = render_var(url('user.admin_permissions', {}, {'fragment': 'module-workflows'})) %}
{% set workflows_url = render_var(url('entity.workflow.collection')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Create or edit a workflow with various workflow states (for example <em>Concept</em>, <em>Archived</em>, etc.) for moderating content. See <a href="{{ workflows_overview }}">Content moderation workflows</a> for more information on workflows.{% endtrans %}</p>
+<p>{% trans %}Create or edit a workflow with various workflow states (for example <em>Concept</em>, <em>Archived</em>, etc.) for moderating content. See {{ workflows_overview_topic }} for more information on workflows.{% endtrans %}</p>
<h2>{% trans %}Who can configure a workflow?{% endtrans %}</h2>
<p>{% trans %}Users with the <em><a href="{{ workflows_permissions }}">Administer workflows</a></em> permission (typically administrators) can configure workflows.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -31,8 +31,8 @@ related:
</li>
<li>{% trans %}Decide which state content should be created in.{% endtrans %}</li>
<li>{% trans %}Decide on the list of allowed transitions between states. For example, you might want a transition between <em>Concept</em> and <em>Review</em>. Each transition has a label; for example, the Concept to Review transition might be labeled "Review concept".{% endtrans %}</li>
- <li>{% trans %}Decide which roles should have permissions to make each transition; see <a href="{{ user_topic }}">Managing user accounts and site visitors</a> for an overview of roles and permissions.{% endtrans %}</li>
- <li>{% trans %}Decide which <a href="{{ entities_topic }}">entity types</a> and subtypes the workflow should apply to. Only entity types that support revisions are possible to define workflows for.{% endtrans %}</li>
+ <li>{% trans %}Decide which roles should have permissions to make each transition; see {{ user_overview_topic }} for an overview of roles and permissions.{% endtrans %}</li>
+ <li>{% trans %}Decide which <em>entity types</em> and subtypes the workflow should apply to. Only entity types that support revisions are possible to define workflows for. See {{ content_structure_topic }} for more information on content entities and fields.{% endtrans %}</li>
</ul>
</li>
<li>{% trans %}To implement your plan, in the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Workflow</em> > <a href="{{ workflows_url}}"><em>Workflows</em></a>. A list of workflows is shown, including the default workflow <em>Editorial</em> that you can adapt.{% endtrans %}</li>
@@ -45,6 +45,6 @@ related:
<li>{% trans %}Click <em>Save</em>.{% endtrans %}</li>
<li>{% trans %}Under <em>Workflow settings</em>, select the <em>Default moderation state</em> for new content.{% endtrans %}</li>
<li>{% trans %}Click <em>Save</em> to save your workflow.{% endtrans %}</li>
- <li>{% trans %}Follow the steps in <a href="{{ permissions_topic }}">Modifying the permissions for a role</a> to assign permissions for each transition to roles. The permissions are listed under the <em><a href="{{ content_moderation_permissions }}">Content Moderation</a></em> section; there is one permission for each transition in each workflow.{% endtrans %}</li>
+ <li>{% trans %}Follow the steps in {{ user_permissions_topic }} to assign permissions for each transition to roles. The permissions are listed under the <em><a href="{{ content_moderation_permissions }}">Content Moderation</a></em> section; there is one permission for each transition in each workflow.{% endtrans %}</li>
<li>{% trans %}Optionally (recommended), create a view for your custom workflow, to provide a page for content editors to see what content needs to be moderated. You can do this if the Views UI module is installed, by following the steps in the related <em>Creating a new view</em> topic listed below under <em>Related topics</em>. When creating the view, under <em>View settings</em> > <em>Show</em>, select the revision data type you configured the workflow for, and be sure to display the <em>Workflow State</em> field in your view.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/content_translation.overview.html.twig b/core/modules/help_topics/help_topics/content_translation.overview.html.twig
index ca37878143f36887502f37d081477a684b61eef6..317846d734b34fc68b787b126ea7d450c22520f9 100644
--- a/core/modules/help_topics/help_topics/content_translation.overview.html.twig
+++ b/core/modules/help_topics/help_topics/content_translation.overview.html.twig
@@ -5,9 +5,9 @@ related:
- language.add
---
{% set translation_settings = render_var(url('language.content_settings_page')) %}
-{% set entity_overview = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure language and translation settings for one or more content entity types (see <a href="{{ entity_overview }}">Managing content structure</a> for an overview of content entities). To do this, you must have at least two languages configured. Afterwards, you will have a <em>Translate</em> operation available for your content entities, either as a tab or link when you are viewing or editing content, or on content administration pages.{% endtrans %}</p>
+<p>{% trans %}Configure language and translation settings for one or more content entity types (see {{ content_structure_topic }} for an overview of content entities). To do this, you must have at least two languages configured. Afterwards, you will have a <em>Translate</em> operation available for your content entities, either as a tab or link when you are viewing or editing content, or on content administration pages.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Regional and language</em> > <a href="{{ translation_settings }}"><em>Content language and translation</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/core.appearance.html.twig b/core/modules/help_topics/help_topics/core.appearance.html.twig
index cb4711f4dba096083394e603836d06f8dd913414..4fc6d33bc6f8d3d888492c0cd5bb9f6962c8adb5 100644
--- a/core/modules/help_topics/help_topics/core.appearance.html.twig
+++ b/core/modules/help_topics/help_topics/core.appearance.html.twig
@@ -4,13 +4,13 @@ top_level: true
related:
- core.content_structure
---
-{% set entities = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}What is a theme?{% endtrans %}</h2>
<p>{% trans %}A <em>theme</em> is a set of files that define the visual look and feel of your site. The core software and modules that run on your site determine which content (including HTML text and other data stored in the database, uploaded images, and any other asset files) is displayed on the pages of your site. The theme determines the HTML markup and CSS styling that wraps the content. Several basic themes are supplied with the core software; additional <em>contributed themes</em> can be downloaded separately from the <a href="https://www.drupal.org/project/project_theme">Download & Extend page on drupal.org</a>, or you can create your own theme.{% endtrans %}</p>
<h2>{% trans %}What is a base theme?{% endtrans %}</h2>
<p>{% trans %}A base theme is a theme that is not meant to be used directly on a site, but instead acts as a scaffolding for building other themes. The core Classy theme is one example; other base themes can be downloaded from the <a href="https://www.drupal.org/project/project_theme">Download & Extend page on drupal.org</a>.{% endtrans %}</p>
<h2>{% trans %}What is a layout?{% endtrans %}</h2>
-<p>{% trans %}A <em>layout</em> is a template that defines where blocks and other pieces of content should be displayed. The core Layout Discovery module allows modules and themes to register layouts, and the core Layout Builder module provides a visual interface for placing fields and blocks in layouts for entity sub-types and individual entity items (see <a href="{{ entities }}">Managing content structure</a> for more on entities and fields).{% endtrans %}</p>
+<p>{% trans %}A <em>layout</em> is a template that defines where blocks and other pieces of content should be displayed. The core Layout Discovery module allows modules and themes to register layouts, and the core Layout Builder module provides a visual interface for placing fields and blocks in layouts for entity sub-types and individual entity items (see {{ content_structure_topic }} for more on entities and fields).{% endtrans %}</p>
<h2>{% trans %}Changing site appearance overview{% endtrans %}</h2>
<p>{% trans %}The main way to change the overall appearance of your site is to switch the default theme. You can also change the color palette of some themes, if the core Color module is installed and the theme supports it; some themes also have other settings. The core Layout Builder and Layout Discovery modules allow you to define layouts for your site's content, and the core Breakpoint module helps themes change appearance for different-sized devices. See the related topics listed below for specific tasks.{% endtrans %}</p>
<h2>{% trans %}Additional resources{% endtrans %}</h2>
diff --git a/core/modules/help_topics/help_topics/core.media.html.twig b/core/modules/help_topics/help_topics/core.media.html.twig
index f3152b51fc5a879634579cdcc7797cb00c53e5bd..aecbe9efb01663fda9048c9f623b1019b4e21983 100644
--- a/core/modules/help_topics/help_topics/core.media.html.twig
+++ b/core/modules/help_topics/help_topics/core.media.html.twig
@@ -8,9 +8,9 @@ related:
- field_ui.manage_form
- breakpoint.overview
---
-{% set structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}What are media items?{% endtrans %}</h2>
-<p>{% trans %}Core media items include audio, images, documents, and videos. You can add other media types, such as social media posts, through the use of contributed modules. Media items may be files located in your site's file system, or remote items referenced by a URL. Media items are content entities, and they are divided into media types (which are entity sub-types); media types can have fields. See the <a href="{{ structure }}">Managing content structure</a> topic for more information on content entities and fields.{% endtrans %}</p>
+<p>{% trans %}Core media items include audio, images, documents, and videos. You can add other media types, such as social media posts, through the use of contributed modules. Media items may be files located in your site's file system, or remote items referenced by a URL. Media items are content entities, and they are divided into media types (which are entity sub-types); media types can have fields. See {{ content_structure_topic }} for more information on content entities and fields.{% endtrans %}</p>
<h2>{% trans %}What is the media library?{% endtrans %}</h2>
<p>{% trans %}The media library is a visual user interface for managing and reusing media items. Add media items to content using Media reference fields and the Media library field widget.{% endtrans %}</p>
<h2>{% trans %}What is an image style?{% endtrans %}</h2>
diff --git a/core/modules/help_topics/help_topics/core.translations.html.twig b/core/modules/help_topics/help_topics/core.translations.html.twig
index 9277de16599dbe5bd588e66c1e7bbeae51fa04f2..a23289a5edd2dcf78ab46cf194db08b616566607 100644
--- a/core/modules/help_topics/help_topics/core.translations.html.twig
+++ b/core/modules/help_topics/help_topics/core.translations.html.twig
@@ -5,13 +5,13 @@ related:
- block.place
- block.configure
---
-{% set config_overview = render_var(url('help.help_topic', {'id': 'core.config_overview'})) %}
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set config_overview_topic = render_var(help_topic_link('core.config_overview')) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}What text can be translated in your site?{% endtrans %}</h2>
<p>{% trans %}There are three types of text that can be translated:{% endtrans %}</p>
<ul>
- <li>{% trans %}Content (blocks, content items, etc.) can be written in English or another language, and can be translated into additional languages. See <a href="{{ content_structure }}">Managing content structure</a> to learn more about content.{% endtrans %}</li>
- <li>{% trans %}Many configuration items also include text that can be translated. Default configuration provided by your site's software is provided in English; you can also download community-provided translations. See <a href="{{ config_overview }}">Managing and deploying configuration</a> to learn more about configuration.{% endtrans %}</li>
+ <li>{% trans %}Content (blocks, content items, etc.) can be written in English or another language, and can be translated into additional languages. See {{ content_structure_topic }} to learn more about content.{% endtrans %}</li>
+ <li>{% trans %}Many configuration items also include text that can be translated. Default configuration provided by your site's software is provided in English; you can also download community-provided translations. See {{ config_overview_topic }} to learn more about configuration.{% endtrans %}</li>
<li>{% trans %}User interface text that is provided by the core software, your install profile, themes, and modules is provided in English, but can be translated into other languages. You can also download translations that community-members have provided.{% endtrans %}</li>
</ul>
<h2>{% trans %}Working with languages overview{% endtrans %}</h2>
diff --git a/core/modules/help_topics/help_topics/core.web_services.html.twig b/core/modules/help_topics/help_topics/core.web_services.html.twig
index cab79e8bdd3bb59e163ccba02bd32c7073288b6b..a052e445a90a755fb451d36845d524ff554c98f7 100644
--- a/core/modules/help_topics/help_topics/core.web_services.html.twig
+++ b/core/modules/help_topics/help_topics/core.web_services.html.twig
@@ -4,7 +4,7 @@ top_level: true
related:
- core.content_structure
---
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}What is a web service?{% endtrans %}</h2>
<p>{% trans %}A web service allows your site to provide its content and data to other web sites and applications. Typically, the data is transported via <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol">HTTP</a> in a serialized machine-readable format.{% endtrans %}</p>
<h2>{% trans %}What is serialization?{% endtrans %}</h2>
@@ -17,7 +17,7 @@ related:
<p>{% trans %}The following Drupal core modules provide web services:{% endtrans %}</p>
<dl>
<dt>{% trans %}JSON:API module{% endtrans %}</dt>
- <dd>{% trans %}Exposes <a href="{{ content_structure }}">entities</a> to other applications using a fully compliant implementation of the <a href="https://jsonapi.org">JSON:API Specification</a>.{% endtrans %}</dd>
+ <dd>{% trans %}Exposes <em>entities</em> to other applications using a fully compliant implementation of the <a href="https://jsonapi.org">JSON:API Specification</a>. See {{ content_structure_topic }} for more information on content entities and fields.{% endtrans %}</dd>
<dt>{% trans %}RESTful Web Services module{% endtrans %}</dt>
<dd>{% trans %}Exposes entities and other resources to other applications using a <a href="https://en.wikipedia.org/wiki/Representational_state_transfer">REST</a> implementation. Data is exchanged using a serialization format such as HAL, and transferred using an authentication method such as HTTP Basic Authentication.{% endtrans %}</dd>
<dt>{% trans %}Serialization module{% endtrans %}</dt>
diff --git a/core/modules/help_topics/help_topics/editor.overview.html.twig b/core/modules/help_topics/help_topics/editor.overview.html.twig
index e381e55f2c76dac6f32d83088dc1e3f5bf634b25..4deb28d029726d31c5b2dc9d0898835b845deedc 100644
--- a/core/modules/help_topics/help_topics/editor.overview.html.twig
+++ b/core/modules/help_topics/help_topics/editor.overview.html.twig
@@ -5,19 +5,19 @@ related:
- field_ui.manage_form
- filter.overview
---
-{% set filters = render_var(url('help.help_topic', {'id': 'filter.overview'})) %}
+{% set filter_overview_topic = render_var(help_topic_link('filter.overview')) %}
{% set content_url = render_var(url('filter.admin_overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure a text format so that when a user is editing text and selects this text format, a text editor installed on your site is shown. Configure the text editor, such as choosing which buttons and functions are available. See <a href="{{ filters }}">Managing text filters and text formats</a> for more about text formats.{% endtrans %}</p>
+<p>{% trans %}Configure a text format so that when a user is editing text and selects this text format, a text editor installed on your site is shown. Configure the text editor, such as choosing which buttons and functions are available. See {{ filter_overview_topic }} for more about text formats.{% endtrans %}</p>
<h2>{% trans %}What is a text editor?{% endtrans %}</h2>
<p>{% trans %}A text editor is software (typically, a JavaScript library) that provides buttons and other command mechanisms to make editing HTML text easier. Some editors are called <em>visual</em> or <em>WYSIWYG (What You See Is What You Get)</em> editors; these editors hide the details of HTML from the user, and instead show formatted output on the screen. The core Text Editor module provides a framework for deploying text editors on your site. The core CKEditor module provides CKEditor, which is a widely-used JavaScript WYSIWYG editor that creates clean and valid HTML; the module also enforces the HTML tag restrictions in the associated text format. Various contributed modules provide other editors; to install a new editor, besides installing the module, you may need to download the editor library from a third-party site.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Content Authoring</em> > <a href="{{ content_url }}"><em>Text formats and editors</em></a>. The <em>Text editor</em> column in the table shows the text editor that is currently connected to each text format, if any.{% endtrans %}</li>
- <li>{% trans %}Follow the steps on <a href="{{ filters }}">Managing text filters and text formats</a> to add a new text format or configure an existing text format; when you reach the step about text editors, return to this topic.{% endtrans %}</li>
+ <li>{% trans %}Follow the steps on {{ filter_overview_topic }} to add a new text format or configure an existing text format; when you reach the step about text editors, return to this topic.{% endtrans %}</li>
<li>{% trans %}Select <em>CKEditor</em> as the <em>Text editor</em>, or another text editor that you have installed. The rest of these steps assume you selected <em>CKEditor</em>.{% endtrans %}</li>
<li>{% trans %}Under <em>Toolbar configuration</em>, drag buttons between <em>Available buttons</em> and <em>Active toolbar</em>; only buttons in <em>Active toolbar</em> will be shown to the user. If you are using a mouse, you can hover over a button to see a tooltip explaining what the button does.{% endtrans %}</li>
<li>{% trans %}Drag buttons within <em>Active toolbar</em> to the desired order, and group buttons by dragging them into the grouping boxes; click <em>Add group</em> to add additional groups.{% endtrans %}</li>
<li>{% trans %}Under <em>CKEditor plugin settings</em>, configure the buttons that have configuration. This section will not be present if there are no active buttons with configuration.{% endtrans %}</li>
- <li>{% trans %}Return to <a href="{{ filters }}">Managing text filters and text formats</a> to complete the text format configuration, and be sure to save the text format.{% endtrans %}</li>
+ <li>{% trans %}Return to {{ filter_overview_topic }} to complete the text format configuration, and be sure to save the text format.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/field_ui.add_field.html.twig b/core/modules/help_topics/help_topics/field_ui.add_field.html.twig
index 364539ffe9103f4a8cf79a1732c9e57d207ba8b8..2672450e17025304f121b9d8bb5d05bd916fab72 100644
--- a/core/modules/help_topics/help_topics/field_ui.add_field.html.twig
+++ b/core/modules/help_topics/help_topics/field_ui.add_field.html.twig
@@ -6,15 +6,15 @@ related:
- field_ui.manage_form
---
{% set content_types = render_var(url('entity.node_type.collection')) %}
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Add a field to an entity sub-type; see <a href="{{ content_structure }}">Managing content structure</a> for an overview of entity types and sub-types, as well as an overview of field types.{% endtrans %}</p>
+<p>{% trans %}Add a field to an entity sub-type; see {{ content_structure_topic }} for an overview of entity types and sub-types, as well as an overview of field types.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}Navigate to the page for managing the entity sub-type you want to add the field to. For example, to add a field to a content type, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
<li>{% trans %}Find the particular sub-type that you want to add the field to, and click <em>Manage fields</em>.{% endtrans %}</li>
<li>{% trans %}Click <em>Add field</em>.{% endtrans %}</li>
- <li>{% trans %}In <em>Add a new field</em>, select the type of field you want to add; see <a href="{{ content_structure }}">Managing content structure</a> for an overview of field types.{% endtrans %}</li>
+ <li>{% trans %}In <em>Add a new field</em>, select the type of field you want to add; see {{ content_structure_topic }} for an overview of field types.{% endtrans %}</li>
<li>{% trans %}The <em>Label</em> field should now be visible; enter a label for the field, which is used as the field label for both content editing and content display.{% endtrans %}</li>
<li>{% trans %}Click <em>Save and continue</em>.{% endtrans %}</li>
<li>{% trans %}On the next screen, enter a value for <em>Allowed number of values</em>. You can limit the field to one value per entity item, a set number of values, or set it to have unlimited values. Click <em>Save field settings</em>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/field_ui.manage_display.html.twig b/core/modules/help_topics/help_topics/field_ui.manage_display.html.twig
index 59e93602c8b919f6bd64fc2b136240d52a703d7a..10bd1b55aeed0a905d2f2b69378936659a9a4d1d 100644
--- a/core/modules/help_topics/help_topics/field_ui.manage_display.html.twig
+++ b/core/modules/help_topics/help_topics/field_ui.manage_display.html.twig
@@ -7,9 +7,9 @@ related:
- core.ui_accessibility
---
{% set content_types = render_var(url('entity.node_type.collection')) %}
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure the <em>formatters</em> used to display the fields of an entity sub-type, their order in the display, and the formatter settings. See <a href="{{ content_structure }}">Managing content structure</a> for background information.{% endtrans %}</p>
+<p>{% trans %}Configure the <em>formatters</em> used to display the fields of an entity sub-type, their order in the display, and the formatter settings. See {{ content_structure_topic }} for background information.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}Navigate to the page for managing the entity type you want to add the field to. For example, to add a field to a content type, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/field_ui.manage_form.html.twig b/core/modules/help_topics/help_topics/field_ui.manage_form.html.twig
index 6cc1ed057d9b2584477592e32a2e6d1bb21a2f4f..e3bacec71f499deb7960a64e966f9ecd157dc03f 100644
--- a/core/modules/help_topics/help_topics/field_ui.manage_form.html.twig
+++ b/core/modules/help_topics/help_topics/field_ui.manage_form.html.twig
@@ -7,9 +7,9 @@ related:
- core.ui_accessibility
---
{% set content_types = render_var(url('entity.node_type.collection')) %}
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure the <em>widgets</em> used to edit the fields of an entity sub-type, their order on the form, and the widget settings. See <a href="{{ content_structure }}">Managing content structure</a> for background information.{% endtrans %}</p>
+<p>{% trans %}Configure the <em>widgets</em> used to edit the fields of an entity sub-type, their order on the form, and the widget settings. See {{ content_structure_topic }} for background information.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}Navigate to the page for managing the entity type you want to add the field to. For example, to add a field to a content type, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/field_ui.reference_field.html.twig b/core/modules/help_topics/help_topics/field_ui.reference_field.html.twig
index c2dd8ddfdde78a5fc571ff24f2ed9cc0296e311d..4d5ddcee072b82898c4187418f73431680736bcd 100644
--- a/core/modules/help_topics/help_topics/field_ui.reference_field.html.twig
+++ b/core/modules/help_topics/help_topics/field_ui.reference_field.html.twig
@@ -6,10 +6,10 @@ related:
- field_ui.manage_display
- field_ui.manage_form
---
-{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
{% set content_types = render_var(url('entity.node_type.collection')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Add an entity reference field to an entity sub-type; see <a href="{{ content_structure}}">Managing content structure</a> for more information on entities and reference fields.{% endtrans %}</p>
+<p>{% trans %}Add an entity reference field to an entity sub-type; see {{ content_structure_topic }} for more information on entities and reference fields.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}Navigate to the page for managing the entity sub-type you want to add the field to. For example, to add a field to a content type, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/forum.configuring.html.twig b/core/modules/help_topics/help_topics/forum.configuring.html.twig
index b6d12f7cb15cb6119b0f32d8990119d8c7c29bda..0b2b123b1377c9dc48b2f09d7c2a4ebaa206eaf5 100644
--- a/core/modules/help_topics/help_topics/forum.configuring.html.twig
+++ b/core/modules/help_topics/help_topics/forum.configuring.html.twig
@@ -5,7 +5,7 @@ related:
---
{% set settings = render_var(url('forum.settings')) %}
{% set overview = render_var(url('forum.overview')) %}
-{% set concept = render_var(url('help.help_topic', {'id': 'forum.concept'})) %}
+{% set forum_concept_topic = render_var(help_topic_link('forum.concept')) %}
{% set index = render_var(url('forum.index')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Configure settings for forums, and set up forum structure.{% endtrans %}</p>
@@ -14,7 +14,7 @@ related:
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <em>Forums</em> > <a href="{{ settings }}"><em>Settings</em></a>.{% endtrans %}</li>
<li>{% trans %}Choose the desired settings for <em>Hot topic threshold</em>, <em>Topics per page</em>, and <em>Default order</em>. Click <em>Save configuration</em> if you have made any changes.{% endtrans %}</li>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ overview }}"><em>Forums</em></a>.{% endtrans %}</li>
- <li>{% trans %}Decide on the hierarchy of containers and forums you want for your site; see <a href="{{ concept }}">Creating threaded discussion forums</a> for an overview of forum hierarchy.{% endtrans %}</li>
+ <li>{% trans %}Decide on the hierarchy of containers and forums you want for your site; see {{ forum_concept_topic }} for an overview of forum hierarchy.{% endtrans %}</li>
<li>{% trans %}Create the containers that you want in your forum hierarchy, starting at the top level, if any. To create a container, click <em>Add container</em>, enter the container name and optionally other settings, and click <em>Save</em>.{% endtrans %}</li>
<li>{% trans %}Create the forums that you want in your forum hierarchy, starting at the top level. To create a forum, click <em>Add forum</em> and enter the forum name. If your hierarchy has this forum inside a container or another forum, select the parent forum/container in the <em>Parent</em> field. Review and/or edit the other settings, and click <em>Save</em>.{% endtrans %}</li>
<li>{% trans %}Optionally, delete the provided <em>General discussion</em> forum, if you do not want this forum to be available on your site.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/help.help_topic_search.html.twig b/core/modules/help_topics/help_topics/help.help_topic_search.html.twig
index 0e0e5976f53a1a8aa1f4d24d973a0883cecad25a..ae8ffd8d29d1210fb178df12e439d4c743646842 100644
--- a/core/modules/help_topics/help_topics/help.help_topic_search.html.twig
+++ b/core/modules/help_topics/help_topics/help.help_topic_search.html.twig
@@ -8,8 +8,8 @@ related:
---
{% set extend_url = render_var(url('system.modules_list')) %}
{% set help_url = render_var(url('help.main')) %}
-{% set cache_help = render_var(url('help.help_topic', {'id': 'system.cache'})) %}
-{% set cron_help = render_var(url('help.help_topic', {'id': 'core.cron'})) %}
+{% set cache_topic = render_var(help_topic_link('system.cache')) %}
+{% set cron_topic = render_var(help_topic_link('core.cron')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Set up your site so that users can search for help.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -17,8 +17,8 @@ related:
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em><a href="{{ extend_url }}">Extend</a></em>. Verify that the Search, Help, Help Topics, and Block modules are installed (or install them if they are not already installed).{% endtrans %}</li>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Search and metadata</em> > <em>Search pages</em>.{% endtrans %}</li>
<li>{% trans %}Verify that a Help search page is listed in the <em>Search pages</em> section. If not, add a new page of type <em>Help</em>.{% endtrans %}</li>
- <li>{% trans %}Check the indexing status of the Help search page. If it is not fully indexed, <a href="{{ cron_help }}">run Cron</a> until indexing is complete.{% endtrans %}</li>
- <li>{% trans %}In the future, you can click <em>Rebuild search index</em> on this page, or <a href="{{ cache_help }}">clear the site cache</a>, in order to force help topic text to be reindexed for searching. This should be done whenever a module, theme, language, or string translation is updated.{% endtrans %}</li>
+ <li>{% trans %}Check the indexing status of the Help search page. If it is not fully indexed, see {{ cron_topic }} about how to run Cron until indexing is complete.{% endtrans %}</li>
+ <li>{% trans %}In the future, you can click <em>Rebuild search index</em> on this page, or {{ cache_topic }}, in order to force help topic text to be reindexed for searching. This should be done whenever a module, theme, language, or string translation is updated.{% endtrans %}</li>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <em>Block layout</em>.{% endtrans %}</li>
<li>{% trans %}Click the link for your administrative theme (such as the core Seven theme), near the top of the page, and verify that there is already a search block for help located in the Help region. If not, follow the steps in the related topic to place the <em>Search form</em> block in the Help region. When configuring the block, choose <em>Help</em> as the search page, and in the <em>Pages</em> tab under <em>Visibility</em>, enter <em>/admin/help</em> to make the search form only visible on the main <em>Help</em> page.{% endtrans %}</li>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em><a href="{{ help_url }}">Help</a></em>. Verify that the search block is visible, and try a search.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/image.style.html.twig b/core/modules/help_topics/help_topics/image.style.html.twig
index a8376ed2a0263c41239ed54f3c8fdd22e2fdb748..d520b50bd2cd67c6bf4a6939f98b98350fc37b99 100644
--- a/core/modules/help_topics/help_topics/image.style.html.twig
+++ b/core/modules/help_topics/help_topics/image.style.html.twig
@@ -5,10 +5,10 @@ related:
- field_ui.manage_display
- layout_builder.overview
---
-{% set overview = render_var(url('help.help_topic', {'id': 'core.media'})) %}
+{% set media_topic = render_var(help_topic_link('core.media')) %}
{% set styles = render_var(url('entity.image_style.collection')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Add a new image style, which can be used to process and display images. See <a href="{{ overview }}">Managing media</a> for an overview of image styles.{% endtrans %}</p>
+<p>{% trans %}Add a new image style, which can be used to process and display images. See {{ media_topic }} for an overview of image styles.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Media</em> > <a href="{{ styles }}"><em>Image styles</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/layout_builder.overview.html.twig b/core/modules/help_topics/help_topics/layout_builder.overview.html.twig
index 5b376cbff6d409c427a8fca72ca540c7df09915e..6b6d5b9c34b6350c3c5948cacb49b55a777b00b6 100644
--- a/core/modules/help_topics/help_topics/layout_builder.overview.html.twig
+++ b/core/modules/help_topics/help_topics/layout_builder.overview.html.twig
@@ -7,12 +7,12 @@ related:
- block.overview
---
{% set content_types = render_var(url('entity.node_type.collection')) %}
-{% set entities = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
-{% set blocks = render_var(url('help.help_topic', {'id': 'block.overview'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
+{% set block_overview_topic = render_var(help_topic_link('block.overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure an entity sub-type to have its fields displayed using a layout (see <a href="{{ entities }}">Managing content structure</a> for more on entities and fields).{% endtrans %}</p>
+<p>{% trans %}Configure an entity sub-type to have its fields displayed using a layout (see {{ content_structure_topic }} for more on entities and fields).{% endtrans %}</p>
<h2>{% trans %}What are the parts of a layout?{% endtrans %}</h2>
-<p>{% trans %}A layout consists of one or more <em>sections</em>. Each section can have from one to four <em>columns</em>. You can place blocks, including special blocks for the fields on the entity sub-type, in each column of each section (see <a href="{{ blocks }}">Managing blocks</a> for more on blocks).{% endtrans %}</p>
+<p>{% trans %}A layout consists of one or more <em>sections</em>. Each section can have from one to four <em>columns</em>. You can place blocks, including special blocks for the fields on the entity sub-type, in each column of each section (see {{ block_overview_topic }} for more on blocks).{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}Navigate to the page for managing the entity type you want to add the field to. For example, to add a field to a content type, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/media.media_type.html.twig b/core/modules/help_topics/help_topics/media.media_type.html.twig
index cfb0ded0650f978fc338ffad540191ca709aa790..e36629b41e0f992fca535c0217b8e54dce708ff8 100644
--- a/core/modules/help_topics/help_topics/media.media_type.html.twig
+++ b/core/modules/help_topics/help_topics/media.media_type.html.twig
@@ -5,11 +5,11 @@ related:
- field_ui.add_field
- field_ui.reference_field
---
-{% set structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
-{% set overview = render_var(url('help.help_topic', {'id': 'core.media'})) %}
+{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
+{% set media_topic = render_var(help_topic_link('core.media')) %}
{% set media = render_var(url('entity.media_type.collection')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Add a new media type that can be referenced in Media reference fields; media types are a content entity type. See the <a href="{{ overview }}">Managing media</a> topic for an overview of media items and media types, and the <a href="{{ structure }}">Managing content structure</a> topic for more information on content entities and fields.{% endtrans %}</p>
+<p>{% trans %}Add a new media type that can be referenced in Media reference fields; media types are a content entity type. See {{ media_topic }} for an overview of media items and media types, and {{ content_structure_topic }} for more information on content entities and fields.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ media }}"><em>Media types</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/migrate_drupal_ui.upgrading.html.twig b/core/modules/help_topics/help_topics/migrate_drupal_ui.upgrading.html.twig
index b8cc2d9c74877c33cf1239d060d3edc3f46b8977..9aa5015b140bf047aa8e5ec40eeb2fe0fd81ee4c 100644
--- a/core/modules/help_topics/help_topics/migrate_drupal_ui.upgrading.html.twig
+++ b/core/modules/help_topics/help_topics/migrate_drupal_ui.upgrading.html.twig
@@ -5,9 +5,9 @@ related:
---
{% set migrate_drupal_upgrade = render_var(url('migrate_drupal_ui.upgrade')) %}
{% set migrate_drupal_log = render_var(url('dblog.overview')) %}
-{% set overview_topic = render_var(url('help.help_topic', {'id': 'migrate.overview'})) %}
+{% set migrate_overview_topic = render_var(help_topic_link('migrate.overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Migrate data into a new, empty site, as part of an upgrade from an older version of Drupal. See <a href="{{ overview_topic }}">Migrating and upgrading</a> for an overview of migrating and upgrading.{% endtrans %}</p>
+<p>{% trans %}Migrate data into a new, empty site, as part of an upgrade from an older version of Drupal. See {{ migrate_overview_topic }} for an overview of migrating and upgrading.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em><a href="{{ migrate_drupal_upgrade }}">Upgrade</a></em>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/responsive_image.style.html.twig b/core/modules/help_topics/help_topics/responsive_image.style.html.twig
index fe905b19f7dcb53b438b40da9128d57f2cd05f9a..980bbb45035969b71496da8f1e72d1f482f97c8d 100644
--- a/core/modules/help_topics/help_topics/responsive_image.style.html.twig
+++ b/core/modules/help_topics/help_topics/responsive_image.style.html.twig
@@ -7,19 +7,19 @@ related:
- image.style
- breakpoint.overview
---
-{% set overview = render_var(url('help.help_topic', {'id': 'core.media'})) %}
-{% set image_style = render_var(url('help.help_topic', {'id': 'image.style'})) %}
-{% set breakpoint = render_var(url('help.help_topic', {'id': 'breakpoint.overview'})) %}
+{% set media_topic = render_var(help_topic_link('core.media')) %}
+{% set image_style_topic = render_var(help_topic_link('image.style')) %}
+{% set breakpoint_overview_topic = render_var(help_topic_link('breakpoint.overview')) %}
{% set styles = render_var(url('entity.responsive_image_style.collection')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Configure a responsive image style, which can be used to display images at different sizes on different devices. See <a href="{{ overview }}">Managing media</a> for an overview of responsive image styles, and <a href="{{ breakpoint }}">Managing height, width, and resolution breakpoints</a> for an overview of breakpoints.{% endtrans %}</p>
+<p>{% trans %}Configure a responsive image style, which can be used to display images at different sizes on different devices. See {{ media_topic }} for an overview of responsive image styles, and {{ breakpoint_overview_topic }} for an overview of breakpoints.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Media</em> > <a href="{{ styles }}"><em>Responsive image styles</em></a>.{% endtrans %}</li>
<li>{% trans %}Click <em>Add responsive image style</em>.{% endtrans %}</li>
<li>{% trans %}Enter a descriptive <em>Label</em> for your style.{% endtrans %}</li>
<li>{% trans %}Select a <em>Breakpoint group</em> from the groups defined by your installed themes and modules.{% endtrans %}</li>
- <li>{% trans %}Select a <em>Fallback image style</em> to use when none of the other styles apply. See <a href="{{ image_style }}">Adding an image style</a> if you need to add a new style.{% endtrans %}</li>
+ <li>{% trans %}Select a <em>Fallback image style</em> to use when none of the other styles apply. See {{ image_style_topic }} if you need to add a new style.{% endtrans %}</li>
<li>{% trans %}Click <em>Save</em>.{% endtrans %}</li>
<li>{% trans %}On the next page, locate the fieldsets for the breakpoints provided by the selected <em>Breakpoint group</em>.{% endtrans %}</li>
<li>{% trans %}For each breakpoint that you want to use, expand the corresponding fieldset. Select the <em>Select a single image style.</em> radio button under <em>Type</em> for the breakpoint, and select the <em>Image style</em> to use for images when that breakpoint is in effect. Repeat this step for the rest of the breakpoints you want to use.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/search.configuring.html.twig b/core/modules/help_topics/help_topics/search.configuring.html.twig
index 45673353914c3455f695e96b5caa2699cd1efce9..0c6f7e21867499f5fbc6110f64ddb657a1581d77 100644
--- a/core/modules/help_topics/help_topics/search.configuring.html.twig
+++ b/core/modules/help_topics/help_topics/search.configuring.html.twig
@@ -5,7 +5,7 @@ related:
- search.index
---
{% set search_settings = render_var(url('entity.search_page.collection')) %}
-{% set index_topic = render_var(url('help.help_topic', {'id': 'search.index'})) %}
+{% set search_index_topic = render_var(help_topic_link('search.index')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Configure one or more search pages.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -18,5 +18,5 @@ related:
<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>
+ <li>{% trans %}Follow the steps in {{ search_index_topic }} to make sure that the search index is updated.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/search.index.html.twig b/core/modules/help_topics/help_topics/search.index.html.twig
index c62dca7a98f77b0cea7e2b1bcff01dbabe0d2b6c..1451cebdd11b42fa42144c147d5d030f8bc6377b 100644
--- a/core/modules/help_topics/help_topics/search.index.html.twig
+++ b/core/modules/help_topics/help_topics/search.index.html.twig
@@ -4,12 +4,12 @@ related:
- search.overview
- search.configuring
---
-{% set cron_topic = render_var(url('help.help_topic', {'id': 'core.cron'})) %}
+{% set cron_topic = render_var(help_topic_link('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>
+<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 {{ cron_topic }} 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> > <em>Search and Metadata</em> > <a href="{{ search_settings }}"><em>Search pages</em></a>.{% endtrans %}</li>
@@ -18,6 +18,6 @@ related:
<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 %}Follow the steps in {{ cron_topic }} 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>
diff --git a/core/modules/help_topics/help_topics/search.overview.html.twig b/core/modules/help_topics/help_topics/search.overview.html.twig
index 5b2198d4dd571caac26b2ab0da3d8c66747c3d5c..4635e3f80ac6205edd9c4bdb1d46e67d54eb7ba1 100644
--- a/core/modules/help_topics/help_topics/search.overview.html.twig
+++ b/core/modules/help_topics/help_topics/search.overview.html.twig
@@ -6,7 +6,7 @@ related:
- block.place
---
{% set search_url = render_var(url('search.view')) %}
-{% set user_topic = render_var(url('help.help_topic', {'id': 'user.overview'})) %}
+{% set user_overview_topic = render_var(help_topic_link('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>
@@ -28,7 +28,7 @@ related:
<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>
+<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 {{ user_overview_topic }} 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>
diff --git a/core/modules/help_topics/help_topics/system.maintenance_mode.html.twig b/core/modules/help_topics/help_topics/system.maintenance_mode.html.twig
index 1f6efa16175d10c79b3eeb8264de7e27faf5672e..4969a6b0ee63544657887a9d628fb56b4414589f 100644
--- a/core/modules/help_topics/help_topics/system.maintenance_mode.html.twig
+++ b/core/modules/help_topics/help_topics/system.maintenance_mode.html.twig
@@ -5,7 +5,7 @@ related:
- system.cache
---
{% set maintenance_url = render_var(url('system.site_maintenance_mode')) %}
-{% set cache_help = render_var(url('help.help_topic', {'id': 'system.cache'})) %}
+{% set cache_topic = render_var(help_topic_link('system.cache')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Put your site in maintenance mode to perform maintenance operations, and then return to normal mode when finished.{% endtrans %}</p>
<h2>{% trans %}What is maintenance mode?{% endtrans %}</h2>
@@ -17,5 +17,5 @@ related:
<li>{% trans %}Perform your maintenance operations.{% endtrans %}</li>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> > <em>Development</em> > <em><a href="{{ maintenance_url }}">Maintenance mode</a></em>.{% endtrans %}</li>
<li>{% trans %}Uncheck <em>Put site into maintenance mode</em> and click <em>Save configuration</em>. Your site will be back in normal operation mode.{% endtrans %}</li>
- <li>{% trans %}Clear the site cache. See <a href="{{ cache_help }}">Clearing the site cache</a> for instructions.{% endtrans %}</li>
+ <li>{% trans %}Clear the site cache. See {{ cache_topic }} for instructions.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/system.module_uninstall.html.twig b/core/modules/help_topics/help_topics/system.module_uninstall.html.twig
index 8e014f4d75bedf31c1c0d2a81e5700e1721158c5..20432367fb6cc6757882465877f894e6ff0ac909 100644
--- a/core/modules/help_topics/help_topics/system.module_uninstall.html.twig
+++ b/core/modules/help_topics/help_topics/system.module_uninstall.html.twig
@@ -6,8 +6,9 @@ related:
- system.maintenance_mode
---
{% set uninstall_url = render_var(url('system.modules_uninstall')) %}
-{% set maintenance_topic = render_var(url('help.help_topic', {'id': 'system.maintenance_mode'})) %}<h2>{% trans %}Goal{% endtrans %}</h2>
-<p>{% trans %}Uninstall a module. Your site should be in <a href="{{ maintenance_topic }}">maintenance mode</a> when you uninstall modules.{% endtrans %}</p>
+{% set maintenance_topic = render_var(help_topic_link('system.maintenance_mode')) %}
+<h2>{% trans %}Goal{% endtrans %}</h2>
+<p>{% trans %}Uninstall a module. Your site should be in <em>maintenance mode</em> when you uninstall modules. See {{ maintenance_topic }} for details.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Extend</em> > <a href="{{ uninstall_url }}"><em>Uninstall</em></a>.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/views_ui.add_display.html.twig b/core/modules/help_topics/help_topics/views_ui.add_display.html.twig
index 37adffb5d61f5e7ee016d5a9e414959bfdfb7d8f..013de61b1c35fbd8109f89729dd47223249bf020 100644
--- a/core/modules/help_topics/help_topics/views_ui.add_display.html.twig
+++ b/core/modules/help_topics/help_topics/views_ui.add_display.html.twig
@@ -5,7 +5,7 @@ related:
- views_ui.edit
---
{% set views = render_var(url('entity.view.collection')) %}
-{% set view_edit = render_var(url('help.help_topic', {'id': 'views_ui.edit'})) %}
+{% set view_edit_topic = render_var(help_topic_link('views_ui.edit')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Add a new display to an existing view. This will allow you to display similar data to an existing view, using similar settings, in a new block, page, feed, etc.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
@@ -14,5 +14,5 @@ related:
<li>{% trans %}Under <em>Displays</em>, click <em>Add</em>.{% endtrans %}</li>
<li>{% trans %}In the pop-up list, click the link for the type of display you want to add; the most common types are <em>Page</em> and <em>Block</em>. The new display will be added to your view, and you will be editing that display.{% endtrans %}</li>
<li>{% trans %}Optionally, click the link next to <em>Display name</em> and enter a new name to be shown for this display in the administrative interface.{% endtrans %}</li>
- <li>{% trans %}Follow the steps in <a href="{{ view_edit }}">Editing an existing view display</a> to edit the other settings for the display.{% endtrans %}</li>
+ <li>{% trans %}Follow the steps in {{ view_edit_topic }} to edit the other settings for the display.{% endtrans %}</li>
</ol>
diff --git a/core/modules/help_topics/help_topics/views_ui.edit.html.twig b/core/modules/help_topics/help_topics/views_ui.edit.html.twig
index 5273a25f90d5cbed27ce9f211f8151ac926f2818..1506665c3fef685f4b9c4f1f502f267f0217c2e7 100644
--- a/core/modules/help_topics/help_topics/views_ui.edit.html.twig
+++ b/core/modules/help_topics/help_topics/views_ui.edit.html.twig
@@ -5,14 +5,14 @@ related:
- views_ui.add_display
---
{% set views = render_var(url('entity.view.collection')) %}
-{% set overview = render_var(url('help.help_topic', {'id': 'views.overview'})) %}
+{% set views_overview_topic = render_var(help_topic_link('views.overview')) %}
<h2>{% trans %}Goal{% endtrans %}</h2>
<p>{% trans %}Edit an existing view display, to modify what data is displayed or how it is displayed.{% endtrans %}</p>
<h2>{% trans %}Steps{% endtrans %}</h2>
<ol>
<li>{% trans %}If you are not already editing your view, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <a href="{{ views }}"><em>Views</em></a>. Find the view you want to edit, and click its <em>Edit</em> link.{% endtrans %}</li>
<li>{% trans %}Under <em>Displays</em>, click the display you want to edit.{% endtrans %}</li>
- <li>{% trans %}Find the section whose settings you want to change, such as <em>Format</em> or <em>Filter criteria</em> (see <a href="{{ overview }}">Managing content listings (views)</a> for more information).{% endtrans %}</li>
+ <li>{% trans %}Find the section whose settings you want to change, such as <em>Format</em> or <em>Filter criteria</em>. (See {{ views_overview_topic }} for more information.){% endtrans %}</li>
<li>{% trans %}For sections containing lists (such as <em>Fields</em> and <em>Filter criteria</em>), to modify or delete an existing item, click the name of the item. To add a new item, click <em>Add</em> in the drop-down list. To change the order of items, click <em>Rearrange</em> in the drop-down list.{% endtrans %}</li>
<li>{% trans %}For sections containing individual settings (such as <em>Title</em> and <em>Format</em>), there are often two links for each setting. The first link shows the current value; click that link to change the value. If there is a second link called <em>Settings</em>, click that link to change the settings details. For example, if your <em>Format</em> is currently shown as <em>Unformatted list</em>, click <em>Unformatted list</em> to switch to using a <em>Grid</em> or <em>Table</em> format. Click <em>Settings</em> next to your format type to change the settings for your chosen format.{% endtrans %}</li>
<li>{% trans %}When you have finished changing all the settings, verify that the display is correct by clicking <em>Update preview</em>. Return to editing settings if necessary.{% endtrans %}</li>
diff --git a/core/modules/help_topics/help_topics/workflows.overview.html.twig b/core/modules/help_topics/help_topics/workflows.overview.html.twig
index 20287218ba5c7163bb07901f9cbec5346a8ea7c6..8310cf07bd9ad50a989b1f07deb3e924a161f6a6 100644
--- a/core/modules/help_topics/help_topics/workflows.overview.html.twig
+++ b/core/modules/help_topics/help_topics/workflows.overview.html.twig
@@ -4,12 +4,12 @@ top_level: true
related:
- core.content_structure
---
-{% set configuring_workflows = render_var(url('help.help_topic', {'id': 'content_moderation.configuring_workflows'})) %}
-{% set changing_states = render_var(url('help.help_topic', {'id': 'content_moderation.changing_states'})) %}
+{% set configuring_workflows_topic = render_var(help_topic_link('content_moderation.configuring_workflows')) %}
+{% set changing_states_topic = render_var(help_topic_link('content_moderation.changing_states')) %}
<h2>{% trans %}What is a content moderation workflow?{% endtrans %}</h2>
<p>{% trans %}On some sites, new content and content revisions need to be <em>moderated</em>. That is, they need to pass through several <em>states</em> before becoming visible to site visitors. The collection of states and the definition of the transitions between states is known as a <em>workflow</em>. For example, new content might start out in a <em>Draft</em> state, and then might need to pass through several <em>Review</em> states before it becomes <em>Published</em> on the live site.{% endtrans %}</p>
-<p>{% trans %}The core software allows you to <a href="{{ configuring_workflows }}">define custom workflows</a> in which each transition has an associated permission that can be granted to a particular role.{% endtrans %}</p>
-<p>{% trans %}Users with sufficient permissions can <a href="{{ changing_states }}">move content through the various workflow transitions</a>.{% endtrans %}</p>
+<p>{% trans %}The core software allows you to configure workflows in which each transition has an associated permission that can be granted to a particular role. See {{ configuring_workflows_topic }} for more information.{% endtrans %}</p>
+<p>{% trans %}Users with sufficient permissions can change the workflow state of a particular entity. See {{ changing_states_topic }} for more information.{% endtrans %}</p>
<h2>{% trans %}Overview of content moderation workflows{% endtrans %}</h2>
<ul>
<li>{% trans %}The core Content Moderation module allows you to expand on core software's "unpublished" and "published" states for content. It allows you to have a published version that is live, but have a separate working copy that is undergoing review before it is published. This is achieved by using workflows to apply different states and transitions to entities as needed.{% endtrans %}</li>