This is a simple quiz interface for part of a Web site.
When a visitor lands on the quiz page, they will see a list of about 10 multiple choice and true/false questions. They will choose their options via radio button or checkbox. When they click "submit," the page will (1) add a paragraph of supporting text to each question (text to depend on whether they got the question right or wrong); (2) right and wrong answers will be marked; and (3) the visitor's percentage of right/wrong question answers will be displayed (specific to that visitor, NOT cumulative of all visitors).
Design work will be done here, we will supply you with question and answer text and correct answers.
Heavy commenting is imperative so that our designers will know where to fit things over time (i.e., where to change right/wrong graphic) or to facilitate changing questions, answers, or which is right/wrong.
## Deliverables
* * *This broadcast message was sent to all bidders on Tuesday Nov 9, 2010 5:05:34 PM:
Hi Everyone,
Thanks for all the bids and questions. This is only our fourth or fifth project with VWorker, but the response is much greater than the earlier ones. I thought it would be best to use the “broadcast message to all bidders?? to answer some common questions:
All design work is taken care of here??"no need to worry about that at all as long as languages are limited to HTML/PHP/CSS/Javascript. ?
Perhaps many of your questions can be answered by describing the context a bit more. The site’s main purpose is awareness-raising of poverty issues. The quiz is a tool to engage the interest of a segment of visitors. A sample question is:
*_Poor city dwellers are often totally neglected because public health authorities:_u>
a)? ? ? Do not pay attention to poor city dwellers
**b)? ? Do not collect information in informal or illegal settlements**
c)? ? ? Do not have enough resources to identify poor city dwellers*
There does not need to be any quiz-based security??"if someone *really* wants to look up the answers in the source code, that’s fine. There is no prize or stakes involved, nothing other than quick interest-generation. So to keep things easy to change over time (and easy to implement), there isn’t a need for a database. I can work with SQL statements, but I can’t say that whoever takes it over in the future will be able to. The only “security?? on this area of the site is standard/baseline PHP/HTML protections and conventions.
Along with the lack of database, there doesn’t need to be an admin interface. Anyone who will be changing the site will have, at the very least, a basic knowledge of HTML and will be editing text within the source code. I have a fair knowledge of HTML, PHP, and Javascript (but am **NOT** a professional) and can follow code well enough to know where I shouldn’t make any changes (and if I’m in doubt I know enough to leave it alone!). Anyone I turn this over to will have similar skills in knowing what to and not to change (and will know ahead of time that if they do change something they shouldn’t, they will have to hire someone to re-code or fix it!).
Note that my Flash skills are miserable to non-existent. So this must stay in PHP/HTML so that our designers can fit it into the existing look and feel (one that may change over time).
The percentage at the end is simply a bit of feedback after they hit submit??"nothing fancy, nothing cumulative, nothing too personal. A simple “Congratulations, you got 90 percent of the questions correct!?? (or something similar) and perhaps a bit more explanatory text, depending on the question.
As for timing, we’re hoping to launch over the weekend??"which means we’d really like to have something as close to done as possible by Friday afternoon. Bugs, hiccups, and unforeseen details, of course, frequently monkey with our plans, but we’d appreciate it if we can get mostly there if possible (or all the way there if everyone is lucky!). ?
I hope that’s everything~
Rhythm