I have been working to create a custom dropdown menu with the help of the bot. The following properties code unfortunately does not provide a selector for a folder in the inspector. Is the code correct or does that property not exist or did the bot make an error:
If you are trying to select a page or folder in your project, you should probably use a 'link” property as that will allow you to select a page or folder from the project.
I tested your code and it did not work, but when I swapped out “pages” for “link”, I got a working property that allowed me to make a selection from the project. Not sure if there is a “mode” for “folder” as shown, it does not seem to make any difference.
Are you trying to get a list of pages, or are you trying to point to a folder of links?
I guess I’m not understanding just what you are looking for, are you trying to get a list of all the pages in your project?
What would you be expecting the user to select with this property?
A folder full of links?
Or something else.
If it is all the pages in the project you might have to handle this very differently. The solution is to probably set this up in your hook.js file as there you can access all of the pages and then define an array to export to your code.
The other option is to use a directive in your code to create a drop well into which you could then drop a Top Pages component and it would do all the heavy lifting for you. Unless there is something it cannot handle. But my experience with it has been that you can do pretty much anything with it. For instance, you can define a folder in the project pane that has a bunch of link files in it to create some custom link arrangement. Point the Top Pages at this folder and you are good to go. I have created custom drop-down using the top pages component.
OK, after looking at your site, I can see what you are after with the dropdown. But quite frankly, if it were me, I would go about this in a totally different way. This type of deep navigation lends itself to the use of something like a mega menu, which I think you could build in Elements with a little effort.
With this type of menu you would click on a top-level item, a window would then open below the menubar. In there you would then have the next level items which would open up to the right across the window to whatever depth you need, if they had nested items. Hard to explain but there are plenty of examples of this type of menu on the Internet. You could even go one better and have the second level open in the window and show all of the nested items from left to right. This would make things way more discoverable for your customers. I think it might also be relatively easy to implement using the core elements.
I thought Ben said he was going to be adding support for sub-folders to the top pages, could be wrong.
BTW, you could do this in the custom component, but I think you would have to set it up in the hooks file so you can parse the menu structure and then output something that your code could use to build out the menus.