Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

integrate Explore and Search #3221

Closed
chadwhitacre opened this issue Mar 4, 2015 · 2 comments
Closed

integrate Explore and Search #3221

chadwhitacre opened this issue Mar 4, 2015 · 2 comments

Comments

@chadwhitacre
Copy link
Contributor

They're really two ways of approaching the same task of discovery. The interfaces should bleed into each other. Reticketing from #3220.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Changaco
Copy link
Contributor

Changaco commented Mar 5, 2015

From #3222 (comment):

Not yet. In #3221, I'm proposing that we unify the Explore and Search interfaces.

You mean downgrade the search page to display a table instead of showing the excerpt of the profile statement ?

@chadwhitacre
Copy link
Contributor Author

There are a number of issues to think through here. I have time now to mention one:

We have a browse interface for communities on Explore, which includes a name filter that duplicates the communities results on Search (though the Explore filter doesn't have fuzzy matching; on the other hand it's zippier because the data is already loaded in the client). Why do we have two ways to search communities? We should have one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants