New Organization HTML Design

[aarontitus]

Original author: v...@aarontitus.net (February 18, 2013 06:29:37)

Note: I added the following form fields to the existing fields: Added:

• publish (Publish Organization Profile)
• water_pumping
• muck_out
• interior_debris
• gutting
• tree_removal
• exterior_debris
• sanitizing
• mold_treatment
• design
• permits
• reconstruction
• replace_appliances
• replace_furniture Removed: clean_up, mold_abatement, rebuilding, refurbishing

Use the attached .html file for now, as a template. "--Choose One--" should be the first, default selection on choose_event, and "None" should be the second selection. After that, incidents should be sorted by start_date, with the most recent on top.

Original issue: http://code.google.com/p/sandy-disaster-recovery/issues/detail?id=180

[aarontitus]

From andy.n.g...@gmail.com on February 19, 2013 06:48:15 Those added fields will require a schema update, I don't know if I can implement them tonight.

[aarontitus]

From cpw...@gmail.com on February 19, 2013 20:02:15 Done across /signup and admin and org pages as or r159

[aarontitus]

From cpw...@gmail.com on February 19, 2013 22:03:46 ...with the exception of "None" being a valid event for an organisation.

Open question: does this have any knock-on effects?

[aarontitus]

From v...@aarontitus.net on February 21, 2013 20:08:04 Will mark fixed. Good point about the cascading effects "None" being a valid incident. Either we can create a "None" organization (which I'd prefer NOT to do), or we simply allow individuals to join unassociated with an Incident... in which case we'd have to create special logic for that case.