554126 Help Complete Calendar part of a CMS 2 2

We have an in-house CMS that has a good foundation, but one of its modules is lagging behind so I thought I'd get some outside help from ScriptLance. The CMS is built using a mixture of PHP, MySQL/MySQLi and XML to get and manage the data, with .htm templates for displaying it. We use Subversion in conjunction with Dreamweaver, and host the test site on our web server, so access won't be a problem. I can provide phpMyAdmin access although you shouldn't need it for this stage of the project (we did all that already). This particular project is an Event Calendar with registration capabilities. It needs the following items completed, using what we've already put in place as a guide: FRONT-END * Registration form templates that can add/remove attendees using jQuery and also apply pricing to the # of registrants. * Calculate subtotals and build payment links to Google Checkout, PayPal, and also a local payment form (which would run over SSL) * Process the registration form, send out preformatted emails to admins and registrants as well as a receipt ADMIN AREA * List the registrations for each event, and registrations as a whole for upcoming events * Edit/Delete registrations (there won't be an "Add" form) * Send email reminders to those who haven't been marked as "paid" * Export the list of registrants to Excel, or at least a print-friendly table We'll be actively involved in the design and CSS part of things; you'll see how we structure our HTML and CSS -- as well as how the functions all flow together -- once you begin working on the project. I expect the same formats to be followed. We can provide PayPal Sandbox accounts to test PayPal integration; I don't have a Google Checkout sandbox (if there is such a thing), and at the moment the local credit card form would just capture the information, encrypt it, notify the admin who would process it offline, then mark it as paid via the admin area (at which time the credit card data would be destroyed from the database. SELECTION CRITERIA: Candidates who can demonstrate that they read through this project outline and can provide samples with reasons why they're samples, as well as those who take the time to ask intelligent questions about the project to get a more thorough knowledge, would be viewed in higher favor than those who simply put down 50+ irrelevant links and not much more than "we can do this" in the message board. This may lead to more work on other parts of the CMS, so put your best foot forward. Lastly, I'm not interested in sourcing this to a team, so please do not waste either of our time. Thank you!