Re: docweb update [06.25]
| From: | Nuno Lopes | Date: | Fri, 25 Jun 2004 18:41:06 +0000 |
| Subject: | Re: docweb update [06.25] | ||
| References: | 1 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-95@lists.php.net to get a copy of this message | ||
> I would like to move on with navigation now. The following aspects need
> to be taken care of, when printing out navigation:
>
> - sitewide links (like in the footer)
> - language dependent links (eg. custom pages for the
> Italian translation team)
> - project dependent links (eg. information and contact details
> for PEARdoc interested people)
> - service dependent links (eg. revcheck links on pages where this
> is appropriate)
>
> IMHO we would need some functions returning the list of links
> appropriate for a particular page, so we can print out the relevant
> navigation that way. BUT it would be good if someone would have ideas on
> how can we distribute these in the file structure. So where should the
> information files for Hungarian translators, etc. go in CVS? Currently
> only the revcheck.php file is present and it is in the root. It is a
> service that spans subprojects and languages, so it might have the merit
> to stay in the root. But what about pages spanning though languages or
> projects only, and not both? What about pages which are specific to one
> project and one language only? Where should these go in the file system?
I think that having things in CVS isn't probably the best idea. As we will
have a login system, we could use it and have all the info in a DB.
All language/project specific should be in the DB, IMHO. With this, we can
have a simple and clear file design.
The next week is the last week that I have tests at school. After that I'm
on vacations, so I'll have much more time to help :)
Nuno
P.S.: I like this new fresh look. (althought IE doesn't display it very
well...)