Digg-style Site Builder

I am looking to build a web application that will allow power users to create their own digg-style site (see [login to view URL]), populate it with stories using rss feeds (chosen by them, url entered into the app). The resulting sites will be hosted by the app on our system and be accessible via a subdomain (i.e. [login to view URL]). This system will be based on the Pligg CMS (a PHP digg clone) and MagpieRSS (a PHP rss parser). **We have already completed the integration between Pligg and Magpie RSS! ** What we need is the builder and the multi-site infrastructure. Please take a look at <[login to view URL]> for a mock-up ## Deliverables This project will entail two parts: First: We need to build the "builder" web application -- this web application will allow the user to name their site, enter in a topic, create categories within Pligg and enter RSS urls for each category. The builder will also allow the user to design their look-and-feel by offering template choices, or allowing the user to choose colors for the banner, type in text, choose the layout, buttons, etc The builder may also allow the user to enter in their own banner and background image. The builder will also have a user database, registration, etc. Second: We need to build the multi-site infrastructure and back-end. The builder app will be able to a) initiate a new instance of Pligg + MagpieRSS, create categories in Pligg, create/schedule new RSS crawls. The back-end will be able to host and run everything on one webserver array and one database array (i.e. so a new database will not be needed for each site -- though we are open to other ways of doing this) The back-end will also automatically create a user database for each of the new digg-style sites created by the builder (this should be taken care of by Pligg) as well as automatically create a subdomain, whereby the new site will be accessed. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform PHP/Linus