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

Build search disambiguation UI #31

Closed
theresaanna opened this issue Oct 20, 2014 · 6 comments
Closed

Build search disambiguation UI #31

theresaanna opened this issue Oct 20, 2014 · 6 comments

Comments

@theresaanna
Copy link
Contributor

Type in a search and hit enter or submit, see a summary of candidate results.

Dependency:
API endpoint
https://github.com/18F/openFEC/issues/75

@theresaanna theresaanna self-assigned this Oct 20, 2014
@theresaanna theresaanna added this to the Sprint 1: Osprey milestone Oct 20, 2014
@theresaanna
Copy link
Contributor Author

search_results_-_disambiguation

@jehlers
Copy link

jehlers commented Oct 20, 2014

Based on #33

@theresaanna
Copy link
Contributor Author

This should move to next sprint where the candidate API endpoints will be integrated with the front end.

@rjmajma rjmajma removed this from the Sprint 1: Osprey milestone Nov 4, 2014
@theresaanna
Copy link
Contributor Author

@noahmanger How many summary results should be shown for each data type?

@noahmanger
Copy link

Good question. Let's play around with it and see what works best. Let's
start with max of 5 per category.

On Wed, Nov 5, 2014 at 11:52 AM, Theresa notifications@github.com wrote:

@noahmanger https://github.com/noahmanger How many summary results
should be shown for each data type?


Reply to this email directly or view it on GitHub
https://github.com/18F/openFEC/issues/31#issuecomment-61870194.

Noah Manger
User Experience Designer
18F http://18f.gsa.gov | Work: 415-696-6146

@theresaanna theresaanna added this to the Sprint 2: Crane milestone Nov 5, 2014
@theresaanna
Copy link
Contributor Author

The functionality here is done. @noahmanger I'm hoping that you can take a stab at styling. I applied the table styling I'd already written in a hamfisted manner, to wonky effect.

While we're on the subject, I think we need to do some definition of widths on the table so that it doesn't expand when it becomes populated with rows.

I'm passing the task to you. Hope that's ok.

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

4 participants