What should we do about API documentation?

[Jacob Farber]

+1 for web documentation @ docs.fluidproject.org

Are we sure there is no way to get our existing data into XML for web
processing?

Jacob

On Fri, Jan 16, 2009 at 3:07 PM, Anastasia Cheetham
<a.cheetham at utoronto.ca>wrote:

>
> In response to Anastasia's suggestion, Justin wrote:
>
>  Some questions
>>
>> 1) Would that mean creating a docs.fluidproject.org site? Would this link
>> to the trunk docs or the  docs for the last release?
>>
>
> Good question. I'm not sure if we'd need a new URL, but it would make
> sense. I would expect it to link to the docs for the latest release (just as
> when I go to docs.jquery.org, I assume it's the docs for the latest
> release).
>
>  2) Would that mean that the docs would be included in the release bundle?
>>
>
>
> That's entirely an option. With our use of ant scripts, we can easily
> choose to go either way: either include them in the bundle, or not.
>
> --
> Anastasia Cheetham                   a.cheetham at utoronto.ca
> Software Designer, Fluid Project    http://fluidproject.org
> Adaptive Technology Resource Centre / University of Toronto
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>



-- 
Jacob Farber
University of Toronto - ATRC
Tel: (416) 946-3002
www.fluidproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090116/5c0d74e8/attachment.html>