Talk:The Legend of Zelda: Ocarina of Time

I REALLY think it would be worthwhile to merge this cover page with the TOC. This is how I think it should look. If it's moved the intro and TOC red links will work. Since this is the "feature guide" it should be the most easy to navigate, and with a cover page, it simply isn't. Tell me what you think. -- Mason11987 (Talk - Contributions) 14:40, 23 May 2006 (PDT)


 * Hm. Why not just eliminate the cover part altogether? GarrettTalk 14:47, 23 May 2006 (PDT)


 * Sounds good, I'm going ahead with it then. -- Mason11987 (Talk - Contributions) 19:01, 23 May 2006 (PDT)


 * Better for navigation, but it looks really ugly. You should merge the introduction page at the top, like Super Smash Bros. Melee. --blendmaster 19:57, 23 May 2006 (PDT)


 * I could see how merging the TOC and the introduction would be better. What we did was merging the cover page with the TOC, but furthur merging might look even better and it would still be very easy to  navigate if the TOC/cover page was merged with the intro as well.  -- Mason11987 (Talk - Contributions) 19:10, 29 May 2006 (PDT)


 * Ok, how about now?--blendmaster 10:58, 15 June 2006 (PDT)

What game navigation are we using?
What happened to Template:Zelda:_Ocarina_of_Time_Nav? I saw that it was replaced with Template:Zelda:_OOT_walkthrough_nav. Personally, I think having nav links in the main body makes the links more inaccessible and the article seem more jumbled, but perhaps that's just me. I think we should have more discourse on this matter. What are the pros/cons of each method? echelon  22:14, 25 May 2006 (PDT)
 * Well, Template:Zelda:_Ocarina_of_Time_Nav was on every page of the walkthrough which was to be honest incredibly ugly looking and very jumbled. compare the one with the ZOotNav to the one with the walkthrough nav I created.  The edit (your edit) that added the other template said "new sidebar navigation" but all I see when I look at it is a massive bulleted/numbered list above what is useful information.  If it is meant to provide a well designed sidebar nav then that's great but it is not what I see and probably not what most users would see (using up to date Firefox).  So I created that walkthrough nav.  I'm not sure how your sidebar nav was supposed to work but I don't see how having an organized and yet condensed nav providing all the links a person looking for a walkthrough would need is jumbled.  I based the concept off of the FF7 guide at IGN (you might need insider to view it).  It's very easy to navigate and looks very nice. -- Mason11987 (Talk - Contributions) 19:08, 29 May 2006 (PDT)
 * Wait, are you using Monobook or something? This is what it looks like in BlueCloud (as opposed to like this in Monobook). Currently there are no includes for Monobook so I can't patch it. If you are using BlueCloud you need to hard-refresh MediaWiki:BlueCloud.css and MediaWiki:BlueCloud.js. GarrettTalk 01:46, 30 May 2006 (PDT)
 * Well that's cool, I like that, it just didn't show up anywhere for me because I am using monobook. Couldn't you edit the common.css as it is edited on wikipedia, or does it need js too? I realize blue cloud is the default, but the majority of wiki users are most familiar with monobook (since it is the default on wikipedia), and implementing something that looks horrible on monobook just because it looks good on the default here doesn't seem like a good option, you know?  Until it can be worked out to work on most skins (if not all), I think an alternative would be better, don't you?  Not like we'll delete the other zelda nav, but use something compatible with all until we get something better that's compatible with all. -- Mason11987 (Talk - Contributions) 12:08, 30 May 2006 (PDT)
 * The only skin I can change from MediaWiki: pages at the moment is BlueCloud. I guess using a more compatible template in the meantime makes sense. I'll have to bug echelon about adding support for Common and Monobook. GarrettTalk 13:53, 30 May 2006 (PDT)
 * You can change MediaWiki:Monobook.css can't you? As well as MediaWiki:Monobook.js?  -- Mason11987 (Talk - Contributions) 14:08, 30 May 2006 (PDT)
 * Oh I'm stupid. Yes when using Monobook those do work. I'll have a look. I hope Live Preview's working. GarrettTalk 15:46, 30 May 2006 (PDT)

I finally got a sight of what this was supposed to be and it is quite cool. I have no problem with removing my template now if we are going to put these in, is that the plan? -- Mason11987 (Talk - Contributions) 19:03, 2 June 2006 (PDT)


 * I've been out awhile, and I won't officially be back until the 13th, but I wanted to leave a note about an idea I wanted to pursue that I think will fix this: I really like Template:Zelda:_Ocarina_of_Time_Nav, and it looks excellent on the BlueCloud skin. However, the problem that Mason brought up is a big one; on skins other than BlueCloud, the sidenav doesn't work at all. I think I have an idea of how we can fix this: if we provide two versions of the navigation for each article, one like the sidenav and one in the fashion of Template:Zelda:_OOT_walkthrough_nav, then javascript can be used to determine which to display; on the BlueCloud skin, Sidenav gets displayed, on MonoBook, etc. the topnav is displayed. On print pages, the navigation bar can be eliminated altogether. What do you think of this solution? echelon [[Image:Ocarina.gif|...]] 13:55, 9 June 2006 (PDT)


 * I assume you are suggesting you can do the javascript to make it work. I think it'd be a great idea and would be very useful. -- Mason11987 (Talk - Contributions) 22:59, 9 June 2006 (PDT)