All components · Category: Navigation

Mega menu

A header whose entries open a panel of links with a live preview.

Hover or focus an entry and a panel opens with its links and a preview card that follows the one you point at. It follows the disclosure navigation pattern: the arrow keys, Home, End and Escape work, focus returns where it came from, and the panel stays inside the component.

Try it

<nav-mega-menu>

ViewPreviewCodeCSS

nav-mega-menu: A header whose entries open a panel of links with a live preview. A picture of the real component, drawn from its own code. The controls change the picture and the code beside it; nothing here is sent or stored.

Generated from the component's manifest and the values above.

index.html

<nav-mega-menu locale="en"></nav-mega-menu>

<script>
  const element = document.querySelector("nav-mega-menu");
  element.addEventListener("nav-mega-menu:opened", (event) => {
    console.log(event.detail);
  });
</script>

Add the site's Taggor script once; the component appears when it loads.

taggor-component.js

const element = document.createElement("nav-mega-menu");
element.setAttribute("locale", "en");
element.addEventListener("nav-mega-menu:opened", (event) => {
  console.log(event.detail);
});
document.body.append(element);

Add the site's Taggor script once; the component appears when it loads.

NavMegaMenu.tsx

import { useEffect, useRef } from "react";

export function NavMegaMenu() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onOpened = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("nav-mega-menu:opened", onOpened);
    return () => {
      element.removeEventListener("nav-mega-menu:opened", onOpened);
    };
  }, []);

  return <nav-mega-menu ref={ref} locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 18 sends every prop of a custom element as a text attribute.
The event is heard with addEventListener, inside an effect.

NavMegaMenu.tsx

import { useEffect, useRef } from "react";

export function NavMegaMenu() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onOpened = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("nav-mega-menu:opened", onOpened);
    return () => {
      element.removeEventListener("nav-mega-menu:opened", onOpened);
    };
  }, []);

  return <nav-mega-menu ref={ref} locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 19 sets a property when the element already has it, an attribute otherwise.
The event is heard with addEventListener, inside an effect.

src/NavMegaMenu.vue

<script setup lang="ts">
function onOpened(event: Event) {
  console.log((event as CustomEvent).detail);
}
</script>

<template>
  <nav-mega-menu locale="en" @nav-mega-menu:opened="onOpened" />
</template>

vite.config.ts

import vue from "@vitejs/plugin-vue";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag === "nav-mega-menu",
        },
      },
    }),
  ],
});

Add the site's Taggor script once; the component appears when it loads.
vite.config.ts tells Vue that this tag is not a Vue component.

src/app/nav-mega-menu.component.ts

import { afterNextRender, Component, CUSTOM_ELEMENTS_SCHEMA, DestroyRef, ElementRef, inject } from "@angular/core";

@Component({
  selector: "app-nav-mega-menu",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <nav-mega-menu locale="en"></nav-mega-menu>
  `,
})
export class NavMegaMenuComponent {
  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("nav-mega-menu");
    const onOpened = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("nav-mega-menu:opened", onOpened));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("nav-mega-menu:opened", onOpened));
  }
}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.
The event is heard with addEventListener, inside an effect.

src/TaggorComponent.svelte

<script>
  function onOpened(event) {
    console.log(event.detail);
  }
</script>

<nav-mega-menu locale="en" onnav-mega-menu:opened={onOpened}></nav-mega-menu>

Add the site's Taggor script once; the component appears when it loads.

How an agent gets a component like this onto a site:

taggor checktaggor publish

The CSS variables the component exposes, set the way a customer's page would.

styles.css

nav-mega-menu {
  --nm-radius: 16px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
brand	string	Acme Studio	The name on the left.
links	list	none	Flat list of links; `group` names the top entry each one belongs to.
locale	pt-BR \| en	en	–

Prop names and descriptions are the component's own, in English, as its author wrote them.

Events

Events of the component, read from its manifest
Event	When it fires
opened	A top entry opened its panel.

Build one with your agent

Build me a Taggor component like "Mega menu" (nav-mega-menu): A header whose entries open a panel of links with a live preview. Fetch https://taggor.dev/agent-setup/prompt.md and follow its instructions to set me up for Taggor. Ask me before you sign in, create an account, accept terms, pay for anything or type a secret. Check it with `taggor check` and publish it with `taggor publish`, and stop there. Do not promote it to production, attach it to a site, roll back anything or use --yes, --force or --force-drop-invalid unless I ask for exactly that in this conversation.

Related components

Morphing drawer menu<nav-drawer-morph>
Gliding tabs<tabs-glide>
Breadcrumb trail<breadcrumb-trail>