I meant full fledged demo car keys-included, when they are available :)

Otherwise yes sample code. Something to give the flavor of what is to
come, and also to help the total newbie sense how much community /
momentum there is going (and maybe enchant them a bit).

Whether on the main page or somewhere quick to pop up, fine, just
wanted to emphasize that this is something I look for first.

On Mon, Jun 21, 2010 at 7:53 AM, Michael Snoyman <michael@snoyman.com> wrote:
> Do you mean sample code, or sample full-fledged apps? Either way, I don't
> think it make sense to have it on the main page, but trying to have a link
> to sample code for each library seems like a very good idea.
>
> On Mon, Jun 21, 2010 at 5:49 PM, Thomas Hartman
> <thomashartman1@googlemail.com> wrote:
>>
>> Personally the first thing I look for is a sample app(s), so I would
>> include this prominently in the thinking somehow.
>>
>> On Mon, Jun 21, 2010 at 7:15 AM, Michael Snoyman <michael@snoyman.com>
>> wrote:
>> > Inspiration for this e-mail comes from a post on reddit[1].
>> > I think it's time as a web development community we work together on the
>> > overall Haskell web brand. We need a well thought out approach to
>> > organizing
>> > the information we have on the Wiki, and some people to be responsible
>> > for
>> > keeping it up to date. At the moment, the main web programming page[2]
>> > is
>> > (in my opinion) horribly disorganized, and presents the wrong
>> > information
>> > first. We also have a number of smaller pages floating around [3][4][5]
>> > that
>> > in theory could be subsumed into a more general framework.
>> >
>> > The first step I believe is to create a single page that categorizes all
>> > of
>> > the web projects, gives a brief description, and links to more
>> > information.
>> > One thing this main page should *not* do is give information like how to
>> > create a static binary[6].
>> > So here's a start at the categories I think we should put in:
>> > Servers, eg happstack, snap
>> > Interfaces, eg Hack, WAI. Perhaps it should be included in servers?
>> > Templating: HStringTemplate, Hamlet, HSP
>> > HTML combinators: blaze, html, xhtml. Perhaps included in templating?
>> > Storage: HDBC, macid
>> > Controllers: web-routes, UrlDisp
>> > Frameworks: yesod, kibro, turbinado, happstack, snap
>> > Misc: authenticate, openid, clientsession
>> > Let's try to get a single page that contains as much of a high-level
>> > overview as possible. Just imagine if people new to Haskell could go to
>> > one
>> > page, get up-to-date information and make informed decisions about their
>> > choice in tools.
>> > Michael
>> >
>> > [1] http://www.reddit.com/r/haskell/comments/ch4me/first_impressions_serving_statically_with_snap/c0skia7
>> >
>> > [2] http://www.haskell.org/haskellwiki/Practical_web_programming_in_Haskell
>> > [3] http://www.haskell.org/haskellwiki/Web
>> >
>> > [4] http://www.haskell.org/haskellwiki/Applications_and_libraries/Web_programming
>> > [5] http://www.haskell.org/haskellwiki/Blog_articles/Web
>> > [6]
>> > _______________________________________________
>> > web-devel mailing list
>> > web-devel@haskell.org
>> > http://www.haskell.org/mailman/listinfo/web-devel
>> >
>> >
>>
>>
>>
>> --
>> Need somewhere to put your code? http://patch-tag.com
>> Want to build a webapp? http://happstack.com
>
>
> _______________________________________________
> web-devel mailing list
> web-devel@haskell.org
> http://www.haskell.org/mailman/listinfo/web-devel
>
>



--
Need somewhere to put your code? http://patch-tag.com
Want to build a webapp? http://happstack.com