You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The links to Calendar and Glossary in the header should be available in mobile view.
The global site searchbox adjacent to these links should stay visible regardless of screen size instead of appending it to the mobile menu.
CSS Flexbox or Grid might be a good way to control positioning and visual stacking between desktop and mobile regardless of source-order in the html.
We should consider making the site search field or his whole area (utility-nav list--flat) an html partial that can be included in both Jinja and Django templates which should be possible given that they don't contain expressions specific to either template engine
The site search field, the glossary link and the calendar links all persist in the header on any screen/device size and upon manually resizing the screen between desktop and mobile.
They are accessible
Tech steps or considerations (optional)
List any considerations the tech team should know. Additionally, any specific tech steps can be included here.
Consider whether making the items into a single partial include will not hinder future development given that it would not be able to contain Django-specific or Jinja-specific syntax
Pay attention to accessibility of these items and tabbing order
Should we use Flexbox or Grid?
Future work
The text was updated successfully, but these errors were encountered:
Summary
What we're after:
utility-nav list--flat
) an html partial that can be included in both Jinja and Django templates which should be possible given that they don't contain expressions specific to either template engineRelated issues
List any relevant related issue(s)
Completion criteria
Tech steps or considerations (optional)
List any considerations the tech team should know. Additionally, any specific tech steps can be included here.
Future work
The text was updated successfully, but these errors were encountered: