Build and implement a website using specific technology

Objective The objective of this project is to implement a fully-functional Travel Ideas website by using the technologies and the development methodologies . Technologies and standards involved use any one of the following to implement the website.  The Zend Framework + jQuery + MySQL; or  Ruby on Rails + jQuery + SQLite; or Specifications A user has to log on (with his/her email address and password) in order to use the website’s functions. A user has not logged on should be prompted to sign in or create an account. Upon successful login, the user should see a welcome message with his or her name. The website should include the following functions. Page 1 of 7 1. USER ACCOUNT CREATION  Email address, password, first name and last name are required. 2. MODIFY/MANAGE USER ACCOUNT  View account information  Modify email address, first and last names.  Modify password – requires verification by providing the existing password 3. MANAGE (ADD/DELETE/MODIFY) TRAVEL IDEAS  The user can add a new travel idea with title, destination, start date, end date, and tags.  A user can edit all information about all travel ideas he/she has created. 4. SEARCHING OF TRAVEL IDEAS  Searching by destinations or tags.  For destination, users have an option to do a partial search. For example, if "Hong" is used as the search keyword, "Hong Kong" should be part of the matched results (if such entry is present in the database).  Search results should have the following information for each entry returned: title of the planned trip, destination, date (MM/YYYY), and number of comments.  For all queries, display a total count of matched records. [login to view URL] VALIDATIONS  Data validations are required for user account management and travel idea creation. 6. WEB API MASHUPS  ONE modules that perform mash-up with any ONE web APIs relating to traveling or trip (see [login to view URL]).**  Hint: many web APIs relating to traveling are keyword-based. In our website, the tags, start date, end date and/or destination specified in each travel idea can possibly form those keywords.  Content in the comments might be useful for the mash-ups as well.  For example (just an example - you don't have to adopt it; please feel free to propose to use another API if you wish), you may implement a mash-up with the Hotwire Hotel Deal API (a hotel recommendation service): [login to view URL] [login to view URL]