I agree with your logic. The only question is how much efford it would take to accomplish this.
You lost!Not as much as with other migrations, seeing as there are only a few wicks per page that need to be moved. Anyway, I do agree particularly with the reason #1.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanI like suggestion #1 as well. It would also make searching better.
I'm on the internet. My arguments are invalid.I noticed this when I made the FanficRecs.Team Fortress 2 Machinima page. "FanficRecsMachinim.FeamFortress2" would work a lot better.
edited 1st Apr '15 11:23:36 AM by ObsidianFire
Well, the pending, whenever it happens, TV Tropes 2.0 revamp will remove this as an issue since all subpages will be linked directly to their parent within the database, so there won't be any of these weird URL constructions, and large articles will be auto-paginated rather than hard split.
In the meantime, I don't inherently object to the proposed change, since it would make the pages in question fit our namespace schema a lot more efficiently.
edited 1st Apr '15 3:00:44 PM by Fighteer
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"I support this proposal. How many wicks would actually need to be moved?
I had a dog-themed avatar before it was cool.I'm a little bit uneasy - among other things, it'll really clutter up the subpage list - but it might make subpage migration a teensy bit easier when TV Tropes 2.0 that Fighteer mentioned eventually comes along.
I'm wondering if we could do the same for tropes that have sub pages for their examples. Say Cool Crown got enough examples to split by medium. Should we stick with the convention of CoolCrown.Anime And Manga, or should we instead do something like AnimeAndManga.Cool Crown?
I'm on the internet. My arguments are invalid.That would create a problem when a work has the same name as a trope.
edited 13th Apr '15 2:27:23 AM by DiamondWeapon
Good point.
I'm on the internet. My arguments are invalid.And why is Real Life used as the namespace for some trope subpages?
Trope subpages generally use the medium as a namespace. Real Life is a medium within the scope of that categorization system.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"Bumping with proposal:
- If a work's main trope list has to be split for length, split it alphabetically. Use TropesAToM.Name Of Work and TropesNToZ.Name Of Work, not NameOfWork.Tropes A To M and NameOfWork.Tropes N To Z. Normal alphabetization rules apply for tropes starting with non-letter characters.
- If a work's main trope list has to be split for other reasons, the same rule applies. For example, use AnimeOnlyTropes.Name Of Manga, not NameOfManga.Anime Only Tropes (or create an Anime/ page if possible).
Sometimes, when a work is Trope Overdosed, you just need to make sub-pages. For simplicity's sake, I will take Avatar: The Last Airbender's A-H sub-page (AvatarTheLastAirbender.Tropes A To H) for example. While it may seem useful to split it up (especially for editors who do not want to deal with lots of lag), I think there are a few issues:
In short, I think pages like AvatarTheLastAirbender.Tropes A To H should be changed to TropesAToH.Avatar The Last Airbender, mainly for easier navigation and more consistency.
Edit: I created a page for cataloguing all of these. I hope that tells you about how much spare time I have and just used up.
edited 2nd Apr '15 9:55:07 PM by N1KF