Rev share site design/build (pref. Drupal)

This is the first stage of a potentially large, ongoing site design project, dependent on the success of each stage. The site is for freelance writers. At first, it's just rev share (this stage of the development). Other options will be plugged in later. It is VITAL you understand this, as I don't want to go back to scratch when the new bits are ready: user info, job info and other stuff needs to take future development possibilities into account. I suspect the best choice of platform is Drupal, for better scalability and user access control, both of which will be important as the site and project complexity grow. If you have a different opinion, state it and your reasons, please. Stage One The first part of the project is to implement the basics of a rev share writing site, with the unique addition of editorial input (also based on rev share). To this end, the site needs to be designed and built. That includes user registration, profile, document creation (text editor) and handling, an editing queue, a moderation queue, a work queue, article display, page counting, revenue calculation, ratings, comments, on-site messaging, automatic payments at a given threshold, adjustable rev share percentages, flagging, an editing interface (text editor again), feedback, sharing/social buttons... all the usual stuff you'd expect and probably more. I have a couple of decades of experience in IT and have worked on requirements documents and software designs before, so things should go a little easier on the communication front, I hope. I'm not a design professional, though, so part of your job will be understanding the ideas and turning them into reasonable requirements. Most of the groundwork will be based on your understanding, not my technical knowledge. I'm expecting the whole thing to come in at a maximum of $1,000 total. If you want more, please explain why so I can understand. Although I'm new here, I have an excellent reputation with freelancers (on Elance). I can provide feedback/testimonials. If you're good at what you do, I'm reliable and a great client. If not, I don't want to hear from you, anyway. ;o) Read the detailed info, too: it's important. ## Deliverables Please note the following VITAL information and requirements: 1. I am looking for a reliable, potentially long-term relationship. This is step 1, the basic core system. There are more steps. They won't happen immediately but they're there. Consequently, you need to either be up for the long haul or produce clear, friendly code/processes/designs that other people can jump straight into (and that I can tweak and manage without having to hunt you down while you're on holiday). Slackers and half-assed plugin users are not welcome. 2. Do not paste a template "about our company" bid. No matter how good you are, I WILL IGNORE YOU (and I really don't care what your company does unless it's precisely what I'm looking for). 3. You'll need a sense of humour. I have trouble being serious. Personality is a major bonus here! 4. I will want to see sites you've built AND talk to their owners. I will want PROOF that you built them. I will not choose anyone who does not have experience, knowledge and, preferably, passion. 5. I don't mind if you're new to vWorker as long as you can somehow show me you know what you're doing (see 4). In some ways, it's better 'cos you'll want good feedback. ;o) 6. I only do email. No Skype. No phones. No IMs. I expect you to ASK if there are things you're not sure of, instead of going ahead and creating something I don't want. 7. If you don't include the expression "My hat is made of peanut butter" in your application somewhere, I'll assume you're a bot. Not literally, but I'll ignore your application. 8. I will happily consider individuals provided you can show me you've been around for a while and aren't about to disappear for a year's sabbatical in Timbuktoo. You'll be expected to fix your bugs! 9. There is no definite deadline as yet: I prefer to lay out the details and ensure understanding, THEN set a deadline. 10. This is not a project where you can install Drupal, plug in some pre-built stuff and walk away with the money: there's custom building here (mostly for the rev sharing and work approval processes). Don't bid if you've only ever built blogs or something - if it was that simple, I'd do it myself. :o) 11. In exchange, I'm not someone who obsessively watches that you're spending every minute on the work. I don't mind if you go for a pee or grab a coffee and forget to switch off your timer for 2 minutes. I understand erratic schedules and all the other crap that happens as soon as you accept a job (I'm a freelancer, too). I've tried to include everything I can but I understand that you might need more information to make a proper bid on this. For the first cut I'm interested in a rough guideline that we can hammer out before I finally choose someone: do the best you can and we'll talk from there. Attached documents are a starting point to estimate costs. I know for a fact that several of the processes need tweaking (I need to put in "reject" options at the start of editing, for example, for content that's prohibited and design the whole flagging process) so bear that in mind. They're just the basics.