Elise Kalstad

Gwen's ideas: do a separate repository for wiki, not part of main project code base; could also pair with "discussions" or start with "discussions" then move to wiki when finalized.

Pausing deployment on this until early July (when Swathi is back in).

@msprenke @Miguel-314 -- To bring this up with Product Design Committee (4/30) Options: could be customization on the question or the program level. - Question level--would apply to all programs...

@jcma-google Are you still working on this?

This will be a requirements ahead of Trees next application cycle, May 2025. So plenty of time, but also a complex one, eh?

The other option we've discussed would be a different feature request, separate from visibility conditions. It would force an applicant to "skip" questions, based on how they answered previous questions....

To consider: adding a "pointer" from one screen to jump to another screen. (Per Nick's ideation)

Reviewed at 9/14 cross team meeting: consider short term solution to NOT show "meets eligibility" IF there is no data under eligiblity questions. Long term solution likely tied to updating...

To consider as a good first issue.

@avaleske -- That's a good idea, perhaps for a more advanced solution. There's benefit right now to having test applications easy to access for sharing testing responsibilities across staff. For...