Re: [Rule-www] directory structure for the web site

[Martin Stricker]

Marco Fioretti wrote:
> 
> Hello RULE webmasters,
> 
> so far we've made it going with a flat structure (all the stuff in the
> root directory) but it's time to start thinking to a smarter
> structure. Some random thoughts, just to have something to discuss
> together (IMPORTANT: I wrote everything here to have a common starting
> point, but don't hesitate to split replies in separate threads
> with new subjects along the way)
> 
> OK, here we go:
> 
>         whatever directory structure we choose, must be easy to
>         reproduce/manage in multiple languages,

I see two possible approaches:
1) /en/dir1
       dir2
       dir3
   /de/dir1
       dir2
       dir3
   /fr/dir1
       dir2
       dir3

2) /dir1/en
         de
         fr
   /dir2/en
         de
         fr
   /dir3/en
         de
         fr
Both have their advantages and drawbacks. I prefer version 1) because it
makes it quite easy to extract just one language. OTOH version 2) makes
it easier to link between the languages...

>         applications: eventually, for each application we may have
> 
>                 1) the corresponding records in the database
>                 2) RULE-specific documentation
>                 3) " "  "  "     config/install scripts
>                 4) what else

All this information could be stored in the database, but I think that's
not a good idea.

>         and all this stuff should be linked together in a standard way
>         so that when you query the database for $SOME_APP, the
>         resulting dynamic web page contains links to:
> 
>                 $SOME_APP/$LANG/docs.html
>                 $SOME_APP/config.html(php?)
>                 $SOME_APP/install.html(php?)

Make that
  $LANG/apps/$APP_NAME/docs|config|install.html
Since I fear we won't have documentation for all languages available we
need some way to fall back to English if the desired file does not
exist, along with a short statement in the chosen language. This could
be handled rather easily if every file has a corresponding .pl|.php file
which basically grabs the .html|.txt file, if present, or falls back to
another language (in most cases that would be Englisch, but could even
depend on user preference).

Hmmm, the idea of a Perl|PHP script behind at least the config file is a
good idea, it could ask the surfer some questions and then generate the
desired post-install script.

Best regards,
Martin Stricker
-- 
Homepage: http://www.martin-stricker.de/
Webmaster-Forum: http://www.masterportal24.com/cgi-bin/YaBB.cgi
Red Hat Linux 7.2 for low memory: http://www.rule-project.org/rule/
Registered Linux user #210635: http://counter.li.org/