Integrate Webform.html.twig into existing template I am attempting to add a webform field into an existing content type which has an associated twig template.  I can add the webform field to a new content type and/or use the default webform content type and the form displays without an issue.  If I add the webform to an existing content type the form does not display.  I tried adding the content from webform.html.twig to the existing content types template but it is still not displaying the form.  I know I am missing something simple here.  I can supply a few screenshots and or the twig files if that would be helpful

thank you for your patience.  I have had the debugging turned on for quite some time now the development version of our site.  The inspect screen appears to suggests the problem with displaying the webform field is in the page.html.twig which I have attached.  Interestingly, I tried adding a few other random fields to the page content type and they do not display either so I am fairly certain now that there is a problem with the twig template.

{#
/**
 * @file
 * Default theme implementation to display a page.
 *
 * @see academyhealth.info.yml
 * @see template_preprocess_page()
 * @see html.html.twig
 *
 * @ingroup themeable
 */
#}

&lt;header class="header"&gt;
  &lt;div class="container"&gt;
    &lt;a class="header__logo" href="/"&gt;&lt;span class="element-invisible"&gt;AcademyHealth&lt;/span&gt;&lt;/a&gt;
    &lt;button class="header__menu-button"&gt;&lt;i class="icon-hamburger"&gt;&lt;/i&gt; Menu&lt;/button&gt;
    &lt;div class="header__navs"&gt;
      &lt;a class="js-navs__close" href="javascript:void(0);"&gt;&lt;i class="icon-close"&gt;&lt;/i&gt; &lt;span class="element-invisible"&gt;Close&lt;/span&gt;&lt;/a&gt;
      &lt;nav class="header__main-nav"&gt;
        {{ page.main_navigation }}
      &lt;/nav&gt;
      &lt;div class="header__util"&gt;
        {{ page.utility_navigation }}
        &lt;div class="util__search"&gt;
          {{ page.search }}
        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/header&gt;

&lt;section class="page"&gt;
  {#
    A block titled content will be set if pages are extending this template, so
    print that instead of just printing page.content. The templates that extend
    this template, call page.content and place it appropriately.
  #}
  {% set _block_content = block('content') %}

  {% if _block_content is not empty %}
    {{ _block_content|raw }}
  {% else %}
    {{ page.content }}
  {% endif %}

&lt;/section&gt;

&lt;footer class="footer"&gt;
  &lt;div class="container"&gt;
    &lt;div class="footer__col1"&gt;
      &lt;a class="footer__logo" href="{{ site.url }}"&gt;&lt;span class="element-invisible"&gt;AcademyHealth&lt;/span&gt;&lt;/a&gt;
    &lt;/div&gt;
    &lt;div class="footer__col2"&gt;
      &lt;h6 class="footer__title"&gt;Connect with Us&lt;/h6&gt;
      {{ page.footer_social_media }}
    &lt;/div&gt;
    &lt;div class="footer__col3"&gt;
      &lt;h6 class="footer__title"&gt;Navigate AcademyHealth&lt;/h6&gt;
      {{ page.footer_menu }}
    &lt;/div&gt;
    &lt;div class="footer__col4"&gt;
      &lt;h6 class="footer__title"&gt;Extras&lt;/h6&gt;
      {{ page.footer_extras }}
    &lt;/div&gt;
  &lt;/div&gt;
  &lt;div class="footer__credits"&gt;
    &lt;div class="container"&gt;
      {{ academyhealth_address_line }} | {{ academyhealth_address_line_2 }} | Tel: {{ academyhealth_phone_number }} | Fax: {{ academyhealth_fax_number }}
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/footer&gt;
Conceptually, you shouldn't be thinking about it as including templates in other templates. Other CMS'es are more "template based" so to speak, but Drupal isn't. Building your content types and pages in Drupal means telling Drupal (through configuration or in code) how to construct its render arrays. From there on, Drupal will figure out which templates to use and how to merge the resulting HTML of one template into another template.

So that's the theory... now what's the problem in your case? The most obvious reason I can think of, is that you added the field, but did not yet configure it to be displayed. To do so, make sure Field UI module is enabled and then go the "Manage Display" page of your content type. The URL will look like /admin/structure/types/manage/[type]/display where "[type]" is the machine name of your content type. If you see your field in the "disabled" part of the form, drag it upwards to make it enabled and save the form. (This is an example of the "through configuration" method I mentioned earlier.)

If the above does not solve your problem, please add more details to your original question.