Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do a first round of UX improvements #27

Open
slifty opened this issue Sep 29, 2021 · 2 comments
Open

Do a first round of UX improvements #27

slifty opened this issue Sep 29, 2021 · 2 comments

Comments

@slifty
Copy link
Contributor

slifty commented Sep 29, 2021

I'm keeping this general for right now just as a "meta" issue since this will be a little more like jazz than spec.

The current UX was built in order to make sure the backend worked and to provide a baseline of functionality -- it needs to be improved with the user in mind.

This includes things like:

  1. Basic layout improvements.
  2. Removing unimplemented features.
  3. Adding some color.

This probably shouldn't include larger things like #17 or replacing our autocomplete with a more fully featured one (e.g. one that supports keyboard commands out of the box), but that will come next.

@kfogel
Copy link
Member

kfogel commented Sep 30, 2021

I sent (most of) this in email, but just to put it here for reference / archiving / proper transparency:

The top URL should be https://cgap.opentechstrategies.com/poc-demo/. (We should have a redirect from the old :8080 instance (sorry, unanticipated side effect of impulsive preview access).)

Under that, two paths:

  • gms-apply: New name for what is currently ux/apply.
  • search: New name for what is currently ux/review.

Now, a couple of things:

  1. I realize this would get rid of the ux component. If there's a reason why that component is there, that I just don't understand yet, then let's talk about it -- I'd at least like to understand the tradeoffs before having a firm opinion.
  2. Maybe the reason you currently have .../review/ as the default search path is because it works the same way as the apply screen does, just with some fields hidden at first? Happy to chat about that too. But based on the goals for our intended audience, presenting the search screen as "Search" (both in title and URL, but I can do the title change as part of some more extensive text changes I'll be submitting) would make more sense. They're not coming to that screen to review proposals, they're coming there to find organizations.

@kfogel
Copy link
Member

kfogel commented Sep 30, 2021

And Jim is updating the sample data, so we should pull in the new data (I assume that's costless).

slifty added a commit that referenced this issue Sep 30, 2021
The first round had a `ux` prefix for ux routes (I thought I needed to
have a prefix for flask to be happy; thank goodness that isn't the
case!)

This also renames the `review` pages to `search` (which is more
accurate to the use case, and makes the route for viewing a proposal
a bit more descriptive (`proposal/ID`)

Issue #27
This was referenced Sep 30, 2021
slifty added a commit that referenced this issue Oct 1, 2021
The color isn't robust, but it's better than no color!

Issue #27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants