Source string (Built-in English)
Visit the <a href=":project_link">jQuery UI project page</a> on Drupal.org for more information about this module.
Translated string (German)
Source string (Built-in English)
The Update Manager module periodically checks for new versions of your site's software (including contributed modules and themes), and alerts administrators to available updates. The Update Manager system is also used by some other modules to manage updates and downloads; for example, the Interface Translation module uses the Update Manager to download translations from the localization server. Note that whenever the Update Manager system is used, anonymous usage statistics are sent to Drupal.org. If desired, you may uninstall the Update Manager module from the <a href=":modules">Extend page</a>; if you do so, functionality that depends on the Update Manager system will not work. For more information, see the <a href=":update">online documentation for the Update Manager module</a>.
Translated string (German)
Source string (Built-in English)
The Update Manager also allows administrators to add and update modules and themes through the administration interface.
Translated string (German)
Source string (Built-in English)
Checking for available updates
Translated string (German)
Source string (Built-in English)
The <a href=":update-report">Available updates report</a> displays core, contributed modules, and themes for which there are new releases available for download. On the report page, you can also check manually for updates. You can configure the frequency of update checks, which are performed during cron runs, and whether notifications are sent on the <a href=":update-settings">Update Manager settings page</a>.
Translated string (German)
Source string (Built-in English)
Performing updates through the Update page
Translated string (German)
Source string (Built-in English)
The Update Manager module allows administrators to perform updates directly from the <a href=":update-page">Update page</a>. It lists all available updates, and you can confirm whether you want to download them. If you don't have sufficient access rights to your web server, you could be prompted for your FTP/SSH password. Afterwards the files are transferred into your site installation, overwriting your old files. Direct links to the Update page are also displayed on the <a href=":modules_page">Extend page</a> and the <a href=":themes_page">Appearance page</a>.
Translated string (German)
Source string (Built-in English)
The History module keeps track of which content a user has read. It marks content as <em>new</em> or <em>updated</em> depending on the last time the user viewed it. History records that are older than one month are removed during cron, which means that content older than one month is always considered <em>read</em>. The History module does not have a user interface but it provides a filter to <a href=":views-help">Views</a> to show new or updated content. For more information, see the <a href=":url">online documentation for the History module</a>.
Translated string (German)
Source string (Built-in English)
Configuring help search
Translated string (German)
Source string (Built-in English)
What is a help topic?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
Where are help topics listed?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
How are help topics provided?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
How are help topics translated?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
How can users search for help topics?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
Help Topics Standards
Translated string (German)
Source string (Built-in English)
Translating user interface text
Translated string (German)
Source string (Built-in English)
The Block Content module allows you to create and manage custom <em>block types</em> and <em>content-containing blocks</em>. For more information, see the <a href=":online-help">online documentation for the Block Content module</a>.
Translated string (German)
Source string (Built-in English)
Creating and managing block types
Translated string (German)
Source string (Built-in English)
Users with the <em>Administer blocks</em> permission can create and edit block types with fields and display settings, from the <a href=":types">Block types</a> page under the Structure menu. For more information about managing fields and display settings, see the <a href=":field-ui">Field UI module help</a> and <a href=":field">Field module help</a>.
Translated string (German)
Source string (Built-in English)
Creating content blocks
Translated string (German)
Source string (Built-in English)
Users with the <em>Administer blocks</em> permission can create, edit, and delete content blocks of each defined block type, from the <a href=":block-library">Content blocks page</a>. After creating a block, place it in a region from the <a href=":blocks">Block layout page</a>, just like blocks provided by other modules.
Translated string (German)
Source string (Built-in English)
What are search pages?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
What modules provide site search?
Translated string (German)