PHP style docs website with user comments please:)
There's definitely something in that suggestion.
More generally, the docs are often consulted immediately, and in turn
might prompt the developer to look for applied, expanded or more up-
to-date resources (wiki / manuals / blogs / etc). In this sense, we
can view the api docs as something of a springboard / portal.
This might suggest a number of other ideas, such as a Rollyo search
bar for Rails material [*] in the documentation page header. Or, a
list of wiki articles which relate to the current documentation
topic, somewhere on the page.
Any other ideas?
* - eg http://rollyo.com/goldenv/ruby_rails_resources/
cheers,
David
On 30/04/2006, at 1:18 AM, Peter Michaux wrote:
On 4/26/06, Josh Susser <[EMAIL PROTECTED]> wrote:
Hey folks,
I think Ryan has a good point here:
http://blog.zenspider.com/archives/2006/04/where_is_our_ma.html
I'll follow that up by saying that besides tests, there's also a lot
of documentation work that needs done too. Is there something we can
do to improve the situation?
PHP style docs website with user comments please:)
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
