Coordination Wiki Typle Website

Seeking development of “wiki / living document” type web application to help facilitate coordination of Architecture firm with clients and consultants. We would like launch by mid-October. UI can be similar to Wikipedia or a forum. Programming languages are at the discretion of the programmer. Set-up and initialization of website on our web host will be included. Project will likely have future expansions and tweaking under separate contract. Respondent should be a creative problem solver able to identify how web and mobile technologies can accomplish our needs and able to implement them in an intuitive interface. Please submit examples of your work demonstrating your abilities along with a short description of the technologies and programming languages you will employ to handle the project. Include a list of the capabilities from my description below you plan to include (the more complete the better). Below is a description of the functionality of the application as we imagine. If any ideas are costly to develop we welcome your input on streamlining the project to get it in budget. Application will determine user accessibility based on logging-in with a user name. There will be three types of users: 1. Owners (members of the Architecture firm who will be administrators.) 2. Consultants. 3. Clients. Functions and interfaces are described below: CLIENT We deal largely with schools so our clients often include all the administration, teachers and the school board at a school, a single project could easily have 100 client users (need an easy way to create a mass list of new users assigned to a project). Clients would be restricted to view only documents associated with their projects. Documents will be of the following types: Survey, meeting notes, PDF, Images (jpg, png) and video (flash, mp4). After log-in a client will be taken to a list of available documents for their associated project listed in chronological order. Meeting Notes This is the main function of the Client side interface. We would like to be able to have an editable living document similar to a wiki to easily add documents, edit and format (headers, sections, images). A comment interface would be spectacular, but could be forgone if cost prohibitive. This would allow clients to add notes without editing the document to preserve the fidelity of the original. Surveys Ability to propose surveys to clients in short answer / essay format. Results will be automatically published as new document. Could be forgone if cost prohibitive. PDF Drawings, specifications and presentations will be uploaded as PDFs and will need to be available for review. A comment interface is desired, but could be forgone if cost prohibitive. Images and Video Same as PDFs. Could be forgone if cost prohibitive. Email We would like all users to be automatically emailed each time a document that they have access to is updated. CONSULTANT Consultants will be restricted to viewing only projects they are working on (assigning users to projects). Consultants will be greeted with a list of projects on which they are working after signing in. Each project will have: Action items, meeting notes and PDFs. After log-in consultants will be taken to a list of available documents of the types mentioned above, listed in chronological order except for Action Items which will remain at top. Action Items Action Items will be a “To Do” list. Each item will have the following elements: (1) Assignable to consultants (possibly several consultants, including us), (2) Title, (3) Task Description, (4) Due Date and (5) Completed / Incomplete assignment. When an Action Item is complete it will be moved to a completed list at the bottom of the page. All users will be able to create action items. Possibly a function to email all Action Items to all consultants with single click. Meeting Notes, PDFs and Email similar to Client side. BACK END The back end will have to be developed in future talks.