Planning!

[rachelnicole]

This is the planning branch for Node Together going forward.

What do we still need to get done before we're ready?

• [ ] - Curriculum

  • [ ] - Web Site Basics
  • [ ] - Bot
  • [ ] - Hardware? (If we can find a partner / sponsor for materials)

• [ ] - Update website for new gh-pages branch

• [ ] - Branding

• [ ] - Interested Partners (conferences / meetups / etc)

• [ ] - Seek out mentors

[MylesBorins]

I'm interested in getting involved in this. One thing that I think is of particular interest is deployment, and what platforms we are supporting and educating people on.

Obviously the people running / sponsoring the work will have a bias, and that is totally reasonable. That being said, I think it would likely make sense to make it possible to document the way to do this using multiple platforms / services to avoid their being conflict between various member partners of the foundation.

[rachelnicole]

Curriculum

For the application I'd like to have something simple that shows how a node application handles routing & templating. I'd like 2-3 SPAs that would be useful to a variety of audiences.

I'm thinking Mad Libs, a Personal Bio Site (like about.me), both being more simple, and then one more complicated site?

[rachelnicole]

@MylesBorins do you think appengine would be something that we could use or Zeit maybe? I'd like to keep it as unbiased as possible, and with a very low barrier to entry.

Actually, what about glitch???

[rachelnicole]

If we use glitch, we won't have to worry about the users having to download an IDE as well. The only caveat with that is internet access.

[MylesBorins]

I think we should consider types of runtimes and different places to run those... likely scaling down to the simplest for the event

All in one

• glitch

Funtion

• azure functions
• lambda
• gcf

PAAS

• app engine
• zeit
• Heroku
• Does MSFT have one?

VM

• All the places

(Anyone should feel free to edit this post to add options)

[rachelnicole]

@MylesBorins this is going to be for beginners, I am wary of anything using Function / Serverless. VM's require too much configuration imo, and for the PAAS I'd be interested in what the signup process / configuration requirements to get things running would be.

[MylesBorins]

@rachelnicole so with all of that in mind, glitch might be one of the best options! Do you think they might be interested in collaborating or sponsoring? It might be hard to get sponsorships from organizations if we are going to promote other companies technology.

FWIW GCP has the cloud console that has all the tools and things necessary to deploy + work from in the browser, including an editor. It isn't nearly as streamlined as glitch though. We also have "code labs" which is a framework for making interactive education materials. We would be able to get coupons that would allow people to completely skip the onboarding of the platform

No interest in steamrolling my organizations technology into this though! Please let me know how I can help

[rachelnicole]

@MylesBorins I think the fact that glitch is pretty different from a lot of orgs offerings it might be a better option for trying to be neutral when it comes to member orgs in Node. Unless I'm just being too optimistic.