Re: A complete summary of doc.keliglia.com status
| From: | Nuno Lopes | Date: | Thu, 10 Jun 2004 10:25:34 +0000 |
| Subject: | Re: A complete summary of doc.keliglia.com status | ||
| References: | 1 2 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-20@lists.php.net to get a copy of this message | ||
> > 2 - The unofficial website:
> > ---------------------------
> > Yannick (mostly), Guillaume (admin) and I have been developping
> > a first draft since last week. The url is :
> > http://doc.keliglia.com/
>
> This address is going to be doc[s].php.net. What do you think: should we
> ask systems@ to set these domains up to point to the current server and
> then reconfigure if the new server is up? Having the server under the
> php.net umbrella would help in idetifying logged in PHP.net users (and
> would shed some more official light on the project :).
Yes!
> The official PHP.net layout has two versions now (a CSS-P one used on
> two and one column pages, and a table based one used on the manual pages
> and on the homepage). My efforts to create a CSS-P based layout for the
> manual pages have been stopped by some IE bugs discovered, which I had
> no time to find workarounds for. But if you check the download page for
> example, it is superclean HTML with CSS applied:
> http://php.net/getphp
Those IE bugs doesn't apply to latest version, surelly. I can access that
page without any problems (with IE 6, firefox and Opera).
> > * revcheck :
>
> Since I have a copy of the code, I have seen you are using mysql too. I
> would suggest you stick to sqlite instead, since livedocs will run on
> that anyway, and it will be easier for future contributors to help, if
> only a single database type should be dealt with.
Yes, I agree you should use only use one DB, either sqlite or mysql.
> > Also, I'm an optimistic guy, I believe that if someone reads a
translation
> > of the manual, and sees a warning claiming that this translation is
> > outdated.
> > This someone can help us updating the translation if we provide a
> > simple way
> > to do it. (see the phpdoc/RFC for the findings about a visual editing
> > utility)
>
> That is a bit too optimistic with current conditions, but Christian is
> working on something towards making this possible (his main problem is
> our entity usage).
Something like the bitflux editor? Whats the stats of Cristian's project?
May we test it?
> 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.
If we are gonna use the subdomains, I prefer hu.docs.php.net and
smarty.hu.docs.php.net and so on....
I think is better to have a main subdomain for each language instead of
project.
Nuno