The right-click is yours now.
Build a context menu in the admin, bind it to the pages that should have it, and it reaches the public site resolved server side. Try right-clicking this page.
Build the items, then right-click the Try it panel to see exactly what a visitor will get. Or right-click this page.
A menu is a list of intents.
Items carry a label, an icon, an optional keyboard hint, and an action. Headings and separators group them. A live preview sits beside the editor, so you right-click the preview rather than saving and hunting for the page.
The things a browser's own menu offers.
Reload, back, forward, copy, cut, paste, select all, and open site search.
Each one decides whether it applies to the click that opened it. Back greys out with no history behind the page. Paste greys out outside an editable field. Copy greys out with nothing selected.
That is greyed out rather than hidden, deliberately. A menu that changes shape depending on where you clicked is disorienting, and greying out is what a native menu does.
Actions come from a vocabulary, not a script box.
An action is chosen from a fixed, server-validated list. A menu that let you paste JavaScript into a field and ran it on public pages would be cross-site scripting with extra steps.
Menus register with the framework rather than listening on the document, so a right-click is resolved by walking outward from what you clicked. Script load order cannot decide the winner.
A menu that has nothing to offer for a particular click steps aside, and the click reaches whatever encloses it. Your authored menu and the collection controls coexist.