diff --git a/core/modules/help_topics/help_topics/comment.configuring_content.html.twig b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig new file mode 100644 index 0000000000..35e89df348 --- /dev/null +++ b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig @@ -0,0 +1,61 @@ +--- +label: 'Configuring content commenting' +related: +- comment.overview +- comment.creating_type +- comment.moderating +- comment.disabling +--- +{% set comment_types = render_var(url('entity.comment_type.collection')) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Allow users to comment on content. Comments can be enabled and configured for each content type separately.{% endtrans %}

+

{% trans %}Who can configure comments?{% endtrans %}

+

{% trans %}Users with the Administer comments and comment settings permission (typically an administrator) can configure comments.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Structure > Content types.{% endtrans %}
    2. +
  2. {% trans %}Select Edit from the dropdown button for the content type where you want to enable commenting.{% endtrans %}
    3. +
  3. Click the Manage fields tab.
    4. +
  4. {% trans %}Locate the Comments field and click + Edit. The available options depend on your selection:{% endtrans %} + +
    5. +
  5. Click Save setting to save the comment settings for the chose content type.
    6. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/comment.creating_type.html.twig b/core/modules/help_topics/help_topics/comment.creating_type.html.twig new file mode 100644 index 0000000000..4498d1fd94 --- /dev/null +++ b/core/modules/help_topics/help_topics/comment.creating_type.html.twig @@ -0,0 +1,23 @@ +--- +label: 'Creating custom comment type' +related: +- field_ui.add_field +- field_ui.manage_display +- field_ui.manage_form +- comment.overview +- comment.configuring_content +- comment.moderating +- comment.disabling +--- +{% set comment_types = render_var(url('entity.comment_type.collection')) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Creating a custom comment type in order to have different comment forms for content types.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+

{% trans %}Users with the Administer comment types and settings permission (typically administrators) can create new comment types.{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Structure > Comment types.{% endtrans %}
    2. +
  2. {% trans %}Click Add comment type..{% endtrans %}
    3. +
  3. {% trans %}In the Label field, enter a name for the content type, which is how it will be listed in the administrative interface and selection box when adding comment field on entity sub-types.{% endtrans %}
    4. +
  4. {% trans %}In the Target entity type field, select the entity type for which that comment type will be made available{% endtrans %}
    5. +
  5. {% trans %}Click Save. The comment type will be created. {% endtrans %}
    6. +
diff --git a/core/modules/help_topics/help_topics/comment.disabling.html.twig b/core/modules/help_topics/help_topics/comment.disabling.html.twig new file mode 100644 index 0000000000..15000a6987 --- /dev/null +++ b/core/modules/help_topics/help_topics/comment.disabling.html.twig @@ -0,0 +1,31 @@ +--- +label: 'Disabling comments' +related: +- comment.overview +- comment.configuring_content +- comment.creating_type +- comment.moderating +- comment.disabling +--- +{% set content = render_var(url('system.admin_content')) %} +{% set comment_permission_url = render_var(url('user.admin_permissions', {},{'fragment': 'module-comment'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Turn off commenting for a particular content item.{% endtrans %}

+

{% trans %}Who can disable comments?{% endtrans %}

+

{% trans %}Users with the Administer comments and comment settings permission can disable and enable commenting on content items.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Content.{% endtrans %}
    2. +
  2. {% trans %}Locate the content item that you would like to change and choose Edit from the dropdown button.{% endtrans %}
    3. +
  3. {% trans %}Open the Comment setting fieldset. Three comment options are available.{% endtrans %} + +
    4. +
  4. {% trans %}Select Closed or Hidden.{% endtrans %}
    5. +
  5. {% trans %}Save your changes.{% endtrans %}
    6. +
diff --git a/core/modules/help_topics/help_topics/comment.moderating.html.twig b/core/modules/help_topics/help_topics/comment.moderating.html.twig new file mode 100644 index 0000000000..4a44c40f10 --- /dev/null +++ b/core/modules/help_topics/help_topics/comment.moderating.html.twig @@ -0,0 +1,29 @@ +--- +label: 'Moderating comments' +related: +- comment.overview +- comment.configuring_content +- comment.creating_type +- comment.disabling +--- +{% set comment_types = render_var(url('entity.comment_type.collection')) %} +{% set content = render_var(url('system.admin_content')) %} +{% set comment_unpublished_url = render_var(url('comment.admin_approval')) %} +{% set comment_published_url = render_var(url('comment.admin')) %} +{% set comment_permission_url = render_var(url('user.admin_permissions', {},{'fragment': 'module-comment'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Decide which comments are shown on the website.{% endtrans %}

+

{% trans %}Who can moderate comments?{% endtrans %}

+

{% trans %}Users with the Administer comments and comment settings permission (typically administrators) can moderate comments.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Content and click the Comments tab. A list of all comments is being shown.{% endtrans %}
    2. +
  2. {% trans %}To unpublish comments select one or more comments and select Unpublish comment from the Action select list and Click Apply to selected items.{% endtrans %}
    3. +
  3. {% trans %}To remove comments from the website select one or more comments and select Delete comment from the Action select list and Click Apply to selected items.{% endtrans %}
    4. +
  4. {% trans %}To change the content of a comment select Edit from the dropdown button for a particular comment.{% endtrans %}
    5. +
  5. {% trans %}To publish comments that are not yet visible on the website, click the Unapproved comments tab. Select one or more comments, select Publish comment from the Action select list and click Apply to selected items.{% endtrans %}
    6. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/comment.overview.html.twig b/core/modules/help_topics/help_topics/comment.overview.html.twig new file mode 100644 index 0000000000..3dbdb96274 --- /dev/null +++ b/core/modules/help_topics/help_topics/comment.overview.html.twig @@ -0,0 +1,13 @@ +--- +label: 'Managing comments' +top_level: true +related: +- comment.moderating +- comment.configuring_content +- comment.creating_type +- comment.disabling +--- +

{% trans %}What are comments?{% endtrans %}

+

{% trans %}Drupal allows website visitors to post comments to discuss content like forum topics, blog posts, news articles or collaborative book pages. This way it provides a discussion board for each content item.{% endtrans %}

+

{% trans %}What is moderation?{% endtrans %}

+

{% trans %}Depending on your website's audience you may want to check the comments they are posting before publishing them. You can moderate comments by setting the default status to unpublished and bulk publish them when you reviewed them. You can also bulk unpublish and even delete comments. To deal with large amount of unwanted comments you have to install additional modules.{% endtrans %}

diff --git a/core/modules/help_topics/help_topics/node.creating_content.html.twig b/core/modules/help_topics/help_topics/node.creating_content.html.twig new file mode 100644 index 0000000000..e2e6671592 --- /dev/null +++ b/core/modules/help_topics/help_topics/node.creating_content.html.twig @@ -0,0 +1,61 @@ +--- +label: 'Creating a content item' +related: +- node.overview +- core.content_structure +- node.create_content_type +- field_ui.add_field +- field_ui.manage_display +- field_ui.manage_form +- comment.configuring_content +- path.overview +- menu.overview +- content.revisioning +--- +{% set content_types = render_var(url('entity.node_type.collection')) %} +{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %} +{% set content = render_var(url('system.admin_content')) %} +{% set permissions = render_var(url('user.admin_permissions', {},{'fragment': 'module-node'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Create and publish a content item that will be published on the site.{% endtrans %}

+

{% trans %}Who can create content?{% endtrans %}

+

{% trans %}Users with the Create new content permission can create content.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Content.{% endtrans %}
    2. +
  2. {% trans %}Click Add content. Choose which type of content you want to create.{% endtrans %}
    3. +
  3. {% trans %}The content creation form appears. It depends on the way that the content type has been configured which fields are available. {% endtrans %}
    4. +
  4. {% trans %}In the Title field, enter the title of the page. This will also be used as a meta tag in the source code, and as label of the content item in administration screens.{% endtrans %}
    5. +
  5. {% trans %}If there is a Body field, you can enter the full content of the page there.{% endtrans %}
    6. +
  6. {% trans %}Leave the Published field checked to publish the content immediately or uncheck it to keep it unpublished. {% endtrans %}
    7. +
  7. {% trans %}In the Revision log message field, you can optionally describe why you create the content. This will be visible in the list of content revisions.{% endtrans %}
    8. +
  8. {% trans %}If there is a Menu settings fieldset, check Provide a menu link to create a menu link for this page:{% endtrans %} + +
    9. +
  9. {% trans %}If there is a Comment settings fieldset, you can enable commenting by selecting Open or disable it by selecting Closed:{% endtrans %}
    10. +
  10. {% trans %}If there is a URL alias fieldset, you can define the page's address, for example "/about-us", in the field URL alias.{% endtrans %}
    11. +
  11. {% trans %}Open the Authoring information fieldset if you want to change the author and creation date of the content:{% endtrans %} + +
    12. +
  12. {% trans %}Open the Promotion options fieldset if you want to change the visibility of the content. Note that these options highly depend on the way your site has been configured{% endtrans %} + +
    13. +
  13. {% trans %}Click Save to create the content or click Preview to check what the page will look like in various view modes.{% endtrans %}
    14. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/node.creating_type.html.twig b/core/modules/help_topics/help_topics/node.creating_type.html.twig new file mode 100644 index 0000000000..44616fcd58 --- /dev/null +++ b/core/modules/help_topics/help_topics/node.creating_type.html.twig @@ -0,0 +1,34 @@ +--- +label: 'Creating custom content types' +related: +- node.overview +- core.content_structure +- field_ui.add_field +- field_ui.manage_display +- field_ui.manage_form +--- + +{% set permissions = render_var(url('user.admin_permissions', {},{'fragment': 'module-node'})) %} +{% set content_types = render_var(url('entity.node_type.collection')) %} +{% set add_field = render_var(url('help.help_topic', {'id': 'field_ui.add_field'})) %} +{% set manage_display = render_var(url('help.help_topic', {'id': 'field_ui.manage_display'})) %} +{% set manage_form = render_var(url('help.help_topic', {'id': 'field_ui.manage_form'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Have various content type with different fields, display modes and content editing forms.{% endtrans %}

+

{% trans %}Who can create a content type?{% endtrans %}

+

{% trans %}Users with the Administer content types permission (typically administrators) can create new content types.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Structure > Content types.{% endtrans %}
    2. +
  2. {% trans %}Click Add content type.{% endtrans %}
    3. +
  3. {% trans %}In the Name field, enter a name for the content type, which is how it will be listed in the administrative interface.{% endtrans %}
    4. +
  4. {% trans %}Click Save and edit. Your content type will be created.{% endtrans %}
    5. +
  5. {% trans %}Add fields to the new content type.{% endtrans %}
    6. +
  6. {% trans %}Configure the various display modes of the new content type.{% endtrans %}
    7. +
  7. {% trans %}Configure the content editing form of the content type.{% endtrans %}
    8. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/node.managing_content.html.twig b/core/modules/help_topics/help_topics/node.managing_content.html.twig new file mode 100644 index 0000000000..aebabd0cdb --- /dev/null +++ b/core/modules/help_topics/help_topics/node.managing_content.html.twig @@ -0,0 +1,39 @@ +--- +label: 'Managing content items' +related: +- node.overview +- node.creating_content +--- +{% set content_types = render_var(url('entity.node_type.collection')) %} +{% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %} +{% set content = render_var(url('system.admin_content')) %} +{% set permissions = render_var(url('user.admin_permissions', {},{'fragment': 'module-node'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Find content so that you can edit, unpublish or delete it.{% endtrans %}

+

{% trans %}Who can manage content?{% endtrans %}

+

{% trans %}Users with the Access the Content overview page permission can manage content.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Content.{% endtrans %}
    2. +
  2. {% trans %}Use any of the filtering fields and click Filter to reduce the list of content items:{% endtrans %} + +
    3. +
  3. {% trans %}To sort the list of results click on one of the table headers. Click again to change the order.{% endtrans %}
    4. +
  4. {% trans %}To unpublish content items from the website select one or more items and select + Unpublish content from the Action select list and Click Apply to selected items.{% endtrans %}
    5. +
  5. {% trans %}To publish items select one or more unpublished items and select + Publish content from the Action select list and Click Apply to selected items.{% endtrans %}
    6. +
  6. {% trans %}To delete content from the website select one or more unpublished items and select Delete content from the Action select list and Click Apply to selected items. Deleting cannot be undone.{% endtrans %}
    7. +
  7. {% trans %}To change a content item select Edit from the dropdown button for a particular item.{% endtrans %}
    8. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/node.overview.html.twig b/core/modules/help_topics/help_topics/node.overview.html.twig new file mode 100644 index 0000000000..74e7613472 --- /dev/null +++ b/core/modules/help_topics/help_topics/node.overview.html.twig @@ -0,0 +1,15 @@ +--- +label: 'Content' +top_level: true +related: +- core.content_structure +--- +

{% trans %}What is a content item?{% endtrans %}

+

{% trans %}A content item is any piece of individual content, such as a page, poll, article, forum topic, or a blog entry.{% endtrans %}

+

{% trans %}What is a content type?{% endtrans %}

+

{% trans %}Content items are divided in content types, which have different purposes and are displayed in very different ways on the site. Examples of content types are page, article, recipe, event, forum topic, and blog entry.{% endtrans %}

+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/path.creating_alias.html.twig b/core/modules/help_topics/help_topics/path.creating_alias.html.twig new file mode 100644 index 0000000000..25d078ada7 --- /dev/null +++ b/core/modules/help_topics/help_topics/path.creating_alias.html.twig @@ -0,0 +1,24 @@ +--- +label: 'Creating a URL alias' +related: +- path.overview +- path.managing_aliases +--- +{% set path_aliases = render_var(url('entity.path_alias.collection')) %} +{% set path_permission = render_var(url('user.admin_permissions', {}, {'fragment': 'module-path'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Give content a human- or SEO-friendly URL alias.{% endtrans %}

+

{% trans %}Who can create URL aliases?{% endtrans %}

+

{% trans %}Users with the Create and edit URL aliases permission can create aliases.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}Open a content editing form, for example by creating a new content item.{% endtrans %}
    2. +
  2. {% trans %}Open the URL alias fieldset.{% endtrans %}
    3. +
  3. {% trans %}Enter the alias (for example "/about-us") in the URL alias field. Make sure the alias starts with a "/" character. {% endtrans %}
    4. +
  4. {% trans %}Click Save.{% endtrans %}
    5. +
  5. {% trans %}Verify that the page can be visited with the new alias, for example "http://example.com/about-us".{% endtrans %}
    6. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/path.managing_aliases.html.twig b/core/modules/help_topics/help_topics/path.managing_aliases.html.twig new file mode 100644 index 0000000000..fd2e429277 --- /dev/null +++ b/core/modules/help_topics/help_topics/path.managing_aliases.html.twig @@ -0,0 +1,22 @@ +--- +label: 'Managing URL aliases' +related: +- path.overview +- path.creating_alias +--- +{% set path_aliases = render_var(url('entity.path_alias.collection')) %} +{% set permission = render_var(url('user.admin_permissions', {}, {'fragment': 'module-path'})) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}If you run into problems with aliases (pointing to the wrong location, duplicates or spelling mistakes) Drupal provides you with a list of all the aliases, so that you can quickly locate and edit the alias..{% endtrans %}

+

{% trans %}Who can manage URL aliases?{% endtrans %}

+

{% trans %}Users with the Administer URL aliases permission can manage aliases.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administration menu, navigate to Configuration > Search and Metadata > URL aliases. The list with all the site's aliases will appear.{% endtrans %}
    2. +
  2. {% trans %}Select Edit from the dropdown button for the alias that you would like to change.{% endtrans %}
    3. +
  3. {% trans %}Make the required changes and click on Save{% endtrans %}
    4. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/path.overview.html.twig b/core/modules/help_topics/help_topics/path.overview.html.twig new file mode 100644 index 0000000000..061634c917 --- /dev/null +++ b/core/modules/help_topics/help_topics/path.overview.html.twig @@ -0,0 +1,22 @@ +--- +label: 'Paths, aliases and URLs' +top_level: true +related: +- path.creating_alias +- path.managing_aliases +--- +

{% trans %}What is a URL?{% endtrans %}

+

{% trans %}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 example.com.", example.com is the URL for the home page of your website. Users use URLs to locate content on the web.{% endtrans %}

+

{% trans %}What is a path?{% endtrans %}

+

{% trans %}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 http://example.com/node/7, the path is node/7. Here are some examples of paths you might find in your site:{% endtrans %}

+ +

{% trans %}What is an alias?{% endtrans %}

+

{% trans %}The core software has a feature called "URL Alias" that allows you to provide a more understandable name to the content. So, if you have an "About Us" page with the path node/7, you can set up an alias so that your visitors will see it as http://www.example.com/AboutUs. The core Path module, which supports URL aliasing, provides this functionality. The additional module pathauto automatically generates a URL alias when you create content.{% endtrans %}

+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/taxonomy.configuring.html.twig b/core/modules/help_topics/help_topics/taxonomy.configuring.html.twig new file mode 100644 index 0000000000..0fc76eddb0 --- /dev/null +++ b/core/modules/help_topics/help_topics/taxonomy.configuring.html.twig @@ -0,0 +1,36 @@ +--- +label: 'Configuring taxonomy' +related: +- taxonomy.overview +- field_ui.add_field +- field_ui.manage_display +- field_ui.manage_form +- field_ui.reference_field +--- +{% set taxonomy_permissions = render_var(url('user.admin_permissions', {},{'fragment': 'module-taxonomy'})) %} +{% set taxonomy_admin = render_var(url('entity.taxonomy_vocabulary.collection')) %} +

{% trans %}Goal{% endtrans %}

+

{% trans %}Create a taxonomy and add a taxonomy field to a content type.{% endtrans %}

+

{% trans %}Who can configure a taxonomy?{% endtrans %}

+

{% trans %}Users with the Administer vocabularies and terms permission can configure a taxonomy.{% endtrans %}

+

{% trans %}Steps{% endtrans %}

+
    +
  1. {% trans %}In the Manage administrative menu, navigate to Structure > Taxonomy.{% endtrans %}
    2. +
  2. {% trans %}Click Add vocabulary.{% endtrans %}
    3. +
  3. {% trans %}In the Name 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.{% endtrans %}
    4. +
  4. {% trans %}Click Save. Your vocabulary will be created and you will see the page that lists all the terms in this vocabulary.{% endtrans %}
    5. +
  5. {% trans %}Click Add term{% endtrans %}
    6. +
  6. {% trans %}In the Name field, enter the term name (for example "Butter"). Click Save.{% endtrans %}
    7. +
  7. {% trans %}You will receive a confirmation about the term you created. Add more terms.{% endtrans %}
    8. +
  8. {% trans %}In the Manage administrative menu, navigate to Structure > Content types. Locate the content type that you want to add the field to, and click Manage fields.{% endtrans %}
    9. +
  9. {% trans %}Click Add field. In Add a new field, select Reference > Taxonomy term.{% endtrans %}
    10. +
  10. {% trans %}In the Label field enter the label (for example "Ingredients") that will be used for both content editing and content display.{% endtrans %}
    11. +
  11. {% trans %}Click Save and continue.{% endtrans %}
    12. +
  12. {% trans %}On the next screen, enter a value for Allowed number of values. You can limit the field to one value per entity item, a set number of values, or set it to have unlimited values. Click Save field settings.{% endtrans %}
    13. +
  13. {% trans %}On the next screen, edit the settings for the field. You can edit the Label and Help text and check Required field. In the field Reference method you can select the method used to list the allowed values. In the Vocabulary field, choose the vocabulary that you created. The allowed values in the new field will be the terms that you added to the vocabulary. In the field Default value you can choose a default value for the field.{% endtrans %}
    14. +
  14. {% trans %}Click Save settings. You should be returned to the Manage fields page, with your new field in the list.{% endtrans %}
    15. +
+

{% trans %}Additional resources{% endtrans %}

+ diff --git a/core/modules/help_topics/help_topics/taxonomy.overview.html.twig b/core/modules/help_topics/help_topics/taxonomy.overview.html.twig new file mode 100644 index 0000000000..7a87b0c67f --- /dev/null +++ b/core/modules/help_topics/help_topics/taxonomy.overview.html.twig @@ -0,0 +1,24 @@ +--- +label: 'Taxonomy' +top_level: true +--- +{% set taxonomy_permissions = render_var(url('user.admin_permissions', {},{'fragment': 'module-taxonomy'})) %} +{% set taxonomy_admin = render_var(url('entity.taxonomy_vocabulary.collection')) %} +{% set entity_reference = render_var(url('help.help_topic', {'id':'field_ui.reference_field'})) %} +

{% trans %}What is Taxonomy?{% endtrans %}

+

{% trans %}Taxonomy 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 terms (the blog tags or recipe ingredients in these examples); and a set of terms is known as a vocabulary (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. 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.{% endtrans %}

+

{% trans %}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).{% endtrans %}

+

{% trans %}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:{% endtrans %}

+
+
{% trans %}Free tagging{% endtrans %}
+
{% trans %}New terms can be created right on the content editing form.{% endtrans %}
+
{% trans %}Fixed list of terms{% endtrans %}
+
{% trans %}The list of terms is curated and managed outside the content editing form, and users can only choose from the existing list when editing content.{% endtrans %}
+
+

{% trans %}Taxonomy reference fields can be added to any entity, such as user accounts, custom 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.{% endtrans %}

+

{% trans %}Additional resources{% endtrans %}

+