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

Adding search playground link #7324

Merged
merged 2 commits into from
Sep 21, 2018
Merged

Adding search playground link #7324

merged 2 commits into from
Sep 21, 2018

Conversation

samely
Copy link

@samely samely commented Sep 21, 2018

Context

Our Search Playground tool is live in www.mapbox.com/search-playground

Changes

✔️ Added a link to www.mapbox.com/search-playground.

@@ -3,6 +3,7 @@ title: Add a geocoder
description: >-
Use the [mapbox-gl-geocoder](https://github.com/mapbox/mapbox-gl-geocoder)
control to search for places using Mapbox Geocoding API.
Checkout our [Search Playground](https://www.mapbox.com/search-playground/) to test out geocoding quality.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: "check out" instead of "checkout".

"to test out geocoding quality" also seems like it could be phrased a little differently. It's not like going to the search playground gives you an immediate quality metric or comparison to other tools, right? Put another way, what's the difference between the "search playground" and the geocoder results the reader will already be able to see in the geocoder example on the docs page? Seems like if we're going to point people to the playground we want to highlight what extra capability it exposes.

Copy link
Author

@samely samely Sep 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: "check out" instead of "checkout".
😅

Yeah... you are right. We thought about adding it here since this is the starting point to add a geocoder, we also wanted to show what other options can be set up for a better experience using our geocoder.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah OK, how about something like "Check out our Search Playground to explore geocoding configuration options and test how they might affect results for your users"?

As a separate piece of feedback -- I didn't discover the "settings" option in the search playground until my third visit to the page, and only once I was explicitly looking for a way to control options. I was naturally just drawn to the search interface, and although I did try clicking a few of the buttons in the upper right, the first two I clicked didn't really grab my interest so I stopped exploring. Is the "settings" functionality a central enough part of the "Search Playground" that it makes sense for it to be showing/selected from the beginning?

Copy link
Author

@samely samely Sep 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your suggestion! Already fixed ^^

As a separate piece of feedback -- I didn't discover the "settings" option in the search playground until my third visit to the page

Your feedback about the tool is really valuable! We use it frequently and didn't realize this is not intuitive enough. I'm gonna open an issue to fix this! Thank you

Copy link
Contributor

@ChrisLoer ChrisLoer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@samely samely merged commit 426e09a into mb-pages Sep 21, 2018
samely pushed a commit that referenced this pull request Sep 21, 2018
@samely samely deleted the search-playground branch September 21, 2018 19:39
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

Successfully merging this pull request may close these issues.

None yet

2 participants