Build a Website

We want to upgrade our website. It is based on a Google App Engine (GAE) Python and is currently mostly flat HTML files, but with some database info parsed into some of the HTML files via python. We run a private tutoring business and would like to replicate something one of our competitors has. Google for keystone tutors and look at /tutors; click on any or all of the tutor profiles to see what we want. This is clearly all stored in a datastore and auto generated on site. We already have a simpler version of this, one where each tutor has a name, a short blurb and an image; but not enough to justify a full webpage for each tutor. Our current implementation only works on 1 page of our website, our /tutors webpage. We can't put any tutor profiles on any other page (unless directly in the HTML), because our python script only works on /tutors. We would like to: 1. Create in GAE's datastore a database structure to house the info we want to display for each tutor. These info/fields defined by us before the project start. 2. Create a front-end so that consumer-facing webpages work. Note: we already have HTML and CSS templates etc... the thing we need help with is the datastore and the python. 2a. /tutors: pulling for a list of tutors an image, a name a short biography, links to the tutors full-profile on stand-alone webpage: /tutors/{tutor-name-and-or-id} 2b. /tutors/{tutor-name-and-or-id}. Pulling all information in the datastore for the given tutor. 2c. /{anything} on our website. I'd quite like to be able to pull a few tutor profiles onto any page of our website, not just the /tutors page – we’re currently hard coding into HTML when we want this. 2d. Two other extra cool things might be the ability to filter the tutor selection on any or all of these pages to various tags in the datastore for each tutor (eg qualifications, subjects taught, etc.). Cool-thing-1 is what they do on keystone where there is the button 'filter by subject taught'. Cool-thing2 is different: to be able to define, preferrably in the HTML (or maybe the python), what dimension and value we filter on, so only tutors who teach maths appear on our maths page, etc. 3. Create a subdomain or sub-webpage for tutors to edit their information in the datastore. 3a. Authenticated login... but hopefully no need for https, as no personal or private information will be passed between the browser and the server 3b. Happy to use google accounts to authenticate, but want to discuss with you how we do this given I only want people who we specify to be able to login and set up a profile. 3c. Admin-authentication-or-approval layer. I want edits on individual tutor profiles to be approved by someone who has admin login before they go live on the website... perhaps this can be achieved by having, for each tutor profile, an 'edittable' object in the datastore and a 'live' object. Once an edit has been made it can be approved by an admin. The result of this approval would be to copy the 'edittable' object to the 'live' object... which would then appear on the website. The point of this is to stop tutors deleting their profiles and/or putting swear words into the, etc. Looking forward to hearing from you guys. After we've finished this there is potential for more work adding more functionality to our website... ... Example 1: Testimonials. Ie, adding an ability for tutors to type in testimonials, these testimonials we could tag with 'subject', 'level', 'tutor', etc. We'd then want to be able to insert them into webpages (eg testimonials at the bottom of the tutor's profile page; or 'maths' testimonials from random tutors at the bottom of the 'maths' subject page) ... Example 2: Full tutor login. Where tutors can manage their details (including personal information, which would need to be HTTPS) ... Example 3: we have some more ideas too.