Module names for wiki

[sgold]

@mitm

@sgold

What function do modules serve?

A module can be looked at as a Book. The topics are chapters in that book. No two modules/books contain the same topics.

That’s a nice analogy, but it doesn’t help us decide how to divide the wiki into modules. Paper publications are split into books for reasons that are irrelevant to a website. Once we understand what modules are for, I suspect the answer to your question will be clear.

@mitm

Having one module is what we have now. Everything is lumped into this one module. If all we were going to do is use this one module then what was the use in converting to a modular system in the first place?

You’d know better than I would! Your post indicated a desire to have offsite modules maintained by independent owners. If that’s what modules are for, then perhaps modularization should be based on repositories and/or owners.

@mitm

I really like the detail given in your post but I am surprised you list physics as a topic/chapter rather than a component/book given you have a complete site built around this one subject. That is one thing all engines had listed as a component, physics.

That’s an interesting point. Actually my website consists of 2 modules. There’s a “minie-library-tutorial” module that walks you through using the Minie physics library in a JMonkeyEngine game, and then there’s a “ROOT” module for all other aspects of the Minie Project. My thought was that all the “minie-library-tutorial” topics would eventually be shared between my site and the JMonkeyEngine wiki, while the “ROOT” topics would not be shared.