This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[✨] Allow for multiple keyed menus with useContent #101
Labels
[STAGE-2] incomplete implementation
Remove this label when implementation is complete
[STAGE-2] not fully covered by tests yet
Remove this label when tests are verified to cover the implementation
[STAGE-2] unresolved discussions left
Remove this label when all critical discussions are resolved on the issue
[STAGE-3] docs changes not added yet
Remove this label when the necessary documentation for the feature / change is added
[STAGE-3] missing 2 reviews for RFC PRs
Remove this label when at least 2 core team members reviewed and approved the RFC implementation
Is your feature request related to a problem?
Currently it seems like it's only possible to define a single menu inside of
menu.md
. This makes it frustrating to account for the possibility of multiple menus, such as a header menu and a footer menu (which will probably contain a basic sitemap).Describe the solution you'd like
There are a couple good ways I can think of handling this. Keep in mind that I have done zero digging into the code to see how things are structured, so take these with a grain of salt.
menu.md
using top level headings. For example:menu.md
files the same way we allow for multiple layouts, and allowuseContent
to accept an identifier as a parameter. SouseContent()
would usemenu.md
, whileuseContent('footer')
would usemenu-footer.md
.Describe alternatives you've considered
The obvious one is to just hard code the menu into the component, use a json file, or use an exported javascript object from another file. This is how I will probably handle the problem for now, but I wanted to bring this idea up for discussion anyway.
Additional context
No response
The text was updated successfully, but these errors were encountered: