It'd be great if we could get this template to always position itself on the bottom of the page no matter where you place it. I'm running into this problem when trying to include it in generic templates since it builds the navbar where ever the Template call is. - Tehvamper 06:08, January 4, 2012 (UTC)
- I can't see why we need to include this template in other templates, in special generic ones, which don't refer to any game in specific. That idea implies we are creating templates with a wide array of variables: Templates are not supposed to be dynamic. It's actually the complete opposite of the matter. Templates are supposed to simplify the implementation of constant and static tables which are widely used. And I don't like the idea of making pages automatized with extremely complex templates which are prone to fail if the platform (Wikia) makes some sudden background implementations.
- Thus, these navigation templates do not need a property to assign them at the bottom of the page at all because it should be manually transcluded under a stub template, if necessary, and above the categorization area, for a better organization of our article's code. And articles shouldn't feature only sections and templates. Articles need text to describe their content, images to illustrate that content, and maybe tables to list and chart information and simplify research. Templates get into this picture when there're recurring tables with the same structure and design or features that are used in a number of articles.
- In order to simplify table creation and design, CSS classes are the way to go. Templates aren't meant to be dynamic and mutable: only their fields are meant to be variable. - Henryacores^ 17:27, January 5, 2012 (UTC)
- Perhaps you misunderstood my use of generic, I meant a Template that has a Series switch to grab a sub-template from that Template set. Using the NavBar templates inside of other Templates insures that whoever creates a new page can never not include a NavBar, and those who know what they're doing only have to set the Template switch to the correct term to add the corresponding NavBar(s). So if you choose SO1 you will get the SO1 Template Table and the bottom fixed NavBar will automatically be set for you. This is particularly useful for Item info, Shop info, etc. where you can make a single Template for all series which switches based on the Series variable to display the table defined for that series.
- If we don't do this then we have to go through every article to add the NavBars. It's bad enough we have to go through the older articles. Atleast this will fix any new creations. Even without having them used in other Templates, these NavBars should already be bottom set so no one can put them where we don't want them. Just in case someone decides to put it in the middle of an article.. Fixing this may not be possible, I'm not sure. I tried and the only thing that somewhat worked was using absolute positioning but that layers the Template over any wikia objects it might be on top of, in this case the Category bar.
- P.S. Templates are meant to be dynamic and semi-mutable, that is why they have #if and #switch to hide, move or mutate objects based on given variables. If you wanted to be insane you could put every Template on this site in a single Template using switch and #if and it would work. They are entirely mutable if you know how to use them. Wiki Functions - Tehvamper 00:13, January 6, 2012 (UTC)