Unverified Commit d5968330 authored by larowlan's avatar larowlan
Browse files

Issue #3192585 by andypost, ankithashetty, Amber Himes Matz: Fix up topics to...

Issue #3192585 by andypost, ankithashetty, Amber Himes Matz: Fix up topics to use new help_topic_link function
parent 7a1c9962
......@@ -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>
......
......@@ -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>
......
......@@ -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> &gt; <a href="{{ node_add }}"><em>Add content</em></a> &gt; <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> &gt; <a href="{{ node_add }}"><em>Add content</em></a> &gt; <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>
......
......@@ -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> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <a href="{{ export }}"><em>Export</em></a>.{% endtrans %}</li>
......
......@@ -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> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <em>Export</em> &gt; <em><a href="{{ single_export }}">Single item</a></em>.{% endtrans %}</li>
......
......@@ -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> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <em><a href="{{ import_page }}">Import</a></em>.{% endtrans %}</li>
......
......@@ -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> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <em>Import</em> &gt; <a href="{{ single_import }}"><em>Single item</em></a>.{% endtrans %}</li>
......
......@@ -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> &gt; <em>Regional and language</em> &gt; <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>
......@@ -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> &gt; <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>
......@@ -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>
......@@ -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>
......
......@@ -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> &gt; <em>Workflow</em> &gt; <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> &gt; <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>
......@@ -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> &gt; <em>Regional and language</em> &gt; <a href="{{ translation_settings }}"><em>Content language and translation</em></a>.{% endtrans %}</li>
......
......@@ -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 &amp; 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 &amp; 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>
......
......@@ -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>
......
......@@ -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>
......
......@@ -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>
......
......@@ -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> &gt; <em>Content Authoring</em> &gt; <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>
......@@ -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> &gt; <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>
......
......@@ -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> &gt; <a href="{{ content_types }}"><em>Content types</em></a>.{% endtrans %}</li>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment