The widget's quick-menu editor
How to build the tappable shortcuts a resident sees before typing anything, with a live preview that drills the same way the real widget does.
The quick menu is what a resident sees the moment they open your widget — before they've typed a word. It's also the screen operators edit most, because it's the actual front door.
1. Open City → Widget → Menu
You get two panels side by side: an editable table on the left, and a live, resident-facing preview on the right — in your city's own palette, right-to-left if your language is Hebrew or Arabic. Opening a submenu in either panel opens it in the other; they share one navigation path, deliberately, so you never edit one level while looking at another.
2. Add a shortcut and pick its action
Six actions are available, in the order the product argues for: ask (keeps the assistant in the loop — the default), article (ends the branch with a knowledge answer drawn in the chat), flow, form, submenu, and link (hands the resident a URL). An article entry searches your approved content only — a draft article resolves to nothing, so this picker can't author a button that draws a blank.
Put article before link in your own decisions too. An article ends the conversation with an answer; a link ends it by making the resident go find one themselves.
3. Reorder with the keyboard, not just the mouse
Every row has Move-up / Move-down buttons alongside drag-and-drop, and every move is announced to a screen reader. This isn't a nicety — a drag-only reorder list fails WCAG 2.2 AA and Israeli standard 5568 outright, and this screen is built so that gap can't reopen.
4. Respect the depth cap — it's shown, not just enforced
A menu holds a limited number of levels of children. At the bottom of that limit, the "submenu" action is offered disabled, with the reason attached to the field — not accepted and refused after you click. This mirrors the exact number the server enforces (WidgetMenuEntry.MaxChildDepth), so nothing you build here can be rejected later for a reason you weren't warned about.
If your build is ever running against an older menu than the server holds (because the server's own cap was raised since you loaded the page), the screen refuses to publish rather than silently truncating a branch you can't see. It names exactly which entry is affected.
5. Twelve shortcuts is the limit per level, on purpose
A quick menu exists to answer "what is this for?" in one glance. A resident scrolling forty options is worse off than one facing a blank composer — which is the actual failure the menu was built to prevent.