I'm currently writing one:
http://www.manning.com/suereth (Chapter 8)
Once done, I'll see what portions I can blog about.
The link you included is a great look at the whole hierarchy. The part that it lacks (from the scaladoc) is performance information for actual collection types vs. the performance-ish abstract guarantees on IndexedSeq/LinearSeq etc.
For general app development, as Daniel suggests, stick to a specific collection type. Staying with Vector for most things should give decent performance and avoid lots of issues with mutable collections. The other frequented collections are ArrayBuffer (for contained mutable sections) and immutable.List (for head-tail decomposition). For some reason, when using Map and Set, most of us just use the generic version (which is generally an 'ok' decision). Unfortunately, doing this with Seq defaults to immutable.List which is not as good as Vector:
scala> val x = Seq(10)
x: Seq[Int] = List(10)
Hope that helps!
- Josh