it'd be cool to track searches and outbound clicks. They have something called a "goal conversion rate" which we could potentially learn about and use to see how often people actually use the site for things.

There is no easy way for users to know about the weather area page:
climbplan.com/#/weather

I only found it after looking through some of Priti's commit. I suggest putting a button on the front page labeled "Weather Area" or "Mountain Forecasts" to goes to that page

map is too big; swiping around on the map moves the map instead of scrolling -> no way to get down to the results!

sites:
peakbagger
cascadeclimbers
weather.gov
caltopo
WTA

hovering over a research link should show a tooltip. This came up in James' user test - he clicked through to SummitPost and started asking questions about what that site was

they change the URL but not the page. Chrome on Windows 10

The typeahead dropdown on the intro search page renders over the search box itself instead of below it

Should give the user a better idea of what the site does without having Jason or Jaime standing over their shoulder.

eg. "Ranier" should correct to "Rainier". It's possible this could be achieved through the fuzzy matching options on the GeoNames API

repro:

go to climbplan.com
type "Forbidden" in the search box quickly.

expected result:

search dropdown changes several times, always with forbidden peak getting closer to the top

actual result:

sometimes, presumably due to a delay in server response, the dropdown contents will actually get less specific (eg. results from the search for "For" might show up in the final state).

note: might want to implement some basic caching as part of this solution to prevent unnecessary calls to the geonames API

This could be fixed by changing that search icon to be a real icon instead of a character

types: 'natural_feature', 'campsite'

older iPhones maybe?

http://climbplan.com/#/search/Forbidden%20Peak/48.51152/-121.05789 -> says 'forbidden peak' but the lat/lon is incorrect, so none of the correct data gets fetched. not sure what the correct behavior is. probably either:

• some kind of 404-type thing, or
• read the location and try to look up the location purely based on that to fix the lat/lon.

related work, not necessarily the same ticket: -> http://climbplan.com/#/search/aldsfjsalkd/48.51152/-121.05789 -> all of the content correctly pulls up Forbidden (from the lat/lon) and the URL even redirects to /Forbidden%20Peak/, but the text in the search bar isn't updated to say Forbidden Peak, it just says 'aldsfjsalkd'

On both Firefox and Chromium (both Linux), the weather widgets are cutoff. Both the ones on the /weather page and the ones for specific mountains.

Firefox:

Chromium:

see reactjs/react-autocomplete#166
one solution could be to use a more mature library such as http://react-autosuggest.js.org/

It was suggested as a consistently good source for trip reports

this includes having them look like nice buttons, and also having an obvious style for when they've been visited already.