4. Changes needed to localStorage.setItem('profileImage') ? Couldn't tell where 'profileImage' was first stored/created and if it could be changed to 'accountImage'

The initial point where profileImage is first stored is SignedInUserContext

I don't think we actually want to change the name of the civic profile to this. IMO it makes the UI more confusing.

This is an object that contains specific, sensitive information that should only be shared with certain people. We need a name that communicates that to users. The purpose of the adjective "civic" in "civic profile" is to communicate this. "Profile" is vague, and not actually all that distinct from an "account."

"Account" itself is also a weird name because that data isn't associated with an account. An account is an entry about you opened in the books at some organization. That's not what happening here. You're instead modifying data on an ID card that has been issued to you.

Fair.

1. Maybe we should have some sort of workflow for Issues, then. So people don't spend hours on things that haven't been agreed upon.

2. Do you have any suggestions for naming then?

3. I probably just don't understand the whole concept of why we have a 'civic profile' and a 'profile', as I've missed a lot of dev meetings. But if it's just some data is private and some is public, why not just have a single profile with two sections - the public section and the private section?

@xscottxbrownx Let's move this discussion over to the issue.

@xscottxbrownx Are you opposed to closing this? I don't think we'll be acting on this PR as is. I think we need to talk more about the fundamental design. We can reopen this once we get the design more hashed out.

Continuing discussion before implementing any changes - closing PR for now.