You will find our community to be one of the biggest advantages to MODx. We do not get offended (well, unless you’re deliberately trying to be offensive), and you’ll usually get the help you need within an hour or so.
You can have multiple Wayfinder calls on the same page. It is very common to have a main menu, a "site utilities" menu (either at the very top of the page or in the footer) and a dynamic submenu in a sidebar.
Keep in mind that not all menus need to be dynamic (using Wayfinder and needing to take up the time and resources to generate the menu). For example, the "site utilities" menu usually contains links to pages that won’t change, so an ordinary static HTML menu will do just fine, and save that few milliseconds processing time and database access.
Product menus are usually more complex, requiring summary text, images, maybe pricing or other details. This is handled by Ditto, which can be used for any kind of flat listing (Wayfinder will do nested structures) taken from a single or multiple parents (use the &parents parameter), such as blog posts, news, or product catalogs. Ditto allows the inclusion of any number of TVs, as well as other fields, has filtering and sorting... well, it’s almost unlimited in how you can display your listing of documents.
Also once menus are created is there a way to map different pages to different menus?
I’m not sure what you mean here, perhaps you could re-phrase the question? Or give an example?
Menus generated by Wayfinder or other page listing snippets will (generally) reflect the structure of your documents in the Document Tree in the left side of the Manager. You use the &startId parameter of the snippet call to specify which document in the Tree you want to use as the parent of the menu structure you want to build. A parent Id of 0 means to start with the very top-level documents. This is common for the main menu.
You can also use another snippet (or a TV) for this value; the UltimateParent snippet is often used, since it travels up the tree structure from the page being generated to get the ID of its top-level ultimate parent (it can be configured to stop at whatever level you want) and returns that ID. This is used for displaying sub-menus; in some cases it is used in multiple language sites, where the top-level documents are used as containers for each language group.