Re: A complete summary of doc.keliglia.com status

> >> hu.docs.php.net, pear.docs.php.net, hu.pear.docs.php.net (or > >> pear.hu.docs.php.net) should pick up the pages and navigation elements > >> relevant for that selection from the matrix. > > > > Since we have livedocs as project on the website, the first idea > > actually used on keliglia.com will need to be changed. I'm now thinking > > about having : PROJECT.docs.keliglia.com/part/LANG*, LANG being optional > > (Nuno, happy ? ;)). As projects, we'll have : presque hereux :) > > 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? > I don't think so that putting the project into the domain and the > language into the path is a good solution. As I have outlined above, I > would like to get everything related to Hungarian efforts, or PEAR > efforts or just the Hungarian PEAR efforts. IMHO it would be diserable > that one picks a row, a column or a cell from the matrix (or the whole > matrix, which is the homepage). > > We aim at helping those who would like to work on PEAR stuff, but would > help translations too, and those who would like to work on French stuff > on all projects (but not with other languages). So there are possible > valid use cases for picking a row or a column from the matrix. > > 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..... Nuno