[jjd-uk]

Since some of the long wiki page names are down to the auto-breadcrumbing you could set manual breadcrumbs instead.

Using the already given example instead of

Code:

http://wiki.xbmc.org/index.php?title=PVR/Backend/MythTV#Connecting_XBMC_to_MythTV

you'd have page

Code:

http://wiki.xbmc.org/index.php?title=MythTV

Then at top a manual breadcrumb of

Code:

<  [[PVR]] < [[Backend]]

I've done an example on page Intel Linux Modifications for HD Audio (wiki)

[Martijn]

PHP Code:

http://wiki.xbmc.org/index.php?title=MythTV 


should in this case go to

PHP Code:

http://wiki.xbmc.org/index.php?title=PVR/Backend/MythTV 


not to the subsection of that page

[un1versal]

why would we want double content in googles search index using tons of aliase pages/urls showing the very same information? Every company website that want's a good google ranking tries to prevent that. Can the redirects be enforced to really redirect to the target URL and not just show it's content?

Would something like this help you guys?

Code:

[[PVR/Backend/MythTV#Connecting_XBMC_to_MythTV:Connect to MythTV]]

or [wiki=PVR/Backend/MythTV#Connecting_XBMC_to_MythTV]Connect to MythTV[/wiki] (which is already possible atm)

Ofc with the requirement that those links don't add to the max length in signatures

If I had to choose between those two, memorability not withstanding I would choose the first maybe for for formatting sake do something like

Code:

[[PVR/Backend/MythTV#Connecting_XBMC_to_MythTV|Connect to MythTV]]

where the colon : is a pipe | just like wiki formatting atm, what jjd-uk done.

Either way remembering to type all of those exactly as they are wouldn't be doable so would have to go somewhere where it could be easily used as reference. within some sane limits to keep things to max two lines and readable.

The breadcrumbs idea is great to keep links cleaner and still meaningful, I currently use that method in wiki (not necessarily ontop of page) but that doesn't make it any easier to remember, its purely readability/cleanliness reason. reading links with # and underscores is not fun.

I think, KISS rule should apply here. Not just for limitation argument of forums so much as for accessibility/sanity reasons too.

thanks

uNi

[Martijn]

why would we want double content in googles search index using tons of aliase pages/urls showing the very same information? Every company website that want's a good google ranking tries to prevent that. Can the redirects be enforced to really redirect to the target URL and not just show it's content?

Would something like this help you guys?

Code:

[[PVR/Backend/MythTV#Connecting_XBMC_to_MythTV:Connect to MythTV]]

or [wiki=PVR/Backend/MythTV#Connecting_XBMC_to_MythTV]Connect to MythTV[/wiki] (which is already possible atm)

Ofc with the requirement that those links don't add to the max length in signatures

just use this and be done with it

[Ned Scott]

why would we want double content in googles search index using tons of aliase pages/urls showing the very same information? Every company website that want's a good google ranking tries to prevent that. Can the redirects be enforced to really redirect to the target URL and not just show it's content?

Google search results are smart enough to handle redirects.

However, I did notice that urls like this do get picked up "http://wiki.xbmc.org/index.php?title=IOS_FAQ&redirect=no" because of a failure on my part. The "&redirect=no" should be filtered out, and when that happens, google handles the situation just fine, just like it does for Wikipedia which has countless MORE redirects than we ever will.

da-anda, if you want you can add the functionality that uNiversal mentions with the vertical pipe: [ [Actual link|Any text here]], but this isn't going to stop the use of redirects. They're a fundamental function of the wiki.

[Ned Scott]

Since some of the long wiki page names are down to the auto-breadcrumbing you could set manual breadcrumbs instead.

Using the already given example instead of

Code:

http://wiki.xbmc.org/index.php?title=PVR/Backend/MythTV#Connecting_XBMC_to_MythTV

you'd have page

Code:

http://wiki.xbmc.org/index.php?title=MythTV

Then at top a manual breadcrumb of

Code:

<  [[PVR]] < [[Backend]]

I've done an example on page Intel Linux Modifications for HD Audio (wiki)

It's my intention to no longer rely on the auto breadcrumbs feature and do something manual as apart of a new effort to make content on the wiki easier to find. It's actually something that Martijn and I have been talking about a lot lately, and that's to use "Index pages" a lot more. Index pages and breadcrumbs, and in some cases, a page will fall under more than one set of topics, so it will have more than one set of breadcrumbs (kind of. It should look nice, though). In some cases it will still make sense, like for Apple TV 1 (wiki) and Apple TV1/FAQ (wiki), but others don't really need the actual title nesting. That's another reason why page titles shouldn't be seen as an indication of structure for mediawiki.

[da-anda]

NedScott - I know we can't turn of redirect in general and they are good to keep old links working, but we shouldn't use them just for the sake of easier linking to wiki pages. That's all I wanted to say.

I'll improve the wiki link parser - but this means I have to remove it from the regular BBcode and create a custom parser using some hooks. Might take a bit.

[Ned Scott]

NedScott - I know we can't turn of redirect in general and they are good to keep old links working, but we shouldn't use them just for the sake of easier linking to wiki pages. That's all I wanted to say.

No one has provided any valid reason for this. Unless it's some random gibberish or using unrelated words/terms, making redirects for alternative titles, abbreviations, search terms, etc is exactly how they're supposed to be used: http://en.wikipedia.org/wiki/Wikipedia:R..._redirects http://www.mediawiki.org/wiki/Help:Redirects

To all of you: