Hmm, are you advertising that this is a series on web development? Do these students have prior development education? I fear that you're agenda is bloated.
* Vim deserves a class of its own. My personal experience is that it takes months of using Vim before it starts paying off. Your students will struggle with and be distracted by Vim.
* Git is an invaluable, industry-standard tool for collaboration. Still, is it helpful for learning to code or is it also a distraction? Pastebin/Dropbox/etc. are sufficient for collaborative efforts when your students are writing no more than 100 lines of code a day.
* Angular/Backbone/Knockout are all opinionated and assuming. jQuery is also too much "magic" for someone who just learned what a variable is a few weeks prior. These are just getting in the way.
* Yeoman/Grunt/Bower are cool. But there is something much more intuitive about just manually linking in a .js file to learn about dependencies.
* Gulp/Coggle/Balsamiq are similarly unnecessary.
In general, I think you're trying to teach opinionated tools that will frustrate, distract, and mislead your students. There will be a lot of "wait, which one's Bower, again?"
I hope I haven't been discouraging and unnecessarily critical... my doubts would certainly need to be revised if these students indeed had prior experience. My idea of a schedule for starting web dev:
* Very short overview of how a web browser and a server communicate.
* HTML: creating interactive elements for humans with textual markup.
* Node.js/Sinatra/etc. (students might benefit from using Node.js here as to not be overwhelmed with languages later): code a simple server to respond to a POST.
* CSS: modifying the visual representation of HTML elements for a better user experience.
* JS: react to HTML element events.
* Expand your Node.js server to respond with JSON instead of HTML, and rig your JS to asynchronously communicate with the server.
* Throw in a simple JSON/SQLite database. Flat file databases are great. Make the tried and true to-do app.
* Teach deployment (real-world servers). Git should probably be fit in here!
* Bonus: a whole class on how to solve problems using Google.
If your students are intermediate/advanced, ignore me completely.