Creation of integrated log-in/comment system on our Drupal website

Project Description: We’re seeking a developer to improve upon our log-in/comment system on our new Drupal website ([login to view URL]). Currently, our system is very fragmented, and user registration data can be saved in separate locations. We’re seeking a more integrated comment system, along the lines of Disqus, which will allow users to log-in, comment, and share via social media. The problem with using Disqus is that it is not native to Drupal, so data are saved external to our Drupal database. We’re looking for a developer that can create this user registration, log-in, and comment system that is fully integrated within our website. We want users to be able to log-in with their Facebook account. Our current system allows for this, but it’s fragmented from our website log-in. Website visitors can only use their e-mail address for either Facebook log-in, or website registration. This current system is clunky to navigate. Disqus could be thought of as a model for this system, though there may be other services that have additional features. Disqus has the professional display that we’re looking for, but we’re open to hearing suggestions for possible model systems. We look forward to seeing your bid. Milestone details: 1. Development of detailed specs and wireframes of the system. These specifications will outline how this system will be fully integrated and easy to use on our website. 2. Creation of the integrated log-in/comment structure. 3. Ability to log in via registered website username, or via Facebook. Currently, users can do one or the other, because a single e-mail account can only be used for one. We’d like users to have the flexibility to do both. Additional project specs: 1. We ask that our developer use Trello, an online project management tool, to communicate for this project. It’s a very simple tool to learn and use, and it helps us keep track of progress. 2. We ask that our developer use our development website for all work that’s done for this project. This will allow all changes to be made in a protected environment before going live on our website. No development work should be done on our live website unless we give confirmation (which will only be done in emergency cases). 3. Each deliverable must be tested on the three major web browsers (Chrome, Explorer, and Firefox). Deliverables are incomplete until they are fully-functional on these major browsers. 4. Project documentation must be delivered with each invoice (or prior to each milestone payment). This documentation should include a detailed summary of the work completed for each milestone, as well as any details for user navigation (if applicable). Finally, this documentation must confirm that all work has been tested to operate on the three largest web browsers (Chrome, Explorer, and Firefox). Payment will only be released after these documentation specifications are met.