Template talk:During
From Guild Wars 2 Wiki
Jump to navigationJump to search
I think it looks better un-italicized. Since we already use bold for conditions in dialogue sections, I think using a regular font type would look/feel better. —Ventriloquist 13:32, 24 December 2018 (UTC)
- The pages have been using italics though, I just copy pasted what was there and threw in a little code to add the festivals. So just to make sure you'd prefer this:
- Queensdale
- Clayent Falls (During related events only)
- Queensdale
- over this:
- Queensdale
- Clayent Falls (During related events only)
- Queensdale
- What if it were bold though? That doesn't look too bad imo.
- Queensdale
- Clayent Falls (During related events only)
- Queensdale
- Either or, I'm not picky. - Doodleplex 19:30, 24 December 2018 (UTC)
- Oh yeah, I know they've been using the italicized format, but figured I'd add my feedback since I assume you'll be botting the existing ones with this template. Hmm, I don't mind bold either, and it would make sense since we use bold for dialogue already — I think it'd work. —Ventriloquist 19:32, 24 December 2018 (UTC)
- Yeah, it'd be a bot task. And okay bold it is. - Doodleplex 19:44, 24 December 2018 (UTC)
- I prefer not in bold. Seems weird to me to use small text to make it not stand out but also bold which stands out. And in bold it stands out more than the location. - BuffsEverywhere (talk) 22:27, 24 December 2018 (UTC)
- I'd like to echo this sentiment - not bold would look better imo. -Chieftain Alex
23:20, 20 January 2019 (UTC)
- We could try unbold, to see how it looks over the course of a few days. —Ventriloquist 22:04, 21 January 2019 (UTC)
- I'd like to echo this sentiment - not bold would look better imo. -Chieftain Alex
- I prefer not in bold. Seems weird to me to use small text to make it not stand out but also bold which stands out. And in bold it stands out more than the location. - BuffsEverywhere (talk) 22:27, 24 December 2018 (UTC)
- Yeah, it'd be a bot task. And okay bold it is. - Doodleplex 19:44, 24 December 2018 (UTC)
- Oh yeah, I know they've been using the italicized format, but figured I'd add my feedback since I assume you'll be botting the existing ones with this template. Hmm, I don't mind bold either, and it would make sense since we use bold for dialogue already — I think it'd work. —Ventriloquist 19:32, 24 December 2018 (UTC)
Template update[edit]
Would it make more sense for the "festival" param to be named "event" instead? I'm not familiar with the correct convention of renaming params, whether it would require editing all existing usages, or if Templates support polymorphism and "event" becomes an alt for the same param, so I don't know how much work this would involve, but I'm happy to help out if necessary. —Caeldom (talk) 10:35, 27 July 2024 (UTC)
- This template needs to be made more intuitive and adaptive to more contexts because I am just seeing more and more manual notes that could easily use this template. I usually don't want to use this template because it's not adaptable at all, so I'm changing it to match the consistency of the style and format of appended notes I have seen across articles. The syntax will be more intuitive to use and allows for better customisation.
- The format that I have seen commonly used right now is:
- See Template:Drops table row for example.
- --Caeldom (talk) 01:58, 16 February 2025 (UTC)
- IMO, template likes this should be simple. I don't see the need of adding
|text =
param for this template. The current used are: - For After__ and Before__, these two can be split the template if needs. For completely custom text, I'm not sure if the template is actually needed, for me just manually add is easier. Using template for a text that doesn't follow the template is a bit non-sense.
- For syntax, in this case, I like the tone of
During __ only
more thanOnly during __
. And for renaming params, Guild Wars 2 Wiki:Botsnot a human jobs.not a one-man job, maybe bring this to discussion and make a Guild Wars 2 Wiki:Projects. edited after stroke through --𝙏ᴇʀʏ 15:54, 16 February 2025 (UTC)
- IMO, template likes this should be simple. I don't see the need of adding