I'm torn on this one. I'm not going to bother retroactively doing documentation for 0.0.0; however, once I release 0.2.0, and I work on 0.4.0, I'd like people to have access to documentation on released code as well as development code. I'm not quite certain...<div>
<br></div><div>As far as that intro page, I was providing that table more as a comparison, but I think I'll be removing it entirely.</div><div><br></div><div>Michael<br><br><div class="gmail_quote">On Tue, Apr 13, 2010 at 1:18 PM, Thomas Hartman <span dir="ltr"><<a href="mailto:thomashartman1@googlemail.com">thomashartman1@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">It looks great.<br>
<br>
My only possible nit is that it seems odd to include docu for 0.0.0 as<br>
well as 0.0.2, why not just do the latest and let the past be done?<br>
<div><div></div><div class="h5"><br>
On Tue, Apr 13, 2010 at 12:54 PM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
><br>
><br>
> On Fri, Apr 9, 2010 at 8:06 AM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:<br>
>><br>
>><br>
>> On Fri, Apr 9, 2010 at 3:32 AM, Gour <<a href="mailto:gour@gour-nitai.com">gour@gour-nitai.com</a>> wrote:<br>
>>><br>
>>> On Fri, 9 Apr 2010 08:36:51 +0200<br>
>>> >>>>>> "Simon" == Simon Hengel wrote:<br>
>>><br>
>>> Simon> My feeling is that we lack mostly short, tutorial-style<br>
>>> Simon> introductions, that just get you started with a topic/library.<br>
>>><br>
>>> I agree.<br>
>>><br>
>>> Moreover, practically every 'framework' (except Happs) is more or less<br>
>>> one-man show band, i.e. it works for their authors without docs, but<br>
>>> that's not the way one can build community around it...And without<br>
>>> some 'critical' mass of users, one is reluctant to invest time/energy<br>
>>> into such products...Kind a catch-22. :-(<br>
>>><br>
>>><br>
>> I can't speak for others, but I personally don't have a problem investing<br>
>> in documentation on my one-man-show libraries. In the specific case of<br>
>> Yesod, I *know* it's going to have some major changes in the next release,<br>
>> so it's not worth it right now.<br>
>> In general, I think the problem for library writers is that- since *we*<br>
>> wrote the code- we don't know what's confusing about it. As far as we're<br>
>> concerned, our code is beautiful, elegant, simple and self-documenting<br>
>> (until we look at it again six months later). We really need an outside<br>
>> voice to tell us what's lacking.<br>
>> So instead of saying "fizzbuzz has no documentation," maybe say "I saw the<br>
>> fizzbuzz tutorial on creating foobars, but I couldn't figure out how to<br>
>> extend that for wibbles. Could you write a tutorial for that?"<br>
>><br>
> So I finally decided to start on the documentation front. Thanks to everyone<br>
> who's kicked me to get it done, and thanks in particular to Gour for<br>
> reviewing some of it for me. I'll be placing on Yesod-related documentation<br>
> on a new site:<br>
> <a href="http://docs.yesodweb.com/" target="_blank">http://docs.yesodweb.com/</a><br>
> I'm using Hakyll to generate the site, which is working very nicely. The<br>
> code is all available on github (<a href="http://github.com/snoyberg/yesoddocs" target="_blank">http://github.com/snoyberg/yesoddocs</a>), so<br>
> if anyone wants to make changes, you can either e-mail me or send a patch.<br>
> It's not *quite* as nice as a wiki for collaboration, but hopefully will be<br>
> easier to follow.<br>
> Next goal will be to put up docs on web-routes-quasi.<br>
> Michael<br>
</div></div><div><div></div><div class="h5">> _______________________________________________<br>
> web-devel mailing list<br>
> <a href="mailto:web-devel@haskell.org">web-devel@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Need somewhere to put your code? <a href="http://patch-tag.com" target="_blank">http://patch-tag.com</a><br>
Want to build a webapp? <a href="http://happstack.com" target="_blank">http://happstack.com</a><br>
</div></div></blockquote></div><br></div>