What's possible

Last time: how I'd lead — open testing, a transparent web committee, and a few ideas beyond the website. Read it here.

Last time: how I'd lead — open testing, a transparent web committee, and a few ideas beyond the website. Read it here.
A good rides site is the start, not the finish. Because tools.nycc.org is built by real engineers from the start, much is possible that the club has never had. Some of it is ready now; the rest is a short build away.
First, the one you can use today.
In beta An Android app. The same rides, filters, and ride creation as the website, in your pocket. It's in beta now, available to any member on request.

The rides feed in the Android app
What's possible, none of it built yet:

Planned Discord linked to membership. Your club membership recognized in Discord automatically, with no email requests or delays
Planned Direct access to the club's Ride with GPS account. The NYCC route library shows in your RWGPS account w/o needing a bookmark
Planned Auto-provisioned Discord channels for big rides. A large ride gets its own channel, created when it's posted and archived when it's done
Planned Ride publication where members already are. Email, Discord, and WhatsApp — opt-in, per member and channel
Planned Delegated ride approvals. Ride coordinators can hand off approvals during vacations or peak season, so nothing stalls waiting on one person
Planned Train coordination with the transit authorities. Request group train space right from the app for rides that take the rails
Planned A clear view of the member journey. For the club, we can see when members join, drop off, or sign up and never ride — and then decide to do something about it

If one of these matters to you — or you'd like to try the Android app — tell me at scottfornycc.site/help.
Scott