What buttons? You mean the templates? Oh, yeah, those are in one part of the tree. Database layer in another (so that when you become famous and have to upgrade to Oracle, you don't have to rewrite your app from the ground up - just the interface layer). Oh, and that interface layer also allows for IPC, if necessary for synchronization.

Hmmm ... Logging in shouldn't be something special. If it is, that specialness should be in the Apache handler, not the place it lives.

As for modules - make modules for business objects, not developer processes. If you can't figure out what business object(s) are involved in a given feature, that means you don't understand what business purpose that feature serves, and, thus, it's a waste of time. (Worse, it'll introduce bugs into code that was fine before.)

Basically - think like a business person who can ask things to take care of business needs. Kinda like top-down decomposition, but in terms of business, not development. Then, build objects/modules to handle those business needs. Your features are now just chains of these business things working together. :-)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.