Maybe that’s a good direction: give people a guide about how to accomplish things with Meteor…
I would love to see blog posts or screencasts that complement/extend the existing meteor documentation instead of jumping topics. Documentation has to be concise but screencasts or blog posts can go further by showing use cases and different implementation/examples…
As long as there’s a bit of quality control on the code samples that get added to the docs…
I think code samples would make the docs even more helpful to newcomers…
I think that’s a pretty good description of what the Meteor Cookbook has been trying to do! ![:slight_smile: :slight_smile:](https://emoji.discourse-cdn.com/twitter/slight_smile.png?v=5)
For what it’s worth, most of these questions have been asked in one form or another on the email lists, and people have been trying to write some docs and best practices (with code samples) and the like for people to refer to. It’s debatable how well written those documents are, but 900+ people seem to think there’s some progress being made.
So, going through the above comments, lets pull out all the suggestions and look at topics:
Fundamentals
- Meteor startup sequence and how to wait or guard for reactive data
that is not available yet.
- when and how is it better to use Meteor method calls and allow/deny rules in combination and,
- sync vs async (vs isomorphic code)
Design
- suitability for certain types of apps (business apps, games, social apps etc.);
- blaze vs {angular, react, polymer, famo.us, ember, jquery ui, etc}
Debugging
- Meteor and debugging on the server
- How to debug when a template fails to render a variable or object sent by a helper.
- How to use or explore a meteor stack trace (especially when it doesn’t mention my file and line number)
Data Layer
- Meteor and Redis
- how livedata works or how we get from html to htmlJS to the client and how we rendered that to the screen
- Best practices on how to determine whether a collection on the client-side is up-to-date.
Security
- Demonstrate allow() and deny() including options such as fetch and
transform
- authorization (who can do what in which situations)
- what are the recommended ways to use Roles and Permissions (or other)
packages in combination
Deployment / Environments
- separating applications, shared databases, etc
Templating
- How to use Blaze without Meteor
- Clarifying ‘this’ in the major contexts / methods
- More understanding on reactivity and templates. For instance, does a rapidly updating reactive variable trigger multiple sequential events in the template, or is there a regular refresh period? I’m trying to determine if my code needs to throttle events, or if that’s built into the reactivity.
Testing & Hardening
- How to properly test a meteor application.
Scaling
- Best practices for designing code that will survive crashes, scaling,
and hot code pushes
- demo that showed Meteor scaling linearly as servers were added
- How to load-test and analyze code performance
Mobile
- Deploying a mobile app using Meteor
- Adding it to the App Store or Google Play Store cross-platform performance
Tracker
- A more concrete/simple explanation on when to use Tracker and its
functions would be really helpful.
I think it’s fairly obvious that there’s a dozen screencasts and/or blog posts right there.
However, I think it’s important to point out that there are already quite a few blog posts on these topics. Here are some topics that are just from the Cookbook (not counting what’s been written in Discover Meteor, EventedMind, etc.) So, if anybody wants to write a blog post or do a screencast, here is some source material to help you get started. ![:books: :books:](https://emoji.discourse-cdn.com/twitter/books.png?v=5)
Design
Schema Design
Data Layer
Debugging
- Console Logging
- Debugging
- Performance Tuning
Fundamentals
- Event Cycle
Security
???
Deployment / Environments
Templating
- Event Cycle
Testing
Scaling
Mobile
Tracker
???
Also, for what it’s worth, I’ve recently started a sabbatical to work exclusively on the Cookbook and Clinical Meteor the next few months. I’m planning on adding end-to-end tests for all the examples in the cookbook, and to start extracting web components that can be shared between apps. I’ll be happy to try to make sure that the next rewrite of the Cookbook addresses some of these questions. This thread has given me quite a few ideas on how to maybe better organize the cookbook, and where some of the missing pieces might be.
If MDG has some specific formatting specs they’d like to see official docs written in, I would be happy to shift the Cookbook in that direction on my next rewrite.