-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Greetings!
Tony Lee wrote: | My thinking was: topic or no it still needs to be presented as a page | and the search engines would prefer to see it as topicname.html, I guess | the alternative would be topicname/index.html.
Search engines will be just happy with /topicname/. Most systems represent the "index document" of a directory at both /directory/ and /directory/index.html (or /directory/default.htm for IIS).
The point here is that relative HREFs become difficult when the articles are at /topicname/article.html but the topic itself is at /topicname.html
| Yes, I had a lot trouble getting my head around linking thing through | the index articles myself. All the breadcrumbs etc. had to be rewritten | but I think the ones in the sample site are working fine.
Note: the breadcrumb element still produces topic URLs as /topicname/ (at least in Aegir Sample Site shipping with Aegir 1.0)
| The thing was, when I first started using Aegir, I had trouble figuring | out what was being generated from where. I just thought it would be | easier for new users to see what's going on that way...
Ok, understood. But maybe this would be better handled by documentation? Not a big issue anyway, though. I just had to spend a while to notice that the actual records were uppercased instead of strtoupper() calls in styles etc.
| Tony
/Bergie
- -- Henri Bergius [EMAIL PROTECTED] Consultant Partner Tel: +358-20-198 6032 Nemein Oy http://www.nemein.com/
Nemein.Net -- Project tracking solution for consulting companies http://www.nemein.com/Nemein.Net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/bFRoNkT8k497k9IRAsm4AJ4v0D3n1YzpS2YKdqWzBtSzJvcXKgCfYYsa 1tBSw++of7IIOqiUhUKcrFA= =OUkc -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
