Skip to main content

Menu Component

Description​

The Menu in Assemble Web is split into separate Components. We also have business logic in place for the Data Fetch and parsing of that data into things that the Component understands.

UI Cases​

Component Library Default state​

component library default

Component Library with Dropdown​

component library Dropdown

Component Library on Mobile​

component library default

Assemble Web Default state​

component library default

Assemble Web Logged in state​

component library default

DataModel​

We have separate DataModels, but basically you can check the Assemble Web CMS Menu and MenuItem Data Model in Confluence

For the Component itself. please review Menu Data types

CMS and UI Map​

  • Logo: The logo uses the CMS Config appLogo

  • Primary Items: items identify as primary on the itemGroup. Any non secondary items will also by defaulted to this type with a few exceptions:

    • items that includes the flag isSignupItem, isSearchItem, isLogoutItem or isProfileItem Which will be included in their own section/group based on the image.

    • Within these flags, as it allows multiple active flags at the same time, a priority order has been defined like:

      1. (1) isSignupItem
      2. (2) isProfileItem
      3. (3) isSearchItem
      4. (4) isLogoutItem

  • Secondary Items: items identify as primary on the itemGroup

isSignupItem isProfileItem isSearchItem isLogoutItem