For the curious, the source code to the wiki (as well as other tools we've written) can be browsed at http://atitd.centauri.org/viewcvs/trunk/
Would it be possible to have Beta information pages in the Wiki have a different background color temporarily? With a distinctive color, people will know whether the information they're looking at pertains to ATITD and ATITD2 information. Either that or some other visual cue that the information belongs to one telling or the other. Ahephron
However, I think the whole Index vs. Strategy Guides vs. Technologies organizational system really needs to be sorted out soon... With the number of pages rapidly increasing, it's getting harder and harder to get to where you need. I mostly resort to the search feature now, but the text box is located in an inconvenient place (at the bottom of the page), and the search itself isn't always perfect either. --Brant
It's definitely time for a reworking of the organizational system. Some parts of the current system are good:
What do we need?
I'd love to have a Manual? page. This page would act as a table of contents for a game manual, as you might expect to find packaged with a boxed game. The manual would include pages introducing people to the game, explaining how to use the interface, and progressing on through advanced topics such as glassmaking and gemcutting.
Future directions I'd like to take:
Suggestions, as always, are more than welcome.
It is now possible to generate index listings of all pages, regardless of whether they have a $INDEX directive or not. "$INCLUDE CONTENTS" will list all top-level pages. "$INCLUDE CONTENTS Users" will list all subpages under the "Users" page.
A page may opt out of this listing by including the "$NOINDEX" directive.
On a dense map with many entries near a single location, it can get pretty hard to select items. What's the best way to fix this?
Suggestion: [Megrez] This sounds like the perfect use of an image map. In any area where the density of targets becomes obfuscating, overlay a solid block, selecting on that block loads a subimage of that area. Creation of the subimages may be a problem, but I believe it can be scripted with pbmplus if you want dynamic maps.
I was wondering if you would allow us to make a french translation of the most useful pages on the wiki. I don't know if it would be possible to have some kind of seperate section for french pages.
I would understand if you didn't want to use some bandwith for pages that are of no use to you. If I knew more about setting up a wiki I would simply find another server to set one up, but it seemed easier to ask first if it would be possible to have everything in one place.
Oh, and bandwidth isn't a problem; the wiki is more or less entirely text, and isn't a major consumer of our available bandwidth.
Something else, you could add this to the top/bottom of a page. http://translate.google.com/translate?u=URL_HERE&langpair=en%7Cfr&hl=en&ie=UTF-8&oe=UTF-8&safe=off&prev=%2Flanguage_tools and replace URL HERE with the current URL of page. You could then do a German translation, even Spanish, etc.
Integrate with DarthBobo's java super map applet at http://www.purplefrog.com/~thoth/atitd/ . Make all atlas pages have both the static image, and the "pop up map" button with all the landmarks.
When you use the admin tools to rename a page, all links to that page are updated automatically. However, the $INDEX/$ATLAS commands are not, resulting in an empty link [like this]? showing up in the index/atlas.
The $MAP directive doesn't work correctly when using the justification parameters in $TABLE. See Gazebo Locations for an example. Notice how all the parameters from the table don't appear in the map unless you remove the justification parameters from the $TABLE directive. I noticed some more detail to this, the problem is that the data from the tables last column does not appear in the summary when you mouse over the location on the map.
Changing format line endings is important. This has the effect of displaying equivalent looking lines on a diff, and causing the file to be updated even though no functional update has taken place. This can be corrected by running dos2unix/unix2dos on each of the page files and running all future pages through a substitution that maps to a common line ending (either Mac, Unix, or DOS). (I forget how I came to this conclusion of the problem, verify that it exists :P -- RedStorm)
Should there be a way to allow anonymous edits of certain Users subpages? I don't particularly mind if somebody decides to anonymously edit my user page to leave a comment or something. In fact, I think it's important that the wiki remains as open as possible, even when it comes to personal pages - that's the whole idea of a wiki in the first place. --Brant
Either a comment or permission system should be setup to address this. I have the idea that users/<name> is <name>'s personal wiki in namespace <name>, not that it should be restricted. Personally, I want it reverted back until permissions are implemented. Is there anyone relying on this feature, or has had problems with their user page being edited that this is addressing? --Redstorm
Is the sky really falling because you need to have a username to edit a user page? Does that really restrict usage of the wiki in general? The idea of a wiki in general was conceived of outside of a game context, but that's besides the point. Make a page of "Messages for Brant" and link it off your user page and let the anonymous edits fly. But it's not like you can't edit someone's user page. You just need a user name to do it. That's hardly restriction. -- silver
It's not that big of a deal, but I will pose to you the same question that you posed to me: Does it really matter if everyone can edit pages under /Users? I have to admit that I had read it as only the User that the page is under can edit it. From an organizational standpoint "Messages for Brant" makes my skin crawl. Furthermore, this affects me two ways: 1) I've got a page under /Users that I want everyone to edit (PyroSim), and 2) my username was created for me. But I'll drop the subject now. --Redstorm