|
I'm quite new to Django and OSQA, so it'd be great if someone could tell me how feasible this is before I dive in too deep. Let's say I install OSQA as per the default procedure on Webfaction. I'd like to use OSQA as the core of my site, but also develop other apps/functionalities that seamlessly integrate OSQA's authentication and user profiles. Can someone describe the basic scaffolding code and/or procedure to begin development of a extension app? Not asking for a full-on Django tutorial, just a description of the minimal codebase for an OSQA piggyback app. Thanks! If someone can give me a starting point, I'd be happy to document/open-source my findings and contribute to the OSQA ecosystem. UPDATE: Upon futher research I've come across the concept of OSQA "modules". Should additional, non-QA related site features (eg. a community photo gallery or events board) be added as modules to OSQA or as higher-level Django apps? Is there documentation somewhere of how modules work and what they're for? |
I have the same problem too,I hope someone can help us!Thank you!
Anyone? I've read all the threads related to this question, and while many have said that integration/extension is readily possible, I've found not the slightest documentation on this matter. A quick rundown for the neophyte would much appreciated by many...