lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan Kurz <>
Subject Re: [lucy-dev] URL design for website API docs
Date Fri, 15 Apr 2011 20:22:20 GMT
On Wed, Apr 13, 2011 at 8:20 PM, Marvin Humphrey <> wrote:
>               <-- homepage
>          <-- TOC for latest Perl bindings
>          <-- TOC for latest Ruby bindings
>    ...

OK.  See below.

> At some future date, we should begin archiving the docs for each release:
>    ...

Versioning approach sounds solid to me.

> We should hold off on archiving for now, though, so that the primary location
> has a chance to establish itself as authoritative.
> To find the documentation for Indexer's Perl bindings in the latest
> API-unstable Lucy release, you would look here:
> Here's where you'd find the analogous page for archived release Lucy X.Y.Z:

Was it intentional that these are "/lucy/docs" and the paths above are "/docs"?

While it's redundant to have 'lucy' repeated in the domain and path,
it might make life easier.   For example, when one migrates from to, all absolute path links will
still work.  And if one ever migrates again, it should just be a drop
in. One could mostly solve this by sticking with directory relative
URL's, but with the multiple versions one will probably want some

So I'm fine with either, but would lean to leaving 'lucy' in the path.
 It also keeps things clear if/when subprojects are added.  But it
doesn't seem worth too much worry.

Rest seems good.


View raw message