php
pear
smarty
gtk
livedocs (or live to have live.docs.php.net ;))
I think we need a livedocs installation for each project. if you create a
domain live.docs.php.net (I like it!), you need to create one directory per
project?
Nope. The livedocs subsite will be about livedocs, and not about the projects. The projects will have their own livedocs setup.
So we need a projects and languages relation array as you suggested and
functions to access projects for a language and languages for a project.
that would enable us to go into a row or a column of the matrix. Then
the projects should have capabilities (revcheck, RFC, etc.) as you
outlines. Beware that there are probably going to be pages for projects
in a particular language (information for Hungarian PEAR documentation
contributors). Or at least the system should be ready to handle these.
These could be handled as capabilities (like revcheck and RFC handling),
and can be selected from the matrix on a per project and/or per language
basis.
I agree with Gabor, as thats why I've suggested to use $lang.docs.php.net.
With this, each language team would have a meeting point.
And then, have: $lang.docs.php.net/smarty; /pear; etc.....
That is why we need *both* of the access ways (either by language or by project). Your example above suggests that the language is the main selection point while Mehdi's examples suggest that the project is the main selection point. I say it should be the users opportunity to select a gate to the site (either by language or project or both).
Goba