Docs: add some usecases for open taco

[MichaelDimmitt]

This issue is for only usecases:

not technical tasks.

In an effort to understand how the app worked

Myself being a non rock climber

I had a quick meeting with a rock climber @clintonlunn to see what features currently existed And have a quick brainstorm about what may be some cool features.

Please add to this ticket if there are better ideas!

---

key: ❤️ - heart represents @clintonlunn's , favorite search filters for using this app.

---

Two potential action items:

1) add link to roadmap on Readme. 2) add some of the current usecases to roadmap looking backward (or add a usecase section to readme)

potential user

1) climber a. mobile phone entrypoint. b. pre-climb research, computer/mobile entrypoint. note: it is easier to research climbs on computer. - is this a problem we are trying to solve? other helpful apps: mountain-project, the crag, strava, guidebooks

current app usecases:

1) trying to find where climbs are at specific difficulty levels. 2) trying to find climbs based on type of climb. 3) all current filters: ❤️ distance radius, ❤️ distance radius exclude , ❤️ filter by name , ❤️ climbtype filter , difficulty filter , 4) climb description. #177 5) heatmap for climbs #118

potential ideas: (feel free to disregard, if out of scope and wont do)

1) future climb filters climb duration - length or time, multi-pitch climbing, quality filter(classics),

2) bookmark and save climbs? #253

3) personal record system? using a stopwatch in the browser, or integrating with strava.

4) how many times have I climbed this climb? attempts vs completions, did I complete or fail? how many times have people app wide climbed this climb?

5) how can I determine how many mistakes I made. (you could hand it off to a friend who critiques you as you go up the climb) this could be private info so not shared with everyone.

6) RPE - physical exercion per climb. (hardness scale) track and have a graph of how difficult was this effort?

7) get social: pictures , reviews of the climb, approach notes, comments of the climb, comments on this climb.

8) Share this climb with others. send to a specific person or broadcast to people of that climb type withing a certain distance.

9) keep track of what taco shops are nearby.

[MichaelDimmitt]

@clintonlunn , mentioned: regarding potential ideas: # 5, a log would be better here

how many mistakes I made is not a metric people often measure for climbing.

[vnugent]

We definitely need more feedback from our users. Thanks for putting this together.

You're right that we tend to focus on what's next in the roadmap, and forget to highlight features we've accomplished. I'm making a note of this and will write a blog post showing some of the current use cases.

Tracking climbs and maintaining a ticklist is very important to a lot of climbers. Also being able to share photos/comments is super valuable.

In order to do any of the items on your wishlist, we need to enable login. The app in its the previous incarnation, a Gatsby/markdown static generation site, had integration with Auth0, but we had to remove it when migrating to Nextjs. Maybe, this should be our focus for the next milestone?

[vnugent]

A new blog article: https://openbeta.substack.com/p/introducing-crag-finder

@MichaelDimmitt can you suggest a specific section on our official docs site to add more use case info?

[MichaelDimmitt]

Personally, I would rename roadmap to technical roadmap

then add a new section called: feature roadmap

technical roadmap feature roadmap

not sure if there is another term for all of the past milestones we accomplished in the past

should that be part of the roadmap? or a seperate section called features list.

I need to think on it a little more.

[MichaelDimmitt]

I think also adding from the readme to the roadmap doc will be helpful. as developers but often non technical people will find the readme on github first.