>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3543102. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !22 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>It's not appropriate for Mercury to provide templates that are specific to particular content types and view modes. Those will heavily vary by site and Mercury cannot assume these things will exist or that the templates it provides will be useful.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We should remove these templates. If there are specific things the templates are doing (classes, for example), we need to find another way to get those things in.</p> <p>The node--blog--card.html.twig file is, generally, a wrapper around the <code>card</code> component, ensuring variables get fed to it. The problem is, it's hard-coding to specific fields. None of this is going to fly.</p> <p>We should remove the template entirely and rely on XB's content type templates instead, which are specific to the site template. That's okay. Mercury need not provide a presentational opinion for specific content types, especially since the template is not using any Tailwind classes directly.</p>