Template talk:post
From Homestar Runner Wiki
- Note: More template discussion can be found at: Talk:@StrongBadActual.
Contents |
[edit] Transcript Column
This looks great, but I think we ought to have separate columns for the tweet text and the video/photo transcript. Or maybe there's an even better way of separating them. (Other than that, it should be implemented as soon as possible.) Happy birthday Lira 00:50, 2 October 2017 (UTC)
- Sounds like an okay idea. But if we do that, should we have a seperate section for Fun Facts/Notes as well?
Gfdgsgxgzgdrc 04:18, 2 October 2017 (UTC)
- Good question. Maybe we should, but too many columns and it might get a little crowded. Possibly we could have the tweet text, transcript, and fun facts stacked vertically, with horizontal bars in between? Which I know is fairly similar to the current design but it might look a tiny bit better. Maybe we could test these in a sandbox and see what looks best. Happy birthday Lira 11:56, 2 October 2017 (UTC)
- About the horizontal bars thing... it sounds good in theory, but the multiple images feature uses the same thing, and it might be hard to make both work in the same template. Plus, I think it would look better to have them all look like they're in the same box, so there's no confusion. Anyway, these are a few ideas I thought of. My favorites are option 4, and to a lesser extent, 5. Gfdgsgxgzgdrc 03:20, 3 October 2017 (UTC)
- I'm kinda liking 5, actually. I mean, the truth is that any of these formats are going to look a bit unfortunately crowded, and I can't really think of a way to fix that without removing actual information, but it still looks pretty nice. Maybe we could do something like slightly darken the "Tweet Text" box so that it stands out more. Happy birthday Lira 01:07, 5 October 2017 (UTC)
- How's this? The tweet text is more obvious, it's a bit smaller, and seperated using lines instead of boxes. I rather like it. (Also, where should the Info box be? It provides important context, so it should probably be higher up. Maybe below the tweet text or the transcript.) Gfdgsgxgzgdrc 02:27, 5 October 2017 (UTC)
- Now that I look at it, increasing the font size is the perfect way to accentuate the tweet text. I approve. If the Info box had to be moved from its current spot, I would definitely say under the tweet text, although really I'm fine with it in either place. Happy birthday Lira 02:53, 5 October 2017 (UTC)
- Okay, cool. I guess I'll change it then. Another question first— what do we do for replies now? Before, the background would turn gray, but now the background is a variety of whites and grays. I think the "Tweet Text" box should say "Reply Text" for replies. Gfdgsgxgzgdrc 03:58, 5 October 2017 (UTC)
- Okay, cool. I guess I'll change it then. Another question first— what do we do for replies now? Before, the background would turn gray, but now the background is a variety of whites and grays. I think the "Tweet Text" box should say "Reply Text" for replies.
- Now that I look at it, increasing the font size is the perfect way to accentuate the tweet text. I approve. If the Info box had to be moved from its current spot, I would definitely say under the tweet text, although really I'm fine with it in either place. Happy birthday Lira 02:53, 5 October 2017 (UTC)
- How's this? The tweet text is more obvious, it's a bit smaller, and seperated using lines instead of boxes. I rather like it. (Also, where should the Info box be? It provides important context, so it should probably be higher up. Maybe below the tweet text or the transcript.)
- I'm kinda liking 5, actually. I mean, the truth is that any of these formats are going to look a bit unfortunately crowded, and I can't really think of a way to fix that without removing actual information, but it still looks pretty nice. Maybe we could do something like slightly darken the "Tweet Text" box so that it stands out more. Happy birthday Lira 01:07, 5 October 2017 (UTC)
- About the horizontal bars thing... it sounds good in theory, but the multiple images feature uses the same thing, and it might be hard to make both work in the same template. Plus, I think it would look better to have them all look like they're in the same box, so there's no confusion. Anyway, these are a few ideas I thought of. My favorites are option 4, and to a lesser extent, 5.
- Good question. Maybe we should, but too many columns and it might get a little crowded. Possibly we could have the tweet text, transcript, and fun facts stacked vertically, with horizontal bars in between? Which I know is fairly similar to the current design but it might look a tiny bit better. Maybe we could test these in a sandbox and see what looks best. Happy birthday Lira 11:56, 2 October 2017 (UTC)
- It looked fine in the example, without all the variables, parser functions, and other template stuff, but it actually looks kinda messy in action. The spacing isn't very great, and it kinda needs improvement. Should we go back to your original idea in the title of this discussion? Maybe I'll try some other things as well. Gfdgsgxgzgdrc 05:29, 26 October 2017 (UTC)
[edit] Pinned Tweets
Instead of writing "This Tweet was pinned" in the fun facts of every tweet that was pinned, might it make more sense to add a pinned flag to this template that will display that message if set to a non-blank value? Happy birthday Lira 09:35, 7 December 2020 (UTC)
- This seems like a good idea given the number of Tweets that have been pinned. DEI
DAT
VM
┌datvm center\super contra┘ 18:37, 7 December 2020 (UTC)
- Or even better: instead of a fun fact, what if the flag added a "Pinned Tweet" label and icon above the Tweet, like on the wedsite? (Or would that not be clear enough?) Gfdgsgxgzgdrc 22:16, 7 December 2020 (UTC)
- Why not both? --Stux 23:01, 7 December 2020 (UTC)
- Something like what Gfd suggested sounds great, with or without an icon. I don't see a reason to have both. Happy birthday Lira 23:28, 7 December 2020 (UTC)
- Not everybody uses twitter or might know what the pinned icon means. So if I had to choose one I'd prefer a text description, maybe with a link explaining what a pinned tweet is (ideally from wikipedia). --Stux 08:30, 9 December 2020 (UTC)
- As a compromise, I added a label and icon above the Tweet text, with the label being the same as what's currently written in the Fun Facts. Now it looks cooler than before, and is equally informative! I would've added a link too, but I couldn't find a good one. Gfdgsgxgzgdrc 21:15, 16 December 2020 (UTC)
- As a compromise, I added a label and icon above the Tweet text, with the label being the same as what's currently written in the Fun Facts. Now it looks cooler than before, and is equally informative! I would've added a link too, but I couldn't find a good one.
- Not everybody uses twitter or might know what the pinned icon means. So if I had to choose one I'd prefer a text description, maybe with a link explaining what a pinned tweet is (ideally from wikipedia). --Stux 08:30, 9 December 2020 (UTC)
- Something like what Gfd suggested sounds great, with or without an icon. I don't see a reason to have both. Happy birthday Lira 23:28, 7 December 2020 (UTC)
- Why not both? --Stux 23:01, 7 December 2020 (UTC)
- Or even better: instead of a fun fact, what if the flag added a "Pinned Tweet" label and icon above the Tweet, like on the wedsite? (Or would that not be clear enough?)
[edit] The Lost Links of Least-Leftmost Column
It seems that somewhere in the recent batch of edits, the link to the original social media post in the date column was lost (this being the first revision to lack the link). I don't have much if any experience in advanced template coding so I'm not entirely sure how to restore it. DEI
DAT
VM┌datvm center\super contra┘ 21:33, 20 January 2021 (UTC)
- Holy smokes! Good catch! I hadn't even noticed that until you said something. It looks like this fixed it. Thanks again! --Stux 23:15, 20 January 2021 (UTC)
[edit] Auto Missing File Detection
Hi Gfd,
Sorry for reverting your template changes, but as I mentioned in the summary, the {{#ifexist:}} parser template adds several pages to the Category:Pages with too many expensive parser function calls category. I tried saving the page to the internet archive but it wouldn't work. Let me see if I can upload some screenshots.
Anyway, the reason the template is so weird is that it's unable to tell if the file exists because it's too expensive on the server, so I had to jump through some hoops to get it to work reasonable well enough. That's why I reverted it back to its previous form. --Stux 14:38, 19 August 2024 (UTC)
