PageAlias

PageAliases

A more HumaneInterface than PageRedirects is to have PageAliases. Redirects are placed on the source page, pointing to the destination page. However, aliases are listed on the destination page, pointing to the source page. Some examples:

SoftSecurity

[::SoftSecurities]
[::SoftlySecure]
[::SoftnessInSecurity]
[::HardAndSoftSecurity]

Not the same as weak security. The idea is to...

AbsentLeader

[::AbsentLeaders]

One of the problems with new wikis -- when they...


If multiple pages alias from the same location, such as if both HardSecurity and SoftSecurity alias from HardAndSoftSecurity, then provide an auto-generated disambiguation (see WikiPedia:Wikipedia:disambiguation) page - "do you want to read about SoftSecurity or HardSecurity?".

If there is in fact a page at AbsentLeaders, then render the alias at AbsentLeader as a SeeAlso link on the bottom of that page. AbsentLeaders is rendered as a link to a non-existent page. By clicking on it, a user can start adding content to AbsentLeaders. Which is one way of undoing the redirect/alias. The other way is to edit AbsentLeader and remove the PageAlias statement from the top.

If you implement PermanentAnchors in the right way, you get PageAliases "for free".

Advantages (over a PageRedirect):

CategoryUnimplementedWikiFeature?

So why did Bayle choose PageRedirects over PageAliases for plurals? Well, the Alias way on OddMuse currently leaves scribbling at the top of the page - perhaps these should be hidden, only showing up when editing or when following that alias. Also, when following an alias, you don't go to the very top of the page, but to the first line. Or maybe Bayle was just more familiar with redirects? --MartinHarper

The latter; I didn't know about PageAliases. But, now that I've seen them, I guess I like redirects better. I don't want to clutter the canonical page with the PageAliases. I don't understand many of the advantages listed here;

The others I don't care about.

I also like the current implementation of redirects better than the current implementation of aliases, but I think that aliases are a fundamentally stronger concept.

Redirect chains: LeaderGone? redirects to AbsentLeader. AbsentLeader redirects to AbsentLeaders?. AbsentLeaders? contains content. Example mode of creation 1: Newcomer creates LeaderGone? as a stub. Someone else comes along and redirects it to the canonical page, but forgot whether the canonical page is plural or not, so misdirected it. Example mode of creation 2: Content starts at LeaderGone?, then it is moved to AbsentLeader, and moved again to AbsentLeaders?. On EnglishWikipedia, most of our redirect chains are the result of RenamePages.

Alias chain: AbsentLeaders? contains content and Alias:AbsentLeader. AbsentLeader contains only Alias:LeaderGone?, LeaderGone? doesn't exist. In mode 1, you'd delete LeaderGone?, then go to AbsentLeader (and be redirected to AbsentLeaders?) and then add the alias with the content. If you're moving a page (mode 2), the aliases will accumulate with the content, not as a trail of redirects. So technically possible, yes, but it wouldn't happen in practice, IMO.

Alias loops (eg SandBoxAliasLoop?) are conceptually not loops, just two pages on very similar topics with SeeAlso links between them. The current implementation details make them look weird, but that's trivia. --MartinHarper

Define external redirect: LeaderGone SandBoxAliasLoop AbsentLeaders CategoryUnimplementedWikiFeature

EditNearLinks: AccidentalLinking RenamePage PermanentAnchor HardSecurity EnglishWikipedia HumaneInterface InvoluntaryTransclusion AbsentLeader PageRedirect MartinHarper SeeAlso

Languages:

The same page elsewhere:
MeatBall:PageAlias