Namely, a template where the default header is not shown (and likely the footer too, although this is not shown in the mock-ups)
Why?
Requested by ParentApp for Kids
How?
Option 1: use fullscreen pop-ups
As the page visually resembles a fullscreen pop-up, it may be that leveraging this functionality is sensible. However, fullscreen pop-ups in their current form are buggy when used for the more complex functionality required (e.g. #2195; fullscreen pop-ups don't handle query params as other templates do, so cannot correctly navigate or launch child pop-ups).
An attempt was made to address these issues in #2329. However, that approach had some unacceptable knock-ons, and didn't sufficiently patch up the fullscreen pop-up functionality. A more thorough overhaul would be a substantial task.
Option 2: hide/show header (and footer) at template level
Mini RFC here.
As well as exposing this option to authors, we would likely need a new display component to be used as the "cross" in the corner that closes the template (the same functionality as the "back" nav arrow in the header that would be hidden. This could also be achieved using an existing component (e.g. button) with a new visual variant, combined with a new action to handle the navigation, e.g. click | nav: back.
What? A way of displaying a template that matches these designs:
Full figma designs available here.
Namely, a template where the default header is not shown (and likely the footer too, although this is not shown in the mock-ups)
Why? Requested by ParentApp for Kids
How?
Option 1: use fullscreen pop-ups
As the page visually resembles a fullscreen pop-up, it may be that leveraging this functionality is sensible. However, fullscreen pop-ups in their current form are buggy when used for the more complex functionality required (e.g. #2195; fullscreen pop-ups don't handle query params as other templates do, so cannot correctly navigate or launch child pop-ups). An attempt was made to address these issues in #2329. However, that approach had some unacceptable knock-ons, and didn't sufficiently patch up the fullscreen pop-up functionality. A more thorough overhaul would be a substantial task.
Option 2: hide/show header (and footer) at template level
Mini RFC here. As well as exposing this option to authors, we would likely need a new display component to be used as the "cross" in the corner that closes the template (the same functionality as the "back" nav arrow in the header that would be hidden. This could also be achieved using an existing component (e.g.
button) with a new visual variant, combined with a new action to handle the navigation, e.g.click | nav: back.