Document tech stack choices #261
Description
As we are working on 40+ repos with 15+ developers (and this will only ever increase), we aim to reduce the number of tools and frameworks we use to aid maintainability, and allow us to more easily help each other. Disseminating this information organically is getting harder as the scale increases, so we should create a page that documents the tools we use, and why we chose them. This doesn't need to be a set of "rules", but information to help developers make the right choice when starting a new project. I was thinking info such as:
- We use web framework X because it's good enough for every project (has features a, b, c). Tool Y was better for project 1, but we decided to pick a single framework
- We tried tool X because of Y, but it became hard to work with after Z
- We use platform X and it works well, but we've never tried Y