Dave Neary wrote:
> [...]
>> - I suggest no extensions to file names, this way resources can act as
>> containers
>> for example:
>> www.gnome.org/start and www.gnome.org/start/2.14
>> instead of
>> www.gnome.org/start.html and www.gnome.org/start/2.14
>>
>
> I don't think this is really an i
> Like Jeff, I also tend to think that query string approach is the
> cleanest. It implies it's the same resource with a different parameter,
> that is "display language". Can be problematic though with some CMS
> engines and usual URL rewriting rules (that for example would
> translate /foo/bar/ba
On Fri, 2006-07-14 at 00:24 +1000, Jeff Waugh wrote:
>
>
> > > Minimal redundancy
> > > Avoid multiple URLs for a given page. Currently both http://gnome.org
> > > and http://www.gnome.org exist. I suggest to forward all gnome.org
> > > access to www.gnome.org. Are there any duplicate pages on wg
> > Minimal redundancy
> > Avoid multiple URLs for a given page. Currently both http://gnome.org
> > and http://www.gnome.org exist. I suggest to forward all gnome.org
> > access to www.gnome.org. Are there any duplicate pages on wgo now?
>
> These are not duplicate pages, they are aliases. gnom
Hi,
Gergely Nagy wrote:
> Minimal redundancy
> Avoid multiple URLs for a given page. Currently both http://gnome.org
> and http://www.gnome.org exist. I suggest to forward all gnome.org
> access to www.gnome.org. Are there any duplicate pages on wgo now?
These are not duplicate pages, they are a
First of all, great work guys,
Quim's list of goals, Sigurd's Policy page and Christian's Localization
document are Excellent! (all in live.gnome.org)
I would like to start discussion on our URL policies.
Requirements
- persistent
- support site partitioning
- minimal redundancy
- friendly urls
-
