I'd highly recommend creating a NavigationItem page type. This will allow you to build your navigation independent of your content tree. It will also allow you to manage the properties you need for naviation independent of the actual pages. While it may be redundant, it gives you a lot more control over your complex mega menu scenario.

Thank you, Brenden Kehren!

We've implemented the NavigationItem page type as you recommended, and it's helped us create drop-down menus successfully. However, we're facing some challenges in achieving the mega-menu functionality we need. Could you please provide us with the necessary documentation or an example to help us achieve the mega menu?

@Brenden Kehren

Thank you We've implemented the NavigationItem page type as you recommended, and it's helped us create drop-down menus successfully. However, we're facing some challenges in achieving the mega-menu functionality we need. Could you please provide us with the necessary documentation or an example to help us achieve the mega menu?

What's your "complex mega-menu functionality"? Need more details to be able to provide any further assistance

After creating the page types with subpages (i.e., subpages are showing as dropdowns in the main page type), the menu dropdown is working as expected.

Now that we are required to have the MegaMenu functionality to have a megamenu, do we need to have a separate logic? We are not sure how to implement this megamenu. Can you please guide us with the details of the steps, or is there any documentation related to the megamenu?

Note: We require this megamenu because we are trying to show the separate page types in the megamenu.

Again, maybe try being specific as to your actual needs. What functionality? What design?

Every "megamenu" is different based on client requirements. The mega menues we've done typically have 3 to 4 levels of navigation. The page type definition has several properties:

• PageName - system reasons
• NavName
• NavUrl
• NavImageUrl
• NavTarget
• NavText

Then in your view after you've retreived those items from the content tree (be sure to include node level and node order), you add some logic to get level 1 items, level 2 items, level 3 items, etc. Additionally add some logic for fields, for example if there's a value in the Image URL field, then place the <img> tag.

Aside from that, you'll have to provide a lot more details as to what you need from functionality standpoint if you want more details.

Hi Brenden we are actually looking to design our megamenu as shown below we want to add images or videos with description : link text