Hello Raymond
The difference between a menu item and a functionally appropriate module, I would not see basically in the range of functions. For example, the J! Module Articles / Categorie the ability to filter recent posts. So you can use the module instead of the module Latest Article, in addition you can use one or the other option, which is missing (unfortunately) in the Latest Article Module.
That's why I find the concept interesting in terms of functionality in a module that is named the same as a menu item, including the same functionalities / options. In the case of the ED Ask Module I can predefine the category
, but at the menu item I can predefine the category, but not at module (among others).
There are situations where it makes sense to create a normal J! Article Page with a module (eg Ask a Question) instead of a menu item (Ask), for example if you want to provide more information or functionality on the same page.
For the argument of the place / extent of a module I must say that the sole choice of options does not yet say anything about the space requirement. The more options a module offers - e.g. on the filtering and sorting of entries / contributions - the more flexible and targeted I can use it, and it could well be that I only want to use one single option (in my case the filter category filter). This usually has no effect on the module's footprint in the output in the frontend.
Do you think that would be possible in principle to further develop the ED modules? I think that would strengthen ED's potential, but perhaps most decisively. And I, in the current project for the Swiss Paraplegis Research would be very helpful ...
Best greetings from Switzerland
Christian