MegaMenu Questions - Get Support not showing and CSS editing

[lawrencemgann]

Good morning!  I'm encountering two stubborn issues with Employee Center megamenu and Advanced Portal Navigation and would greatly appreciate guidance!

1. I can't get the Get Support widget to appear in the megamenu at all.  I've created content items for the widget and reindexed all content tables, but the widget will not show.  Screenshots attached of the current configuration -- am I missing something?

2. The CSS styling of the megamenu is a bit off -- specifically the unhighlighted text color on menu layer 1 and the underline highlighted color on menu layer 2 -- and I can't correct it comprehensively with the Branding Editor. 

Does anyone have / know where documentation of the MegaMenu CSS can be found?

[Susan Britt · Accepted solution]

If you have Advanced Portal Navigation active, instead of using Taxonomy Topics alone, the below code can also be added to control the drop-down and expansion of those menus.  I put this on the portal record's Theme.

//== Advanced Portal Navigation active (from Employee Center Navigation widget)
.menu-container, .tab-list-container, .dropdown-container, .tab-list, .sub-topics-container, .mega-menu__items, .browse-button-container {
     background-color: #000 !important;
     color: #fff !important;
}
.dropdown-container, .tab-list, .sub-topic-list {
     &:hover {
          background-color: #e1f7d7 !important;
          color: #fff !important;
     }
}
.navigation-menu-item.selected-item, .menu-link, .expanded-menu, .sub-topic-groups {
     background-color: #000 !important;
     color: #fff !important;
}

[lawrencemgann]

Thank you for this!  Any thoughts on why the Get Support modal isn't appearing in the MegaMenu based on the configuration shared?

[lawrencemgann]

Disregard -- found the culprit -- the item also needed to be activated on the Portal > Menu after being created in the APN record.

[lawrencemgann]

Thank you!  By reviewing the portal style css and with the example you provided, I was able to spot and correct the errant element 🙂