Difference between revisions of "Template talk:Hidan no Aria Nav"

From Baka-Tsuki
Jump to navigation Jump to search
m
Line 5: Line 5:
 
----
 
----
   
  +
==Reasons==
 
Talking about the nav bar at the end of the chapters. Why would this be used since we already have the 'previous chapter', 'next chapter' and 'main page' buttons? [[User:Kira0802|<font color="228B22">Kira</font>]] ([[User_talk:Kira0802|<font color="C71585">Talk</font>]]) 16:39, 8 July 2011 (UCT)
 
Talking about the nav bar at the end of the chapters. Why would this be used since we already have the 'previous chapter', 'next chapter' and 'main page' buttons? [[User:Kira0802|<font color="228B22">Kira</font>]] ([[User_talk:Kira0802|<font color="C71585">Talk</font>]]) 16:39, 8 July 2011 (UCT)
   

Revision as of 00:45, 25 July 2011

Red Links vs Blue Links will show the progress of translation. Clicking on the blue links will navigate to the chapter page and clicking on the red links will create the chapter page. All red links are compatible with previous and current naming sense.

Zero2001 - Talk - 21:49, 24 July 2011 (UCT)


Reasons

Talking about the nav bar at the end of the chapters. Why would this be used since we already have the 'previous chapter', 'next chapter' and 'main page' buttons? Kira (Talk) 16:39, 8 July 2011 (UCT)

Let's say that there are two events or dialogues that are interrelated but separated by one or more chapters or even books. Which would be preferable? Going through multiple pages to check and compare the info or simply using one link. That is why full nav templates are more preferable. I mean even for projects that have two or more points of development(ie: two or more chapters being translated at the same time) can be easily navigated between rather than having to go back to the main page and then the other one. It was taught to me in Uni. Websites that can allow the surfer to navigate from one point to another in the least amount of steps (ie: page loads) are considered more user friendly and popular than those who take more steps. I mean which would you prefer? Zero2001 - Talk - 18:59, 8 July 2011 (UCT)

Just my two cents to your navigation: Looks fine so far, but I wonder if it is even necessary to make it collapsible? It's not like it's disturbing down there, and less clicks can also improve usability (IMO it's quite annoying to click that small "show" link, but that's just me). On the other hand, the user will want to just jump to the next chapter most of the time, so leaving a pair of next/previous buttons outside of the collapsible box would do as well. EusthEnoptEron 22:03, 24 July 2011 (UCT)

Read my previous post in this section for my answer. As for making it default expanaded see wikipedia help for details (uncollapsed parameter in template call). Finally, figures don't lie. Use of new template reduces page size thus reducing overall website storage space thus allowing for more meaningful data to be written. Zero2001 - Talk - 22:05, 24 July 2011 (UCT)

If you mean that post above mine: that only explains why you want a complete navigation, but I asked why you would bother making it collapsible. Also, you're right with it being nice to jump between chapters, but as I said, most of the time that's not the case. EusthEnoptEron 22:11, 24 July 2011 (UCT)

The reason for that is if I did not make it collapsible someone would have complained about the template being too big. If I did then someone might have complained about opening the template. But you see you don't need to open the template until you have read through the whole chapter. So it's the lesser of two evils. Templates are more often rejected because of their size. Thus collapsibility was implemented. Zero2001 - Talk - 22:15, 24 July 2011 (UCT)