While I really like the course from what I see, I also think that Haskell is not a good subject for a "crash course". In the Learn Haskell From First Principles book[1] it is given why a "crash course" Haskell is not working for many, and I second it.
Non the less, the more options the better. And of course I do not know how you do your course. Naturally I wish you best of luck: that your students may succeed in mastering the subject :)
I agree, and that's why we didn't go with "crash course." There's a certain amount of stuff you simply have to work through and know in order to use Haskell, for sure. This course isn't mutually exclusive to something like Haskell Book. The intention is to provide a comprehensive overview so you can quickly get up to speed, have a sense for what real world programming in Haskell looks like and gain a familiarity with the basic concepts that are used over and over. If, after that, you're motivated to go through a 1000 page book, that will serve you well.
> In the Learn Haskell From First Principles book[1] it is given why a "crash course" Haskell is not working for many, and I second it.
What's their reasoning? I didn't find this on the page you linked.
I don't think that it would be impossible to do a "crash course" in Haskell well, but it's certainly harder than doing the same in e.g. Python, simply because the language will flout so many expectations/assumptions that developers would be able to make in other languages.
Non the less, the more options the better. And of course I do not know how you do your course. Naturally I wish you best of luck: that your students may succeed in mastering the subject :)
[1] http://haskellbook.com