Prototype: A Call For Documentation
We’re hard at working getting the Prototype documentation site ready for launch. However, we know there is already a lot of great documentation scattered throughout the web. Instead of us rewriting a lot of this documentation, we’d like to ask that the community lend us a helping hand.
If you’ve documented parts of Prototype, we’d be tickled pink if you’d be willing to share that with us. We’re looking for all types of documentation, everything from examples, tutorials, to general api docs.
How to send in your documentation
There are a few ways you can send in your documentation. Please include your name and Website (url included) when sending in documentation because we’ll eventually have a contributors list published on the site.
Send an email to encytemedia ( at ) gmail dot com with [PROTOTYPE DOCS] some where in the subject line, and the following applicable information:
- Attached file of your documentation (can be in txt, html, textile, markdown, etc).
- A link to documentation on the web that you’ve written.
- A link to a writeboard/writley/etc document.
Get on Board
We’re also wanting to bring a few people in to help out officially with the documentation site. If your interested in helping maintain the documentation, please let me know. It’d be mighty square of you to have an example of documentation or articles you’ve written regarding Prototype and please be sure you have time to commit to the effort. For example, if your a Carny or have your own Traveling Road Show, your probably not cut out for this gig.
So, without further ado, lets get this moving!
UPDATE: We’ve got enough volunteers for now. Thanks to everyone who volunteered to help out and to those who sent in documentation.
Sorry, comments are closed for this article.



Discussion
Most of my stuff is tutorial like. I don’t have them posted on my site, but one of my prototype tutorial is going to be in the rails cookbook. Drop me a line if you’re interested in tutorial like documentation or real life code examples.
Seems like a wiki would be a far better way to approach this problem.
@ Kroc Camen: You should try compressing it with shrinkSafe, Dojo’s Compressor.
@Arthur: The best compressor on the web is Dean Edwards Packer, it replaces relevant strings by shortcuts. Compression ratio can be up to 1/3.
See http://dean.edwards.name/packer/
Here is a quite comprehensive list of prototype rescources:
http://del.icio.us/subzero/prototype
It would be nice to see a lot of examples in the documentation. Unfortunately I am not a protoype pro so I can’t help much. The mootools.net documentation looks quite good. They are useing naturaldocs.org for documentation which seems to do a nice job.
I would like to help out, but I question your intentions as you have not disclosed how this material will be used and released.
What license will this content be released in? Will I be compensated in any way? How will I be credited for my work?
Currently this call for documentation is a black box. I don’t know what’s been submitted, what is needed, or how this content will be display. These factors are key for any real documentation project. Seriously, where’s the Wiki in all this?
I agree with Seg, I got the link here from [http://mir.aculo.us/articles/2006/11/02/prototype-documentation-call]. I was expecting to see the start of a website/wiki. Something I could see.
I do not mind contributing, but without understanding how it will be used/displayed/organized/distributed it is hard to commit time to it. Can you open up a demo of the app?
Personally I do not care about being compensated, as having a resource for prototype that I can sink my teeth into would be invaluable. Please do not be discouraged, this is a good idea!
I vote for a wiki too.
@Andreas K, packer doesn’t work, because Prototype uses whitespace shortcuts such as braceless Ifs and one line Ifs. JSMin will work on regular mode, but not on agressive (equivilent of packer). If prototype validated their code (with something like JSLint) and got rid of the hackish typing by adding a handfull of {}s and ;s then it would pack better and be more readable.