Can you describe how this would look to you? e.g. is it a " menu, page1,2,3" “options menu, options1,2,3” type deal, where you just have some preset shortcuts to change pages or show and hide stuff?
The reason I ask is that “we should have a template menu” is pretty vague, and I can’t actually imagine what core functionality it would have that can’t be done with an empty UMG just as quickly. As is, you just drag and drop some buttons on the page, then click the “on pressed” event and make that show/hide a widget, or open a new widget… or whatever. I honestly can’t imagine what you could template that would produce a time saving system. The button functions are mostly unique to each project, and anything else is usually just a simple visibility switching / animation triggering. The one exception I can see is the visual / sound settings. But the problem with those isn’t the lack of a template menu system, it’s their lack of easy blueprint access in general.
P.S. if you are just talking examples, then the more examples the better. But I was under the impression that the content examples had UMG stuff (haven’t really checked)