Bikecollectives.org and bikebike.org 2020 redesign vision
What is wrong with our sites?
Our sites are maintained by one person
Our current infrastructure for bikebike.org is a monolith, it is very difficult for anyone who would like to help to get started. All of our sites are maintained by Godwin, but he doesn't have the time to continue supporting them on a regular basis.
Our infrastructure is outdated
Without the time to keep our sites updated, our infrastructure has put us in a position where were are vulnerable to security exploits and memory leaks which cause the site to crash.
Why now?
The sooner the better
As time passes, Godwin will have less and less time to devote to bike collectives, if we don't start now we may need to start again from scratch.
We have a team
We have a team of at least two volunteers who will dedicate time to redeveloping our sites.
We are failing our users
For the second year in a row, Bike!Bike! organizers are not primarily English speaking, our non-English base of users is set to grow. As of 2019, our administrative tools were only available in English so not all organizers in Tijuana could easily use the tools provided. Our infrastructure has become so difficult to update, it has also become very difficult to translate. We must provide better support for all of our users.
What must be retained?
Our data
Our database of users and organizations is our greatest asset.
Collaboration tools
The ThinkTank and the wiki.
Localization
We must retain and expand our Spanish and French translations.
What new features would we like to see?
A list and map of organizations on bikecollective.org
We have abundant information about collectives throughout North America and beyond, this data should be shared with everyone.
More translations
All of bikecollectives.org and bikebike.org's administrative interfaces should be available in Spanish and French.
Better mobile support
I mean it's 2019 already.
Improved accessibility
We're not doing too bad with accessibility overall but there are some major improvements that we can make.
Lessons learned from past development
Who will be organizing this?
The current team is Godwin and Arlin Schaffel but could include you too. You can get involved in whatever capacity and amount you think could help, we don't just need development support (but of course, that's super important right now). There are many ways to get in touch, if all else fails, you can use the contact link on bikebike.org.
Requirements
Current feature sets are listed in the docs for bikecollectives.org and bikebike.org, below are infrastructure requirements that must be kept in mind when deciding on our new infrastructure:
- Both sites must share common data
- User authentication
- Mass and individual email
- Online payments for registration
- Internationalization
- Easy onboarding and deployments
- Continuous deployment
Nice to have features
- Site health monitoring
- Single sign-on for both sites
- Collaboration tools for internationalization
- A/B testing or feature gating support
- Metric utilities for understanding how users are using the site
Proposals
The following are our main proposals. Please feel free to add a new proposal to the list, if your idea is similar to one of those listed, consider suggesting changes or alternatives to one of those below instead:
Concerns
List your concerns below, let's talk about them:
- Start here