Source string (Built-in English)
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>.
Translated string (German)
Source string (Built-in English)
Optionally, change other settings on the form.
Translated string (German)
Source string (Built-in English)
Click <em>Create new account</em>.
Translated string (German)
Source string (Built-in English)
You will be left on the <em>Add user</em> page; repeat these steps if you have more user accounts to create.
Translated string (German)
Source string (Built-in English)
Create a new role.
Translated string (German)
Source string (Built-in English)
In the <em>Manage</em> administrative menu, navigate to <em>People</em> > <em>@roles_link</em>.
Translated string (German)
Source string (Built-in English)
Click <em>Add role</em>.
Translated string (German)
Source string (Built-in English)
Enter the desired <em>Role name</em>. If desired, click <em>Edit</em> to change the <em>Machine name</em> for the role.
Translated string (German)
Source string (Built-in English)
Click <em>Save</em>. You should be returned to the <em>Roles</em> page and your new role should be in the role list.
Translated string (German)
Source string (Built-in English)
System path
Translated string (German)
Source string (Built-in English)
Filter aliases
Translated string (German)
Source string (Built-in English)
An alias defines a different name for an existing URL path - for example, the alias 'about' for the URL path 'node/1'. A URL path can have multiple aliases.
Translated string (German)
Source string (Built-in English)
Add alias
Translated string (German)
Source string (Built-in English)
Change an existing URL alias, to correct the path or the alias value. See @path_overview_topic for more about aliases.
Translated string (German)
Source string (Built-in English)
Who can manage URL aliases?
Translated string (German)
Source string (Built-in English)
Users with the <em>@path_permissions_link</em> permission can edit aliases.
Translated string (German)
Source string (Built-in English)
In the <em>Manage</em> administration menu, navigate to <em>Configuration</em> > <em>Search and metadata</em> > <em>@path_aliases_link</em>. A list of all the site's aliases will appear.
Translated string (German)
Source string (Built-in English)
Click <em>Edit</em> in the dropdown button for the alias that you would like to change.
Translated string (German)
Source string (Built-in English)
Make the required changes and click <em>Save</em>. You will be returned to the URL alias list page.
Translated string (German)
Source string (Built-in English)
Note that you can also add new aliases from this page, for any path on your site.
Translated string (German)
Source string (Built-in English)
What content visits are tracked?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
What options are available for using this tracking information?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
What are breakpoints?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
What are media queries?
Translated string (German)
Source string (Built-in English)
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.
Translated string (German)
Source string (Built-in English)
What are resolution multipliers?
Translated string (German)
Source string (Built-in English)
What is a breakpoint group?
Translated string (German)