ToME Wikiamaurea: I made an article about Deathwatch a while back, and named it simply that: Deathwatch. When I now look at the spoilers page it is pointing to /Spoilers/Dungeons/Deathwatch, which has no article instead. I can move it, but should nothing be at the root level? The links get very long this way, and I'm not sure I like it. I would have prefered that the actual articles had straight-forward names so that they are easy to link to. I would like to be able to write Deathwatch to link to it, and not Spoilers/Dungeons/Deathwatch or something like that. We want to make it easy for people to make links, after all. One would need a way to specify wether one wants the spoiler version of some pages or not, though. Perhaps all the plain names should be to non-spoiler pages (or as unspoily as possible) and link to more spoily versions. Yes, this is a problem we avoid with the directory structure in the names, but I think the drawbacks are too great there.
NeilStevens: Er, that's exactly what I'm trying to do. The only catch is, the existance of special levels and certain dungeons are inherently spoily. I'd like to see some discussion of this, though.
ReenenLaurie: I agree that when I type DeathWatch I should find the dungeon. Though, I'd like to have 'order' in the system, and therefore the longer name is better. One could have a Very short page named DeathWatch which has a link to the spoiler, and prompts the user that the page is spoily. This will create every subpage + rootpage for every topic, which is clumsy, but it navigates easier.
NeilStevens: That's worth a try.
MayLith: I like the concept of finding something easily when you type, say, a dungeon name. OTOH, I don't know about you, but I like to browse through directory-style information, too.
I like ReenenLaurie's idea, if it works.
I've been working on a structure for Documentation; it's basically a tree-style form of the in-game help. I had thought to have (where appropriate) links from Documentation to Spoiler pages. If I need to wait, or change things, while this redirection idea is ironed out, please let me know. Thanks.
MayLith: One more thought: Part of the reason I initially was thinking of the Spoilers/Dungeons/Deathwatch style of naming was this: If I type "Class", will that take me to the spoilers version of character class (e.g. why certain characters have mysterious XP loss around CL20), or the equivalent of the in-game descriptions of character classes?
amaurea: I suggest that "Class" should point to the least spoily version: the normal help file. That file should then have a link to the spoily version. So one would have "Documentation/Class", "Spoilers/Class" and then "Class", which is a symlink to "Documentation/Class". That would be somewhat tidy. I think. Someone would have to go around and add this. For things that are inherently spoily the plain version could either link to the spoily version or be an as unspoily as possible version, which then links to the really spoily one.
How are we going to get people who make articles to remember to do this, though? Would it be possible to add some sort of automation, or add this to the guidelines for making pages here? When adding a documentation page one would:
- Add the entry to a parent page.
- Create the page.
- Consider if this page should have a plain symlink.
Steps 1 and 2 could use a handy macro that automizes this. Perhaps something for step 3 could be added too? When adding a page with a "directory structure"-ish name, one could get the last part, and check if an article with just that name exists. If it doesn't one could add a symlink page for it, and if it does exist one could present the user with a link to it and suggest that they consider replacing the old symlink with one to the new page if the new version is less spoily.