description.html.twig

Same filename in this branch
  1. 8.x-1.x menu_example/templates/description.html.twig
  2. 8.x-1.x form_api_example/templates/description.html.twig
  3. 8.x-1.x js_example/templates/description.html.twig
  4. 8.x-1.x page_example/templates/description.html.twig
  5. 8.x-1.x pager_example/templates/description.html.twig
  6. 8.x-1.x block_example/templates/description.html.twig
  7. 8.x-1.x tabledrag_example/templates/description.html.twig
  8. 8.x-1.x testing_example/templates/description.html.twig
  9. 8.x-1.x tour_example/templates/description.html.twig
  10. 8.x-1.x config_entity_example/templates/description.html.twig
  11. 8.x-1.x tests/modules/examples_description_test/templates/description.html.twig
  12. 8.x-1.x phpunit_example/templates/description.html.twig
  13. 8.x-1.x render_example/templates/description.html.twig
  14. 8.x-1.x field_permission_example/templates/description.html.twig
  15. 8.x-1.x stream_wrapper_example/templates/description.html.twig
  16. 8.x-1.x ajax_example/templates/description.html.twig
  17. 8.x-1.x hooks_example/templates/description.html.twig
  18. 8.x-1.x field_example/templates/description.html.twig
Same filename in other branches
  1. 3.x modules/menu_example/templates/description.html.twig
  2. 3.x modules/form_api_example/templates/description.html.twig
  3. 3.x modules/js_example/templates/description.html.twig
  4. 3.x modules/page_example/templates/description.html.twig
  5. 3.x modules/node_type_example/templates/description.html.twig
  6. 3.x modules/pager_example/templates/description.html.twig
  7. 3.x modules/block_example/templates/description.html.twig
  8. 3.x modules/tabledrag_example/templates/description.html.twig
  9. 3.x modules/rest_example/templates/description.html.twig
  10. 3.x modules/testing_example/templates/description.html.twig
  11. 3.x modules/tour_example/templates/description.html.twig
  12. 3.x modules/config_entity_example/templates/description.html.twig
  13. 3.x modules/phpunit_example/templates/description.html.twig
  14. 3.x modules/render_example/templates/description.html.twig
  15. 3.x modules/field_permission_example/templates/description.html.twig
  16. 3.x modules/stream_wrapper_example/templates/description.html.twig
  17. 3.x modules/ajax_example/templates/description.html.twig
  18. 3.x modules/hooks_example/templates/description.html.twig
  19. 3.x modules/field_example/templates/description.html.twig
  20. 3.x tests/modules/examples_description_test/templates/description.html.twig
  21. 4.0.x modules/menu_example/templates/description.html.twig
  22. 4.0.x modules/form_api_example/templates/description.html.twig
  23. 4.0.x modules/js_example/templates/description.html.twig
  24. 4.0.x modules/page_example/templates/description.html.twig
  25. 4.0.x modules/node_type_example/templates/description.html.twig
  26. 4.0.x modules/pager_example/templates/description.html.twig
  27. 4.0.x modules/block_example/templates/description.html.twig
  28. 4.0.x modules/tabledrag_example/templates/description.html.twig
  29. 4.0.x modules/rest_example/templates/description.html.twig
  30. 4.0.x modules/testing_example/templates/description.html.twig
  31. 4.0.x modules/tour_example/templates/description.html.twig
  32. 4.0.x modules/config_entity_example/templates/description.html.twig
  33. 4.0.x modules/phpunit_example/templates/description.html.twig
  34. 4.0.x modules/render_example/templates/description.html.twig
  35. 4.0.x modules/field_permission_example/templates/description.html.twig
  36. 4.0.x modules/stream_wrapper_example/templates/description.html.twig
  37. 4.0.x modules/ajax_example/templates/description.html.twig
  38. 4.0.x modules/hooks_example/templates/description.html.twig
  39. 4.0.x modules/field_example/templates/description.html.twig
  40. 4.0.x tests/modules/examples_description_test/templates/description.html.twig
  41. 4.0.x modules/config_simple_example/templates/description.html.twig
{#

Description text for the Node type Example.

#}


{% set content_type_path = path('entity.node_type.collection') %}
{% set add_types = path ('node.type_add') %}

{% trans %}



Config Node Type Example is a basic example of defining a content type through configuration YAML files.


In this example we create two content types for Drupal 8, using only YAML files. Well, mostly only YAML files...
    One of our content types is locked, so the user can't delete it while the module is installed. For this we need
    a very tiny amount of support code.


You can observe these content types on the content type admin page.


The simplest way to author the per-type YAML files is to create the content types within Drupal and then take the
    YAML files from the configuration directory. Like this:


    
    
  • Install Drupal 8.
    • 
    
  • Create a new content type at {{ add_types }}. Let's call it 'Nifty Content Type'.
    • 
    
  • Export the configuration from admin/config/development/configuration. Specific steps depending
        on needs, and decisions made during Drupal 8 beta. You'll see a file called
        node.type.nifty_content_type.yml.
    • 
    
  • Copy or move that file to your module's config/install directory, along with associated field
        and form yml files.
    • 
    
  • Remove the uuid information from the configuration files.
    • 



You can see some of these YAML files in this module's config/install directory.


If you want to lock a content type created in this way, you'll have to implement hook_install() and
    hook_uninstall(). In hook_install(), you'll set the content type to be locked.
    In hook_uninstall() you'll set the content type to be unlocked.


Content types created in this way will remain available after the user has uninstalled the module.
    If you were to fail to set the content type as unlocked, the user would not be able to delete it.


This example is based on this change notification: https://drupal.org/node/2029519


{% endtrans %}

File

node_type_example/templates/description.html.twig

View source 
  1. {#

  2. 

  3. Description text for the Node type Example.

  4. 

  5. #}

  6. 

  7. 

  8. {% set content_type_path = path('entity.node_type.collection') %}

  9. {% set add_types = path ('node.type_add') %}

  10. 

  11. {% trans %}

  12. 

  13. 

  14. <p>Config Node Type Example is a basic example of defining a content type through configuration YAML files.</p>

  15. <p>In this example we create two content types for Drupal 8, using only YAML files. Well, mostly only YAML files...

  16.     One of our content types is locked, so the user can&#39;t delete it while the module is installed. For this we need

  17.     a very tiny amount of support code.</p>

  18. <p>You can observe these content types on <a href= {{ content_type_path }}>the content type admin page</a>.</p>

  19. <p>The simplest way to author the per-type YAML files is to create the content types within Drupal and then take the

  20.     YAML files from the configuration directory. Like this:</p>

  21. <ul>

  22.     <li>Install Drupal 8.</li>

  23.     <li>Create a new content type at {{ add_types }}. Let&#39;s call it &#39;Nifty Content Type&#39;.</li>

  24.     <li>Export the configuration from <code>admin/config/development/configuration</code>. Specific steps depending

  25.         on needs, and decisions made during Drupal 8 beta. You&#39;ll see a file called

  26.         <code>node.type.nifty_content_type.yml</code>.</li>

  27.     <li>Copy or move that file to your module&#39;s <code>config/install</code> directory, along with associated field

  28.         and form yml files.</li>

  29.     <li>Remove the uuid information from the configuration files.</li>

  30. </ul>

  31. <p>You can see some of these YAML files in this module&#39;s <code>config/install</code> directory.</p>

  32. <p>If you want to lock a content type created in this way, you&#39;ll have to implement <code>hook_install()</code> and

  33.     <code>hook_uninstall()</code>. In <code>hook_install()</code>, you&#39;ll set the content type to be locked.

  34.     In <code>hook_uninstall()</code> you&#39;ll set the content type to be unlocked.</p>

  35. <p>Content types created in this way will remain available after the user has uninstalled the module.

  36.     If you were to fail to set the content type as unlocked, the user would not be able to delete it.</p>

  37. <p>This example is based on this change notification: <a href="https://drupal.org/node/2029519">https://drupal.org/node/2029519</a></p>

  38. 

  39. {% endtrans %}