Gavin Sinclair wrote:
In the tarball I uploaded, the base directory was 'stdlib', which is a
bit vague for someone downloading and unpacking it. 'ruby-stdlib-doc'
is probably right on the money.
I think that may depend on where it gets unpacked.
It it went into an exitisting ruby/doc dir, or doc/ruby, then stdlib
would probably be OK.
James, is it OK with you if we use 'ruby-stdlib-doc' as the base
directory of the tarball, but www.ruby-doc.org/stdlib as the URL?
That's fine; I can redirect the path.
Also, as for naming and versioning the tarball, I can use a script to
fetch and download the latest version.
ruby-stdlib-doc.tar.gz, for example, can in fact be a script that
locates the latest version of the tarball and does a redirect. Then the
documentation can have a consistent URL. You can make the link relative
to the base of the documentation so that you don't need to know any site
directory structure.
BTW, is there a way to get the stdlib HTML to include a reference to a
css file? Such as
<link rel='stylesheet' type='text/css' href='/css/stdlib.css'/>
And a link to the root of the web site?
Perhaps something like <a href='/'>Site home</a> would work; it
wouldn't hardcode any domain name.
Right now, if you are browsing the docs, there is no link to get back to
the main page of ruby-doc.org.
Thanks,
James
Gavin
|
