m (might as well reformat) |
(add) |
||
Line 37: | Line 37: | ||
{{User:Technobliterator/Talk|text= |
{{User:Technobliterator/Talk|text= |
||
I'll be clear first of all; this is a meta-template. Say if you were to use that in [[Template:FFVI]]. Once you've put it there, you'll never need to use that again, and will still just be using <code><nowiki>{{FFVI}}</nowiki></code> in the articles like before.|time=22:58, February 25, 2014 (UTC)}} |
I'll be clear first of all; this is a meta-template. Say if you were to use that in [[Template:FFVI]]. Once you've put it there, you'll never need to use that again, and will still just be using <code><nowiki>{{FFVI}}</nowiki></code> in the articles like before.|time=22:58, February 25, 2014 (UTC)}} |
||
+ | {{User:Catuse167/Templates/Bubble|time=05:32, February 28, 2014 (UTC)|text=It really isn't *that* hard to figure out how to use, and the common user never has to touch it; my main concern is how much of an effect this will have on loading times on say, [[Cloud Strife]], with its ten million navboxes. If this isn't an issue I'll gladly start implementing this metatemplate this weekend.}} |
Revision as of 05:32, 28 February 2014
Hey guys;
As you can see here, I've created meta-template - basically a template of a template - to be used in the coding of navboxes. I created this because I feel the navboxes on the wiki are somewhat inadequate and limited, as well as slightly difficult to code. The navbox code I've created is flexible and can be used as the base for any navbox, be it one of the side or one at the bottom of pages. It allows for collaspible sections basically anywhere while still allowing to change colors based on the different game (the only issue I see is transferring some code that allows an easy way for it to recognize the different games, though I think that's certainly plausible with parser functions).
Essentially; an easier to code navbox, just as (if not more) flexible than the ones currently existing, not overly reliant on css and in my opinion easier to use. One key thing I'd like to point out; for instance with Template:FFVI, if I'm on a page for Abilities (like, say, Tools), then naturally I want to navigate to other Abilities articles, like Blitz. However, first I have to open the navbox at the bottom of Tools, and then scroll down to find the abilities, which aren't instantly obvious. With this navbox, the Abilities part would appear shown by default (once the rest of the template is shown), while the rest would be hidden. It just makes more practical sense for navigation, and that's only one thing that it can do. It allows the navboxes to look prettier in general, though they don't have to.
So what does everyone think? Should this be made official?--Technobliterator 22:24, February 25, 2014 (UTC)
Just looking at, e.g.: {{User:Technobliterator/Sandbox |1 ={{{1|}}} |editlink =Navbox example |title =Title |optionsB =collapsible |blockA =Block A |groupA1 =Group A1 |contentA1 =Content A1 |contentA2 =Content A2 |groupA3 =Group A3 |contentA3 =Content A3 |headerB =Header B |blockB =Block B |groupB1 =Group B1 |contentB1 =Content B1 |groupB2 =Group B2 |contentB2 =Content B2 |groupB3 =Group B3 |contentB3 =Content B3 }} and its results is very overwhelming, at least for me. I wouldn't really like to work with this, and I'm actually okay with our current template, no matter how prehistoric they may be seen. Is there an article you think is of an exceptional quality? Vote for it here! | |||
I'll be clear first of all; this is a meta-template. Say if you were to use that in Template:FFVI. Once you've put it there, you'll never need to use that again, and will still just be using {{FFVI}} in the articles like before. | |||
Catuse says at 05:32, February 28, 2014 (UTC) "Somewhere a zealous god threads these strings between the clouds and the earth, preparing for a symphony it fears impossible to play. And so it threads on, and on, delaying the raise of the conductor's baton." | |||
It really isn't *that* hard to figure out how to use, and the common user never has to touch it; my main concern is how much of an effect this will have on loading times on say, Cloud Strife, with its ten million navboxes. If this isn't an issue I'll gladly start implementing this metatemplate this weekend. | |||