Initial Drupal 11 with DDEV setup
This commit is contained in:
gluebox
@ -0,0 +1,36 @@
|
||||
---
|
||||
label: 'Creating a content item'
|
||||
related:
|
||||
- node.overview
|
||||
- node.creating_type
|
||||
- path.creating_alias
|
||||
---
|
||||
{% set content_link_text %}
|
||||
{% trans %}Content{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_link = render_var(help_route_link(content_link_text, 'system.admin_content')) %}
|
||||
{% set content_permissions_link_text %}
|
||||
{% trans %}Access the Content overview page{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_permissions_link = render_var(help_route_link(content_permissions_link_text, 'user.admin_permissions.module', {'modules': 'node'})) %}
|
||||
{% set content_overview_topic = render_var(help_topic_link('node.overview')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Create and publish a content item. See {{ content_overview_topic }} for more about content types and content items.{% endtrans %}</p>
|
||||
<h2>{% trans %}Who can create content?{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>{{ content_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Add content</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
<li>{% trans %}Fill in the other fields shown on the edit form for this specific content type.{% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
<li>{% trans %}Optionally, click <em>Preview</em> to preview the content.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Save</em>. You will see the content displayed on a page.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/content-chapter.html">{% trans %}Basic Page Management (Drupal User Guide){% endtrans %}</a></li>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/content-create.html">{% trans %}Creating a Content Item (Drupal User Guide){% endtrans %}</a></li>
|
||||
</ul>
|
||||
@ -0,0 +1,36 @@
|
||||
---
|
||||
label: 'Creating a content type'
|
||||
related:
|
||||
- node.overview
|
||||
- core.content_structure
|
||||
- field_ui.add_field
|
||||
- field_ui.manage_display
|
||||
- field_ui.manage_form
|
||||
---
|
||||
{% set content_permissions_link_text %}
|
||||
{% trans %}Administer content types{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_permissions_link = render_var(help_route_link(content_permissions_link_text, 'user.admin_permissions.module', {'modules': 'node'})) %}
|
||||
{% set content_types_link_text %}
|
||||
{% trans %}Content types{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_types_link = render_var(help_route_link(content_types_link_text, 'entity.node_type.collection')) %}
|
||||
{% set content_overview_topic = render_var(help_topic_link('node.overview')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}Create a new content type. See {{ content_overview_topic }} for more about content types.{% endtrans %}</p>
|
||||
<h2>{% trans %}Who can create a content type?{% endtrans %}</h2>
|
||||
<p>{% trans %}Users with the <em>{{ content_permissions_link }}</em> permission (typically administrators) can create new content types.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> > <em>{{ content_types_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Click <em>Add content type.</em>{% endtrans %}</li>
|
||||
<li>{% trans %}In the <em>Name</em> field, enter a name for the content type, which is how it will be listed in the administrative interface.{% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
<li>{% trans %}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.){% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/structure-content-type.html">{% trans %}Adding a Content Type (Drupal User Guide){% endtrans %}</a></li>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/content-structure-chapter.html">{% trans %}Setting Up Content Structure (Drupal User Guide){% endtrans %}</a></li>
|
||||
</ul>
|
||||
39
web/core/modules/node/help_topics/node.editing.html.twig
Normal file
39
web/core/modules/node/help_topics/node.editing.html.twig
Normal file
@ -0,0 +1,39 @@
|
||||
---
|
||||
label: 'Editing a content item'
|
||||
related:
|
||||
- node.overview
|
||||
- node.creating_content
|
||||
---
|
||||
{% set content_link_text %}
|
||||
{% trans %}Content{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_link = render_var(help_route_link(content_link_text, 'system.admin_content')) %}
|
||||
{% set content_permissions_link_text %}
|
||||
{% trans %}Access the Content overview page{% endtrans %}
|
||||
{% endset %}
|
||||
{% set content_permissions_link = render_var(help_route_link(content_permissions_link_text, 'user.admin_permissions.module', {'modules': 'node'})) %}
|
||||
{% set node_overview_topic = render_var(help_topic_link('node.overview')) %}
|
||||
<h2>{% trans %}Goal{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
<h2>{% trans %}Who can find and edit content?{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
<h2>{% trans %}Steps{% endtrans %}</h2>
|
||||
<ol>
|
||||
<li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>{{ content_link }}</em>.{% endtrans %}</li>
|
||||
<li>{% trans %}Optionally, use filters to reduce the list of content items shown:{% endtrans %}
|
||||
<ul>
|
||||
<li>{% trans %}<em>Title</em>: key word(s) from the title{% endtrans %}</li>
|
||||
<li>{% trans %}<em>Content type</em>{% endtrans %}</li>
|
||||
<li>{% trans %}<em>Published status</em>{% endtrans %}</li>
|
||||
<li>{% trans %}<em>Language</em>{% endtrans %}</li>
|
||||
</ul>
|
||||
{% trans %}If you enter or select filter values, click <em>Filter</em> to apply the filters.{% endtrans %}</li>
|
||||
<li>{% trans %}Optionally, sort the list by clicking a column header. Click again to reverse the order.{% endtrans %}</li>
|
||||
<li>{% trans %}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>.{% endtrans %}</li>
|
||||
<li>{% trans %}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.{% endtrans %}</li>
|
||||
</ol>
|
||||
<h2>{% trans %}Additional resources{% endtrans %}</h2>
|
||||
<ul>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/content-chapter.html">{% trans %}Basic Page Management (Drupal User Guide){% endtrans %}</a></li>
|
||||
<li><a href="https://www.drupal.org/docs/user_guide/en/content-edit.html">{% trans %}Editing a Content Item (Drupal User Guide){% endtrans %}</a></li>
|
||||
</ul>
|
||||
19
web/core/modules/node/help_topics/node.overview.html.twig
Normal file
19
web/core/modules/node/help_topics/node.overview.html.twig
Normal file
@ -0,0 +1,19 @@
|
||||
---
|
||||
label: 'Managing content'
|
||||
top_level: true
|
||||
related:
|
||||
- core.content_structure
|
||||
- field_ui.add_field
|
||||
- field_ui.manage_display
|
||||
- field_ui.manage_form
|
||||
- node.creating_type
|
||||
- node.creating_content
|
||||
- node.editing
|
||||
---
|
||||
{% set content_structure_topic = render_var(help_topic_link('core.content_structure')) %}
|
||||
<h2>{% trans %}What is a content item?{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
<h2>{% trans %}What is a content type?{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
<h2>{% trans %}Overview of managing content{% endtrans %}</h2>
|
||||
<p>{% trans %}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.{% endtrans %}</p>
|
||||
Reference in New Issue
Block a user