You lose nothing but gain great benefit using a flat URL namespace in a radiant system. It is "having your cake and eating it too!" The benefit accrues because the namespace is not contaminated by the directory structure while at the same time radiant retains and allows the use of and for you to use the directory structure.
You design it that way for much the same reasons rails uses id in a SQL database design rather than some form of content based key. It is just fundamentally overall better design being intrinsically more flexible and resilient to change. On 6/10/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote: > > On 6/11/07, dave4c03 <[EMAIL PROTECTED]> wrote: > > > > I am not certain about this but I think that from a SEO perspective, it > > would be better if the URL namespace was flat. > > > > A flat URL namespace means the navigation structure is not part of the > > page > > name. This means a page could participate in or be dropped out of > several > > navigation/menu structures without affecting any local or external pages > > referencing them. It also means that pages could be dragged/dropped and > > reordered between directories. > > > At first I was shocked at what you're suggesting, but now that you've > explained it I see you have some valid points. But I'm still not convinced > that you should go for flat structure just to please spiders and ease the > building of some navigation menus. You should resolve your issues > otherwise: > for instance, set redirects for spiders from old URLs to the new paths > when > you move pages around. > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
