You are reading a single comment by @youramericanlover and its replies.
Click here to read the full conversation.
London Fixed Gear and Single-Speed is a community of predominantly fixed gear and single-speed cyclists in and around London, UK.
This site is supported almost exclusively by donations. Please consider donating a small amount regularly.
Velocio
@youramericanlover
First of all, thank you for all your hard work up to this point and so much of the new platform is awesome. But apologies if this isn't the place for it, and if it's been discussed elsewhere, but I am struggling with the hierarchy of the new forum, especially when it comes to Rides and Races.
I appreciate that giving ongoing rides SPFG, WNKR, etc their own forums, but these are the most consistent rides on LFGSS. That they don't show up in the Rides and Races section doesn't make much sense to me. As we are now encouraged to create an event for each ride within those specific forums, the actual ride itself is buried, or too segregated from the rest of the forum (3 levels deep). Essentially what I'm concerned about is that WNKR, SPFG, and potentially future repeat rides being buried away from those who aren't currently involved. For example, it wouldn't make any sense for all of M3CK's rides to have his own forum. They are popular rides – so they sit in Rides and Races. Why SPFG and WNKR rides/events don't doesn't make any sense to me. It's nice to have a 'thread of one's own' (to bastardise Virginia Woolfe) but I think the current 'own forum' technique is having (or will have) a detrimental effect on new people joining in on rides. For people looking to go on rides, they will look under Rides and Races, yet many rides will never show up there.
Is it possible to: rduplicate (or be a redirect) to the other's forum's events (ie WNKR) so they show up in Rides and Races? Or is it possible to move the WNKR/STFG forums to within Rides and Races forum? From my point of view (taxonomy/librarian) to have the most common rides outside the Rides and Races thread is counter-intuitive.
Anyway thanks for listening.