So, I'm going to humbly suggest that there are two projects in the Meteor ecosystem that have already been working with rough analogs of the proposed charter: Meteor Cookbook and the Meteorpedia.
I can't speak for Meteorpedia, but as far as Meteor Cookbook goes, I (we) had roughly the same Vision and Values as what you're proposing. Meteor Cookbook is the result of 2 years of working with the Meteor NY community as a NY Meteor Meetup organizer. It's got 1400 stars on GitHub, and 31 contributors.
And to be perfectly frank; even if I've been the primary curator of the project, the vast bulk of all the recipes, snippets, and code samples are from other people. It truly is a community effort. I've merely been acting as a secretary and taking notes.
As far as how it's organized; some people may take exception to some of it's assumptions; particularly around MVC, SQL, and a few other topics. That's fine. I'm not claiming it's the only approach. Merely that it's been a popular and pragmatically useful one. And it sort of represents a distillation and record of 2yrs of community contributions from the NY community and Meteor Talk/Core mailing lists.
So, yeah. This isn't the first time the community has approached this kind of resource. And I guess that makes me want to ask questions like: How can we leverage past efforts? What can we learn from the attempts at using GitHub and dogfooding a Wiki to create this resource? How does Angular and React integration effect previous Blaze-oriented attempts at writing similar guides and cookbooks? etc.
From my experience working on a similar project for 2 years, the biggest challenges were:
- APIs were moving targets, and when they changed, all the articles would get out of date.
- Lack of officially-sanctioned flow-charts and architecture diagrams.
- Difficulty in finding the right 'voice' for articles. Should a topic be a FAQ? A checklist? A tutorial? A demo app? I suspect the 'Guide' will run into the same problem.
- People without animation / rendering / video driver / graphic design experience second guessing the MVC approach. More generally, people second guessing articles who hadn't read their Knuth.
Anyhow, I'd guess that Meteor Cookbook can take care of about 20% of the proposed outline, with an article, code recipe, or applet. Meteorpedia could probably take care of another 20%. I don't envy you and the technical writer who will need to write this so it works with Blaze, Angular, and React.