Daniela Baron

Tricky part may be on each given save of a section, determining which is the next section to render as expanded (and to ensure all the others are rendered as...

@cielf A question about the `Submit for Approval` button that shows up in each step/section from an earlier [comment](https://github.com/rubyforgood/human-essentials/issues/4504#issuecomment-2310243674): > Submit for Approval, in addition to saving, changes the status...

@cielf It's still a work-in-progress, but at this point, there's enough of the flow working that it might be useful if you have a chance to try it out and...

@cielf I'm thinking maybe I should hold off on further development (such as those TODOs) until hearing back on results of UX research?

Currently every time the "Save and Next" button is clicked, it should be saving whatever is entered into that section, no matter what order the user goes on. Did you...

Just to confirm the alternate interaction: 1. User has a current section open, for example "Agency stability" 2. They start filling it in, for example "Year Founded: 2014" 3. Then...

More on the above, it _might_ be possible to capture _both_ the section being closed and new section being opened if the close/open events always occur in a predictable sequence....

Here's how it works currently (and this could be considered a first attempt and discarded if there's a better way): Each section is built out as an individual form, they...

Another thing to think about if we start connecting server-side behaviour to the open/close caret icons: User could simply close the section they're currently working on, without opening anything else....

The last [commit](https://github.com/danielabar/human-essentials/commit/a5078f05deca2b96914ad6a6cd73293cab788b3d) on this branch has a first attempt at connecting the server-side submit behavior with the accordion open/close events. The following scenario should now work: 1. User starts...