In the release for the new Menu system it documents how to configure it in the rc file but mentions you can use the component as well, it'd be nice for the documentation to reflect both these things.
Do we still use the mdx header matter @pedronauck
name: Setup
route: /package/setup
---
module.exports = {
menu: [
{
name: 'Pakage',
menu: [
{
name: 'Setup',
route: '/package/setup',
},
{
name: 'Components',
route: '/package/components',
},
],
}
],
};
How do I migrate to this new system and organize my pages? The old way wasn't very documented either (mostly figured out from watching the preview video on the main site), and I'm seeing weird funkiness trying to get menus to play nice and find pages.
New menu feature seems awesome! It works fine and is able to show the menu in nested. However, how could we categorize mdx content into the submenu? e.g.
alert.mdx
name: Alert
---
doczrc.js
โโโ menu
โย ย โโโ Home
โย ย โโโ Components
โย ย โโโ Alert <--- how to categorize alert.mdx into here?
โย ย โโโ Button
@Chun-MingChen indeed, that's what I'm wondering as well. I couldn't figure it out! ๐
How I told on the #436: You can see how configure menu in the release link. I didn't have time to update docs yet ๐Will be awesome have some help here ๐
The release link shows one level of nesting. Is it possible to nest multiple levels?
| Intro
| Components
|-- Buttons
|--|-- Simple <-- nested twice
|--|-- Complex
|-- Menu
|-- Footer
No @Jayphen, it's not possible yet!
+1
can we support it in the future?
any update on nesting multiple levels? Not sure if known workarounds exist or not? I would love something like @Jayphen mentions too.
Thanks in advance.
Most helpful comment
+1
can we support it in the future?