- Issue created by @michaellander
- π³πΏNew Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies β .
The scope of β¨ Allow modules to hook into top of content/footer sections of new core navigation Active has narrowed to focus on the top section of content, but I still feel modules(particularly ones around users[ Masquerade β ], help, etc) would benefit from being able to hook into the footer section of navigation.
Per the previous issue:
A potential follow-up issue could look at adding the same kind of extensibility to the footer region. The footer region is more sensitive from a design perspective to a big number of blocks that content region. Hence it needs further discusssion and is out of scope for this issue.
Add the ability for module developers to add integrations to a new footer_top region that sits above the footer region.
Provide hooks to easily extend the footer_top region.
Output footer_top variable/slot in the template.
New hook navigation_footer_top to define content_top blocks
New hook navigation_footer_top_alter to alter content_top blocks
Active
11.1 π₯
navigation.module
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies β .