CANS: Update CANS for IFPS providers to 1 column version

[tinhart]

Is your feature request related to a problem? Please describe. This was brought up in relation to the family disengages work item (GitHub #210) with Delton. Basically, the current 3 column layout or paradigm for CANS isn't ideal. A single column layout, for IFPS providers, has been proposed and conversation with IFD is needed, first, to determine how to approach the revision and what else may need to be considered/included in the work.

Describe the solution you'd like IFD to help us define the request (at mtg on 12/7/23), TBD for now, but it sounds like the layout for CANS would need to be revised so some amount of engineering time seems to be needed.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

Prioritization Process

• [x] Confirm the issue is a feature to which we want to devote resources.

• [x] Write user story in as a (role) I want (something) so that (benefit) format.

• [ ] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.

• [ ] Label story as an active backlog issue (i.e. an issue on which we will be actively working).

• [ ] Prioritize the story relative to other items in the active backlog.

• [ ] Review progress/priorities in weekly collaboration meeting.

[tinhart]

For user story/requirements information, see recording of discussion with Institute for Family Development (IFD) users/Homebuilders Program:

https://uwnetid.sharepoint.com/:v:/r/sites/og_cssat/Shared%20Documents/General/Sprout%20related%20development%20(mtg%20notes,%20requirements%20etc.)/Updating%20CANS%20for%20IFPS%20requirements%20discussion_120723.mp4?csf=1&web=1&e=Nw4XqM

[tinhart]

@subaykan should we close this issue, now that it is dev complete and deployed?