Open IsabelleWaltzing opened 7 years ago
There will be situations where the wrapper will actually end up being somewhere between the default header w full navbar and this minimal header/footer. See the stuff on transactional scenarios that's already in spec 1.3.2. It's not always going to be a strictly binary choice. Not sure if that needs to be reflected in the code somehow?
Hi gang! Two things I wanted to mention:
1) Peter is right: in cases where the transactional template is permitted, authors are free to include some of the missing elements if desired. They can retain the crumb trail, language toggle, etc. So it's definitely not an all-or-nothing kind of template.
2) We have been slowly making progress on an updated design which will expand on the transactional template, allowing for some new UI elements that can be leveraged when the templates are applied to more advanced applications. Basically we'll be tweaking the transactional template to give people the option of adding a title in the header, log in/out buttons, and application navigation, if desired. The new navigation menu sort of replaces the global themes/topics menu in cases where the user is in an authenticated app. It will still be quite a while before it's ready for prime time (maybe this winter) but I thought I should let you know it will be coming down the pipe eventually. Below are a couple of screenshots, definitely not finalized but they'll show you the direction we're headed.
We need a template on GCWeb that uses the reduced header and footer, as defined in the Content and Information Architecture Specification, version 1.4:
The header is reduced to the following elements:
All other parts of the global header are removed.
The footer is reduced to the following elements:
All other parts of the global footer are removed.
Small screen
This template may only be used in the following scenarios: