search

Bloc / meteor-chat-checkpoints

Ain't no party like a bloc chat party because a bloc chat party uses meteor to do cool stuff.
0 stars 1 forks source link

first pass at introduction checkpoint #1

Closed joelip closed 9 years ago

joelip commented 9 years ago

@mikesjewett ready for your review. Took a different take on curriculum this time. Let me know if you think it goes overboard.

joelip commented 9 years ago

Realized I forgot to include something about git and github in here. Do you think I should spend time explaining how to use each?

mikesjewett commented 9 years ago

Re: Git and Github, let's ave for the end. That is, everything will be local, and if want to add Git at the end we can. I don't think it's necessary though, most likely.

mikesjewett commented 9 years ago

Hey @joelip few initial thoughts. Gifs are great, but I think there's a fine line where too many are distracting. I think this checkpoint may cross that line. I like the humor (and hope that we can continue the theme throughout) - but I also wonder if we inject too much initially. A subtle joke or two in the beginning is great to set the tone, but I think too many may turn people off.... just a gut feeling.

The other thing would be to provide a little more info (for the layman) about Meteor. That is, make it clear that it's an awesome all-in-one solution for web development. All you need to know is JS, CSS and HTML, and Meteor handles the rest. No Amazon, no Heroku, nothing... I wonder if Meteor has a nice diagram somewhere to visualize this.

mikesjewett commented 9 years ago

On Mon, Aug 25, 2014 at 1:55 PM, Joe Lipper notifications@github.com wrote:

@mikesjewett https://github.com/mikesjewett Completely fair. I'll turn down the volume a bit.

Re: Meteor explanation/handling Meteor in general - I'm sort of conflicted about this, because most of what I've internalized about Meteor is through the Discover Meteor book. I'm worried about stepping too close on their toes because a lot of the stuff that will be explained in an introductory way would best be elucidated by using similar analogies to their book (which of course, is behind a paywall). This includes some of the diagrams they use. Do you think it's worth trying to whip up similar but proprietary diagrams to explain things?

Yeah, I don't want to rip them. If it's something that is crucial to our book, let's create our own visual, if not, we can just talk around it. We can also skip this stuff in favor of the core features for now. Maybe a full-context read will offer better perspective.

Also just an FYI, hosting Meteor is often done on heroku or on Meteor's website, which has the same requirements for hosting that Heroku does. They both use a tool called demeteorizer https://github.com/onmodulus/demeteorizer to run it as a standard Node App with a Meteor Architecture.

— Reply to this email directly or view it on GitHub https://github.com/Bloc/meteor-chat-checkpoints/pull/1#issuecomment-53300694 .