feat: support section metadata handling for new rendering v2#222
Merged
Conversation
maximilianvoss
approved these changes
Jun 22, 2026
hannessolo
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adopts the same section metadata processing introduced in helix-html-pipeline#1059. When a div.section-metadata block is found in the body, its key/value rows are extracted and applied to the parent section: style values become CSS class names, all other keys become data-* attributes. The block itself is then removed from the DOM. Unlike the pipeline implementation, no feature flag is needed — the transform always runs.
fixes: https://jira.corp.adobe.com/browse/SITES-45376