An anchor menu lets visitors jump straight to a specific section on the same page. It's the go-to navigation for one-page sites, long landing pages, and scroll-driven storytelling, where every link is a shortcut to a part of the page rather than a new page.
Wix once had a different menu for every job: horizontal, vertical, mega, hamburger, and anchor. Each lived in its own component with its own rules, so users had to choose the right menu before they even knew what they needed. Wix set out to merge them all into one menu, a single component that can be simple or rich, horizontal or vertical, a row of links or a full mega menu, and that collapses into a hamburger with its own customizable popup. It's one of the most powerful components in the editor, and also one of the easiest to get lost in. Every new option has to earn its place, because each one adds weight for two very different people: the site creator, who might be a seasoned pro or someone on their first day in the editor and expects this menu to behave like every other component in the system, and the site visitor, who simply expects navigation to work the way it does everywhere else on the web.
When the menus were unified, the anchor menu didn't make the cut. I was asked to bring it back.
I owned this project end to end: product research, UX and UI design, defining user flows, and talking directly with users. I worked closely with product management, development, and our accessibility expert to turn research insights into a solution that fit both the users' needs and the system's constraints.
As the UX/UI and product designer, I started by analyzing user tickets to understand what users were actually missing. I researched anchor menus across the web to map the design capabilities they rely on, then defined how the anchor experience should live inside the unified menu without adding another layer of complexity.
Bringing the Anchor Menu Home
