DataAfterContent is the data after the content (extension content added via the SkinAfterContent hook); it should be displayed as its own thing after the content, not in the same block.
Examples:
- Pending changes options
- RelatedArticles cards (ideally; currently is just manually placing itself in skins via js)
While it would be consistent with some other elements in these skins to just include it in the same block (such as the SiteNotice, despite also not being page content semantically), in terms of visually organising the content, having this non-content content in its own container, aligned with the content, generally makes more sense.
Currently:
How RelatedArticles does it (give or take), and we probably should be doing in general: