You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've seen we end up with a templates for the node body field, for the full view mode -- i.e. field--node--body--full.html.twig (sometimes also field--node--body--default.html.twig). ⚠️ Also needs mytheme_theme_suggestions_field_alter() added to cwd_base.theme to support view mode field templates, like what's in the Bright Beams child theme (cwd_cbb). (See comment in thread below for details.)
For --full, the body gets a div.field-body.double-margin wrapper. For --default, the body gets a div.summary wrapper -- but I think --default isn't used much, because usually there's a specific teaser field, usually the body field isn't shown except on the full view mode.
Is this treatment pretty standard, or just a sometimes thing?
NOTE: If we do this, we'll just need to update a couple templates in cwd_project, that currently put the wrapper markup in the node templates. (Benefit of these field templates is they get used across content types, so you don't have to have duplicate implementation.)
The text was updated successfully, but these errors were encountered:
I've seen we end up with a templates for the node body field, for the full view mode -- i.e.
⚠️ Also needs
field--node--body--full.html.twig
(sometimes alsofield--node--body--default.html.twig
).mytheme_theme_suggestions_field_alter()
added to cwd_base.theme to support view mode field templates, like what's in the Bright Beams child theme (cwd_cbb
). (See comment in thread below for details.)For
--full
, the body gets adiv.field-body.double-margin
wrapper. For--default
, the body gets adiv.summary
wrapper -- but I think--default
isn't used much, because usually there's a specific teaser field, usually the body field isn't shown except on the full view mode.Is this treatment pretty standard, or just a sometimes thing?
NOTE: If we do this, we'll just need to update a couple templates in cwd_project, that currently put the wrapper markup in the node templates. (Benefit of these field templates is they get used across content types, so you don't have to have duplicate implementation.)
The text was updated successfully, but these errors were encountered: