The missing HAppS documentation, and what to do about it

When I started building this demo/tutorial, the documentation for HAppS was cringeworthy. So bad that honestly I wasn't sure where to start with trying to fix it.

Instead of tackling the documentation probablem directly by doing the obvious thing and writing patches for haddock, I decided to create an easy-to-install demo project that included clear step-by-step instructions for getting from zero to final product. There is still a lot of work to be done in the documentation and usability department. That haddock still needs to be written, and more than anything, HAppS needs to be used and discussed by more people in forums, blogs, wikis, and real applications like hackage (which I think is already using HAppS or will be soon). These things tend to snowball. My hope is that this tutorial will play a part in bringing commercial-use HAppS and haskell into the real world.

I figured what the HAppS ecosystem needs most, after better documentation, is the opportunity for developers to make real money doing real work by leveraging this technology.

In this spirit, the demo project is a job board. It's full of dummy data at the moment, but feel free to post real jobs here if you have them on offer. (But cc the happs googlegroup as well!   :)   )

My hope is that that this material will tempt people to try HAppS out. Both curious developers, and investors that want a non-trivial website and are willing to gamble on a new technology if it can get the job better, and most importantly, faster. With enough users, I believe the documentation and other "batteries not included" issues with HAppS will matter less and less, as the gaps get plugged in a gradual way.

On this note, I am currently available for haskell, HAppS, and startup consulting: thomashartman1 at gmail. Write me if there is anything you need.

Now let's get started.