On 6/1/08, Gabriele Romanato <[EMAIL PROTECTED]> wrote: > Yesterday I've finished to write my first CSS article in English. > This is the first of a series of articles that I'm going to _deliver_ in the > next fall or something. > I've a problem with my site structure. > As some of you know, a page named /articoli.html already exists. > My site is static, so I've the following options: > > 1. add a link to /articoli.html >> articles.html > 2. create a /en section > 3. create a third-level domain > 4. rebuild my site navigation > > so: > > 1. most probable. do you think English/American/Foreign people will have > some problems with finding it on Google? > 2. this doesn't fit to the rest... > 3. expensive! > 4. baaz! I'm too lazy *^.^*
I would opt for an /en section - it gives you the most flexiblity, especially if you have the same article in multiple languages. It is reasonable that the default language of the site doesn't have /it, and if you come up with a language-based navigation management as the site grows, you can always create a redirect from /it to / if that assists automated generation of links. -- Richard Grevers, New Plymouth, New Zealand Dramatic Design www.dramatic.co.nz ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
