Skip to content

Closes #5461: Add support for the new full-screen navigation as an option#5521

Draft
bberndt-uaz wants to merge 2 commits intomainfrom
issue/5461
Draft

Closes #5461: Add support for the new full-screen navigation as an option#5521
bberndt-uaz wants to merge 2 commits intomainfrom
issue/5461

Conversation

@bberndt-uaz
Copy link
Copy Markdown
Contributor

@bberndt-uaz bberndt-uaz commented Apr 21, 2026

Description

(Work in progress!)

  • Adds support for AZ Navbar Fullscreen

To Do:

  • Update styling of mobile menu
  • ...

Release notes

Related issues

How to test

  1. Go to Arizona Barrio settings (/admin/appearance/settings/az_barrio), click the Arizona Bootstrap tab, and set the CSS and JS CDN versions to "AZ NAVBAR FULLSCREEN". This setting will be removed from this PR once Arizona Bootstrap has been updated.
  2. In the same Arizona Barrio settings, go to Components -> Navbar Behaviour and check the "Enable AZ Navbar Fullscreen" checkbox.
  3. Go to Block Layout (/admin/structure/block) and in the Navigation Bar region, disable "Main navigation" and enable "AZ Navbar Fullscreen Menu".
  4. Edit the AZ Navbar Fullscreen Menu block as desired. You may also edit the menus for testing: add more nesting for the main navigation menu and add more links to the additional menus.

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

  • Patch release changes
    • Bug fix
    • Accessibility, performance, or security improvement
    • Critical institutional link or brand change
    • Adding experimental module
    • Update experimental module
  • Minor release changes
    • New feature
    • Breaking or visual change to existing behavior
    • Upgrade experimental module to stable
    • Enable existing module by default or database update
    • Non-critical brand change
    • New internal API or API improvement with backwards compatibility
    • Risky or disruptive cleanup to comply with coding standards
    • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
  • Other or unknown
    • Other or unknown

Drupal core

  • Patch release changes
    • Security update
    • Patch level release (non-security bug-fix release)
    • Patch removal that's no longer necessary
  • Minor release changes
    • Major or minor level update
  • Other or unknown
    • Other or unknown

Drupal contrib projects

  • Patch release changes
    • Security update
    • Patch or minor level update
    • Add new module
    • Patch removal that's no longer necessary
  • Minor release changes
    • Major level update
  • Other or unknown
    • Other or unknown

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My change requires release notes.

@bberndt-uaz bberndt-uaz self-assigned this Apr 21, 2026
@bberndt-uaz bberndt-uaz added the enhancement New feature or request label Apr 21, 2026
@bberndt-uaz bberndt-uaz added the high priority Must get done for this milestone label Apr 21, 2026
@bberndt-uaz bberndt-uaz linked an issue Apr 21, 2026 that may be closed by this pull request
@az-digital-bot
Copy link
Copy Markdown
Contributor

Tugboat has finished building the preview for this pull request!

Link:

Dashboard:

@bberndt-uaz bberndt-uaz moved this from Todo to In Progress in 3.4.0-alpha1 Apr 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.4.x only enhancement New feature or request high priority Must get done for this milestone

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Add support for the new full-screen navigation as an option

2 participants