How can you say slash would be the perfect architecture if you have no idea about how to go about doing what you're trying to do?
But presuming slash's applicability... the first step would be to look at the database and see what's missing and what can be reused. Once that's done you'd start implementing the different elements of the interface. These same steps would apply to just about anything you'd want to do.
I understand the slash architecture in the sense that it allows users to submit stories much like a bulletin board and is self-regulated. I am admittingly ignorant to the backend or the inner workings of slash, however, if you look at http://answer.google.com it seems to me that slash is a lot like this architecture but far superior. I appreciate your suggestion and would appreciate other suggestions related the setting this up with mysql, mod_perl, and apache. Basically I'm looking for someone willing to help me with this project because the site is not that difficult to maintain and this seems like a good business plan with the potential to make some extra money!
I personally found the O'Reilly book on slash [oreilly.com] very helpful in learning how slash works. Once you've gotten that under your belt, figuring out the rest should be pretty self-evident.
Not to be rude, but. (Score:1)
But presuming slash's applicability... the first step would be to look at the database and see what's missing and what can be reused. Once that's done you'd start implementing the different elements of the interface. These same steps would apply to just about anything you'd want to do.
</chris>
Allow me to clarify my statement........ (Score:1)
Re:Allow me to clarify my statement........ (Score:1)
Parent