New Organization HTML Design

[GoogleCodeExporter]

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 reported on code.google.com by v...@aarontitus.net on 18 Feb 2013 at 6:29

Attachments:

• [New Org Signup.html](https://storage.googleapis.com/google-code-attachments/sandy-disaster-recovery/issue-180/comment-0/New Org Signup.html)

[GoogleCodeExporter]

Those added fields will require a schema update, I don't know if I can 
implement them tonight.

Original comment by andy.n.g...@gmail.com on 19 Feb 2013 at 6:48

[GoogleCodeExporter]

Done across /signup and admin and org pages as or r159

Original comment by cpw...@gmail.com on 19 Feb 2013 at 8:02

[GoogleCodeExporter]

...with the exception of "None" being a valid event for an organisation.

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

Original comment by cpw...@gmail.com on 19 Feb 2013 at 10:03

• Changed state: Started

[GoogleCodeExporter]

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.

Original comment by v...@aarontitus.net on 21 Feb 2013 at 8:08

[GoogleCodeExporter]

Original comment by v...@aarontitus.net on 21 Feb 2013 at 8:19

• Changed state: Fixed