Basic question - setting up a simple (dynamic) menu

I apologize for being as dim as it gets here and hope you’ll indulge me.

In the "Create/Edit Document" tab under resource management, there are three form inputs labelled: "Parent Resource", "Menu Title" & "Menu Index" (also a checkbox labelled "Hide From Menus". What I’ve spectacularly failed to do is figure out, or find examples of/guidance on, how to access these to build a simple menu for a not very big site.

I’m hoping someone will give me a link to some ’simple menu’ examples (harnessing the above inputs). I’m a bit freaked that my searches haven’t found any, something feels very odd. Maybe it’s the realization that I’m awesomely dumb.

I suppose what I’m asking for is where info is on the level of menu between: static plain html coded snippet and Wayfinder, if you follow... a menu capable of scaling rather than needing recoding every time a page is added - the basic (no plugin, no addon, comes-fitted-as-standard) menu.

No problems with people explaining the ’obvious’ I’ve managed to walk past and not see.

Thank you.

MODx by itself does not generate menus. Use the Wayfinder snippet to do this. Wayfinder uses the Resource Tree structure to generate nested unordered lists (by default; you can configure it to generate any kind of structure you want), and uses the variables you mentioned for the menu items.

Start with just plain [[Wayfinder? &startId=`xx`]] where xx is the parent level (0 if you want to make a menu using the top-level resources) to start from. Check the Wayfinder documentation; it has a LOT of options as well as its own mini-templating system to structure the menu.

Use CSS to position and style the menu and its items.

http://modxcms.com/forums/index.php/topic,34176.msg207851.html#msg207851

Hi Susan

Thank you for clarifying. Understood. I’d kinda come to the conclusion ("MODx by itself does not generate menus") shortly after posting this topic.

I’ve been naughty and a typical designer - diving in wellington-boots first to see how far I could get entirely intuitively. Always feel it’s a good test of anything.... been impressed with how far I got. Had a blog sorted very quickly, considering I’ve no previous experience of MODx at all. The blog navigates to a ’fit for purpose’ standard with getResource and tagLister.. and a couple of static coded [[-id]] links - simple stuff.

Been bookmarking all the online documentation so hope not to bug you guys in here much.
All the best

Feel free to bug, your questions and the answers you get will help others. That’s how the community is built. I don’t do Revo, but there’s plenty of high-powered help here in that area.

Thank you for the encouragement Susan. I’ve been browsing enough to see there is indeed "high-powered" help here. Well out of my league. The posts in here have already helped me.

Revo = MODx Revolution. (A note just for anyone new like me wondering "what is Revo"... something I tripped up on to begin with. Evo is the older version: MODx Evolution. Like most things: obvious when you know).

Thanks again.