The non-technical aspects of this are being rewritten and transferred to my wiki

Please note that these pages below are intended to be read solely as wireframe models. They illustrate the information to be presented and choices to be made, not the actual interface design, which can be vastly improved.

RegenCHOICE interaction screens

  1. Registration process (a dialogue)
  2. Year of birth
  3. User preferences
  4. All the enquiries overview (entry point when registered)
  5. Help to choose an enquiry type
  6. An enquiry type, with details of enquiries etc.
  7. Enquiry basics
  8. Enquiry location
  9. Enquiry times
  10. Define or edit location
  11. Form an enquiry
  12. Add enquiry question (a dialogue)
  13. What I want in an enquiry
  14. A question in all enquiries
  15. Propose modification to a question
  16. Processing to establish correspondence and feedback
  17. Unanswered question
  18. My answer
  19. no-results
  20. many-results
  21. show-results candidates for enquiry
  22. Candidates for a particular enquiry
  23. Look at a candidate
  24. Their answer (with history for properties)
  25. Open invitations to contact
  26. Contacts across all enquiries
  27. Look at a contact
  28. Break contact with candidate / report abuse
  29. My answers and refusals
  30. Answer and muting in different enquiries
  31. My answer history
  32. Answer change confirmation

This is the index to the basic outlines of a set of user interaction pages for RegenCHOICE. They are written using only very basic HTML, so have no functionality – they show simply the kind of information that could be displayed on each page / screen or the system. Pages displayed will often start off much simpler than appears here, because the user will not yet have input the information that requires the space illustrated to display.

A localstorage test allows us to monitor what is in local storage,
and the genui page tests the most basic stuff.

Or see the Information architecture

The pages here adopt the following conventions.

Information that might be on the screen itself is shown inside the green box.
Links and buttons move you on to whichever next screen you would be taken to.
(Notes within the screen sections are given like this.)
Fields [in square brackets] would be replaced by information from the database.

The rest of each page gives further information about the interaction, including what the user is expected to be doing, and what the system has to do, and details remaining issues. It starts off visible, but with an icon showing that when you press ...
show info

link back here to index; name of page; pages that link to it

Diagnostics: ?

you hide the above information, and the icon changes colour – press again and this information will resappear.