6,566
edits
m (→fgaddon aircraft: for future reference) |
|||
Line 106: | Line 106: | ||
:: yeah, basically I was thinking that we could have some kind of fgaddon-aircraft parameter, that would automatically "official" aircraft URLs properly, or even just fgaddon-url. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:14, 11 May 2016 (EDT) | :: yeah, basically I was thinking that we could have some kind of fgaddon-aircraft parameter, that would automatically "official" aircraft URLs properly, or even just fgaddon-url. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 11:14, 11 May 2016 (EDT) | ||
::: Using {{tl|fgaddon url}} would save one level of template recursion: {{tl|infobox aircraft}} -> {{tl|fgaddon url}} -> {{tl|repo link}} instead of {{tl|infobox aircraft}} -> {{tl|fgaddon aircraft url}} -> {{tl|fgaddon aircraft source}} -> {{tl|repo link}}. Extending on this idea, should this template be made hangar specific? I.e. having a pair of parameters: <code>hangar</code> and <code>aircraft</code>. This could allow for hangar specific modifications. For example a banner advertising the hangar at the top of the info box. | |||
::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:25, 11 May 2016 (EDT) |