QUESTION: As we cannot rely on `vf-body` being on the body element - what should we do? about vf-core

[khawkins98]

I think we could make it a requirement that .vf-body be a parent of a pattern, but not on a specific element, like body.vf-body

We won't always be able to guarantee that body.vf-body > .vf-global-header ... often it might be body.vf-body > div > span > godknowswhatelse > .vf-global-header , and that won't fly with CSS Grid :(

Aside: I think the .vf-header grid takes priority over .vf-body for the .vf-global-header (pattern)

I think some of this ties into the documentation/expected behaviour.

Given that we have a few different "centering" grids at work (vf-body, vf-header and the data-protection one), perhaps we evolve the "page grids" category to do something like:

• vf-body grid becomes vf-grid-page-center for when you want to centre your page
• vf-header grid becomes vf-grid-header for the header, naturally!
• vf-data-protection-banner grid becomes vf-grid-data-protection-banner

[khawkins98]

Forgot to finish my thought: the above would open up for "exoctic" variations of vf-body/vf-grid-page-center:

• vf-grid-page-left for when for some reason you want content fixed to the left
• vf-grid-narrow-page-center when you need a really narrow column
• other weird use cases that we can't quite imagine yet

[khawkins98]

I think we're pretty aware of this issue space and the conversation here has been fully eclipsed, yes?

Being bold and closing.