a:953:{s:6:"Export";b:1;s:4:"Goal";b:1;s:165:"Create and download an archive containing all your site's configuration, exported as YAML files. See @config_overview_topic for more information about configuration.";b:1;s:5:"Steps";b:1;s:176:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <em>@export_link</em>.";b:1;s:48:"Click <em>Export</em> and save the archive file.";b:1;s:11:"Single item";b:1;s:188:"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.";b:1;s:204:"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; <em>@single_import_link</em>.";b:1;s:63:"Select the <em>Configuration type</em> that you want to import.";b:1;s:110:"On your computer or other device, copy the YAML-format configuration that you want to import to the clipboard.";b:1;s:85:"Paste the clipboard text into the box labeled <em>Paste your configuration here</em>.";b:1;s:22:"Click <em>Import</em>.";b:1;s:114:"Export a single configuration item to a file. See @config_overview_topic for more information about configuration.";b:1;s:204:"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>@single_export_link</em>.";b:1;s:131:"Select the <em>Configuration type</em> that you want to export, and then select the specific <em>Configuration name</em> to export.";b:1;s:105:"Use your browser to copy the text in the box marked <em>Here is your configuration</em> to the clipboard.";b:1;s:142:"Paste the copied text into a plain-text editor on your computer or other device, and save it using the suggested file name below the text box.";b:1;s:6:"Import";b:1;s:204:"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.";b:1;s:176:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>Configuration synchronization</em> &gt; <em>@import_link</em>.";b:1;s:74:"Browse to find the <em>Configuration archive</em> that you want to import.";b:1;s:186:"Click <em>Upload</em>. Your configuration archive will be unpacked and placed in the configuration synchronization directory, and you will be redirected to the <em>Synchronize</em> page.";b:1;s:149:"Review the differences between your uploaded configuration and the active configuration, if any, and click <em>Import all</em> to import the changes.";b:1;s:13:"Contact forms";b:1;s:46:"the form displayed on the default contact page";b:1;s:113:"Set a site-wide contact form to be the default contact form (@contact_page_link; for example, <em>/contact</em>).";b:1;s:103:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@contact_link</em>.";b:1;s:70:"Click <em>Edit</em> for the site-wide form you want to be the default.";b:1;s:66:"Check <em>Make this the default form</em> and click <em>Save</em>.";b:1;s:16:"Account settings";b:1;s:11:"Permissions";b:1;s:69:"Configure personal contact forms for registered users on the website.";b:1;s:127:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>People</em> &gt; <em>@config_link</em>.";b:1;s:121:"In the <em>Contact settings</em> section, check/uncheck the box to enable/disable the contact form for new user accounts.";b:1;s:34:"Click <em>Save configuration</em>.";b:1;s:103:"In the <em>Manage</em> administrative menu, navigate to <em>People</em> &gt; <em>@permission_link</em>.";b:1;s:451:"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).";b:1;s:32:"Click <em>Save permissions</em>.";b:1;s:153:"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.";b:1;s:36:"Create a new site-wide contact form.";b:1;s:32:"Click <em>Add contact form</em>.";b:1;s:104:"Fill in the <em>Label</em> (title) for the form, <em>Recipients</em>, and optionally the other settings.";b:1;s:101:"Click <em>Save</em>. You should see your new contact form in the table, along with a link to view it.";b:1;s:77:"Add, remove, or rearrange the fields on personal and site-wide contact forms.";b:1;s:37:"What are the fields on contact forms?";b:1;s:284:"Both personal and site-wide contact forms will always have <em>Subject</em> and <em>Message</em> fields. You can add additional fields for users to fill out if desired. Note that if you want to display other content on a form page, such as text or images, you can use a content block.";b:1;s:125:"Click <em>Manage fields</em> for the form you want to change the fields of, and add or remove one or more fields on the form.";b:1;s:98:"Click <em>Manage form display</em> to change the order or configuration of the fields on the form.";b:1;s:23:"What are contact forms?";b:1;s:437:"There are two different types of contact forms provided by the core Contact module: personal contact forms, which allow users to contact other users on the site, and site-wide contact forms, which allow users to contact site managers or administrators. A site can have more than one site-wide contact form; each has its own fields to fill out, recipients, and URL; you can also change the fields that are shown on personal contact forms.";b:1;s:31:"Using the personal contact form";b:1;s:438:"Site visitors can email registered users on your site by using the personal contact form, without knowing or learning the email address of the recipient. When a user with the correct permissions is viewing another user's profile, the viewer will see a <em>Contact</em> tab or link, which leads to the personal contact form if the user whose profile is being viewed has their personal contact form enabled (this is a user account setting).";b:1;s:29:"Contact form management tasks";b:1;s:48:"See the related topics below for specific tasks.";b:1;s:25:"What is site performance?";b:1;s:138:"Site performance, in this context, refers to speed factors such as the page load time and the response time after a user action on a page.";b:1;s:16:"What is caching?";b:1;s:532:"Caching is saving already-rendered HTML output and other calculated data for later use the first time it is needed. This saves time, because the next time the same data is needed it can be quickly retrieved instead of recalculated. Automatic caching systems also include mechanisms to delete cached calculations or mark them as no longer valid when the underlying data changes. To facilitate that, cached data has a <em>lifetime</em>, which is the maximum time before the data will be deleted from the cache (forcing recalculation).";b:1;s:25:"What is file aggregation?";b:1;s:208:"Aggregation is when CSS and JavaScript files are merged together and compressed into a format that is much smaller than the original. This allows for faster transmission and faster rendering on the other end.";b:1;s:47:"What can I do to improve my site's performance?";b:1;s:87:"The following core software modules and mechanisms can improve your site's performance:";b:1;s:26:"Internal Page Cache module";b:1;s:157:"Caches pages requested by users who are not logged in (anonymous users). Do not use if your site needs to send different output to different anonymous users.";b:1;s:34:"Internal Dynamic Page Cache module";b:1;s:160:"Caches data for both authenticated and anonymous users, with non-cacheable data in the page converted to placeholders and calculated when the page is requested.";b:1;s:15:"Big Pipe module";b:1;s:275:"Changes the way pages are sent to users, so that cacheable parts are sent out first with placeholders, and the uncacheable or personalized parts of the page are streamed afterwards. This allows the browser to render the bulk of the page quickly and fill in the details later.";b:1;s:25:"Performance page settings";b:1;s:265:"In the <em>Manage</em> administrative menu, if you navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>Performance</em>, you will find a setting for the maximum cache lifetime, as well as the ability to turn on CSS and JavaScript file aggregation.";b:1;s:20:"Additional resources";b:1;s:55:"Online documentation for the Internal Page Cache module";b:1;s:63:"Online documentation for the Internal Dynamic Page Cache module";b:1;s:43:"Online documentation for the BigPipe module";b:1;s:23:"Edit settings in place.";b:1;s:22:"What is quick editing?";b:1;s:185:"The core Settings Tray module provides the ability to quickly edit settings inline. It requires the core Contextual Links module in order to expose the links that let you edit in place.";b:1;s:31:"Who can edit settings in place?";b:1;s:321:"In order to follow these steps to edit settings in place, the core Settings Tray module must be installed. Also, either the core Toolbar module or a contributed replacement must be installed. You will need to have <em>Use contextual links</em> permission, as well as permission to edit the particular content or settings.";b:1;s:85:"Find and visit a page on your site that has the settings that you would like to edit.";b:1;s:186:"Click the contextual links <em>Edit</em> button on the toolbar (in most themes, it looks like a pencil). Contextual <em>Edit</em> links with the same icon will appear all over your page.";b:1;s:224:"Find the contextual link for the part of the page you want to edit. For example, if you want to edit the settings for a block, the link should be in the top-right corner of the block, or top-left for right-to-left languages.";b:1;s:140:"Click the link to open the contextual links menu, and click <em>Quick edit</em>. An editing form for the settings should appear on the page.";b:1;s:36:"Make your edits and submit the form.";b:1;s:17:"What is a module?";b:1;s:379:"A <em>module</em> is a set of PHP, JavaScript, and/or CSS files that extends site features and adds functionality. A set of <em>Core modules</em> is distributed as part of the core software download. Additional <em>Contributed modules</em> can be downloaded separately from the <a href="https://www.drupal.org/project/project_module">Download &amp; Extend page on drupal.org</a>.";b:1;s:31:"What is an Experimental module?";b:1;s:162:"An <em>Experimental</em> module is a module that is still in development and is not yet stable. Using Experimental modules on production sites is not recommended.";b:1;s:37:"What are installing and uninstalling?";b:1;s:410:"Installing a core or downloaded contributed module means turning it on, so that you can use its features and functionality. Uninstalling means turning it off and removing all of its configuration. A module cannot be uninstalled if another installed module depends on it, or if you have created content on your site using the module -- you would need to delete the content and uninstall dependent modules first.";b:1;s:18:"Extending overview";b:1;s:114:"See the related topics listed below for help performing tasks related to extending the functionality of your site.";b:1;s:119:"<a href="https://www.drupal.org/docs/user_guide/en/understanding-modules.html">Concept: Modules (Drupal User Guide)</a>";b:1;s:131:"<a href="https://www.drupal.org/docs/user_guide/en/extend-chapter.html">Extending and Customizing Your Site (Drupal User Guide)</a>";b:1;s:26:"What are security updates?";b:1;s:303:"Any software occasionally has bugs, and sometimes these bugs have security implications. When security bugs are fixed in the core software, modules, or themes that your site uses, they are released in a <em>security update</em>. You will need to apply security updates in order to keep your site secure.";b:1;s:29:"What are security advisories?";b:1;s:419:"A security advisory is a public announcement about a reported security problem in the core software. Contributed projects with a shield icon and "Stable releases for this project are covered by the security advisory policy" on their project page are also covered by Drupal's security advisory policy. Security advisories are managed by the <a href="https://www.drupal.org/drupal-security-team">Drupal Security Team</a>.";b:1;s:14:"Security tasks";b:1;s:198:"Keeping track of updates, updating the core software, and updating contributed modules and/or themes are all part of keeping your site secure. See the related topics listed below for specific tasks.";b:1;s:122:"<a href="https://www.drupal.org/docs/user_guide/en/security-chapter.html">Security and Maintenance (Drupal User Guide)</a>";b:1;s:155:"<a href="https://www.drupal.org/drupal-security-team/security-advisory-process-and-permissions-policy">Security advisory process and permissions policy</a>";b:1;s:16:"What is a theme?";b:1;s:652:"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.";b:1;s:21:"What is a base theme?";b:1;s:319:"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 Stable 9 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>.";b:1;s:17:"What is a layout?";b:1;s:403:"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).";b:1;s:33:"Changing site appearance overview";b:1;s:343:"The main way to change the overall appearance of your site is to switch the default theme. 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.";b:1;s:55:"Extending and Customizing Your Site (Drupal User Guide)";b:1;s:14:"Theming Drupal";b:1;s:55:"What administrative interface components are available?";b:1;s:158:"The following administrative interface components are provided by the core software and its modules (some contributed modules offer additional functionality):";b:1;s:123:"Accessibility features, to enable all users to perform administrative tasks. See @accessibility_topic for more information.";b:1;s:392:"A menu system, which you can navigate to find pages for administrative tasks. The core Toolbar module displays this menu on the top or left side of the page (right side in right-to-left languages). There are also contributed module replacements for the core Toolbar module, with additional features, such as the <a href="https://www.drupal.org/project/admin_toolbar">Admin Toolbar module</a>.";b:1;s:104:"The core Shortcuts module enhances the toolbar with a configurable list of links to commonly-used tasks.";b:1;s:133:"If you install the core Contextual Links module, non-administrative pages will contain links leading to related administrative tasks.";b:1;s:162:"In-place or <em>quick</em> editing. In-place editing of configuration is provided by the core Settings Tray module. See @settings_tray_topic for more information.";b:1;s:158:"The core Help module displays help topics, and provides a Help block that can be placed on administrative pages to provide an overview of their functionality.";b:1;s:49:"What are the sections of the administrative menu?";b:1;s:275:"The administrative menu, which you can navigate by visiting <em>@admin_link</em> on your site or by using an administrative toolbar, has the following sections (some may not be available, depending on which modules are currently installed on your site, and your permissions):";b:1;s:88:"<strong>Content:</strong> Find, manage, and create new pages; manage comments and files.";b:1;s:161:"<strong>Structure:</strong> Place and edit blocks, set up content types and fields, configure menus, administer taxonomy, and configure some contributed modules.";b:1;s:95:"<strong>Appearance:</strong> Switch between themes, install themes, and update existing themes.";b:1;s:64:"<strong>Extend:</strong> Update, install, and uninstall modules.";b:1;s:122:"<strong>Configuration:</strong> Configure the settings for various site functionality, including some contributed modules.";b:1;s:62:"<strong>People:</strong> Manage user accounts and permissions.";b:1;s:104:"<strong>Reports:</strong> Display information about site security, necessary updates, and site activity.";b:1;s:70:"<strong>Help:</strong> Get help on using the administrative interface.";b:1;s:33:"Administrative interface overview";b:1;s:207:"Install the core modules mentioned above to use the corresponding aspect of the administrative interface. See the related topics listed below for more details on some aspects of the administrative interface.";b:1;s:4:"Help";b:1;s:36:"What types of data does a site have?";b:1;s:565:"There are four main types of data. <em>Content</em> is the information (text, images, etc.) meant to be displayed to website visitors. <em>Configuration</em> is data that defines how the content is displayed; some configuration (such as field labels) may also be visible to site visitors. <em>State</em> is temporary data about the state of your site, such as the last time the system <em>cron</em> jobs ran. <em>Session</em> is a subset of State information, related to users' interactions with the site, such as site cookies and whether or not they are logged in.";b:1;s:25:"What is a content entity?";b:1;s:781:"A <em>content entity</em> (or more commonly, <em>entity</em>) is an item of content data, which can consist of text, HTML markup, images, attached files, and other data. Content entities are grouped into <em>entity types</em>, which have different purposes and are displayed in very different ways on the site. Most entity types are also divided into <em>entity sub-types</em>, which are divisions within an entity type to allow for smaller variations in how the entities are used and displayed. For example, the <em>Content item</em> entity type that stores page-level content is divided into <em>content type</em> sub-types; the <em>Content block</em> entity type has <em>block types</em>; but the <em>User</em> entity type (for user profile information) does not have sub-types.";b:1;s:16:"What is a field?";b:1;s:486:"Within entity items, the data is stored in individual <em>fields</em>, each of which holds one type of data, such as formatted or plain text, images or other files, or dates. Fields can be added by an administrator on entity sub-types, so that all entity items of a given entity sub-type have the same collection of fields available, and they can be single-valued or multiple-valued. When you create or edit entity items, you are specifying the values for the fields on the entity item.";b:1;s:26:"What is a reference field?";b:1;s:319:"A <em>reference field</em> is a field that stores a relationship between an entity and one or more other entities, which may belong to the same or different entity type. For example, a <em>Content reference</em> field on a content type stores a relationship between one content item and one or more other content items.";b:1;s:31:"What field types are available?";b:1;s:123:"The following field types are provided by the core system and core modules (many more are provided by contributed modules):";b:1;s:83:"Boolean, Number (provided by the core system): Stores true/false values and numbers";b:1;s:88:"Comment (provided by the core Comment module): Allows users to add comments to an entity";b:1;s:57:"Date, Timestamp (Datetime module): Stores dates and times";b:1;s:84:"Date range (Datetime range module): Stores time/date periods with a start and an end";b:1;s:43:"Email (core system): Stores email addresses";b:1;s:45:"Link (Link module): Stores URLs and link text";b:1;s:151:"List (Options module): Stores values chosen from pre-defined lists, where the values can be numbers or text; see section below for more on list fields.";b:1;s:68:"Reference (core system): Stores entity references; see section above";b:1;s:54:"Telephone (Telephone module): Stores telephone numbers";b:1;s:101:"Text (Text module): Stores formatted and unformatted text; see section below for more on text fields.";b:1;s:49:"What settings are available for List field types?";b:1;s:598:"List fields associate pre-defined <em>keys</em> (or value codes) with <em>labels</em> that the user sees. For example, you might define a list field that shows the user the names of several locations, while behind the scenes a location code is stored in the database. Each list field type corresponds to one type of stored key. For example, a <em>List (integer)</em> field stores integers, while the <em>List (text)</em> field stores text strings. Once you have chosen the field type, the main setting for a list field is the <em>Allowed values</em> list, which associates the keys with the labels.";b:1;s:40:"What types of Text fields are available?";b:1;s:804:"There are several types of text fields, with different characteristics. Text fields can be either <em>plain</em> or <em>formatted</em>: plain text fields do not contain HTML, while formatted fields can contain HTML and are processed through <em>text filters</em> (these are provided by the core Filter module; if you have that module enabled, see the related topic below on filters for more information). Text fields can also be regular-length (with a limit of 255 characters) or <em>long</em> (with a very large character limit), and long formatted text fields can include a <em>summary</em> attribute. All possible combinations of these characteristics exist as text field types; for example, <em>Text (plain)</em> and <em>Text (formatted, long, with summary)</em> are two examples of text field types.";b:1;s:20:"What is a formatter?";b:1;s:329:"A <em>formatter</em> is a way to display a field; most field types offer several types of formatters, and most formatters have settings that further define how the field is displayed. It is also possible to completely hide a field from display, and you have the option of showing or hiding the field's label when it is displayed.";b:1;s:17:"What is a widget?";b:1;s:427:"A <em>widget</em> is a way to edit a field. Some field types, such as plain text single-line fields, have only one widget available (in this case, a single-line text input field). Other field types offer choices for the widget; for example, single-valued <em>List</em> fields can use a <em>Select</em> or <em>Radio button</em> widget for editing. Many widget types have settings that further define how the field can be edited.";b:1;s:35:"Managing content structure overview";b:1;s:142:"Besides the field modules listed in the previous section, there are additional core modules that you can use to manage your content structure:";b:1;s:147:"The core Node, Comment, Content Block, Custom Menu Links, User, File, Image, Media, Taxonomy, and Contact modules all provide content entity types.";b:1;s:101:"The core Field UI module provides a user interface for managing fields and their display on entities.";b:1;s:111:"The core Layout Builder module provides a more flexible user interface for configuring the display of entities.";b:1;s:113:"The core Filter, Responsive Image, and Path modules provide settings and display options for entities and fields.";b:1;s:236:"Depending on the core and contributed modules that you currently have installed on your site, the related topics below and other topics listed on the main help page (see @help_link) will help you with tasks related to content structure.";b:1;s:122:"<a href="https://www.drupal.org/docs/user_guide/en/understanding-data.html">Concept: Types of Data (Drupal User Guide)</a>";b:1;s:116:"<a href="https://www.drupal.org/docs/user_guide/en/planning-chapter.html">Planning your Site (Drupal User Guide)</a>";b:1;s:133:"<a href="https://www.drupal.org/docs/user_guide/en/structure-reference-fields.html">Concept: Reference Fields (Drupal User Guide)</a>";b:1;s:25:"Overview of accessibility";b:1;s:305:"The core administrative interface has built-in compliance with many accessibility standards so that most pages are accessible to most users in their default state. However, certain pages become more accessible to some users through the use of a non-default or improved interface. These interfaces include:";b:1;s:37:"Disabling drag-and-drop functionality";b:1;s:490:"The default drag-and-drop user interface for ordering tables in the administrative interface presents a challenge for some users, including keyboard-only users and users of screen readers and other assistive technology. The drag-and-drop interface can be disabled in a table by clicking a link labeled <em>Show row weights</em> above the table. The replacement interface allows users to order the table by choosing numerical weights (with increasing numbers) instead of dragging table rows.";b:1;s:27:"Enabling inline form errors";b:1;s:472:"Errors that occur when you submit a form, such as not filling in a required field, are sometimes difficult for users to understand and locate. In order to make these errors easier to find, the best practice is to put a summary of the errors at the top of the form page. To make them easier to understand, the best practice is to display error messages with the form fields they are related to. Both of these practices are implemented by the core Inline Form Errors module.";b:1;s:21:"What are media items?";b:1;s:472:"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.";b:1;s:26:"What is the media library?";b:1;s:174:"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.";b:1;s:23:"What is an image style?";b:1;s:321:"An image style is a set of processing steps, known as <em>effects</em>, that can be applied to images. Examples of effects include scaling and cropping images to different sizes. Responsive image styles can associate image styles with your theme's size breakpoints. This allows serving images sized for the browser width.";b:1;s:26:"Overview of managing media";b:1;s:58:"The following modules provide media-related functionality:";b:1;s:65:"Media items and media types are managed by the core Media module.";b:1;s:232:"The core Media module provides a Media reference field to add media to content entities. The core File and Image modules also provide reference fields. It is recommended to use the Media reference field because it is more versatile.";b:1;s:214:"The core Media Library module provides the media library and the Media library field widget. With this module installed, the Media library field widget becomes the default widget for editing Media reference fields.";b:1;s:271:"The core Image module provides a user interface for defining image styles. The core Responsive Image module provides responsive image styles. Using the core Breakpoint module, and a breakpoint-enabled theme, these responsive styles can serve images sized for the browser.";b:1;s:55:"See the related topics listed below for specific tasks.";b:1;s:75:"<a href="https://www.drupal.org/docs/8/core/modules/media">Media module</a>";b:1;s:26:"User interface translation";b:1;s:21:"What is a help topic?";b:1;s:200:"A help topic describes a concept, or steps to accomplish a task, related to a feature provided by one or more modules or themes. If the core Search module is enabled, these topics are also searchable.";b:1;s:29:"Where are help topics listed?";b:1;s:179:"The top-level help topics are listed at @help_link. Links to other topics, including non-top-level help topics, can be found under the "Related" heading when viewing a topic page.";b:1;s:29:"How are help topics provided?";b:1;s:461:"Modules and themes can provide help topics as Twig-file-based plugins in a project sub-directory called <em>help_topics</em>; plugin metadata is provided in YAML front matter within each Twig file. Plugin-based help topics provided by modules and themes will automatically be updated when a module or theme is updated. Use the plugins in <em>core/modules/help/help_topics</em> as a guide when writing and formatting a help topic plugin for your theme or module.";b:1;s:31:"How are help topics translated?";b:1;s:375:"The title and body text of help topics provided by contributed modules and themes are translatable using @translate_link (provided by Interface Translation module). Topics provided by custom modules and themes are also translatable if they have been viewed at least once in a non-English language, which triggers putting their translatable text into the translation database.";b:1;s:37:"How can users search for help topics?";b:1;s:515:"To enable users to search help, including help topics, you will need to install the core Search module, configure a search page, and add a search block to the Help page or another administrative page. (A search page is provided automatically, and if you use the core Claro administrative theme, a help search block is shown on the main Help page.) Then users with search permissions, and permission to view help, will be able to search help. See the related topic, @help_search_topic, for step-by-step instructions.";b:1;s:21:"Help Topics Standards";b:1;s:33:"What is the configuration system?";b:1;s:206:"The configuration system provides the ability for administrators to customize the site, and to move and synchronize configuration changes between development sites and the live site. It does this in 2 ways:";b:1;s:35:"Providing storage for configuration";b:1;s:162:"Providing a process in which configuration changes can be imported and exported between instances of the same site; for example, from "dev" to "staging" to "live"";b:1;s:27:"What is configuration data?";b:1;s:327:"Configuration data describes settings that define how your site behaves or is displayed. For example, when a site administrator updates settings using an administrative form, these settings are stored as configuration data. Configuration data describes settings as simple as a site name and as complex as a view or image style.";b:1;s:38:"What kinds of configuration are there?";b:1;s:20:"Active configuration";b:1;s:164:"Active configuration is the current working configuration of a site. Storage of active configuration is defined by the site, and resides in the database by default.";b:1;s:20:"Simple configuration";b:1;s:156:"A simple configuration item is a group of settings, such as the settings for a module or theme. Each simple configuration item has its own unique structure.";b:1;s:22:"Configuration entities";b:1;s:189:"Configuration entities are user-defined configuration items grouped by type, such as views, image styles, and content types. Each configuration entity within a type has a similar structure.";b:1;s:21:"Default configuration";b:1;s:624:"Default configuration can be defined by a module, theme, or installation profile in its <em>config/install</em> or <em>config/optional</em> directories. Configuration is provided in YAML files (file extension .yml); YAML is a human-readable data serialization standard that is used by the core software for several purposes. Once the default configuration has been imported into the site's active configuration (through installing the extension), that configuration is owned by the site, not the extension. This means that future updates of the extension will not override the site's active configuration for that extension.";b:1;s:38:"What is configuration synchronization?";b:1;s:217:"Configuration synchronization is the process of exporting and importing configuration to keep configuration synchronized between different versions of a site; for example, between a development site and the live site.";b:1;s:481:"Each site has unique identifier, also called a <em>UUID</em>, which identifies the site to the system in any instance of the site, as long as the site instances have been reproduced as clones (cloning is when the codebase and database are copied to create a new site instance). When site instances are cloned, a "dev" instance of the site has the same UUID as the "live" instance. When site instances share the same UUID, configuration can be exported from one instance to another.";b:1;s:88:"The following list contains terms and concepts related to configuration synchronization:";b:1;s:22:"Exported configuration";b:1;s:316:"When configuration is exported, the active configuration is exported as a set of files in YAML format. When using the <em>Configuration synchronization</em> administrative UI, configuration can be exported as a full-export or single-item archive. This archive can then be imported into the destination site instance.";b:1;s:22:"Imported configuration";b:1;s:273:"Imported configuration is configuration that has been exported from another instance of the site (the "source") and is now being imported into another site instance (the "destination"), thereby updating its active configuration to match the imported configuration data set.";b:1;s:28:"Configuration sync directory";b:1;s:481:"The configuration sync directory location is set in the site's <em>settings.php</em> file. When configuration is exported, the active configuration is exported and described in YAML files which are stored in the configuration sync directory. After the first export, the system compares the site's active configuration with the configuration data in the sync directory and will only export active configuration items that are different than their counterparts in the sync directory.";b:1;s:31:"Managing configuration overview";b:1;s:391:"Configuration management tasks, such as exporting or importing configuration and synchronizing configuration, can be done either through the administrative UI provided by the core Configuration Manager module or a command-line interface (CLI) tool. Defining a configuration sync directory path other than the default value requires read/write access to the site's <em>settings.php</em> file.";b:1;s:152:"Most modules and themes also provide settings forms for updating the configuration they provide. See the related topics listed below for specific tasks.";b:1;s:134:"<a href="https://www.drupal.org/docs/configuration-management/workflow-using-drush">Configuration Management: Workflow using Drush</a>";b:1;s:125:"<a href="https://www.drupal.org/docs/user_guide/en/install-dev-sites.html">Concept: Development Sites (Drupal User Guide)</a>";b:1;s:125:"<a href="https://www.drupal.org/docs/user_guide/en/install-dev-making.html">Making a Development Site (Drupal User Guide)</a>";b:1;s:15:"What is a menu?";b:1;s:146:"A menu is a collection of <em>menu links</em> used to navigate a web site. Menus and menu links can be provided by modules or site administrators.";b:1;s:23:"Managing menus overview";b:1;s:561:"The core Menu UI module provides a user interface for managing menus, including creating new menus, reordering menu links, and disabling links provided by modules. It also provides the ability for links to content items to be added to menus while editing, if configured on the content type. The core Custom Menu Links module provides the ability to add custom links to menus. Each menu can be displayed by placing a block in a theme region; some themes also can display a menu outside of the block system. See the related topics listed below for specific tasks.";b:1;s:20:"Additional Resources";b:1;s:107:"<a href="https://www.drupal.org/docs/user_guide/en/menu-concept.html">Concept: Menu (Drupal User Guide)</a>";b:1;s:4:"Cron";b:1;s:58:"Configure your system so that cron will run automatically.";b:1;s:20:"What are cron tasks?";b:1;s:397:"To ensure that your site and its modules continue to function well, a group of administrative operations should be run periodically. These operations are called <em>cron</em> tasks, and running the tasks is known as <em>running cron</em>. Depending on how often content is updated on your site, you might need to run cron on a schedule ranging from hourly to weekly to keep your site running well.";b:1;s:44:"What options are available for running cron?";b:1;s:118:"If the core Automated Cron module is installed, your site will run cron periodically, on a schedule you can configure.";b:1;s:118:"You can set up a task on your web server to visit the <em> cron URL</em>, which is unique to your site, on a schedule.";b:1;s:104:"You can also run cron manually, but this is not the recommended way to make sure it is run periodically.";b:1;s:170:"In the <em>Manage</em> administration menu, navigate to <em>Configuration</em> &gt; <em>System</em> &gt; <em>@cron_link</em>. Note the <em>Last run</em> time on the page.";b:1;s:87:"If you want to run cron right now, click <em>Run cron</em> and wait for cron to finish.";b:1;s:396:"If you have a way to configure tasks on your web server, copy the link where it says <em>To run cron from outside the site, go to</em>. Set up a task to visit that URL on your desired cron schedule, such as once an hour or once a week. (On Linux-like servers, you can use the <em>wget</em> command to visit a URL.) If you configure an outside task, you should uninstall the Automated Cron module.";b:1;s:231:"If you are not configuring an outside task, and you have the core Automated Cron module installed, select a schedule for automated cron runs in <em>Cron settings</em> &gt; <em>Run cron every</em>. Click <em>Save configuration</em>.";b:1;s:116:"<a href="https://www.drupal.org/docs/user_guide/en/security-cron-concept.html">Concept: Cron (Drupal User Guide)</a>";b:1;s:129:"<a href="https://www.drupal.org/docs/user_guide/en/security-cron.html">Configuring Cron Maintenance Tasks (Drupal User Guide)</a>";b:1;s:17:"Tracking overview";b:1;s:181:"The core History module tracks how recently users have viewed content items, and provides a Views field and filter that can be used to show users content that they haven't yet seen.";b:1;s:120:"If you have one or more tracking modules installed on your site, see the related topics listed below for specific tasks.";b:1;s:22:"What is a web service?";b:1;s:256:"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.";b:1;s:22:"What is serialization?";b:1;s:272:"Serialization is the process of converting complex data structures into text strings, so that they can be exchanged and stored. The reverse process is called <em>deserialization</em>. JSON and XML are the two most-commonly-used data serialization formats for web services.";b:1;s:34:"What is HTTP Basic authentication?";b:1;s:196:"<a href="http://en.wikipedia.org/wiki/Basic_access_authentication">HTTP Basic authentication</a> is a method for authenticating requests by sending a user name and password along with the request.";b:1;s:34:"What modules provide web services?";b:1;s:57:"The following core software modules provide web services:";b:1;s:15:"JSON:API module";b:1;s:233:"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.";b:1;s:27:"RESTful Web Services module";b:1;s:306:"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 JSON, and transferred using an authentication method such as HTTP Basic Authentication.";b:1;s:20:"Serialization module";b:1;s:88:"Provides a framework for adding specific serialization formats for other modules to use.";b:1;s:32:"HTTP Basic Authentication module";b:1;s:111:"Provides a way for web services to be authenticated using HTTP Basic authentication against site user accounts.";b:1;s:61:"There are also contributed modules that provide web services.";b:1;s:56:"Online documentation for the RESTful Web Services module";b:1;s:44:"Online documentation for the JSON:API module";b:1;s:59:"Comparison of the RESTFul Web Services and JSON:API modules";b:1;s:6:"Extend";b:1;s:51:"Set up your site so that users can search for help.";b:1;s:193:"In the <em>Manage</em> administrative menu, navigate to <em>@extend_link</em>. Verify that the Search, Help, and Block modules are installed (or install them if they are not already installed).";b:1;s:140:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Search and metadata</em> &gt; <em>Search pages</em>.";b:1;s:124:"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>.";b:1;s:144:"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.";b:1;s:244:"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.";b:1;s:102:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>Block layout</em>.";b:1;s:515:"Click the link for your administrative theme (such as the core Claro 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.";b:1;s:135:"In the <em>Manage</em> administrative menu, navigate to <em>@help_link</em>. Verify that the search block is visible, and try a search.";b:1;s:41:"What text can be translated in your site?";b:1;s:53:"There are three types of text that can be translated:";b:1;s:191:"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.";b:1;s:262:"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.";b:1;s:241:"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.";b:1;s:31:"Working with languages overview";b:1;s:662:"The core Language module lets you add new languages to your site, provides the <em>Language switcher</em> block, and provides the ability to configure block visibility by language; the block and block visibility settings are only available if you have multiple languages configured. The core Content Translation, Configuration Translation, and Interface Translation modules let you translate content, configuration, and the built-in user interface, respectively. The core Update Manager module manages automatic downloads of community-provided translations of default configuration and user-interface text. See the related topics listed below for specific tasks.";b:1;s:40:"Maintaining and troubleshooting overview";b:1;s:174:"Here are some tasks and hints related to maintaining your site, and troubleshooting problems that may come up on your site. See the related topics below for more information.";b:1;s:119:"When performing maintenance, such as installing, uninstalling, or updating a module, put your site in maintenance mode.";b:1;s:51:"Configure your site so that cron runs periodically.";b:1;s:96:"If your site is not behaving as expected, clear the cache before trying to diagnose the problem.";b:1;s:179:"There are several site reports that can help you diagnose problems with your site. There are also two core modules that can be used for error logging: Database Logging and Syslog.";b:1;s:127:"<a href="https://www.drupal.org/docs/user_guide/en/prevent-chapter.html">Preventing and Fixing Problems (Drupal User Guide)</a>";b:1;s:12:"Search pages";b:1;s:84:"Manage the search index, and make sure that the site is fully indexed for searching.";b:1;s:25:"What is the search index?";b:1;s:467:"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.";b:1;s:149:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Search and Metadata</em> &gt; <em>@search_settings_link</em>.";b:1;s:250:"Under <em>Indexing throttle</em>, select the <em>Number of items to index per cron run</em>. A smaller number will make cron faster and reduce the possibility of timeout; a larger number will make sure more of your site is indexed in fewer cron runs.";b:1;s:206:"Under <em>Default indexing settings</em>, enter the desired <em>Minimum word length to index</em>. Words smaller than this length will be dropped from both keywords when searching and content when indexing.";b:1;s:189:"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.";b:1;s:96:"Click <em>Save configuration</em>, and you should be returned to the <em>Search pages</em> page.";b:1;s:146:"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.";b:1;s:77:"Follow the steps in @cron_topic to make sure a cron task has been configured.";b:1;s:293:"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.";b:1;s:35:"Configure one or more search pages.";b:1;s:122:"Scroll down to the <em>Search pages</em> section. You will see a list of the already-configured search pages on your site.";b:1;s:161:"To configure an existing search page, click <em>Edit</em>. Or, to add a new search page, select the <em>Search page type</em> and click <em>Add search page</em>.";b:1;s:80:"Enter the desired <em>Label</em> name and URL <em>Path</em> for the search page.";b:1;s:149:"For <em>Content</em> search pages, select the desired level of influence in ranking search results of the available <em>Content ranking</em> factors.";b:1;s:76:"Click <em>Save</em>. You will be returned to the <em>Search pages</em> page.";b:1;s:195:"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.";b:1;s:152:"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).";b:1;s:86:"Follow the steps in @search_index_topic to make sure that the search index is updated.";b:1;s:6:"Search";b:1;s:22:"What are search pages?";b:1;s:310:"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.";b:1;s:283:"When users visit the main search page (see @search_link), 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.";b:1;s:33:"What modules provide site search?";b:1;s:192:"The core Search module provides the ability to configure search pages; search page types are provided by both core and contributed modules. The core modules that provide search page types are:";b:1;s:44:"The Node module, for searching content pages";b:1;s:44:"The User module, for searching user profiles";b:1;s:42:"The Help module, for searching help topics";b:1;s:344:"As an alternative to the core Search module's system of search pages, you can use contributed modules to provide site search. For example, the <a href="https://www.drupal.org/project/apachesolr">Apache Solr</a> and <a href="https://www.drupal.org/project/sphinx">Sphinx</a> contributed modules use third-party technology to provide site search.";b:1;s:51:"What are the limitations of the core Search module?";b:1;s:642:"There are two main limitations of the core Search module. First, it is not appropriate for very large sites -- if you have a large site, look into other search technologies like Apache Solr. Second, the Node search page type only supports exact keyword matching, which is not the behavior that most users will expect. You can improve this by installing a language-specific stemming module for your language (such as <a href="https://www.drupal.org/project/porterstemmer">Porter Stemmer</a> for American English), which makes it so that, for example, a search for the word walk would match pages containing the words walk, walking, and walked.";b:1;s:32:"What are the search permissions?";b:1;s:187:"Users with <em>Use search</em> permission can use the <em>Search form</em> block and <em>Search</em> page; this permission is required for any search configured in the core Search module.";b:1;s:108:"In addition to <em>Use search</em>, <em>View user information</em> permission is needed for searching users.";b:1;s:111:"In addition to <em>Use search</em>, <em>View published content</em> permission is needed for searching content.";b:1;s:122:"Users with <em>Use advanced search</em> permission can use more complex search filtering when performing content searches.";b:1;s:32:"Configuring site search overview";b:1;s:642:"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.";b:1;s:108:"<a href="https://www.drupal.org/documentation/modules/search">Online documentation for the Search module</a>";b:1;s:80:"Install a core module, or a contributed module that has already been downloaded.";b:1;s:78:"In the <em>Manage</em> administrative menu, navigate to <em>@extend_link</em>.";b:1;s:145:"Enter a word from the module name or description into the filter box, to make the list of modules smaller. Locate the module you want to install.";b:1;s:328:"Check the box next to the name of the module you want to install; you can also check more than one box to install multiple modules at the same time. If the checkbox is disabled for the module you are trying to install, expand the information to see why -- you may need to download an additional module that your module requires.";b:1;s:211:"Click <em>Install</em> at the bottom of the page. If you chose to install a module with dependencies that were not already installed, or if you chose an Experimental module, confirm your choice on the next page.";b:1;s:160:"Wait for the module (or modules) to be installed. You should be returned to the <em>Extend</em> page with a message saying the module or modules were installed.";b:1;s:16:"Maintenance mode";b:1;s:114:"Put your site in maintenance mode to perform maintenance operations, and then return to normal mode when finished.";b:1;s:25:"What is maintenance mode?";b:1;s:370:"When your site is in maintenance mode, most site visitors will see a simple maintenance mode message page, rather than being able to use the full functionality of the site. Users with <em>Use the site in maintenance mode</em> permission who are already logged in will be able to use the full site, and the log in page at <em>/user</em> will also be accessible to anyone.";b:1;s:137:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>@maintenance_link</em>.";b:1;s:200:"Check <em>Put site into maintenance mode</em>, optionally change the <em>Message to display when in maintenance mode</em>, and click <em>Save configuration</em>. Your site will be in maintenance mode.";b:1;s:36:"Perform your maintenance operations.";b:1;s:135:"Uncheck <em>Put site into maintenance mode</em> and click <em>Save configuration</em>. Your site will be back in normal operation mode.";b:1;s:56:"Clear the site cache. See @cache_topic for instructions.";b:1;s:13:"Status report";b:1;s:62:"Run reports to learn about the status and health of your site.";b:1;s:318:"In the <em>Manage</em> administrative menu, navigate to <em>Reports</em> &gt; <em>@status_link</em> to see a report that summarizes the health and status of your site. If there are any warnings or errors, you will need to fix them. Take note of any upcoming highly critical security releases that may impact your site.";b:1;s:342:"If you have the core Database Logging module installed, in the <em>Manage</em> administrative menu, navigate to <em>Reports</em> &gt; <em>Recent log messages</em> to see a report of the error and informational messages your site has generated. You can filter the report by <em>Severity</em> to see only the most critical messages, if desired.";b:1;s:469:"If you have the core Update Manager module installed, in the <em>Manage</em> administrative menu, navigate to <em>Reports</em> &gt; <em>Available updates</em> to see a report of the updates that are available for your site software. If <em>Last checked</em> is far in the past, click <em>Check manually</em> to update the report. Scan the report; if the core software or any modules or themes have security updates available, you should update them as soon as possible.";b:1;s:215:"<a href="https://www.drupal.org/docs/user_guide/en/security-chapter.html">Security and Maintenance (Drupal User Guide)</a>, which includes information on how to update your site's core software, modules, and themes.";b:1;s:17:"Regional settings";b:1;s:19:"Basic site settings";b:1;s:21:"Date and time formats";b:1;s:160:"Configure the basic settings of your site, including the site name, slogan, main email address, default time zone, default country, and the date formats to use.";b:1;s:132:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>System</em> &gt; <em>@information_link</em>.";b:1;s:66:"Enter the site name, slogan, and main email address for your site.";b:1;s:100:"Click <em>Save configuration</em>. You should see a message indicating that the settings were saved.";b:1;s:142:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; <em>@regional_link</em>.";b:1;s:63:"Select the default country and default time zone for your site.";b:1;s:142:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; <em>@datetime_link</em>.";b:1;s:211:"Look at the <em>Patterns</em> for the Default long, medium, and short date formats. If any of them does not match the date format you want to use on your site, click <em>Edit</em> in that row to edit the format.";b:1;s:153:"Adjust the <em>Format string</em> until the <em>Displayed</em> format matches what you want. (Date format strings are composed of PHP date format codes.)";b:1;s:90:"Click <em>Save format</em>. You should see a message indicating that the format was saved.";b:1;s:83:"Repeat the previous three steps for any other date formats that need to be changed.";b:1;s:128:"<a href="https://www.php.net/manual/datetime.format.php#refsect1-datetime.format-parameters">PHP date format codes reference</a>";b:1;s:10:"Appearance";b:1;s:89:"Uninstall a theme that was previously installed, but is no longer being used on the site.";b:1;s:78:"In the <em>Manage</em> administrative menu, navigate to <em>@themes_link</em>.";b:1;s:86:"Locate the theme that you want to uninstall, in the <em>Installed themes</em> section.";b:1;s:291:"Click the <em>Uninstall</em> link to uninstall the theme. If there is not an <em>Uninstall</em> link, the theme cannot be uninstalled because it is either being used as the site default theme, being used as the <em>Administration theme</em>, or is the base theme for another installed theme.";b:1;s:9:"Uninstall";b:1;s:132:"Uninstall a module. Your site should be in <em>maintenance mode</em> when you uninstall modules. See @maintenance_topic for details.";b:1;s:102:"In the <em>Manage</em> administrative menu, navigate to <em>Extend</em> &gt; <em>@uninstall_link</em>.";b:1;s:147:"Enter a word from the module name or description into the filter box, to make the list of modules smaller. Locate the module you want to uninstall.";b:1;s:337:"In the <em>Description</em> column, see if there are reasons that this module cannot be uninstalled. For example, you may have created content using this module (which you would need to delete first), or there may be another module installed that requires this module to be installed (you would need to uninstall the other module first).";b:1;s:137:"If there are no reasons listed, the module can be uninstalled. Check the box in the <em>Uninstall</em> column, next to the module's name.";b:1;s:184:"Click <em>Uninstall</em> at the bottom of the page. Verify the list of modules to be uninstalled and configuration to be deleted on the confirmation page, and click <em>Uninstall</em>.";b:1;s:142:"Wait for the module to be uninstalled. You should be returned to the <em>Uninstall</em> page with a message saying the module was uninstalled.";b:1;s:18:"Logging and errors";b:1;s:95:"Set up your site to respond appropriately to site errors, including 403 and 404 page responses.";b:1;s:31:"What are 403 and 404 responses?";b:1;s:437:"When a user visits a web page, the web server sends a response code in addition to the page content. A normal, non-error response has code 200. If the page does not exist on the site, the response code is 404. If the page exists, but the user is not authorized to visit the page, the response code is 403. The core software provides default responses for both 403 and 404 codes, but if you prefer, you can create your own pages for each.";b:1;s:28:"What other errors can occur?";b:1;s:417:"Under some situations, your site can generate error messages. These can be due to user errors (such as entering invalid values in a form, or incorrect configuration), PHP runtime errors, or software bugs. Some errors may result in a <em>white screen of death</em> (a totally blank web page response); less drastic errors will generate error messages. You can configure what happens when an error message is generated.";b:1;s:89:"If desired, create pages to use for 403 and 404 responses. Note the URLs for these pages.";b:1;s:273:"In the <em>Error pages</em> section, enter the URL for your 403/404 pages, starting after the site home page URL. For example, if your site URL is <em>https://example.com</em> and your 404 page is <em>https://example.com/not-found</em>, you would enter <em>/not-found</em>.";b:1;s:138:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>@log_settings_link</em>.";b:1;s:218:"For a production site, select <em>None</em> under <em>Error messages to display</em>. For a site that is in development, select one of the other options, so that you are more aware of the errors the site is generating.";b:1;s:154:"Install a core theme, or a contributed theme that has already been downloaded. Choose the default themes to use for the site and for administrative pages.";b:1;s:94:"Locate the themes that you want to use as the site default theme and for administrative pages.";b:1;s:266:"For each of these themes, if the theme is in the <em>Uninstalled themes</em> section, click the <em>Install</em> link to install the theme. Wait for the theme to be installed (translations might be downloaded). You should be returned to the <em>Appearance</em> page.";b:1;s:218:"Locate the theme that you want to be your default theme, which should now be in the <em>Installed themes</em> section. If it is not already labeled as the <em>default theme</em>, click the <em>Set as default</em> link.";b:1;s:176:"At the bottom of the page, select the <em>Administration theme</em> that you want to use on administrative pages. Click <em>Save configuration</em> if you selected a new theme.";b:1;s:281:"If you changed the default theme for your site, visit the site home page or another page on the non-administration part of your site and verify that the site is using the new theme. If you changed the administration theme, verify that the new theme is used on administrative pages.";b:1;s:11:"Performance";b:1;s:33:"Clear the data in the site cache.";b:1;s:18:"What is the cache?";b:1;s:509:"Some of the calculations that are done when your site loads a page take a long time to run. To save time when these calculations would need to be done again, their results can be <em>cached</em> in your site's database. There are internal mechanisms to <em>clear</em> cached data when the conditions or assumptions that went into the calculation have changed, but you can also clear cached data manually. When your site is misbehaving, a good first step is to clear the cache and see if the problem goes away.";b:1;s:137:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Development</em> &gt; <em>@performance_link</em>.";b:1;s:73:"Click <em>Clear all caches</em>. Your site's cached data will be cleared.";b:1;s:109:"<a href="https://www.drupal.org/docs/user_guide/en/prevent-cache.html">Concept: Cache (Drupal User Guide)</a>";b:1;s:6:"People";b:1;s:26:"Create a new user account.";b:1;s:78:"In the <em>Manage</em> administrative menu, navigate to <em>@people_link</em>.";b:1;s:24:"Click <em>Add user</em>.";b:1;s:100:"Enter the <em>Email address</em>, <em>Username</em>, and <em>Password</em> (twice) for the new user.";b:1;s:68:"Verify that the <em>Roles</em> checked for the new user are correct.";b:1;s:130:"If you want the new user to receive an email message notifying them of the new account, check <em>Notify user of new account</em>.";b:1;s:46:"Optionally, change other settings on the form.";b:1;s:34:"Click <em>Create new account</em>.";b:1;s:108:"You will be left on the <em>Add user</em> page; repeat these steps if you have more user accounts to create.";b:1;s:72:"Configure settings related to how user accounts are created and deleted.";b:1;s:68:"What are the settings related to user account creation and deletion?";b:1;s:247:"You can make it possible for new users to register themselves for accounts, with or without email verification or administrative approval. Or, you can make it so only administrators with <em>Administer users</em> permission can register new users.";b:1;s:111:"You can configure what happens to content that a user created, if their account is <em>canceled</em> (deleted).";b:1;s:167:"You can edit the email messages that are sent to users when their accounts are pending, approved, created, blocked, or canceled, or when they request a password reset.";b:1;s:41:"What are variables in email message text?";b:1;s:259:"<em>Variables</em> are short text strings, enclosed in square brackets [], that you can insert into configured email message text. When an individual message is generated, data from your site is substituted for the variables. Some commonly-used variables are:";b:1;s:38:"[site:name]: The name of your website.";b:1;s:36:"[site:url]: The URL of your website.";b:1;s:62:"[site:login-url]: The URL where users can log in to your site.";b:1;s:47:"[user:display-name]: The user's displayed name.";b:1;s:45:"[user:account-name]: The user's account name.";b:1;s:36:"[user:mail]: The user's email alias.";b:1;s:116:"[user:one-time-login-url]: An expiring URL that a user can use to log in once, if they need to reset their password.";b:1;s:137:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>People</em> &gt; <em>@account_settings_link</em>.";b:1;s:170:"Select the method you want to use for creating user accounts, and check or uncheck the box that requires email verification, to match the settings you want for your site.";b:1;s:103:"Select the desired option for what happens to content that a user created if their account is canceled.";b:1;s:69:"Optionally, edit the text of email messages related to user accounts.";b:1;s:43:"Verify that the other settings are correct.";b:1;s:15:"What is a user?";b:1;s:168:"A user is anyone accessing or viewing your site. <em>Anonymous</em> users are users who are not logged in, and <em>Authenticated</em> users are users who are logged in.";b:1;s:15:"What is a role?";b:1;s:173:"<em>Roles</em> are used to group and classify users; each user can be assigned one or more roles. There are also special roles for all anonymous and all authenticated users.";b:1;s:21:"What is a permission?";b:1;s:305:"Granting a <em>permission</em> to a role allows users who have been assigned that role to perform an action on the site, such as viewing content, editing or creating  a particular type of content, administering settings for a particular module, or using a particular function of the site (such as search).";b:1;s:47:"Overview of managing user accounts and visitors";b:1;s:377:"The core User module allows users to register, log in, and log out, and administrators to manage user roles and permissions. The core Ban module allows administrators to ban certain IP addresses from accessing the site. Depending on which modules you have installed on your site, the related topics below will help you with tasks related to managing user accounts and visitors.";b:1;s:44:"Modify the permissions for an existing role.";b:1;s:104:"In the <em>Manage</em> administrative menu, navigate to <em>People</em> &gt; <em>@permissions_link</em>.";b:1;s:339:"Review the permissions for the role, paying particular attention to the permissions marked with <em>Warning: Give to trusted roles only; this permission has security implications.</em> Uncheck permissions that this role should not have, in the row of the permission and the column of the role; check permissions that this role should have.";b:1;s:5:"Roles";b:1;s:18:"Create a new role.";b:1;s:98:"In the <em>Manage</em> administrative menu, navigate to <em>People</em> &gt; <em>@roles_link</em>.";b:1;s:24:"Click <em>Add role</em>.";b:1;s:119:"Enter the desired <em>Role name</em>. If desired, click <em>Edit</em> to change the <em>Machine name</em> for the role.";b:1;s:116:"Click <em>Save</em>. You should be returned to the <em>Roles</em> page and your new role should be in the role list.";b:1;s:42:"Update or delete an existing user account.";b:1;s:299:"Enter all or part of the user name or email address of the user account you want to update or delete, and click <em>Filter</em>. A short list of user accounts, including the account of interest, should be shown in the table; if not, modify the filter text until you can find the account of interest.";b:1;s:79:"Click <em>Edit</em> in the <em>Operations</em> area of the account of interest.";b:1;s:191:"To delete the user account, scroll to the bottom and click <em>Cancel account</em>. Select what you want to happen to the user's content on the next screen, and click <em>Cancel account</em>.";b:1;s:81:"To update the user account, enter new values in the form and click <em>Save</em>.";b:1;s:13:"Announcements";b:1;s:45:"View official announcements related to Drupal";b:1;s:30:"What are Drupal announcements?";b:1;s:81:"A feed of announcements about the Drupal project and Drupal Association programs.";b:1;s:275:"The purpose of this feed is to provide a channel for outreach directly to Drupal site owners. This content must be highly relevant to site owners interests, serve the strategic goals of the project, and/or promote the sustainability of the project and the Drupal Association.";b:1;s:233:"The module sources its content from a JSON feed generated from <a href="https://www.drupal.org/about/announcements">here</a>. The governance policy for the content is documented <a href="https://www.drupal.org/node/3274085">here</a>.";b:1;s:43:"How can I see the Announcements in my site?";b:1;s:199:"If you have the toolbar module enabled, you will see a direct link to them in the toolbar. If the toolbar module is not enabled, the content can always be accessed in the <em>@actions_link</em> page.";b:1;s:30:"Who can see the Announcements?";b:1;s:83:"Users with the <em>@permissions_link</em> permission can view Drupal announcements.";b:1;s:28:"Announcement module overview";b:1;s:12:"Block layout";b:1;s:36:"Place a block into a theme's region.";b:1;s:93:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; @layout_link.";b:1;s:64:"Click the name of the theme that you want to place the block in.";b:1;s:85:"Optionally, click <em>Demonstrate block regions</em> to see the regions of the theme.";b:1;s:116:"Find the region where you want the block, and click <em>Place block</em> in that region. A modal dialog will pop up.";b:1;s:117:"Find the block you want to place and click <em>Place block</em>. A <em>Configure block</em> modal dialog will pop up.";b:1;s:98:"Configure the block and click <em>Save block</em>; see @configure_topic for configuration details.";b:1;s:84:"Configure the settings of a block that was previously placed in a region of a theme.";b:1;s:102:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@layout_link</em>.";b:1;s:52:"Click the name of the theme that contains the block.";b:1;s:177:"If you only want to change the region where a block is located, or the ordering of blocks within a region, drag blocks to their desired positions and click <em>Save blocks</em>.";b:1;s:182:"If you want to change additional settings, find the region where the block you want to update is currently located, and click <em>Configure</em> in the line of the block description.";b:1;s:138:"Edit the block's settings. The available settings vary depending on the module that provides the block, but for all blocks you can change:";b:1;s:166:"<em>Block title</em>: The heading for the block on your site -- for some blocks, you will need to check the <em>Override title</em> checkbox in order to enter a title";b:1;s:69:"<em>Display title</em>: Check the box if you want the title displayed";b:1;s:74:"<em>Visibility</em>: Add conditions for when the block should be displayed";b:1;s:66:"<em>Region</em>: Change the theme region the block is displayed in";b:1;s:26:"Click <em>Save block</em>.";b:1;s:16:"What are blocks?";b:1;s:151:"Blocks are boxes of content rendered into an area, or region, of a web page of your site. Blocks are placed and configured specifically for each theme.";b:1;s:24:"What are content blocks?";b:1;s:213:"Content blocks are blocks whose content you can edit. You can define one or more <em>block types</em>, and attach fields to each block type. Content blocks can be placed just like blocks provided by other modules.";b:1;s:30:"What is the block description?";b:1;s:141:"The block description is an identification name for a block, which is shown in the administrative interface. It is not displayed on the site.";b:1;s:24:"What is the block title?";b:1;s:110:"The block title is the heading that is optionally shown to site visitors when the block is placed in a region.";b:1;s:28:"Overview for managing blocks";b:1;s:262:"The <em>Block</em> module allows you to place blocks in regions of your installed themes, and configure block settings. The <em>Block Content</em> module allows you to manage block types and content blocks. See the related topics listed below for specific tasks.";b:1;s:102:"<a href="https://www.drupal.org/docs/user_guide/en/blocks-chapter.html">Blocks (Drupal User Guide)</a>";b:1;s:24:"Text formats and editors";b:1;s:35:"Configure text formats on the site.";b:1;s:39:"What are text filters and text formats?";b:1;s:363:"A text filter is a processing step that can be applied to text, either to transform it in some way (such as converting URLs in the text into HTML links), or to defend against potentially-dangerous input from site users. A text format is an ordered sequence of text filters. Text filters are provided by modules; text formats are managed by the core Filter module.";b:1;s:458:"Text fields that have "formatted" in the field type name, such as <em>Text (formatted)</em>, use text formats. Users choose the text format when editing the field text; when the field text is shown on the site, it is processed by the chosen text format. Administrators can configure text formats and assign permissions for who can use each format. If the core Text Editor module is enabled, administrators can also associate visual editors with text formats.";b:1;s:32:"What text filters are available?";b:1;s:48:"Some of the more commonly used text filters are:";b:1;s:47:"Limit allowed HTML tags and correct faulty HTML";b:1;s:92:"Limits which HTML tags can be used; useful both for site security and enforcing site design.";b:1;s:29:"Convert line breaks into HTML";b:1;s:136:"Line breaks in HTML source are displayed as horizontal spaces. This filter converts line breaks into HTML paragraph and line break tags.";b:1;s:23:"Convert URLs into links";b:1;s:56:"Takes plain URLs in text and turns them into HTML links.";b:1;s:28:"Restrict images to this site";b:1;s:87:"For text formats that allow HTML image tags, restricts images to URLs within this site.";b:1;s:266:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Content Authoring</em> &gt; <em>@overview_link</em>. If you do not have the core Text Editor module installed, the menu link and page title will instead be <em>Text formats</em>.";b:1;s:121:"Click <em>Configure</em> to configure an existing text format, or <em>+ Add text format</em> to create a new text format.";b:1;s:52:"Enter the desired <em>Name</em> for the text format.";b:1;s:357:"Check the <em>Roles</em> that can use this text format. Some HTML tags allow users to embed malicious links or scripts in text. To ensure security, anonymous and untrusted users should only have access to text formats that restrict them to either plain text or a safe set of HTML tags. <strong>Improper text format configuration is a security risk.</strong>";b:1;s:112:"If the core Text Editor module is installed, see the related topic to connect a text editor to this text format.";b:1;s:76:"Under <em>Enabled filters</em>, check the text filters that you want to use.";b:1;s:315:"Under <em>Filter processing order</em>, drag the filters to the correct order. Choose the order carefully; for example, if you have a filter that results in a particular HTML tag being added to the text, that should run after a filter that restricts HTML tags, to avoid deleting the new tags the first filter added.";b:1;s:117:"Under <em>Filter settings</em>, verify and adjust the settings for each active filter that has configuration options.";b:1;s:103:"Click <em>Save configuration</em>, which will return you to the <em>Text formats and editors</em> page.";b:1;s:68:"Repeat these steps if you have additional text formats to configure.";b:1;s:11:"Block types";b:1;s:35:"Define a block type and its fields.";b:1;s:101:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@types_link</em>.";b:1;s:31:"Click  <em>Add block type</em>.";b:1;s:152:"Enter a label for this block type (shown in the administrative interface). Optionally, edit the automatically-generated machine name or the description.";b:1;s:75:"Click <em>Save</em>. You will be returned to the <em>Block types</em> page.";b:1;s:110:"Click <em>Manage fields</em> in the row of your new block type, and add the desired fields to your block type.";b:1;s:138:"Optionally, click <em>Manage form display</em> or <em>Manage display</em> to change the editing form or field display for your block type.";b:1;s:14:"Content blocks";b:1;s:62:"Create a content block, which can later be placed on the site.";b:1;s:73:"In the <em>Manage</em> administrative menu, navigate to <em>Content</em>.";b:1;s:27:"Open the @library_link tab.";b:1;s:139:"Click <em>Add content block</em>. If you have more than one block type defined on your site, click the name of the type you want to create.";b:1;s:99:"Enter a description of your block (to be shown to administrators) and the body text for your block.";b:1;s:20:"Click <em>Save</em>.";b:1;s:21:"What are breakpoints?";b:1;s:576:"Breakpoints are the point at which your site's content will respond to provide the user with the best possible layout to consume the information. A breakpoint separates the height or width of viewports (screens, printers, and other media output types) into steps. For instance, a width breakpoint of 40em creates two steps: one for widths up to 40em and one for widths above 40em. Breakpoints can be used to define when layouts should shift from one form to another, when images should be resized, and other changes that need to respond to changes in viewport height or width.";b:1;s:23:"What are media queries?";b:1;s:269:"Media  queries are a formal way to encode breakpoints. For instance, a width breakpoint at 40em would be written as the media query "(min-width: 40em)". Breakpoints are really just media queries with some additional meta-data, such as a name and multiplier information.";b:1;s:32:"What are resolution multipliers?";b:1;s:418:"Resolution multipliers are a measure of the viewport's device resolution, defined to be the ratio between the physical pixel size of the active device and the <a href="http://en.wikipedia.org/wiki/Device_independent_pixel">device-independent pixel</a> size. The Breakpoint module defines multipliers of 1, 1.5, and 2; when defining breakpoints, modules and themes can define which multipliers apply to each breakpoint.";b:1;s:27:"What is a breakpoint group?";b:1;s:221:"Breakpoints can be organized into groups. Modules and themes should use groups to separate out breakpoints that are meant to be used for different purposes, such as breakpoints for layouts or breakpoints for image sizing.";b:1;s:51:"Managing breakpoints and breakpoint groups overview";b:1;s:276:"The <em>Breakpoint</em> module allows you to define breakpoints and breakpoint groups in YAML files. Modules and themes can use the API provided by the <em>Breakpoint</em> module to define breakpoints and breakpoint groups, and to assign resolution multipliers to breakpoints.";b:1;s:34:"Working with breakpoints in Drupal";b:1;s:31:"W3C standards for media queries";b:1;s:279:"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.";b:1;s:22:"What is a text editor?";b:1;s:824:"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 5 module provides CKEditor 5, which is a widely-used JavaScript text 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.";b:1;s:264:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Content Authoring</em> &gt; <em>@overview_link</em>. The <em>Text editor</em> column in the table shows the text editor that is currently connected to each text format, if any.";b:1;s:171:"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.";b:1;s:168:"Select <em>CKEditor 5</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 5</em>.";b:1;s:272:"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. Focusing or hovering over a button will display a tooltip explaining what the button does.";b:1;s:205:"Drag buttons within <em>Active toolbar</em> to the desired order, and group buttons by dragging them between group identifiers; drag <em>a new group identifier</em> to the toolbar to add additional groups.";b:1;s:161:"If you add buttons that require configuration, the <em>CKEditor 5 plugin settings</em> section will be visible, and provide their respective configuration forms.";b:1;s:112:"Return to @filter_overview_topic to complete the text format configuration, and be sure to save the text format.";b:1;s:40:"Administer comments and comment settings";b:1;s:233:"Configure a content entity type/subtype to allow commenting, using a comment type that you have configured. See @content_structure_topic for more about content entities and fields, and @comment_type_topic to configure a comment type.";b:1;s:27:"Who can configure comments?";b:1;s:503:"In order to follow these steps, the Field UI module must be installed. You'll need the Comment module's <em>@comment_permissions_link</em> permission, in order to change comment settings for a comment field. You'll also need to have the appropriate permission for adding fields to the entity type or subtype that the comments are attached to. For example, to add a comment field to content items provided by the Node module, you would need the Node module's <em>Administer content types</em> permission.";b:1;s:164:"Follow the steps in the related <em>Adding a field to an entity sub-type</em> topic to add a field of type <em>Comments</em> to the desired entity type or sub-type.";b:1;s:213:"On the first field settings page, choose the <em>Comment type</em> to use for this entity type or sub-type. You'll also notice that the <em>Allowed number of values</em> field cannot be changed for comment fields.";b:1;s:82:"On the next field settings page, enter the desired settings for the comment field:";b:1;s:163:"<em>Threading</em>: whether or not the comments are collected by threads, with people able to reply to particular comments instead of to the content entity itself.";b:1;s:130:"<em>Comments per page</em>: the maximum number of comments displayed on one page (a pager will be added if you exceed this limit).";b:1;s:207:"<em>Anonymous commenting</em>: whether or not anonymous commenters are allowed or required to leave contact information with their comments (only applies if anonymous users have permission to post comments).";b:1;s:223:"<em>Show reply form on the same page as comments</em>: whether the comment reply form is displayed on the same page as the comments. If this is not selected, clicking <em>Reply</em> will open a new page with the reply form.";b:1;s:135:"<em>Preview comments</em>: whether previewing comments before submission is <em>Required</em>, <em>Optional</em>, or <em>Disabled</em>.";b:1;s:197:"<em>Default value</em>: each individual entity has its own comment settings, but here you can set defaults for the comment settings for this entity type or subtype. The comment settings values are:";b:1;s:36:"<em>Open</em>: comments are allowed.";b:1;s:79:"<em>Closed</em>: past comments remain visible, but no new comments are allowed.";b:1;s:75:"<em>Hidden</em>: past comments are hidden, and no new comments are allowed.";b:1;s:49:"Online documentation for content comment settings";b:1;s:346:"Turn off commenting for a particular entity (see @content_structure_topic for more about content entities and fields). Note that if you want to turn off commenting for all entities of an entity type or subtype, you will need to edit the field settings for the comment field; see @comment_config_topic for more about configuring the comment field.";b:1;s:25:"Who can disable comments?";b:1;s:170:"You will need the <em>@comment_permissions_link</em> permission in order to disable commenting. You will also need permission to edit the entity that the comments are on.";b:1;s:275:"Find the entity you want to disable comments for, and edit it. For example, to turn off comments on a content item, you could find it by navigating in the <em>Manage</em> administrative menu to <em>Content</em>, filtering to find the content item, and clicking <em>Edit</em>.";b:1;s:68:"Under <em>Comment settings</em>, select the desired comment setting:";b:1;s:16:"Save the entity.";b:1;s:13:"Comment types";b:1;s:37:"Administer comment types and settings";b:1;s:104:"Create a new comment type. See @comment_overview_topic for information about comments and comment types.";b:1;s:30:"Who can create a comment type?";b:1;s:113:"Users with the <em>@comment_permissions_link</em> permission (typically administrators) can create comment types.";b:1;s:109:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@comment_types_link</em>.";b:1;s:32:"Click <em>Add comment type</em>.";b:1;s:127:"In the <em>Label</em> field, enter a name for the comment type, which is how it will be listed in the administrative interface.";b:1;s:157:"In the <em>Target entity type</em> field, select the entity type to be commented on. See @content_structure_topic for more about content entities and fields.";b:1;s:54:"Click <em>Save</em>. The comment type will be created.";b:1;s:196:"Optionally, if you have the core Field UI module installed you can follow the steps in the related topics to add fields to the new comment type, set up the editing form, and configure the display.";b:1;s:19:"Unapproved comments";b:1;s:8:"Comments";b:1;s:47:"Decide which comments are shown on the website.";b:1;s:26:"Who can moderate comments?";b:1;s:272:"Users with the <em>@comment_permissions_link</em> permission (typically administrators) can moderate comments. You will also need the <em>Access the Content Overview page</em> permission from the Node module (if it is installed) to navigate to the comment management page.";b:1;s:144:"In the <em>Manage</em> administrative menu, navigate to <em>Content</em> &gt; <em>@comment_published_link</em>. A list of all comments is shown.";b:1;s:347:"To unpublish comments, select one or more comments by checking the boxes on the left side (right side in right-to-left languages). Then select <em>Unpublish comment</em> from the <em>Action</em> select list and click <em>Apply to selected items</em>. If you select the <em>Delete comment</em> action, you can instead delete the unwanted  comments.";b:1;s:105:"To change the content of a comment click <em>Edit</em> from the dropdown button for a particular comment.";b:1;s:342:"To publish comments that are not yet visible on the website, navigate to the <em>@comment_unpublished_link</em> tab. Select one or more comments by checking the boxes on the left side (right side in right-to-left languages). Then select <em>Publish comment</em> from the <em>Action</em> select list and click <em>Apply to selected items</em>.";b:1;s:44:"Online documentation for moderating comments";b:1;s:18:"What is a comment?";b:1;s:409:"A comment is a piece of content, typically posted by a website visitor, which provides discussion or commentary on other content like blog posts and news articles. Comments are a type of content entity, and can have fields that store text, HTML markup, and other data. Comments are attached to other content entities via Comment fields. See @content_structure_topic for more about content entities and fields.";b:1;s:23:"What is a comment type?";b:1;s:547:"Comments are divided into <em>comment types</em>, which are the entity sub-types for the comment entity type. Each comment type has its own fields and its own form and display settings; each type can be used to comment on a single entity type. You can set up different comment types for different commenting purposes on your web site; for example, you might set up a comment type for recipes that has fields "How did it taste?" and "Did the instructions work?", and another comment type for blog entries that has only a generic comment body field.";b:1;s:19:"What is moderation?";b:1;s:678:"<em>Moderation</em> is a workflow where comments posted by some users on your site are verified before being published, to prevent spam and other bad behavior. The core software provides basic moderation functionality: you can configure permissions so that new comments posted by some user roles start as unpublished until a user with a different role reviews and publishes them. Contributed modules provide additional moderation and spam-reduction functionality, such as requiring untrusted users pass a CAPTCHA test before submitting comments and letting community members flag comments as possible spam. See @users_overview_topic for more about users, permissions, and roles.";b:1;s:29:"Overview of managing comments";b:1;s:61:"The core Comment module provides the following functionality:";b:1;s:16:"Posting comments";b:1;s:183:"Creating comment types; the core Field UI module allows you to attach fields to comment types and attach comment reference fields to other entities so that people can comment on them.";b:1;s:22:"Configuring commenting";b:1;s:38:"Moderating comments as discussed above";b:1;s:23:"Detection and selection";b:1;s:94:"Configure the methods used to decide which language will be used to display text on your site.";b:1;s:36:"What is a language detection method?";b:1;s:583:"A language detection method is a way for your site to decide what language should be used to display text. This decision is made by evaluating a series of detection methods for languages; the first detection method that gets a result will determine which language is used. If you have more than one language on your site, you can configure the detection methods that are used and the order they are evaluated, for both user interface text and content text. Configuration text always uses the interface text method, and most sites use the same detection methods for all types of text.";b:1;s:46:"What language detection methods are available?";b:1;s:137:"The available detection methods depend on what modules you have installed. Some of the most commonly-used language detection methods are:";b:1;s:3:"URL";b:1;s:187:"Use the language from the URL, which can either be in a path prefix like <em>example.com/fr/page_path</em> for French (fr) language, or in a domain like <em>fr.example.com/page_path</em>.";b:1;s:4:"User";b:1;s:70:"For logged in users, use the language they have set in their profiles.";b:1;s:7:"Browser";b:1;s:53:"Use the language preferences from the user's browser.";b:1;s:17:"Selected language";b:1;s:80:"Use the language most recently selected from a <em>Language switcher</em> block.";b:1;s:7:"Session";b:1;s:130:"Use the language from a session parameter or a request parameter; for example, adding <em>?language=fr</em> to the end of the URL.";b:1;s:158:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; <em>Languages</em> &gt; @detection_link.";b:1;s:123:"Check the boxes to enable the desired language detection methods, and uncheck boxes for the methods you do not want to use.";b:1;s:51:"Drag the methods to change their order, if desired.";b:1;s:29:"Click <em>Save settings</em>.";b:1;s:140:"Click <em>Configure</em> on each enabled detection method and verify that its configuration is correct (or update the configuration if not).";b:1;s:9:"Languages";b:1;s:28:"Add a language to your site.";b:1;s:134:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; @languages_link.";b:1;s:28:"Click <em>Add language</em>.";b:1;s:98:"If your language is in the <em>Language name</em> list, select it and click <em>Add language</em>.";b:1;s:210:"If your language is not in the list, select <em>Custom language...</em> and enter the <em>Language code</em>, <em>Language name</em>, and <em>Direction</em> for the language. Click <em>Add custom language</em>.";b:1;s:270:"Wait for the translation system to be updated. Also, if you have the core Update Manager module installed and translations are available for your language, wait for translations to be downloaded. You should be returned to the <em>Languages</em> page when this completes.";b:1;s:111:"Translate user interface text strings from English into a non-English language that is configured on your site.";b:1;s:134:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; @translate_link.";b:1;s:207:"Using the filters, search for a string or set of strings that you want to translate; make sure to select the correct <em>Translation language</em> if you have more than one non-English language on your site.";b:1;s:60:"Enter new translations and click <em>Save translations</em>.";b:1;s:109:"Repeat these steps until all of the desired user interface text is translated for all languages on your site.";b:1;s:29:"Available translation updates";b:1;s:95:"Check the current status of interface translations, and see if there are any updates available.";b:1;s:133:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; @language_link.";b:1;s:162:"Look at the <em>Interface translation</em> column in the language table, to find the percentage of user interface text that has been translated for each language.";b:1;s:190:"In the <em>Manage</em> administrative menu, navigate to <em>Reports</em> &gt; <em>@translation_updates_link</em>. This report is only available if the core Update Status module is installed.";b:1;s:63:"Optionally, click <em>Check manually</em> to update the report.";b:1;s:92:"View the report to find out if any languages have translation updates that you can download.";b:1;s:78:"Import a file (.po extension) containing translations for user interface text.";b:1;s:172:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; <em>User interface translation</em> &gt; @import_link.";b:1;s:122:"Browse to find the <em>Translation file</em> you want to import. Select the language and check the desired import options.";b:1;s:60:"Click <em>Import</em> and wait for your file to be imported.";b:1;s:95:"Use contextual links to access administrative tasks without navigating the administrative menu.";b:1;s:26:"What are contextual links?";b:1;s:592:"<em>Contextual links</em> give users with the <em>Use contextual links</em> permission quick access to administrative tasks related to areas of non-administrative pages. For example, if a page on your site displays a block, the block would have a contextual link that would allow users with permission to configure the block. If the block contains a menu or a view, it would also have a contextual link for editing the menu links or the view. Clicking a contextual link takes you to the related administrative page directly, without needing to navigate through the administrative menu system.";b:1;s:264:"Make sure that the core Contextual Links module is installed, and that you have a role with the <em>Use contextual links</em> permission. Optionally, make sure that a toolbar module is installed (either the core Toolbar module or a contributed module replacement).";b:1;s:68:"Visit a non-administrative page on your site, such as the home page.";b:1;s:78:"Locate a block or another area on the page that you want to edit or configure.";b:1;s:519:"Make the contextual links button visible by hovering your mouse over that area in the page. In most themes, this button looks like a pencil and is placed in the upper right corner of the page area (upper left for right-to-left languages), and hovering will also temporarily outline the affected area. Alternatively, click the contextual links toggle button on the right end of the toolbar (left end for right-to-left languages), which will make all contextual link buttons on the page visible until it is clicked again.";b:1;s:204:"While the contextual links button for the area of interest is visible, click the button to display the list of links for that area. Click a link in the list to visit the corresponding administrative page.";b:1;s:132:"Complete your administrative task and save your settings, or cancel the action. You should be returned to the page you started from.";b:1;s:13:"Content types";b:1;s:149:"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.";b:1;s:240:"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; <em>@content_types_link</em>.";b:1;s:97:"Find the particular sub-type that you want to add the field to, and click <em>Manage fields</em>.";b:1;s:25:"Click <em>Add field</em>.";b:1;s:131:"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.";b:1;s:155:"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.";b:1;s:33:"Click <em>Save and continue</em>.";b:1;s:222:"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>.";b:1;s:422:"On the next screen, optionally edit the settings for the field, which vary depending on what field type you are creating. For all fields, you can edit the <em>Label</em>, <em>Help text</em> (text to be displayed below the field on the content editing page), and <em>Required field</em> (to make it so a value must be entered in order to save the content when editing). You can also configure a default value for the field.";b:1;s:121:"Click <em>Save settings</em>. You should be returned to the <em>Manage fields</em> page, with your new field in the list.";b:1;s:184:"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.";b:1;s:236:"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; <em>@content_types_link</em>.";b:1;s:149:"Find the particular sub-type that you want to configure the editing form for, and click <em>Manage form display</em> in the <em>Operations</em> list.";b:1;s:64:"Use the drag arrows to order the fields in your preferred order.";b:1;s:97:"Drag any fields that you do not wish to see on the editing form to the <em>Disabled</em> section.";b:1;s:72:"In the <em>Widget</em> column, select the widget for editing each field.";b:1;s:111:"After selecting the desired widgets, click the settings gear in each row to change the settings for the widget.";b:1;s:54:"When you are done making changes, click <em>Save</em>.";b:1;s:141:"Test the editing form for your entity sub-type by editing or creating an entity. If needed, return to these steps to further refine the form.";b:1;s:196:"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.";b:1;s:138:"Find the particular sub-type that you want to configure the display of, and click <em>Manage display</em> in the <em>Operations</em> list.";b:1;s:92:"Drag any fields that you do not wish to see in the display to the <em>Disabled</em> section.";b:1;s:314:"In the <em>Label</em> column, select the position for each field label in the display, or <em>- Hidden -</em> to hide a label. You can also choose <em>- Visually Hidden-</em> if you want the label's text to appear in the HTML page, so that screen readers and search engines can read it, but it will not be visible.";b:1;s:78:"In the <em>Format</em> column, select the formatter for displaying each field.";b:1;s:117:"After selecting the desired formatters, click the settings gear in each row to change the settings for the formatter.";b:1;s:127:"Test the display for your entity sub-type by viewing an entity. If needed, return to these steps to further refine the display.";b:1;s:136:"Add an entity reference field to an entity sub-type; see @content_structure_topic for more information on entities and reference fields.";b:1;s:259:"In <em>Add a new field</em>, select the type of reference field you want to add. The <em>Reference</em> section of the select list shows the most common types of reference field; choose <em>Other...</em> if the entity type you want to reference is not listed.";b:1;s:344:"On the next screen, verify that the type of entity you want to reference is shown in <em>Type of item to reference</em>, or select it if not. 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>.";b:1;s:266:"On the next screen, optionally edit the settings for <em>Label</em>, <em>Help text</em> (text to be displayed below the field on the content editing page), and <em>Required field</em> (to make it so a value must be entered in order to save the content when editing).";b:1;s:365:"In the <em>Reference type</em> section, you will usually want to limit the entity sub-types that can be referenced; for example, if you are creating a <em>Content</em> reference, you can check one or two <em>Content type</em> choices. The choices will be easier for content editors to scan if you also choose a sort value (normally the entity title or label field).";b:1;s:24:"Administer content types";b:1;s:84:"Create a new content type. See @content_overview_topic for more about content types.";b:1;s:30:"Who can create a content type?";b:1;s:117:"Users with the <em>@content_permissions_link</em> permission (typically administrators) can create new content types.";b:1;s:109:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@content_types_link</em>.";b:1;s:32:"Click <em>Add content type.</em>";b:1;s:126:"In the <em>Name</em> field, enter a name for the content type, which is how it will be listed in the administrative interface.";b:1;s:158:"Optionally, enter a <em>Description</em> for the content type. You may also want to adjust some of the settings in the vertical tabs section of the edit page.";b:1;s:306:"Click <em>Save and manage fields</em>. Your content type will be created, and assuming you have the core Field UI module installed, you will be taken to the <em>Manage fields</em> page for the content type. (If you do not have the core Field UI module installed, the button will say <em>Save</em> instead.)";b:1;s:177:"If you have the core Field UI module installed, follow the steps in the related topics to add fields to the new content type, set up the editing form, and configure the display.";b:1;s:41:"Adding a Content Type (Drupal User Guide)";b:1;s:48:"Setting Up Content Structure (Drupal User Guide)";b:1;s:23:"What is a content item?";b:1;s:240:"A <em>content item</em> is a type of content entity for page-level content, which can have fields that store text, HTML markup, images, attached files, and other data. See @content_structure_topic for more about content entities and fields.";b:1;s:23:"What is a content type?";b:1;s:295:"Content items are divided into <em>content types</em>, which are the entity sub-types for the content item entity type; each content type has its own fields and display settings. For example, you might set up content types for pages, articles, recipes, events, and blog entries on your web site.";b:1;s:28:"Overview of managing content";b:1;s:463:"The core Node module allows you to define content types, and add and edit content items. The core Field UI module allows you to attach fields to each content type and manage the edit form and display for each content type. See the related topics listed below for specific tasks. Many other core and contributed modules and installation profiles provide pre-defined content types, modify the permission structure for content items, and provide other functionality.";b:1;s:7:"Content";b:1;s:32:"Access the Content overview page";b:1;s:149:"Find a content item and edit it, or update a group of content items in bulk. See @node_overview_topic for more about content types and content items.";b:1;s:30:"Who can find and edit content?";b:1;s:624:"Users with the <em>@content_permissions_link</em> permission can use the <em>Content</em> page to find content. Each content type has its own edit permissions. For example, to edit content of type Article, a user would need the <em>Article: Edit own content</em> permission to edit an article they created, or the <em>Article: Edit any content</em> permission to edit an article someone else created. In addition, users with the <em>Bypass content access control</em> or <em>Administer content</em> permission can edit content items of all types. Some contributed modules change the permission structure for editing content.";b:1;s:79:"In the <em>Manage</em> administrative menu, navigate to <em>@content_link</em>.";b:1;s:66:"Optionally, use filters to reduce the list of content items shown:";b:1;s:42:"<em>Title</em>: key word(s) from the title";b:1;s:21:"<em>Content type</em>";b:1;s:25:"<em>Published status</em>";b:1;s:17:"<em>Language</em>";b:1;s:81:"If you enter or select filter values, click <em>Filter</em> to apply the filters.";b:1;s:88:"Optionally, sort the list by clicking a column header. Click again to reverse the order.";b:1;s:156:"To edit the title or other field values for one content item, click <em>Edit</em> in the row of the content item. Update the values and click <em>Save</em>.";b:1;s:430:"A few types of edits can be done in bulk to multiple content items. For example, to publish several unpublished content items, check the boxes in the left column (right column in right-to-left languages) to select the desired content items. For <em>Action</em>, select the <em>Publish content</em> action. Click <em>Apply to selected items</em> to make the change. The other actions under <em>Action</em> work in a similar manner.";b:1;s:41:"Basic Page Management (Drupal User Guide)";b:1;s:42:"Editing a Content Item (Drupal User Guide)";b:1;s:110:"Create and publish a content item. See @content_overview_topic for more about content types and content items.";b:1;s:23:"Who can create content?";b:1;s:511:"Users with the <em>@content_permissions_link</em> permission can visit the <em>Content</em> page as described in this topic. Each content type has its own create permissions. For example, to create content of type Article, a user would need the Article: Create new content permission. In addition, users with the <em>Bypass content access control</em> or <em>Administer content</em> permission can create content items of all types. Some contributed modules change the permission structure for creating content.";b:1;s:27:"Click <em>Add content</em>.";b:1;s:153:"If there is more than one content type defined on your site that you have permission to create, click the name of the type of content you want to create.";b:1;s:217:"On the content edit form, enter the <em>Title</em> of your content, which will show as the page title when the content item is displayed on a page, and also as the label for the content item in administration screens.";b:1;s:79:"Fill in the other fields shown on the edit form for this specific content type.";b:1;s:193:"Leave the <em>Published</em> field checked to publish the content immediately, or uncheck it to make it unpublished. Unpublished content is generally not shown to non-administrative site users.";b:1;s:58:"Optionally, click <em>Preview</em> to preview the content.";b:1;s:66:"Click <em>Save</em>. You will see the content displayed on a page.";b:1;s:43:"Creating a Content Item (Drupal User Guide)";b:1;s:32:"What content visits are tracked?";b:1;s:413:"The core History module tracks when each logged-in user has most recently visited each content item page on the site. This allows content to be marked as <em>new</em> or <em>updated</em> for each user, meaning that it was newly created or has been updated since the last time they visited its page. These records are kept for one month, meaning that content older than one month is never marked as new or updated.";b:1;s:63:"What options are available for using this tracking information?";b:1;s:288:"You can display the new/updated status of content by creating or editing a view. There is a <em>Has new content</em> field for <em>Content</em> views, which displays the new/updated marker. There is also a <em>Has new content</em> filter, which limits the view to new and updated content.";b:1;s:12:"Image styles";b:1;s:121:"Add a new image style, which can be used to process and display images. See @media_topic for an overview of image styles.";b:1;s:117:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Media</em> &gt; @styles_link.";b:1;s:31:"Click <em>Add image style</em>.";b:1;s:83:"Enter a descriptive <em>Image style name</em>, and click <em>Create new style</em>.";b:1;s:72:"Under <em>Effect</em>, choose an effect to apply and click <em>Add</em>.";b:1;s:287:"Configure the effect on the next page. Most effects require some additional configuration after they are added.  For example, for the <em>Crop</em> effect, enter the <em>Width</em> and <em>Height</em> to crop the image to, and choose the <em>Anchor</em> point. Click <em>Add effect</em>.";b:1;s:71:"Repeat the previous two steps until all of the effects have been added.";b:1;s:88:"Drag to change the order of the effects. Then click <em>Save</em> to save the new order.";b:1;s:220:"The image style can now be used to format a field containing an image in your layouts or traditional field displays. It can also be used as part of a responsive image style. See related topics below for more information.";b:1;s:15:"What is a view?";b:1;s:337:"A <em>view</em> is a listing of items on your site; for example, a block showing the most recent comments, a page listing news items, or a list of registered users. The listings can be formatted in a table, grid, list, calendar, RSS feed, and other formats (some output formats may require you to install additional contributed modules).";b:1;s:34:"What are the components of a view?";b:1;s:291:"When you first create a view, you will specify what type of <em>base data</em> is being displayed in the view, which cannot be changed. After choosing a base data type, you can edit the following components, which allow you to specify which data to output, in what order, and in what format:";b:1;s:144:"<em>Displays</em>: whether the output goes to a page, block, feed, etc.; a single view can have multiple displays, each with different settings.";b:1;s:100:"<em>Format</em>: the output style for each display, such as content item, grid, table, or HTML list.";b:1;s:72:"<em>Fields</em>: if the Format allows, the particular fields to display.";b:1;s:207:"<em>Filter criteria</em>: criteria to limit the data to output, such as whether the content is published, the type of content, etc. Filters can be <em>exposed</em> to let users choose how to filter the data.";b:1;s:84:"<em>Sort criteria</em>: how to order the data. Sorting can also be exposed to users.";b:1;s:274:"<em>Page settings</em>, <em>Block settings</em>, etc.: settings specific to the display type, such as the URL for a page display. Most display types support an <em>Access</em> setting, where you can choose a Permission or Role that a user must have in order to see the view.";b:1;s:97:"<em>Header</em> and <em>Footer</em>: content to display at the top or bottom of the view display.";b:1;s:100:"<em>No results behavior</em>: what to do if the filter criteria result in having no data to display.";b:1;s:104:"<em>Pager</em>: how many items to display, and how to paginate if there are additional items to display.";b:1;s:187:"<em>Advanced</em> &gt; <em>Contextual filters</em>: like regular filters, except the criteria come from the <em>context</em>, such as the current date, page the view is displayed on, etc.";b:1;s:195:"<em>Advanced</em> &gt; <em>Relationships</em>: additional data to pull in and display, related in some way to the base data of the view (such as data about the user who created the content item).";b:1;s:120:"<em>Advanced</em> &gt; <em>Exposed form</em>: if you have exposed filters or sorts, how to display the form to the user.";b:1;s:25:"What are bulk operations?";b:1;s:488:"Views using a table display format can include a bulk operations form, which allows users with sufficient permission to select one or more items from the view and apply an administrative action to them. The bulk actions available are specific to the base data type of the view; for example, a view of content items could support bulk publishing and unpublishing actions. If you have the core Actions UI module installed, see the related topic "Configuring actions" for more about actions.";b:1;s:23:"Managing views overview";b:1;s:252:"The core Views module handles the display of views, and the core Views UI module allows you to create, edit, and delete views in the administrative interface. See the related topics listed below for specific tasks (if the Views UI module is installed).";b:1;s:123:"<a href="https://www.drupal.org/docs/user_guide/en/views-chapter.html">Creating Listings with Views (Drupal User Guide)</a>";b:1;s:5:"Menus";b:1;s:18:"Create a new menu.";b:1;s:98:"In the <em>Manage</em> administration menu, navigate <em>Structure</em> &gt; @structure_menu_link.";b:1;s:24:"Click <em>Add menu</em>.";b:1;s:203:"Enter the title for the menu, which is used as the default block title if the menu is displayed as a block. If desired, also edit the machine name of the menu, which is by default derived from the title.";b:1;s:79:"Enter an administrative summary, which is displayed on the <em>Menus</em> page.";b:1;s:74:"If your site has more than one language, choose the language for the menu.";b:1;s:178:"Click <em>Save</em>. You will be on the menu editing page, ready to add links to the menu if the core Custom Menu Links module is installed; see related topics for further tasks.";b:1;s:152:"Add a link to a menu. Note that you can also add a link to a menu from the content edit page if menu settings have been configured for the content type.";b:1;s:101:"In the <em>Manage</em> administration menu, navigate to <em>Structure</em> &gt; @structure_menu_link.";b:1;s:84:"Locate the desired menu and click <em>Add link</em> in the <em>Operations</em> list.";b:1;s:51:"Enter the <em>Menu link title</em> to be displayed.";b:1;s:46:"Enter the <em>Link</em>, one of the following:";b:1;s:44:"An internal path, such as <em>/node/add</em>";b:1;s:19:"A full external URL";b:1;s:83:"Start typing the title of a content item and select it when the full title comes up";b:1;s:92:"<em>&lt;nolink&gt;</em> to display the <em>Menu link title</em> as plain text without a link";b:1;s:61:"<em>&lt;front&gt;</em> to link to the front page of your site";b:1;s:88:"Make sure that <em>Enabled</em> is checked; if not, the menu link will not be displayed.";b:1;s:99:"Optionally, enter a <em>Description</em>, which will be displayed when a user hovers over the link.";b:1;s:125:"Optionally, check <em>Show as expanded</em> to automatically show the children of this link (if any) when this link is shown.";b:1;s:102:"Optionally, select the <em>Parent link</em>, if this menu link should be a child of another menu link.";b:1;s:92:"Click <em>Save</em>. You will be returned to the <em>Add link</em> page to add another link.";b:1;s:97:"Locate the menu you just added a link to and click <em>Edit</em> in the <em>Operations</em> list.";b:1;s:125:"Verify that the order of links is correct. If it is not, drag menu links until the order is correct, and click <em>Save</em>.";b:1;s:197:"For an existing content type, configure the available menus that will be shown as options on content editing screens; links to content items of this type can be added to these menus during editing.";b:1;s:100:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; @content_types_link.";b:1;s:103:"Locate the content type you want to configure, and click <em>Edit</em> in the <em>Operations</em> list.";b:1;s:117:"Under <em>Menu settings</em>, check the menus that you want to be available when editing a content item of this type.";b:1;s:130:"Optionally, select the <em>Default parent item</em>, to put links to content items under a default location in the menu structure.";b:1;s:67:"Disable menu links or change the order and hierarchy of menu links.";b:1;s:60:"Click <em>Edit menu</em> for the menu that you want to edit.";b:1;s:100:"Drag menu links into a new order, or check/uncheck <em>Enabled</em> to enable or disable menu links.";b:1;s:41:"Click <em>Save</em> to save your changes.";b:1;s:27:"Create and edit URL aliases";b:1;s:178:"Give a content item page a human- or SEO-friendly URL alias; you can follow similar steps to create an alias for a taxonomy term page. See @overview_topic for more about aliases.";b:1;s:27:"Who can create URL aliases?";b:1;s:168:"Users with the <em>@path_permissions_link</em> permission can create aliases. To follow the steps in this topic, you will also need permission to edit the content item.";b:1;s:142:"Locate and open the content edit form for the content item, or create a new content item (see related topics on creating and editing content).";b:1;s:143:"Under <em>URL alias</em> on the edit form, enter the desired alias (for example, "/about-us"). Make sure the alias starts with a "/" character.";b:1;s:106:"Verify that the page can be visited with the new alias, for example <em>https://example.com/about-us</em>.";b:1;s:22:"Administer URL aliases";b:1;s:11:"URL aliases";b:1;s:118:"Change an existing URL alias, to correct the path or the alias value. See @path_overview_topic for more about aliases.";b:1;s:27:"Who can manage URL aliases?";b:1;s:75:"Users with the <em>@path_permissions_link</em> permission can edit aliases.";b:1;s:192:"In the <em>Manage</em> administration menu, navigate to <em>Configuration</em> &gt; <em>Search and metadata</em> &gt; <em>@path_aliases_link</em>. A list of all the site's aliases will appear.";b:1;s:87:"Click <em>Edit</em> in the dropdown button for the alias that you would like to change.";b:1;s:99:"Make the required changes and click <em>Save</em>. You will be returned to the URL alias list page.";b:1;s:81:"Note that you can also add new aliases from this page, for any path on your site.";b:1;s:14:"What is a URL?";b:1;s:339:"URL is the abbreviation for "Uniform Resource Locator", which is the page's address on the web. It is the "name" by which a browser identifies a page to display. In the example "Visit us at <em>example.com</em>.", <em>https://example.com</em> would be the URL for the home page of your website. Users use URLs to locate content on the web.";b:1;s:15:"What is a path?";b:1;s:256:"A path is the unique, last part of the URL for a specific function or piece of content. For example, for a page whose full URL is <em>https://example.com/node/7</em>, the path is <em>node/7</em>. Here are some examples of paths you might find in your site:";b:1;s:42:"node/7: Path to a particular content item.";b:1;s:46:"taxonomy/term/6: Path to a taxonomy term page.";b:1;s:36:"user/3: Path to a user profile page.";b:1;s:17:"What is an alias?";b:1;s:317:"The core software allows you to provide more understandable URLs for pages on your site, which are called <em>aliases</em>. For example, if you have an "About Us" page with the path <em>node/7</em>, you can set up an alias of <em>about</em> so that your visitors will see it as <em>https://www.example.com/about</em>.";b:1;s:48:"Overview of configuring paths, aliases, and URLs";b:1;s:298:"The core Path module provides the URL aliasing functionality. The contributed <a href="https://www.drupal.org/project/pathauto">Pathauto</a> module allows you to configure automatically-generated URL aliases for content items and other pages. See the related topics listed below for specific tasks.";b:1;s:53:"Concept: Paths, Aliases, and URLs (Drupal User Guide)";b:1;s:72:"Create, view, and use a set of shortcuts to access administrative pages.";b:1;s:19:"What are shortcuts?";b:1;s:763:"<em>Shortcuts</em> are quick links to administrative pages; they are managed by the core Shortcut module. A site can have one or more <em>shortcut sets</em>, which can be shared by one or more users (by default, there is only one set shared by all users); each set contains a limited number of shortcuts. Users need <em>Use shortcuts</em> permission to view shortcuts; <em>Edit current shortcut set</em> permission to add, delete, or edit the shortcuts in the set assigned to them; and <em>Select any shortcut set</em> permission to select a different shortcut set when editing their user profile. There is also an <em>Administer shortcuts</em> permission, which allows an administrator to do any of these actions, as well as select shortcut sets for other users.";b:1;s:284:"Make sure that the core Shortcut module is installed, and that you have a role with <em>Edit current shortcut set</em> or <em>Administer shortcuts</em> permission. Also, make sure that a toolbar module is installed (either the core Toolbar module or a contributed module replacement).";b:1;s:71:"Navigate to an administrative page that you want in your shortcut list.";b:1;s:293:"Click the shortcut link to add the page to your shortcut list -- in the core Claro administrative theme, the link looks like a star, and is displayed next to the page title. However, if the page is already in your shortcut set, clicking the shortcut link will remove it from your shortcut set.";b:1;s:72:"Repeat until all the desired links have been added to your shortcut set.";b:1;s:104:"Click <em>Shortcuts</em> in the toolbar to display your shortcuts, and verify that the list is complete.";b:1;s:157:"Optionally, click <em>Edit shortcuts</em> at the right end of the shortcut list (left end in right-to-left languages), to remove links or change their order.";b:1;s:77:"Click any link in the shortcut bar to go directly to the administrative page.";b:1;s:33:"Administer vocabularies and terms";b:1;s:8:"Taxonomy";b:1;s:214:"Create a taxonomy vocabulary and add a reference field for that vocabulary to a content entity. See @taxonomy_overview_topic for information about taxonomy and @content_structure_topic for more on content entities.";b:1;s:40:"Who can configure a taxonomy vocabulary?";b:1;s:290:"Users with the <em>@taxonomy_permissions_link</em> permission can configure a vocabulary. To add a field in the administrative interface, the core Field UI module must be installed, and you will also need the <em>Administer fields</em> permission for the entity you are adding the field to.";b:1;s:110:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@taxonomy_admin_link</em>.";b:1;s:30:"Click <em>Add vocabulary</em>.";b:1;s:182:"In the <em>Name</em> field, enter a name for the vocabulary (for example "Ingredients"), which is how it will be shown in the administrative interface. Optionally, add a description.";b:1;s:123:"Click <em>Save</em>. Your vocabulary will be created and you will see the page that lists all the terms in this vocabulary.";b:1;s:272:"Optionally, click <em>Add term</em> to add a term to the new vocabulary. In the <em>Name</em> field, enter the term name (for example "Butter"). Click <em>Save</em>. You will receive a confirmation about the term you created. You may optionally continue to add more terms.";b:1;s:328:"If you have the Field UI module installed, follow the instructions on the related <em>Adding a reference field to an entity sub-type</em> topic to add a taxonomy reference field to the entity type of your choice. The settings page will allow you to choose the <em>Vocabulary</em> that you created as the vocabulary to reference.";b:1;s:98:"You may also want to configure the display and form display of the new field (see related topics).";b:1;s:41:"Setting Up a Taxonomy (Drupal User Guide)";b:1;s:17:"What is taxonomy?";b:1;s:773:"<em>Taxonomy</em> is used to classify website content. One common example of taxonomy is the tags used to classify or categorize posts in a blog website; a cooking website could use an ingredients taxonomy to classify recipes. Individual taxonomy items are known as <em>terms</em> (the blog tags or recipe ingredients in these examples); and a set of terms is known as a <em>vocabulary</em> (the set of all blog post tags, or the set of all recipe ingredients in these examples). Technically, taxonomy terms are an entity type and the entity subtypes are the vocabularies; see @content_structure_topic for more on content entities. Like other entities, taxonomy terms can have fields attached; for instance, you could set up an image field to contain an icon for each term.";b:1;s:317:"An individual vocabulary can organize its terms in a hierarchy, or it could be flat. For example, blog tags normally have a flat structure, while a recipe ingredients vocabulary could be hierarchical (for example, tomatoes could be a sub-term of vegetables, and under tomatoes, you could have green and red tomatoes).";b:1;s:221:"Taxonomy terms are normally attached as reference fields to other content entities, which is how you can use them to classify content. When you set up a taxonomy reference field, you can let users enter terms in two ways:";b:1;s:12:"Free tagging";b:1;s:59:"New terms can be created right on the content editing form.";b:1;s:19:"Fixed list of terms";b:1;s:145:"The list of terms is curated and managed outside the content editing form, and users can only select from the existing list when editing content.";b:1;s:338:"Taxonomy reference fields can be added to any entity, such as user accounts, content blocks, or regular content items. If you use them to classify regular content items, your site will automatically be set up with taxonomy listing pages for each term; each of these pages lists all of the content items that are classified with that term.";b:1;s:29:"Overview of managing taxonomy";b:1;s:317:"The core Taxonomy module allows you to create and edit taxonomy vocabularies and taxonomy terms. The core Field UI module provides a user interface for adding fields to entities, including the taxonomy reference field, and configuring field editing and display. See the related topics listed below for specific tasks.";b:1;s:37:"Concept: Taxonomy (Drupal User Guide)";b:1;s:5:"Views";b:1;s:62:"Create a new view to list content or other items on your site.";b:1;s:101:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@views_link</em>.";b:1;s:24:"Click <em>Add view</em>.";b:1;s:123:"In the <em>View name</em> field, enter a name for the view, which is how it will be listed in the administrative interface.";b:1;s:126:"In <em>View settings</em> &gt; <em>Show</em>, select the base data type to display in your view. This cannot be changed later.";b:1;s:117:"Optionally, select or enter filtering, sorting, and page/block display settings; these can be added or changed later.";b:1;s:113:"Click <em>Save and edit</em>. Your view will be created; edit it following the steps in the related topics below.";b:1;s:160:"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.";b:1;s:209:"If you are not already editing your view, in the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@views_link</em>. Find the view you want to edit, and click its <em>Edit</em> link.";b:1;s:44:"Under <em>Displays</em>, click <em>Add</em>.";b:1;s:217:"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.";b:1;s:139:"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.";b:1;s:80:"Follow the steps in @view_edit_topic to edit the other settings for the display.";b:1;s:16:"Administer views";b:1;s:214:"Add one or more existing actions as bulk operations to an existing table-style view. If you have the core Actions UI module installed, see the related topic "Configuring actions" for more information about actions.";b:1;s:19:"Who can edit views?";b:1;s:132:"The core Views UI module will need to be installed and you will need <em>@views_permissions</em> permission in order to edit a view.";b:1;s:126:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <em>@views</em>. A list of all views is shown.";b:1;s:179:"Find the view that you would like to edit, and click <em>Edit</em> from the dropdown button. Note that bulk operations work best in a view with a Page display, and a Table format.";b:1;s:469:"If there is not already an <em>Operations bulk form</em> in the <em>Fields</em> list for the view, click <em>Add</em> in the <em>Fields</em> section to add it. (The exact name of the bulk form field will vary, and may contain keywords like "bulk update", "form element" or "operations" -- not to be confused with <em>operations links</em>, which are applied to each item in a row.) If the bulk operations field already exists, click the field name to edit its settings.";b:1;s:125:"Check the action(s) you want to make available in the <em>Selected actions</em> list and click <em>Apply (all displays)</em>.";b:1;s:265:"Verify that the <em>Access</em> settings for the view are at least as restrictive as the permissions necessary to perform the bulk operations. People with permission to see the view, but who don't have permission to do the bulk operations, will experience problems.";b:1;s:84:"Click <em>Save</em>. The action(s) will be available as bulk operations in the view.";b:1;s:87:"Edit an existing view display, to modify what data is displayed or how it is displayed.";b:1;s:60:"Under <em>Displays</em>, click the display you want to edit.";b:1;s:154:"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.)";b:1;s:290:"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.";b:1;s:585:"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.";b:1;s:162:"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.";b:1;s:154:"When you have verified the display, click <em>Save</em>. Alternatively, if you have made mistakes and want to discard your changes, click <em>Cancel</em>.";b:1;s:11:"Media types";b:1;s:256:"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.";b:1;s:92:"In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; @media_link.";b:1;s:119:"If there is not already a media type for the type of media you want to use on your site, click <em>Add media type</em>.";b:1;s:105:"Enter a <em>Name</em> and <em>Description</em> for your media type, and select the <em>Media source</em>.";b:1;s:295:"For most media sources, there is additional information that will need to be stored with your media item, in a field on your media type. Under <em>Media source configuration</em>, select an existing field to re-use to store this information, or select <em> - Create -</em> to create a new field.";b:1;s:113:"Note the types of metadata in the <em>Field mapping</em> section that can be mapped to fields on your media type.";b:1;s:194:"Optionally, add additional fields for the metadata noted above or for other information that you want to store to your media type by clicking on <em>Manage fields</em> (see related topic below).";b:1;s:153:"If you have added metadata fields, click <em>Edit</em>. Under <em>Field mapping</em>, select the fields you added for each piece of metadata information.";b:1;s:122:"You can now use this media type by adding a Media reference field to any content entity sub-type. See related topic below.";b:1;s:136:"Configure an entity sub-type to have its fields displayed using a layout (see @content_structure_topic for more on entities and fields).";b:1;s:31:"What are the parts of a layout?";b:1;s:273:"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).";b:1;s:227:"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; @content_types_link.";b:1;s:133:"Find the particular sub-type that you want to create a layout for, and click <em>Manage display</em> in the <em>Operations</em> list.";b:1;s:267:"Under <em>Layout options</em>, check <em>Use Layout Builder</em>. You can also check the box below to allow each entity item to have its layout individually customized (if it is left unchecked, the site will use the same layout for all items of this entity sub-type).";b:1;s:157:"Click <em>Save</em>. You will be returned to the <em>Manage display</em> page, but you will no longer see the table of fields of the classic display manager.";b:1;s:182:"Click <em>Manage layout</em> to enter layout management view. A default layout will be set up for you, with a single one-column section containing the fields on your entity sub-type.";b:1;s:209:"To remove the default section and start from an empty layout, find and click the <em>Remove</em> button for the default section, which looks like an X. Confirm by clicking <em>Remove</em> in the pop-up dialog.";b:1;s:406:"Add new sections, each with one to four columns, to your layout. For instance, you might want a one-column section at the top, a two-column section in the middle, and then a one-column section at the bottom. To add a section, click <em>Add section</em> and click the desired number of columns. For multi-column sections, set the column width percentages and click <em>Add section</em> in the pop-up dialog.";b:1;s:445:"In each section, click <em>Add block</em> to add a block. You will see a list of the blocks available on your site, plus a section called <em>Content fields</em> with a block for each field on your content item. Each block can be configured, if desired, with a <em>Title</em>, and for content field blocks, you can also configure the field formatter. Continue to add blocks to your sections until all the desired blocks and fields are displayed.";b:1;s:190:"Verify your layout. You can check <em>Show content preview</em> to show a preview of what your layout will look like, or uncheck it to see the names of the fields and blocks in each section.";b:1;s:271:"If needed, reorder the blocks by dragging them to new locations. If you hover over a block, a contextual menu will appear that will let you change the configuration of the block, remove the block, or <em>Move</em> blocks within the section using a more compact interface.";b:1;s:68:"When you are satisfied with your layout, click <em>Save layout</em>.";b:1;s:24:"Creating layout defaults";b:1;s:44:"Building Layouts Using the Layout Builder UI";b:1;s:32:"Content language and translation";b:1;s:404:"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.";b:1;s:154:"In the <em>Manage</em> administrative menu, navigate to <em>Configuration</em> &gt; <em>Region and language</em> &gt; <em>@translation_settings_link</em>.";b:1;s:235:"Under <em>Custom language settings</em>, find the content entity types that should have customized language settings on your site. Check the box next to each one. A section will appear below the list with settings for that entity type.";b:1;s:259:"For each entity type you checked, in the settings section below check the boxes for each entity sub-type that should be <em>Translatable</em> on your site. If the entity type does not have sub-types, there is just one check box for the entity type as a whole.";b:1;s:228:"For each entity type or subtype, select the <em>Default language</em>. Also, if you want to have languages other than the default available when you create content, check <em>Show language selector on create and edit pages</em>.";b:1;s:318:"For each <em>Translatable</em> type or sub-type, look through the list of fields for the type or sub-type, and verify that only the fields that should be translatable are checked. For example, you would probably want to translate a <em>Title</em> field, but you might not want to translate a <em>Start date</em> field.";b:1;s:72:"Click <em>Save configuration</em> when all of your changes are complete.";b:1;}