It's certainly useful that entities can be exported. This way we can skip long paths. However, what actually happens is JUST passing an entity for visibility. No docs exporting, no module hiding. Which is quite weird for me.
Why I think submodules would be useful? * better encapsulation * smaller files (git will thank you later) * better documentation pages Actually, it seems to me the solution would be pretty easy: * _main modules_ \-- let every package define which modules will it expose * _submodules_ \-- all the other modules are only visible is explicitly exported in these modules (and then use motation mainmodule.submodule) * _visibility_ \-- if a submodule is visible, its exposed entities are both in its docpage and its parent docpage, but in a separate section (possibly "from submodules", "reexporting" or something like that) So the question is: is there any possibility to provide a nice, encapsulated module tree without sacrificing docpages right now? Includes are not a good solution.
