Editing Talk:Strong Bad Email

From Homestar Runner Wiki

Jump to: navigation, search
Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
Current revision Your text
Line 2: Line 2:
{{featuredarticle}}
{{featuredarticle}}
{{talkchecklist|Checklist for new Strong Bad Email:}}
{{talkchecklist|Checklist for new Strong Bad Email:}}
-
*Create an article with the title of the new email (as listed on the [[HR:sbemails|Strong Bad Email menu]]) with the content <tt><nowiki>{{subst:newsbemail|###}}</nowiki></tt> (substitute the new email number for <tt>###</tt>). If you already know the forum thread number, use <tt><nowiki>{{subst:newsbemail|###|#####}}</nowiki></tt>.
+
*Create an article with the title of the new email (as listed on the [[HR:sbemail.html|Strong Bad Email menu]]) with the content <tt><nowiki>{{subst:newsbemail|###}}</nowiki></tt> (substitute the new email number for <tt>###</tt>). If you already know the forum thread number, use <tt><nowiki>{{subst:newsbemail|###|#####}}</nowiki></tt>.
-
*Update [[Template:sbenav-lookup]].
+
*Update [[Template:sbemail]]. Be sure to set the value of "last" to the new email.
-
*Update main [[Strong Bad Email]] list, the [[Template:Strong Bad Email|template list]], and the [[Strong Bad Email Menu|menu list]].
+
*Update main [[Strong Bad Email]] list, and the [[Template:Strong Bad Email|template list]].
*On the main [[Strong Bad Email]] page, update the total emails and various fun facts.
*On the main [[Strong Bad Email]] page, update the total emails and various fun facts.
*Update each list in the Strong Bad Email [[Template:StrongBadEmailInfo|navigation template]] (and verify in each page's history that the previous email's entries were updated as well).
*Update each list in the Strong Bad Email [[Template:StrongBadEmailInfo|navigation template]] (and verify in each page's history that the previous email's entries were updated as well).
*Update [[Template:recenttoons]].
*Update [[Template:recenttoons]].
 +
*Update [[HRWiki:Subtitles/Data#Strong Bad Emails]].
*Link the email page to the forum and vice versa, if necessary.
*Link the email page to the forum and vice versa, if necessary.
*Redirect <tt><nowiki>[[</nowiki>sbemail###]]</tt>, <tt><nowiki>[[</nowiki>sbemail ###]]</tt>, and <tt><nowiki>[[</nowiki>Strong Bad Email ###]]</tt> to the current email.
*Redirect <tt><nowiki>[[</nowiki>sbemail###]]</tt>, <tt><nowiki>[[</nowiki>sbemail ###]]</tt>, and <tt><nowiki>[[</nowiki>Strong Bad Email ###]]</tt> to the current email.
-
*Update [[HRWiki:Subtitles/Data#Strong Bad Emails]], [[Template:whatsnew]], [[H*R.com updates {{CURRENTYEAR}}]], [[Index Page Messages]], [[Main Page Messages]], [[Strong Bad Emails By Length]], [[All Toons]], and [[YouTube]] (if applicable) with an entry to the new toon.
+
*Update [[Template:whatsnew]], [[H*R.com updates {{CURRENTYEAR}}]], [[New Stuff]], and [[All Toons]] with an entry to the new toon.
 +
*Update [[Secret Pages XML Source#Random Toon XML File]] with [[HR:rando.xml|rando.xml]] (click View->Page Source and copy/paste).
*Check your work using [[Special:Sbemailcheck]].
*Check your work using [[Special:Sbemailcheck]].
|}<br/>
|}<br/>
Line 175: Line 177:
A little while ago, I {{p|l=http://hrwiki.org/w/index.php?title=Strong_Bad_Email&diff=783935&oldid=783934 changed the list}} to use &mdash; em dashes instead of <small>(tiny text in parentheses)</small>. Not only does it look much better (in my opinion), but it's also more consistent with other lists on the wiki. However, it was reverted because it didn't have as much of a "feel" to it. But I don't think that's necessarily a good thing. How should this list be formatted? {{User:Gfdgsgxgzgdrc/sig‎}} 19:59, 29 June 2019 (UTC)
A little while ago, I {{p|l=http://hrwiki.org/w/index.php?title=Strong_Bad_Email&diff=783935&oldid=783934 changed the list}} to use &mdash; em dashes instead of <small>(tiny text in parentheses)</small>. Not only does it look much better (in my opinion), but it's also more consistent with other lists on the wiki. However, it was reverted because it didn't have as much of a "feel" to it. But I don't think that's necessarily a good thing. How should this list be formatted? {{User:Gfdgsgxgzgdrc/sig‎}} 19:59, 29 June 2019 (UTC)
-
:Anyone else have an opinion? The em dashes look clean and consistent, and the tiny text looks aesthetically displeasing. {{User:Gfdgsgxgzgdrc/sig‎}} 23:36, 21 January 2020 (UTC)
 
-
: i dunno, the tiny text looks nice to me, with text being the same size it looks a bit cluttered {{User:Timmodonuts/sig}} 15:37, 22 January 2020 (UTC)
 
-
::I'm for the em dash list. The current style doesn't match any other list on the wiki that I'm aware of, and I think changing text size in-line decreases readability. (What does "has a feel to it" mean anyway?) {{User:Lira/sig}} 19:39, 22 January 2020 (UTC)
 
-
:::I agree that the full size text seems very cluttered and hard to read.  Perhaps there’s a different way to present the information? -[[Special:Contributions/166.170.0.121|166.170.0.121]] 22:43, 22 January 2020 (UTC)
 
-
::::That's weird. For me it's the opposite; the full size text is pleasant and readable, while the small text looks cluttered and arbitrary. Maybe we could make it a table, with one column for the email number, one for the title, and one for the description. That way, we can keep the full size text, with borders between each item so it isn't as cluttered. {{User:Gfdgsgxgzgdrc/sig‎}} 23:21, 22 January 2020 (UTC)
 
-
::::: I am down for tables, I love tables, they make it much easier to digest the information! {{User:Timmodonuts/sig}} 16:08, 23 January 2020 (UTC)
 
-
::::::Not so into the table idea. That just sounds unnecessarily bulky and a weird format for the information. Maybe I just need to see a preview, but I still like the standard list with plain text. {{User:Lira/sig}} 20:58, 23 January 2020 (UTC)
 
-
:::::::I don't understand the desire to table everything. I think a table is best applied in situations when paired with an image or other critical data, such as dates. If it's just an example with an explanation, an ordinary list should suffice. -- [[Special:Contributions/68.37.43.131|68.37.43.131]] 03:10, 24 January 2020 (UTC)
 
-
::::::::Yeah, I mostly agree. I only suggested it because it seemed like a good way to include full size text without some people finding it cluttered. {{User:Gfdgsgxgzgdrc/sig‎}} 05:40, 24 January 2020 (UTC)
 
-
:::::::::The thing is it's no more cluttered than any other list of information on the wiki. If the style is cramping people's style, that should be a larger question for another talk page. Myself, I have no trouble reading it. {{User:Lira/sig}} 16:13, 24 January 2020 (UTC)
 
-
::::::::::Most other places in the wiki don’t have long sentence descriptions within this kind of list. -[[Special:Contributions/166.137.90.18|166.137.90.18]] 18:29, 24 January 2020 (UTC)
 
-
:::::::::::No? What about [[Homestar Runner and Strong Bad's Relationship|character relationships]]? What about [[Style|running gags]] and [[Doughnuts|item pages]]? How is this different? {{User:Lira/sig}} 19:08, 24 January 2020 (UTC)
 
-
So far, it seems there are 3 votes for em dashes, 1 votes for parentheses, 1 vote for tables, and 1 vote for an alternative solution. That's probably the closest we'll get to a consensus, so I've made the changes. I'm putting my reasoning here in place of an edit summary:<br>
 
-
The wiki's font size is intended to be read comfortably, so this list should stick to that. Like Lira said, if the text looks cluttered, that's a problem with the wiki rather than this list, so the discussion should be moved elsewhere. Every list on the wiki is formatted the same way, and no one has ever complained of their clutteredness before, to my knowledge. This list is no different in content, and that should be reflected in its appearance. Additionally, I think the consistent size looks cleaner and less arbitrary, and the em dash creates a neat separation between title and description. {{User:Gfdgsgxgzgdrc/sig‎}} 21:26, 14 February 2020 (UTC)
 
-
 
-
== {reading} ==
 
-
 
-
Some emails have ''{reading}'' (or some variant) before the email, and some don't. Should we remove them from those emails, or add them to the rest? Or even leave them as is? {{User:Gfdgsgxgzgdrc/sig‎}} 02:33, 8 July 2019 (UTC)
 
-
:For the discussion purposes, when present [http://www.hrwiki.org/w/index.php?title=dragon&diff=next&oldid=784857 it looks like this].
 
-
:Honestly, I'd be in favour of removing such instances. This mostly seems to be present in some older transcripts. I think just the presence of the email template is shorthand for him reading it out loud. --[[User:DorianGray|DorianGray]] 05:31, 8 July 2019 (UTC)
 
-
::I am on the fence whether or not we should remove such instances.  Although 99% of email entries are read, sometimes they just show up on the screen. Also, "training" the new reader into expecting "hey this block will be read out loud" the first few emails (assuming they somehow went through each email sequentially) wouldn't be a bad thing.  And, in a detailed wiki like this, it might not hurt to have the "reading" portion in every email (although it should look sleeker).  Now, my own comment ago kind of thwarted an idea I had, and that was: add the "Reading" portion to the email templates or block quotes.  However, since this isn't going to be used 100% of the time, it's probably counter productive (instead a template that adds the notice would probably be better -- that is if we keep the notices at all.) --[[User:Stux|Stux]] 12:37, 15 July 2019 (UTC)
 
-
:::Since I haven't given my opinion yet, I don't think the notices are necessary. The email box is kind of a continuation of Strong Bad's dialogue, and in cases where it isn't read aloud, the transcript usually states ''{The following email can be seen:}'' or something similar. Going straight from the email song to the email makes for a smoother transition.
 
-
:::We don't necessarily have to edit every email page right away, since that would be a huge undertaking. But it would be nice to reach a consensus, just so the notices can be added or removed during unrelated edits, if that makes sense. {{User:Gfdgsgxgzgdrc/sig‎}} 23:36, 21 January 2020 (UTC)
 
-
 
-
== Strong Bad Email Menu ==
 
-
 
-
Two points to make
 
-
1. Why did we never have an article for the Strong Bad Email menus in general when the Toon Time and the speciality sbemail ones have a page?
 
-
2. The new menu works completely differently and will probably need it's won page or subsection. Still trying figurue out if there's a pattern to Strong Bad's comments on the emails. [[User:Guybrush20X6|Guybrush20X6]] 02:02, 1 January 2021 (UTC)
 
-
:Yeah, I was just wondering that myself. We need to create [[Strong Bad Email Menu]], stat! (Also, I notice you've been adding descriptions to each email's page. I'd suggest holding off on that for now. It's a big project that needs consensus for how it's going to be implemented.) {{User:Gfdgsgxgzgdrc/sig‎}} 02:43, 1 January 2021 (UTC)
 
-
::Discussion about descriptions continues at [[HRWiki:Projects#Toon Descriptions|HRWiki:Projects → Toon Descriptions]]
 
-
 
-
== anyone like tge sbemaiil homsar? ==
 
-
 
-
anyone? no? ok...
 
-
 
-
==Sbemail209 release date==
 
-
March 25th, 2022 --[[User:Jeffjman|J∃ffJ]][[User_talk:Jeffjman|Man]][[File:jeffjsigchrismas.png|23px]] 17:13, 22 March 2022 (UTC)
 
-
:I wouldn’t get my hopes up. I don’t think we’re gonna see it for quite a while. And is there any source for that date or are you just making it up? [[User:TheOneAndOnlyDanky|TheOneAndOnlyDanky]] 18:27, 22 March 2022 (UTC)
 
-
::Mostly making it up, but hey, it might be out on either then OR april fools day, since they've been doing it every 4 years now. --[[User:Jeffjman|J∃ffJ]][[User_talk:Jeffjman|Man]][[File:jeffjsigchrismas.png|23px]] 11:18, 23 March 2022 (UTC)
 
-
 
-
== sbemail templates ==
 
-
 
-
I had an idea a while ago. What if instead of putting a whole blockquote thingy for an email, say [[strong badathlon]], instead we made a template for the email. I tried it out and it works.
 
-
 
-
The template could be:
 
-
<nowiki>{{sbemail165}}</nowiki>
 
-
and it would look like:
 
-
<blockquote class="lappy email">
 
-
<div>subject: the cheat</div>
 
-
Strong bad,<br>
 
-
For a long time i've been wondering.... How far can you<br>
 
-
throw the cheat?  If you don't want to do that, could you<br>
 
-
beat the crud out of homestar for no reason?<br>
 
-
<br>
 
-
Lewis Rudkin<br>
 
-
Essex, England.
 
-
</blockquote>
 
-
What do you guys think? Cool idea? Stupid idea? I have made more templates over on my [[User:HoveringSombrero/Sandbox|sandbox]]. - [[User:HoveringSombrero|HoveringSombrero]] ([[User talk:HoveringSombrero|talk]]) [[File:Shoulder shoomps.png|23px]]
 
-
:In theory, the idea isn't bad: I've thought of making a template with all the block quotes.  But making 200 different templates is too tedious and problematic to maintain.  Better to have a single template that has all the quotes in one place, selectable by a switch statement.  That way you can just programmatically pass the email number as a variable (for example <code><nowiki>{{sbemailTemplate|165}}</nowiki></code>; name pending) and maintain the code in a single location.  The downside would be that of performance as template limits might be reached if all 200 emails are included in a single page.  Either way, most likely the already-created templates will be deleted. --[[User:Stux|Stux]] 20:23, 7 January 2023 (UTC)
 
-
<blockquote class="lappy email">
 
-
Dear Homestar Runner Wiki,<br>
 
-
<br>
 
-
I was wondering why someone was creating hundreds of templates for individual emails that in practice, would only be used once. It seems more logical to have a
 
-
single template with spaces that can be customized so it can be used many
 
-
times in many different ways, when the needs arise.<br>
 
-
<br>
 
-
Also, a customizable template would also provide the opportunity for me to
 
-
play around with it and write my own hilarious Strong Bad Emails whenever the
 
-
mood strikes me.<br>
 
-
 
-
[[Crapfully yours|With excrement]],<br>
 
-
 
-
-- [[Special:Contributions/68.37.43.131|68.37.43.131]] 23:19, 7 January 2023 (UTC)</blockquote>
 
-
::I would only approve of this if they were combined into one template as Stux suggested, and even then I don't think it's necessary. Either way, I think the created templates should be deleted. {{User:Gfdgsgxgzgdrc/sig}} 05:22, 8 January 2023 (UTC)
 
-
:::These templates don't do anything except move one instance of code off the page where it appears. I don't see any benefit to this. Templates are useful for formatting, which these don't help with, or repetition, which I'd do a different way if we really thought we needed. (Given that sbemails aren't updating, I also don't think we currently need any formatting templates.) &mdash; [[User:It's dot com|It's dot com]] 01:31, 9 January 2023 (UTC)
 

Your changes will be visible immediately. If you would like to test or practice editing, please do so in the sandbox. You are encouraged to create, expand, and improve upon articles; however, bad edits to articles are watched for and will be quickly removed.


CAPTCHA Image
Image Code:
Cancel | Editing help (opens in new window)
You are required to enter a code from an image in order to perform certain operations. This image is designed to protect the site from vandalism. If the images are too obscured to read, just give it your best shot and a new image will be shown next time. If you are visually impaired or limited to text-based browsing, you can contact the site administrator and something can be arranged. The code is not case-sensitive.

The Homestar Runner Wiki is neither owned by nor affiliated with homestarrunner.com. Much of the material presented here is copyrighted by The Brothers Chaps and/or Harmless Junk, Inc. For more information, see the legal stuff page on the official Homestar Runner website. The proprietor of this site asserts that publication of such material on the wiki qualifies as fair use under United States copyright law.

Material on this site that is not copyrighted by The Brothers Chaps (e.g. opinions and mindless chatter) is licensed to the various authors, where indicated, and is released under a Creative Commons Deed, which simply ensures that none of this information may legally be used for commercial purposes.