Improvements to PhotoSchool's Rails3 Website

We are a photo school with a dynamic Rails 3 website developed in-house
- we host on heroku.com - developer MUST have heroku experience and knowledge as well as fluency in Git, Rails 3, i18n, Active Record.
- we value super-clean, organized, simple, dry code and work habits, good communication skills.
- modifications must be documented and explained (skype or text-chat) to site owner who wants to maintain the code in the future

A. Small improvements of existing features and environement
A1. update of project to rails 3.2 (gem file) shouldn't pose any problems, everything is standard
A2. creation of a staging environment on heroku to deploy dev versions of website for testing & review, including a dev version of database (currently there is only one live environment)
A3. explanation to site owner on how to migrate site and database schema and data from dev to prod
A4. Improvement of contact form and newsletter subscribe form to include validations (non-empty, email format), return to page with previously entered values displayed in case of error

B. Implementation of i18n with a Redis or ActiveRecord backend
B0. discussion to decide on chosen backend (redis, active record or else, speed and caching aspects)
B1. implementation of i18n in our app with chosen backend
B2. creation of simple but clean crud admin interface with authentication to list existing translation keys, organized by website section, including a search box to search / filter the list of existing keys
- clicking on existing key goes to editing page
- delete button with each key to erase it from DB
- add button to add new key / values
B3. edit view to edit existing or new translation key / value - form shows key, value in locale1, value in locale2, submit, cancel

C. Implementation of course calendar in DB - ActiveRecord
- model include courses, classes, course type, dates, language - more detailed brief will be given
- future classes pertaining to a course - appear in course page
- future classes appear in calendar page grouped by course / location / language
- every class listed has link to registration form
C0. architecture discussion to establish schema
C1. dev and implementation of model, controllers and view modifications, including migrations
C2. improvement of registration form, including validations, error messages, send email with registration data
C2. creation of admin interface with authentication to CRUD courses, course types & classes