Final Fantasy Wiki
Advertisement
Final Fantasy Wiki
FFWiki forum logo.png
Forums: Index > Rin's Travel Agency > Stub Templates


Technobliterator.png

Support. Plus, I'd like for a third, optional parameter to also appear so we can specify what exactly is needed in regards to certain articles or their sections. It'd be much better than having the details shown in those hidden commentaries thing.—Kaimi (999,999 CP/5 TP) ∙ 15:17, July 7, 2015 (UTC)

Yeah, definitely. Demo of the idea; <code>{{abil-stub|Final Fantasy VI|reason goes here}}</code> leads to:
Edgar - Chainsaw2.png
This article or section is a stub about an ability in Final Fantasy VI. You can help the Final Fantasy Wiki by expanding it. (How? (reason goes here))
Any good? I think "How?" is probably the best way to do it, or just a "?" or something.--Magicite-ffvi-ios.png Technobliterator TC 15:33, July 7, 2015 (UTC)
That sounds a little like general "how do I start editing" kind of beginner's advice, but I don't really have a better suggestion either.Keltainentoukokuu (talk) 16:44, July 7, 2015 (UTC)
Oh, yeah. How about...
Edgar - Chainsaw2.png
This article or section is a stub about an ability in Final Fantasy VI. (Why? (reason goes here)) You can help the Final Fantasy Wiki by expanding it.
?--Magicite-ffvi-ios.png Technobliterator TC 16:55, July 7, 2015 (UTC)

No, that doesn't look good. We usually would just do "expanding it with: {{{reason}}}".

Third parameter is probably a bad idea. Because a stub template can have a reason without being attributed to a specific game in our scope. I mean, we could still do it but we would still need a named parameter to use when a rel is not present.

Since we're meta-templating it, we can also have the rel parameter search to see if the parameter is a codename before searching elsewhere. So if it is a codename it can resolve itself to the full game name. We do use codenames in other places anyway. JBed (talk) 18:38, July 7, 2015 (UTC)

Only problem with "expanding with: {{{reason}}} is that it could end up with really long text, but as has been seen, the mouse hover idea doesn't work too well. I like the codename idea. If we go with numbered params, there may be a way to check if the parameter doesn't contain only the codename or only the game name to determine if it's for the reason or for the release, but either way I will end up making named parameters optional anyway.
Not sure if we're merging or metatemplating, but I imagine metatemplating is the less controversial choice, and people seem to be assuming it, so metatemplating it is.--Magicite-ffvi-ios.png Technobliterator TC 18:55, July 7, 2015 (UTC)
Advertisement