This outline provides a wide array of content, focused on practical lessons towards writing real-world applications. It presumes a basic knowledge of Haskell, as would be gained from books such as Real World Haskell and Learn You a Haskell.

Much of the content described below does not yet exist, and therefore contributions are highly welcome. Additionally, some of the lists below should be expanded. If you have thoughts on missing pieces, please bring them up on the issue tracker.

Core information

You understand the basics of Haskell syntax and some common library functions. This section should get you up to speed with many commonly used features of Haskell, to provide a foundation for understanding code in general, and to follow the rest of this outline in particular.

Data structures

Covers some of the most commonly used data structures in Haskell, and the libraries providing them.

General patterns

This section demonstrates some common Haskell coding patterns, how they work, when they're useful, and possible pitfalls.



Standard programming needs

System programming

Best practices

Streaming data

Streaming data libraries allow you to process large amounts of input with reliable resource usage, be that memory, file descriptors, or other resources. There are a number of different libraries for doing this in Haskell. Instead of a single library, each library can have its own subsection here. In addition, the following provides an overview of the different options.


Concurrency and parallelism

Simon Marlow's book Parallel and Concurrent Programming in Haskell is a highly recommended read on the subject. In addition, we have the following topics:

Web programming

Web programming is another topic with many different approaches. Like streaming data, we need an overview of the different options, and then a drilldown on individual approaches. For now:

Big library guide

The following libraries are somewhat "large" in the sense that they address many different concerns.

Alternate Preludes

Sometimes it is useful to use an alternative to the standard Prelude. Reasons include avoiding cross-version incompatibility, support for better data structures, and avoiding partial functions. Here are some commonly used preludes (in alphabetical order).

Advanced topics

Database Programming


Code and project structuring

As a project grows, there are many "patterns" that might save developer some time by just doing some restructuring work. Some tricks might save development time, while others help to re-compile less.

Application infrastructure and support

As part of "commercial haskell", I think it would be great to have both, haskell-specific and non-specific description with examples in haskell for how do you manage all the standard needs for your application infrastructure and support. Some topics would include: