I wouldn't worry about it yet. If you do only what you really need to do to meet your current needs, you'll probably find it easier to add modules in the future when you know what you need. Since you don't have much code now, you'll have better results getting the basic forum and bulletin board code working solidly.
When people start asking for two or three features that you think would make good modules, you'll have a better idea what people want for modules and how to add them to the system. That's when I'd start thinking about them.
The best way I know of to make software easy to extend is not to extend it until I know exactly what I need. One rule of thumb is, "If I'm thinking about features I don't need yet, I'm probably going to design and implement them wrong and will have to rework them when I really do need them."
In reply to Re: Best way to 'add modules' to web app?
by chromatic
in thread Best way to 'add modules' to web app?
by BUU
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |