| 57 | === Developers === |
| 58 | The idea that I'm working on is that people volunteer Money, Time or Goods |
| 59 | |
| 60 | Money is an Organisation Need stored in the req_organisation_needs component |
| 61 | - essentially we will just give people a list of Orgs which are soliciting cash & the websites they can visit to donate...there is also a Rich-text box to add extra details |
| 62 | |
| 63 | Goods is a Site (currently generic org_facility) Need stored in the req_site_needs component |
| 64 | - essentially we will give people a list of Sites which are accepting drop-off donations, along with direction for how to get there, opening times & a rich-text box for them to describe the types of goods they're accepting |
| 65 | - later we'll add a search for 'closest'. |
| 66 | |
| 67 | Time is split into 2: |
| 68 | * Remote time is an Organisation Need |
| 69 | * Local time is a Site Need |
| 70 | The basic workflow is as above |
| 71 | |
| 72 | So what needs doing? |
| 73 | * Custom Forms for creating Orgs/Sites with their Needs |
| 74 | * Renderers for Orgs & Sites including their Needs (I think datalist will work better for the Rich text) |
| 75 | * Filters |
| 76 | * Location 'Nearest' Search |
| 77 | * Security Policy |
| 78 | * Latest Needs widget on homepage (like DRM's Latest Incidents) |
| 79 | * Needs summaries per Lx |
| 80 | * We almost certainly want to be able to zoom-in within an L1 to see the component L2s in the Profile Selector page (& maybe within the Profile) |
| 81 | |
| 82 | Obviously there are UI design aspects too, but we can integrate what any volunteer who steps forward on that does. |
| 83 | |
| 84 | Other ideas also welcomed. |
| 85 | |
| 86 | e.g. I can think of an alternate workflow where Needs are all just cms_posts of type 'money', 'time' or 'goods' & we have a single 'newsfeed' of all |
| 87 | |
| 88 | |