Mapbox does this too, even as we've grown to 300 people. When I first joined every single employee had to put themselves on the team page, going through the whole commit, test, and push process with the help of someone who knew how. We have repos for everything, and use issues for things most people would write an email about.
Not only is our website easier for non-technical folks to update, but that means we have built-in transparency for much of the business. There are private repos for things that don't need to be aired company-wide, but public is the default.
> We have repos for everything, and use issues for things most people would write an email about.
I really like this.
When it comes to productivity in the enterprise I'm quite fascinated by the intersections of communication immediacy versus persistence. We like things that are immediate when we speak, but like things that are persistent when we're digging around years later.
A searchable per-theme repo with searchable issues and dialog sounds like a dream. I dunno if github has this built-in, but their integration API is very nice so having direct email integration and notifications or even local notification clients should be highly solvable.
Of course, you have to work with people where reading/writing isn't an issue. I've worked in several environments where it seemed nobody could read, and nobody could fathom why what they wrote wasn't 100% clear.
Not only is our website easier for non-technical folks to update, but that means we have built-in transparency for much of the business. There are private repos for things that don't need to be aired company-wide, but public is the default.