Closed timbot1789 closed 7 months ago
This is a simple form right now. It just allows you to upload an address. It hasn't gone through any UI design pass, and we will need a somewhat sophisticated design to figure out simple ways to ask about a person's homelessness history.
Are these being left for [Part 2]? What will that PR entail?
This is a simple form right now. It just allows you to upload an address. It hasn't gone through any UI design pass, and we will need a somewhat sophisticated design to figure out simple ways to ask about a person's homelessness history.
Are these being left for [Part 2]? What will that PR entail?
I haven't really thought about it too much. I'd like to be able to include the other 3 fields referenced in the PR. But we also need a separate question "Are you currently homeless?" because that would exclude the field "How long until you lose your house." There are also additional questions we can ask about their history in shelters. How worthwhile those would be I don't know for sure.
I haven't really thought about it too much. I'd like to be able to include the other 3 fields referenced in the PR. But we also need a separate question "Are you currently homeless?" because that would exclude the field "How long until you lose your house." There are also additional questions we can ask about their history in shelters. How worthwhile those would be I don't know for sure.
Makes sense.
So would updating the UI be next or wait until later on?
I haven't really thought about it too much. I'd like to be able to include the other 3 fields referenced in the PR. But we also need a separate question "Are you currently homeless?" because that would exclude the field "How long until you lose your house." There are also additional questions we can ask about their history in shelters. How worthwhile those would be I don't know for sure.
Makes sense.
So would updating the UI be next or wait until later on?
I don't think there's any rush. We can pass this kind of thing over to the UI team as well and see what their thoughts are. Ultimately we as a project team need to figure out what data points we want to capture, and what use we have for them, then send that over to both UI and dev.
My goal in the meantime is to get the Civic profile to a point where it has the information you need to fill out an I9 form or other employment forms. An address is a necessary part of that.
I don't think there's any rush. We can pass this kind of thing over to the UI team as well and see what their thoughts are. Ultimately we as a project team need to figure out what data points we want to capture, and what use we have for them, then send that over to both UI and dev.
My goal in the meantime is to get the Civic profile to a point where it has the information you need to fill out an I9 form or other employment forms. An address is a necessary part of that.
I assume you meant UX that first time rather than UI? They have asked what the difference(s) will be between the civic profile and the user profile in terms of design. If they're intended to be mostly the same then that would save them some effort.
They have asked what the difference(s) will be between the civic profile and the user profile in terms of design. If they're intended to be mostly the same then that would save them some effort.
I think it's safe to say that the "Civic Profile" is the personal profile of people where we'll have sensitive information like housing, financial, etc. For what we have as "Profile" or user profile is something akin to an online account for a web service, where only things like names or emails are available and can be seen publicly.
Think "Account" would be a better term for what we have as "Profile" right now and we could actually have "Civic Profile" be named as "Profile" proper.
I think it's safe to say that the "Civic Profile" is the personal profile of people where we'll have sensitive information like housing, financial, etc. For what we have as "Profile" or user profile is something akin to an online account for a web service, where only things like names or emails are available and can be seen publicly.
Think "Account" would be a better term for what we have as "Profile" right now and we could actually have "Civic Profile" be named as "Profile" proper.
I wonder if "Profile" is a bit too analogous to "Account" in peoples' minds. Maybe something as simple as making "Profile" into "Profiles" would help differentiate the two.
I wonder if "Profile" is a bit too analogous to "Account" in peoples' minds. Maybe something as simple as making "Profile" into "Profiles" would help differentiate the two.
Not having them both with the same base wording, it'll would be too confusing, more so than now. Even if "Profile" is "too analogous" to "Account", we could still make a distinction that they should be two separate things.
Personally, I do see the distinction with "Account" related more on the administrative side of things, namely related with PASS, with "Profile" related more to information related to the user themselves.
For example, it's like having a bank "Account" which is associated with the "bank" (like account number and names), and user information (i.e. "Profile") which is associate with you (like mailing address, phone numbers, email addresses) which banks asks for after you have an account.
I don't think there's any rush. We can pass this kind of thing over to the UI team as well and see what their thoughts are. Ultimately we as a project team need to figure out what data points we want to capture, and what use we have for them, then send that over to both UI and dev. My goal in the meantime is to get the Civic profile to a point where it has the information you need to fill out an I9 form or other employment forms. An address is a necessary part of that.
I assume you meant UX that first time rather than UI? They have asked what the difference(s) will be between the civic profile and the user profile in terms of design. If they're intended to be mostly the same then that would save them some effort.
This is a good question. Let's follow up in discord about it.
First part of a housing section for the civic profile. Uploading this in order to fix some bugs with the
useCivicProfile
hook, and to provide an example of how to use it.This is a simple form right now. It just allows you to upload an address. It hasn't gone through any UI design pass, and we will need a somewhat sophisticated design to figure out simple ways to ask about a person's homelessness history.
Also added a new devtool to allow you to start up both the pod server and the react server at the same time. Run
npm start
and you'll launch both. We use a small package calledconcurrently
to manage both commands in one process.