Back to Blog

Introducing the Meteor Guide

January 07, 2016 By Tom Coleman
Vote on Hacker News

Meteor has always been one of the easiest full-stack frameworks to get started with thanks to the quick introductory tutorial. There are also lots of specific tips for advanced developers on various blogs and Stack Overflow. What’s been missing, though, is a complete resource for everything you need to build a production JavaScript app in Meteor - from frontend UI interactions to backend server code to deployment, analytics, and monitoring.

That’s where the Meteor Guide comes in. Check it out now!


For the last several months, Sashko and I, assisted by Evan, Zoltan, and several members of the Meteor community have been hard at work writing the first version of the Meteor Guide. Our goal is to provide official guidance from the developers behind the framework, and also distill the best practices for writing Meteor apps that have emerged through years of ideas and discussions in the community. We called for community discussion and contributions, got a lot of feedback from prominent community members for the outlines and then wrote drafts of the articles for the first version of the guide.

We’re not done yet—this is just the beginning! We are going to be constantly improving and updating the Guide with new ideas and Meteor features. New articles and updates will launch in the coming months alongside Meteor 1.3 and contain plenty of guidance about the new ES2015 module system and testing improvements.

We hope this will be a helpful resource for the whole Meteor community and for anyone trying to build a modern full-stack JavaScript application. We hope this can provide the extra direction that the community has been asking for in how to build an application in Meteor. Having a standard set of guidelines will make your code simpler to write, your features faster to complete, and your applications easier to maintain.

We’d really love to hear your input. Each guide article has a link at the bottom to post pull requests with changes or fix typos, and we encourage you to post issues on GitHub if you feel we’ve missed any important content.

What are you waiting for? Dive in and let us know what you think in the comments!

Vote on Hacker News