On 12/06/07 12:16 AM, jf was heard to say: > I think the original person's point was that a flat namespace allows > you to design the URL structure that fits your scenario best. So, if > you want a page to appear to be part of a folder, then you can assign > it an appropriate slug. If you want child pages to not carry the name > of a folder in the URL, then you have that option as well. Drupal is > a good example of a CMS that allows this flexibility.
The question I have here is: Why would you want to put the child in
that folder in the first place?
> Carefully choosing a URL does not mean that someone is "link
> spamming", or "only cares about ranking". Let's face it, if you're
> going to go through the trouble of spending 100's of hours building
> your killer app, or fabulous website, you might as well do all you can
> to help people find it.
Exactly and finding a site is about achieving a high ranking despite
the content. There is a difference between allowing a user to find the
information they are looking for and bringing the user to your website
based on the information they are looking for. Current search engines
are not the Yellow Pages and I don't think they want to be [1]. So
they will always focus on finding the user what she/he is looking for
and that is content driven.
Cheers,
Oliver
[1] Certainly there are exceptions to the rule and for example Google
does a fairly good job in distinguishing between those two types
of queries and produces reasonable results for each of them.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
