asked 2010-09-07 06:36:42 -0500omat
from the organization of code, it seems to me that askbot is designed as a standalone project, which is good as a turnkey solution. but if it is to be used as a part of a larger project there may be problem due to non-core functions (tagging, authentication, reputations, etc.) being tightly coupled.
what would you think of having apps like authentication, reputation management, tagging, etc. as separate applications that can be used out of the box, or can be replaced by existing solutions in a larger project?
edit: regarding askbot being designed as a standalone application - actually it's not a goal, there's no plan to keep it "closed up" this way. The login application will be the first one to be decoupled.
I don't want to "go overboard" in splitting out components too fast (although you are bringing valid points), because in practice too much redo at once often leads to chaos.
But that said, your suggestions sound interesting. Maybe you will be willing to add those features? If you do - please maintain migrations and test cases.
answered 2010-09-08 06:14:05 -0500kocakafa
I agree to the idea, modularity is an important issue when it comes to specific concepts as reputation or tagging and so on. In my humble opinion, reputation, tagging and authentication are basic concepts for a Q&A based web community and should be considered particularly.
Create your Q&A site at askbot.com. Managed Askbot hosting at just $15/mo. Dedicated hosting, support contracts, consulting services.create your Q&A site
Asked: 2010-09-07 06:36:42 -0500
Seen: 95 times
Last updated: Sep 08 '10