Template talk:EventLink

Extra information
Could this this template include an additional field for extra information, such as the wind reading for the sprints and implement details for some age group events? Right now, all I can do is this:

(+0.1 m/s)

but then the extra information gets displayed below the details link. It should rather be displayed between the event name and the details link, preferably in smaller font. Pietaster (talk) 19:54, 24 July 2016 (UTC)
 * Great idea! I've implemented as you described and updated the documentation. Looks much nicer. See the change on 2016 African Championships in Athletics. Thanks. SFB 23:27, 28 July 2016 (UTC)
 * Nice job! However, could we we also have the option to add the weight of implements and height of hurdles for junior and youth competitions? I've already seen people add those to 2016 IAAF World U20 Championships. Hope that won't be too troublesome. Cheers. Pietaster (talk) 00:17, 29 July 2016 (UTC)
 * Hmmmm... The junior/youth implement notations are going to be much less used. Do you think it's better to add a fourth, free-form parameter for that? (i.e. type in anything you want and it will appear in small and in brackets beneath the event). I suppose that might cover other things you might want to note (course lengths, notes)? SFB 02:20, 29 July 2016 (UTC)
 * Maybe to keep it simple we could just have one extra field for notes in parentheses where users could write any of those things, including the wind? I imagine it this way: Now, this is an extreme example of junior high hurdles that requires two extra parameters, and maybe you have a better idea what it should look like, but in all other cases it would be pretty straightforward I think. Pietaster (talk) 17:16, 29 July 2016 (UTC)
 * Could we put in an option to use coding (to assist layout)?   Or would this work already? Trackinfo (talk) 18:26, 29 July 2016 (UTC)
 * I'm trying to avoid as much coding as possible. I've added a plain "notes" style field in small after the event name. This is a free form entry so you could put wind straight in there, or put wind in the third one if you want them on different lines. My thinking was that out of all the uses the ones requiring this free form parameter are the real outliers, so best to make it really simple for most events, and only slightly more complex (i.e. leaving a blank 3rd parameter) for when you want to do free form. Does this make sense? SFB 22:12, 29 July 2016 (UTC)
 * I'm in agreement on making coding simpler. The common problem with these layouts is space, so maybe for each additional piece of data, an automatic line feed can be inserted, saving the need for individual editors to code. Trackinfo (talk) 02:08, 30 July 2016 (UTC)
 * The way it works now is that wind and details will always have their own line. The notes will appear on the same line as the event if there is room (as in example) or will be on its own line(s) if there isn't room. SFB 11:36, 30 July 2016 (UTC)