HRWiki:Projects

From Homestar Runner Wiki

Revision as of 01:31, 4 March 2021 by It's dot com (Talk | contribs)
Jump to: navigation, search
Shortcut:
HRW:PR

Contents


Unfinished and ongoing projects

Wiki Cleanup

Ongoing cleanup tasks can be found at HRWiki:Cleanup

DVD Commentary

DVD commentary needs to be added to many toons. See HRWiki:DVD commentary transcripts for a list of toons that need DVD commentary, or check Category:Section Stubs.

Subtitles

Since nearly all subtitles have been done in English, it is time to improve their quality. Here are some starters.

Now is also a good time to translate them to other languages. See the project's section.

List all Homestarrunner.com files

I am starting a project to list all known files on Homestarrunner.com, starting with the SWFs, to make them easy for people to download with download managers. The list so far is at User:Nerd42/List. --NERD42  email  talk   h²g²  pedia  uncyc  01:09, 24 October 2006 (UTC)

Here is my equivalent of that list, but with a much larger scope. -- ■■   PURPLE Φ ORNAMENT   ■■ 19:31, 22 February 2015 (UTC)

Locations

Many locations do not have a full filmography; many still need to be added.

Physical Descriptions

Most of the articles about characters and such lack basic physical descriptions. I know that this is largely because we rely heavily on accompanying each article with appropriate images. However, on the off chance that the pictures are not viewable by a user (say, if the user has visual disability and uses a text-reading accessibility aid-type program, for example..), a short, very basic description might be appropriate.. Thoughts? -DAGRON 00:51, 12 April 2008 (UTC)

This is one of those things that seems so obvious once someone points it out and you wonder why nobody thought of it before. Yes, definitely, add physical descriptions to articles that don't have them. — It's dot com 05:08, 13 April 2008 (UTC)
All of the main characters now have descriptions. I just need to add some of the minor characters (All The King's Men, Storybook, Misc.). wbwolf (t | ed) 19:49, 8 June 2008 (UTC)
After a few days of working on this I'm pretty sure almost all of the character pages have at least some physical description now. I got all the ones listed on the Characters page that didn't have a description, with the exception of characters too minor to get their own page (should those be listed separately?) and like, animals or inanimate objects where just saying what it is gives a pretty good impression of what it looks like. I was also operating on the assumption that for pages on character variations we can assume that the reader already knows what the main character looks like, so if someone disagrees those probably need to be fleshed out. Freshasabagel 16:43, 25 June 2017 (UTC)

Image Cleanup

Here are some images that should be re-uploaded with a better quality. Either with better cropping or with better colors. The list is monitored and updated mostly by OptimisticFool. Elcool (talk)(contribs) 15:29, 20 July 2008 (UTC)

Well I re-did the 404'd one, but I'm not gonna do all of them by myself! Someone help out! Rondleman! Stuff I did.Talk. 02:48, 10 May 2010 (UTC)
JPG is not better quality. --DorianGray 05:20, 10 May 2010 (UTC)
BTW Wasd98: additionally, the check mark means that image has already been improved, so there's no need to work on those images. --Stux 06:03, 10 May 2010 (UTC)

Image Summaries

The image summaries of all the images on the wiki need to be checked and if necessary, changed to be descriptive and linked to the proper toon and anything else relevant. Pay attention to make sure that the correct licensing template is used as well. Also, some images lack the proper "Summary" and "Licensing" headers. I have a series of pages here For keeping track of images that have been checked. — Defender1031*Talk 11:11, 1 March 2009 (UTC)

Guitar Tablature

The purpose of this project is to provide guitar tabs for amateur guitarists who wish to learn how to play songs from the Homestar Runner body of work. I brought up making guitar tabs in a HRWiki:Da Basement discussion a while ago, and I've noticed that the idea lost a lot of momentum over the year, so I'm labeling it a project. I posted a list of songs that need tabbing in a user subpage. --Mario2.PNG Super Martyo boing! 03:15, 15 October 2009 (UTC)

YouTube Descriptions in Trivia

Currently, most Podstar Runner descriptions are in the Trivia section of the toon's page. For some reason, we don't do the same thing for YouTube uploads. They should be added. (A not-yet-complete list of descriptions can be found over here.) Gfdgsgxgzgdrc 22:53, 30 August 2017 (UTC)

Done ampersand done. At least, I think I did them all for now. Skills of an Artist, check. SBEmails, check. All the other toons listed on the wiki's YouTube page, check. Question is, should they stay under "trivia" or do we migrate some to the YouTube Version section of respective toon pages? 99.48.86.26 00:10, 9 April 2018 (UTC)
I think that the YouTube Version section of the pages is a better place for this information. I noticed that you were halfway through adding them to the Trivia section of the pages before you said anything about it, and then you kept going in Trivia. That makes for that much more work if we decide to move them to the YouTube Version sections. The Knights Who Say Ni 00:11, 11 April 2018 (UTC)
And one more thing: If the page doesn't have a YouTube Version section, I don't think this constitutes a pressing need to create it; it can stay in Trivia in those cases regardless. The Knights Who Say Ni 00:14, 11 April 2018 (UTC)
On the third hand, if there isn't a "Trivia" section or a "YouTube Version" section, that would be a sufficient reason to create a "YouTube Version" section to add the information. The Knights Who Say Ni 18:19, 5 May 2018 (UTC)
I can agree with YouTube descriptions going into the "YouTube Version" section if one's available. I'd say "YouTube Version" sections could be made (if there isn't already one) if there's a noticeable difference between the website version and the YouTube version other than the description, but yes, just having description text doesn't mean it needs its own section.
There are some pages that have a "DVD and YouTube" section, should those be split into separate sections? DEI DAT VMdatvm center\super contra 12:30, 11 April 2018 (UTC)
This won't answer your question regarding where to place the descriptions, but I did want to say, thank you 99.48.86.26 for your hard work! --Stux 15:47, 11 April 2018 (UTC)
Update It would seem that this item is now related to this project is it not? --Stux 18:13, 21 February 2021 (UTC)

Strong Bad's Cool Game for Attractive People Responses

SBCG4AP has been around for ten years now, and yet most (if not all) of the pages documenting all the game dialogue are still labelled as incomplete. I'd like to know what it would take to get those pages improved so they'll be classified as no-longer-stubs before the game becomes old and outdated enough to wind up on the abandonware circuit, and you have to turn off all the RAM and hit the computer with a brick just to play it. -- 68.37.43.131 21:44, 27 April 2018 (UTC)

@StrongBadActual

The @StrongBadActual pages are missing information. Gfdgsgxgzgdrc 04:29, 2 March 2019 (UTC)

I believe I've gotten a bare-bones version of all the replies from November 9, but it could use another set of eyes. DEI DAT VMdatvm center\super contra 15:37, 4 April 2019 (UTC)
Current Progress with tweet updates can be found in the talk page. --Stux 18:30, 4 April 2019 (UTC)

Transcript Standardization

This is by no means a high-priority project, since hardly anyone will even notice. And since there are so many transcripts, it's unrealistic to expect to finish in the near future. But anyway, I noticed a lot of transcripts don't follow the HRWiki:Standards guidelines. Sometimes they don't add proper capitalization and punctuation in long stage directions, and sometimes they do in the short ones. Sometimes the short stage directions are put on a separate line, and sometimes the long ones are in a line of dialogue. Instead of this:

{cut to Homestar}
HOMESTAR RUNNER: Oh, hello! {He smiles.} I'm Homestar.
{Homestar spins his buzzer}
HOMESTAR RUNNER: Here's Strong Bad! {cut to Strong Bad.}

...it should be this:

{Cut to Homestar.}
HOMESTAR RUNNER: Oh, hello! {smiles} I'm Homestar. {spins his buzzer} Here's Strong Bad!
{Cut to Strong Bad.}

Gfdgsgxgzgdrc 23:17, 5 July 2019 (UTC)

Nav Template Automation

See #Navigation templates for background

As some of you may have noticed, I've created a new category that contains a few templates aimed at automating the generation of the previous/next links in navigation templates (and other things). The reason I started this project was that given all the shuffling around caused by the post-Flash site update many links and other things have to be updated and one of them are navigation templates.

This process is prone to errors and issues (as I myself discovered to have caused) because anywhere from 3-5 pages have to be updated when moving a single page around (the page itself + prev*2 + next*2). The templates created make this easier by providing a single location where the nav ordering can be set! To my surprise I had forgotten that Strong Bad Emails already had such a system! Because emails have a numerical order, they're somewhat easy to code, but even Character pages can have a sort as shown in {{charnav-lookup}}.

Finally, since most pages still use the original templates, i created new templates that use the original templates. Eventually we can fold the code of each template into a single template but we should keep the old templates so that we don't break how page history looks.

Here's an outline of the work needed and completed thus far:
Here's a list of steps I've taken to update each nav:
  1. Create the lookup template. The standard I've been using for the template name has been {{sourcenav-lookup}}. Please feel free to use {{charnav-lookup}} as the reference template. Please use the Toons page or a relevant template in order to figure out the most appropriate ordering.
  2. Update the {{{link}}} parameter in the {{sourcenav}} template so that it handles empty parameters correctly during transclusion. Please use this diff as reference.
  3. Create the automation wrapper template. The standard I've been using for the template name has been {{asourcenav}}. This allows gradual updates to the affected articles and for page history rendering to remain unaffected. Please feel free to use {{acharnav}} as the reference template. Also notice how the lookup template can also be used to get the current reference name or identifier.
  4. Update each page to use the new template with the new numeric parameter corresponding to its order in the sequence. Here's a recent example.

I think I'm done for the day so please feel free to continue where I left off! Feel free to ask questions here! --Stux 12:31, 24 January 2021 (UTC)

I like this idea, but I do have some questions. Would it be possible to create one singular "lookup" template for all toons? (For Hremails it could be something like {{nav-lookup|hre}}, for Answering Machines {{nav-lookup|mam}}, etc.) Likewise, could the navigation templates be combined as well? That would be a more efficient use of space, using one page instead of multiple, and would cut down on the number of templates required.
Secondly, I notice that the lookup templates are determined by numbers, which makes it easy to add new entries at the end, but what about the middle? Let's pretend the shorts use this automated method, and the total number of shorts is 72. Suddenly, Hremail 7 is added in the middle, at #58, bumping the total up to 73. Would this require editing the pages of shorts 59-73 to reflect their new numbers, or would we only need to update the lookup template? (Does that make any sense?) Gfdgsgxgzgdrc 23:21, 24 January 2021 (UTC)
Regarding the singular template: I had originally thought of than then I decided not too thinking that a single global template would be "too big". This was taking into consideration the size of the SB Emails list and before I learned {{sbemail}} already existed. To be honest I am on the fence about this, slightly leaning towards keeping them separate: having one place for many small lists might be convenient in some ways but it might also be too brittle: a typo might break the nav for all pages invovled, not just the set being worked on. And I've been learning the hard way how easy it is to break something when multiple templates and parser functions are involved. Also, more page caches would be invalidated by the template change. Instead of just pages in the nav being recreated, all toons in the template would be recreated after every edit, adding a bit more strain on the server than necessary. On the other hand, it would make it easier to spin off new nav groups and use generic nav group templates. This may need to be the solution for the different toon categories anyway.
"(Does that make any sense?)" Oh! That makes total sense! I hadn't thought about that! Or I think I forgot. In my original plan I had two templates: the nav-lookup template that returns an item name based on its index, and an index-lookup template that would give you the index based on the page name. I actually wanted a single template with both data points next to each other (easier to update this in a single location) but I couldn't think of a way to solve this. I then thought it would be enough to just have the current nav-lookup setup until you brought this point up! Sequential items such as SBEmails, HRemails (sequential by release date) and MAM don't suffer from this problem, but the other lists would!
So this actually adds a bit of complexity: I think we need the second look up (from name back to index) but instead of two templates that I had originally thought of, we should do everything on one template (better to update everything in a single place). The problem then becomes that a combined nav-lookup template would be kind of tricky: one #switch for the list type, one #switch/if for selecting the lookup type (by name or by index) and then the two lists for each lookup. Maybe something like:
{{#switch:{{{cat}}}
|shorts= ...
|tgs= ...
|pbtc=...
|bigtoons=
{{#if:{{{n|}}}
|{{#switch:{{{1}}}<!-- lookup big toons by name -->
|Toon X=1
|Toon Y=2
}}<!-- end switch {{{1}}} -->
|{{#switch:{{{1}}}<!-- lookup big toons by index -->
|0
|17=Toon Zed
.
.
.
|3=Bubs
|2=Toon X
|1|#default=Toon Y
}}<!-- end switch {{{1}}} -->
}}<!-- end if -->
}}<!-- end switch cat -->

Still not a great solution but at the very least there's only one place to update when adding new toons. I don't know if using #count to dynamically generate IDs would work, not work or if it would just kill the wiki due to performance issues. If the wiki had like SQL querying support, this would be a cinch XD! If we keep separate templates then we'd only need to worry about adding the if and the second switch. In any case, the count version might look something like this:
{{#resetcount:idx}}
{{#if:{{{n|}}}
|{{#switch:{{{1}}}<!-- lookup big toons by name -->
|Toon X={{#count:idx}}
|Toon Y={{#count:idx}}
}}<!-- end switch {{{1}}} -->
|{{#switch:{{{1}}}<!-- lookup big toons by index -->
|{{#count:idx}}|#default=Toon Y
|{{#count:idx}}=Toon X
|{{#count:idx}}=Bubs
.
.
.
|0
|{{#count:idx}}=Toon Zed
}}<!-- end switch {{{1}}} -->
}}<!-- end if -->
Since the if should only select one switch, it *might* be okay to use a single index, but perhaps having two different counters might be better (the counters might execute prior to the switch, or not at all). We'd have to do thorough testing to see if that dynamic method would work. Of course that would mean that if any of the toons are out-of-sync between the name lookup and the idx lookup then very weird things will happen! So perhaps this counter idea should be shelved until we have a more unified system where we can have both |Toon X=1 and |1=Toon X on the same line. I hope my technical explanation made sense and I would appreciate any help you can provide! --Stux 00:28, 25 January 2021 (UTC)
I made a parser function, {{#navlist:}}, to look up page names from a list. All the -lookup templates can be converted to simple bulleted lists. I implemented it on {{charnav-lookup}} and {{acharnav}}. See the help page for instructions and let me know if you have any questions or feature requests. — It's dot com 20:47, 28 January 2021 (UTC)
That's pretty cool! Thank you for providing such an elegant solution :). I don't know anything about the internals of the parser function but one thing I'm wondering if why it doesn't work well when browsing a page's history. However it works fine during show preview and that was my main concern so with this I can continue the work much more quickly :). Thanks again Dot com! --Stux 07:37, 29 January 2021 (UTC)
There was a variable that was being set implicitly that needed to be set explicitly. It's fixed now. — It's dot com 17:21, 29 January 2021 (UTC)
Ah, I see. Good, it works now in the page history too! :) I wonder if that's the same issue or same kind of issue with auto redirect not working in page history? Anyway, in either case, thanks again for making this process 1000x easier! Also, thank you for unleashing The Cheatbot to replace all the regular nav instances with autonav instances! This saves everybody a lot of time! I've created {{apuppetnav}} and will work on the {{gamenav}} replacement soon-ish so if you could direct The Cheatbot to help with those, I'd be much obliged. That should leave us with Shorts, PBTC and any other toon category I can't think of off the top of my head. Again, many, many thanks! --Stux 11:55, 31 January 2021 (UTC)

Toon Descriptions

Descriptions are currently being added to the top of email pages, but I don't know if that's the best place for them. They're not so important that they need to be listed alongside date and running time. (Especially considering TV Time Toons Menu descriptions have never been documented on toon pages. I think that should change, but that's another discussion for another time.) I would add them to the Trivia section (alongside YouTube and Podstar Runner descriptions), like so: *The [[Strong Bad Email menu]] description for this email is "X" Gfdgsgxgzgdrc 22:07, 8 January 2021 (UTC)

But it's a fact that now can exist for literally every sbemail, and most if not all toons. If we're putting them on the sbemail/toon pages anyway, I think having a dedicated space for them, not under "Trivia", is the way to go. Maybe not necessarily at the top, but not in "Trivia". --Jay (Gobble) 23:18, 8 January 2021 (UTC)
Here are a couple of things that we will need to account for as we decide where and how to standardize this info:
  • Most of the menu descriptions are identical to the description on YouTube, but some are different.
  • Some of the YouTube descriptions are in the Trivia section, while some are in a YouTube Version section.
I think we should list the menu description, the YouTube description (if any), and the Podstar description (if any) together in a standard place, either in the upper area of the page or perhaps in a new Description(s) section above Explanations. If descriptions are identical, they should be combined and noted as such. — It's dot com 18:46, 1 February 2021 (UTC)
I definitely support listing all the descriptions together on each page. I like the idea of a Descriptions section. That would also be a good place to note the hidden page descriptions that Gfd brought up. Lira (talk) 20:47, 1 February 2021 (UTC)
Yeah, listing descriptions together is a good idea. Here's an idea I stole from User:It's dot com/replacement — I think it's a good way to include descriptions alongside the rest of the toon information without it being too intrusive. Then again, that would require drastically altering every toon page, so maybe a section in the Fun Facts is a better idea. Gfdgsgxgzgdrc 04:36, 3 February 2021 (UTC)
I really like the look of that (naturally), but I think it's too ambitious for this discussion. I think we should focus on the simple task of adding the info to each page (putting them in their own section is seeming more and more plausible) and not jump into a massive site overhaul (not yet anyway). — It's dot com 04:59, 3 February 2021 (UTC)
Nice job with the infobox Gfd. I also see that it's a little bit wider, allowing for more information and more space. I also do think it's a little early for a site overhaul and that implementing an infobox style layout merits serious consideration and discussion since we'd be drastically changing how we present information on the wiki. Also note there's already been some negative feedback on this matter before. --Stux 07:13, 3 February 2021 (UTC)
Yeah, that makes sense. I should've clarified better: it wasn't quite a serious proposal as much as a mock-up of something I thought might be cool. It can't be feasibly implemented without months/years of discussion and editing. If it wasn't clear before, I support a Descriptions section in the Fun Facts above Explanations. Gfdgsgxgzgdrc 20:27, 3 February 2021 (UTC)

It seems like the consensus is that the best way to include descriptions on pages is in a dedicated "Descriptions" section in the Fun Facts, above Explanations. I have created two templates to help with this: {{description}} (which should contain the description of every toon) and {{descriptionslist}} (which creates a Descriptions section using the data from the first template). However, before these are implemented, there are still some potential concerns that should be addressed by someone more knowledgeable than myself.

{{description}}

This template returns a description for a specific toon: for example, {{description|title=dragon|youtube}} returns "Strong Bad teaches the world how to draw a dragon." It can be used to automate {{descriptionslist}}, among other things (see template page for more details).

My main concern is that if we include every description in one template, it might get excessively large. And I'm no expert on loading and caches, but having every single description transcluded on every toon page could potentially make pages load longer. I don't know how much of a difference that would make, but if it's significant, one possible solution is to split this up into multiple templates (and possibly split up {{descriptionslist}} as well).

It will also take a lot of work to list every description, but this isn't exclusive to the template, so it's not really a concern. The alternative is to manually add Descriptions sections to each page (assuming that's the plan), which would take an equal amount of work. Either way, we'll have to round up a ton of descriptions, and the only difference is that the template allows the data to be transcluded elsewhere (not just the Fun Facts). It's not a huge difference, so I understand if it's decided that this template is not worth keeping (especially if the template size will be an issue).

{{descriptionslist}}

This template uses the data from {{description}} to automatically generate a "Descriptions" section on a page, just by adding {{descriptionslist}} above Explanations (or wherever this section may go).

I can't think of any concerns regarding this template. I think it's useful enough to keep even if {{description}} is deleted, although it will need to be reprogrammed to allow manual entry. In this case, instead of {{descriptionslist}} automatically generating a list, it would work like so:
{{descriptionslist
|toons = Strong Bad plays old PC games so you never will! In this episode, it's the classic DOS collection FriendlyWare P.C. Introductory Set!
|youtube = Join Strong Bad as he plays old PC games. This episode he tackles classic DOS collection FriendlyWare PC Introductory set!
}}

Does anyone have any thoughts on these two templates? Are they perfect and should be completed and implemented immediately, or are they horrible ideas that should be deleted and never spoken of again? Or maybe even somewhere in between? Gfdgsgxgzgdrc 22:20, 15 February 2021 (UTC)

I like this general approach. I can see the advantages of having the descriptions all in one place and then loaded into the page or the Toons page or whatever. I don't want to get too into the nitty-gritty of the format of the templates because I think we could possibly simplify them a bit with a parser function. I'm going to do some research on that and then report back when I can. — It's dot com 00:40, 16 February 2021 (UTC)
I have gathered all (or nearly all) of the descriptions from the H*R source code, menus, and YouTube. Now I'm just trying to figure out the best format to upload it to the wiki. — It's dot com 05:42, 17 February 2021 (UTC)
Okay, I've searched high and low to gather every description I could find and compiled the list onto HRWiki:Descriptions. I've temporarily protected that page while we verify and discuss the data. I used as much automation as I could when making it, so if you see something that's missing or wrong (especially if it's very wrong) please note it on HRWiki talk:Descriptions.
As for how we display them on pages, I think we're going to want simple labels (similar to how we do the page title at the top of the article) instead of the full sentences currently in the template above, because there are a number of descriptions with quotation marks in them (which are inconsistent). On each page, we could have a small link in the Descriptions section to a new Descriptions page where we go into detail about the different types. Also there are a few multi-line YouTube descriptions that I think we'll want to make collapsible.
But first, is the data right? — It's dot com 02:14, 21 February 2021 (UTC)
That's awesome!! Thanks a lot. I unfortunately don't have the time to verify every description right now, but I skimmed through the page and almost everything looks perfect. (I left a few minor nitpicks on the talk page.) Thanks for adding those old Games menu descriptions by the way, I forgot about those. I also hadn't considered how the format could be affected by quotation marks and line breaks. As you suggested, simple labels and collapsible multi-line text sounds like the best solution, and I'm excited for collapsible text to be implemented if we go that route. Tables are another potential solution, although they might be needlessly large and unwieldy, especially for regular one-line descriptions. Gfdgsgxgzgdrc 06:48, 21 February 2021 (UTC)
So, if I understand correctly:
I'm trying to get a sense for what the end goal will be here. Also, as mentioned earlier thank you very much for your hard work on this project Dot com and Gfd! --Stux 09:08, 21 February 2021 (UTC)
  • No, Descriptions will be an article about descriptions (as an idea, not the actual text): how they're used in the Homestar Runner body of work, and going into detail explaining the brief labels that we'll almost certainly want to use in other articles.
  • Not exactly. I imagine there will be a small link to Descriptions in every relevant article, but only for the context and explanations mentioned above.
  • The text of the descriptions will be listed in each respective article. Whether this is just plain text that we copy to each page or whether we use some kind of template or parser function is still TBD. My main goal this past week has been simply to get all the data in one place so that we can make better decisions on what to do with it, and HRWiki:Descriptions is currently serving as that repository. Whether it becomes a permanent repo or is just a temporary holding page before we break all the data up is also TBD. If it is permanent, its final form and location are TBD.
  • Those templates will not be used in their current forms, but whether they will be used at all is TBD. A lot is still TBD.
The end goal is obviously to get the content into the articles, but as I mentioned above the intermediate goal for me has been just to compile all the data so that we can figure out what to do next. — It's dot com 16:49, 21 February 2021 (UTC)

Now that all the data is compiled, we need to decide two things: (1) what do we want the actual Descriptions sections to look like, and (2) do we want the data to be centralized or split onto each page.

Descriptions section appearance

I envision a parser function that would turn this:

== Fun Facts ==

{{#descriptions:
source = toons = Crack Stuntman teaches kids about knife safety and how to have fun on spring break.
toons_flash = new_stuff = Crack Stuntman drops science.
youtube = Crack Stuntman delivers a two-pronged message about knife safety and spring break.
podstar_2006 = Crack Stuntman drops science and knife moderation. 
}}

=== Explanations ===
* This data is from [[An Important Rap Song]].

Into something like this:

Fun Facts
Descriptions
  • Page Source/Toons Menu: Crack Stuntman teaches kids about knife safety and how to have fun on spring break.
  • Flash Menu/New Stuff: Crack Stuntman drops science.
  • YouTube: Crack Stuntman delivers a two-pronged message about knife safety and spring break.
  • Podstar 2006: Crack Stuntman drops science and knife moderation.
Explanations

Here are all the codes that we need to fill in (feel free to edit this table as consensus dictates):

Code Label
source Page Source
email Strong Bad Email Menu
toons Toons Menu
toons_flash Flash Menu
new_stuff New Stuff
toons_old Flash Menu Old
chinese_food Chinese Food Menu
telebision Telebision Menu
lava_lamp Lava Lamp Menu
oldest Oldest Toons Menu
scrolling_shooter Scrolling Shooter Menu
scrolling_shooter_old Scrolling Shooter Menu Old
second_games Second Games Menu
original_games Original Games Menu
youtube Youtube
podstar_2008 Podstar 2008
podstar_2006 Podstar 2006

Some of the labels as of this writing are a little long, and I don't love that, but this should get the ball rolling. — It's dot com 20:20, 3 March 2021 (UTC)

Looks good to me. But in the example above, I find the "Page Source" and "New Stuff" labels redundant. The toons menu and email menu both call the page source description, so if the descriptions are identical in every case, it shouldn't have to be noted for every toon. Likewise, the New Stuff description is identical to the flash toons menu description is almost all cases, so not every toon on the New Stuff menu necessarily needs to be labeled as such. But even if we remove these labels, it should still be noted on Descriptions that toons and email descriptions come from the page source, and that New Stuff descriptions are usually identical to the rest of the toons menu. (And obviously, the "Page Source" label would be used for pages not on the toons or email menu, and "New Stuff" for toons with a different New Stuff description.)
I'm also uncertain of whether Podstar 2006 and 2008 should be labeled separately. In my original {{description}} template, I added separate codes for both Podstars, but only so the template would know which one to link to. I'm not super knowledgeable about how different both podcasts are, so I'm not sure if the years are relevant enough to be noted. Also, there don't appear to be any toons on both podcasts, so there are no instances where they need to be differentiated. Gfdgsgxgzgdrc 21:49, 3 March 2021 (UTC)
I could go along with not listing the Page Source label for things listed on the Toons menu and Strong Bad Email menu, as long as we had a note on Descriptions stating that the page source description was identical to the menu listing for every such page. We should still put source = email = <description> in our code just so that it's clear internally (because they're coded in two places: on the menu and each individual page, so there is the potential for them to be different; so far they're just not), but that can be suppressed on the output. I'm less keen on not listing the New Stuff label, because if it's not, you can't tell whether something that was on the Flash Toons menu was on New Stuff with the same description or simply not on New Stuff at all. There was no overlap between the Podstars at all, so I agree that we can probably leave the years off the labels (but not the codes) if we want.
You mentioned links. Should the be links on the labels? — It's dot com 01:31, 4 March 2021 (UTC)

Location of data

As much as I would like for all the data to stay in one centralized place and be transcluded onto individual pages, I don't think it's practical. There would need to be a really big advantage to outweigh several technical disadvantages, and right now I'm not seeing that. Moving the data from the current repo to each page should be no problem for The Cheatbot, so that's not a concern. (Removing existing descriptions that are currently on each page might be a chore, but that's true no matter what we do.) — It's dot com 20:20, 3 March 2021 (UTC)

Yeah, that makes sense. Having The Cheatbot move the data to each page sounds just as convenient, without all the technical issues of transcluding everything.
(I'm assuming there's no way for The Cheatbot to find and remove specific lines on a page? For YouTube descriptions, you'd need to search for lines starting with "*The [[YouTube]] description for this toon/email is". Podstar Runner descriptions are a bit more complicated, as they're kind of inconsistent, but they're all along the lines of *The summary of/on/for the [[Podstar Runner]] RSS feed [for this video] says/reads/read") Gfdgsgxgzgdrc 21:49, 3 March 2021 (UTC)
The Cheatbot (which essentially is a collection of scripts that when necessary uses an account to directly manipulate the database) can totally find and remove specific lines on a page. The question is whether we've been consistent enough with the descriptions currently on pages that a regex has a fighting chance of finding them. — It's dot com 01:31, 4 March 2021 (UTC)

Possible Page Disambiguations

Based on this discussion, there are several pages whose names only differ by the case of the first letter. I believe these are all topics whose names coincide with Strong Bad Email titles. Some of these links should probably be disambiguated in order to avoid confusion as to which page should be linked to. This would apply only to the upper case titles since the Strong Bad Email titles should remain unchanged. Here's a table that list the known collisions:

Strong Bad Email Upper case title Proposed Upper case Solution (if any)
tape-leg Tape-leg Move to "Tape-leg (running gag)"
crying Crying Move to "Crying (running gag)"
marzipan Marzipan Leave as-is?
pom pom Pom Pom Leave as-is?
making out Making Out Move to "Making Out (running gag)"
trogday Trogday trogday redirects to Happy Trogday as a filename redirect, while Trogday redirects to Holidays#Trogday (January 13). The latter should probably be turned into a disambiguation? (See Talk:trogday for some background.)
toons Toons Much ado about subtitles?
games Games Much ado about subtitles?
fhqwhgads Fhqwhgads Much ado about subtitles?
sbcg4ap SBCG4AP Much ado about subtitles?

I don't know if there are more examples. If they are they should be added to this list. I'm not sure if this is the best solution (and if the links should be automatically moved). I welcome any useful feedback! --Stux 11:45, 27 February 2021 (UTC)

I definitely think the (running gag) suffix would help sort things out a lot. Heck, it would make the whole mess we've got with Stinkoman 20X6 Level 10 easier to solve. Guybrush20X6 21:37, 27 February 2021 (UTC)
There are a few more somewhat obtrusive filename redirects, such as toons/Toons, games/Games, fhqwhgads/Fhqwhgads, and sbcg4ap/SBCG4AP. Are these redirects still necessary, since the subtitles project isn't really a thing right now?
As for the (running gag) suffix, I feel like the examples listed (with the exception of Tape-leg) aren't really running gags. A running gag is a joke that is repeated and developed over time, but these are just... occurences. But on the other hand, they're categorized as running gags, and "Crying (occurence)" isn't quite as catchy, so I guess (running gag) is fine. Gfdgsgxgzgdrc 22:02, 27 February 2021 (UTC)
So I've added the filename redirects to the list. Even though the subtitles don't work right now I still think they can be brought back to life would like to give them a chance. That said it would probably be good to explore the technical aspects of such a solution given the url changes between the old and new website (both of which are still active).
Looking at the content for Crying and Making Out I noticed that they're both Activity running gags, so why not "Crying (activity)"? If not running gag still works. --Stux 00:57, 28 February 2021 (UTC)
I don't have much to add here, but I should point out that filename redirects are good for more than just subtitles. They still work on the Homestar All-In-One script (or they would, if we fixed all the ones that are now changed). — It's dot com 03:35, 3 March 2021 (UTC)

Completed or overruled projects

Font Redirects

The main purpose of this project is to make all the fonts redirect to their page and their appropriate anchor. Currently, typing in AhnbergHand to the search bar redirects you to Fonts#AhnbergHand.

Typing in a certain font currently does not redirect to the page and its anchor. My project will change that, but we need more users to claim. MichaelXX2 mail_icon.gif link_icon.gif 23:14, 27 April 2009 (UTC)

I see absolutely no reason to do this. The search box at the left works just fine. So does Google. So does going to the Fonts page and pressing Ctrl + F. Fonts aren't special to the Homestar Runner universe, and so there's no reason for someone to expect there to be an article proper on any one font. (AhnbergHand, being one of the most used fonts, is a special case.) We would just be adding redirects for their own sake. — It's dot com 23:46, 27 April 2009 (UTC)
So I take it this project is overruled? DENNIS T/C 17:40, 7 September 2010 (UTC)

Image Captions

Some images need their captions updated, such as having links to the characters that are in the picture, links to where they are from, and links to where they are going. Also, I think it would be a good idea for all floppy disks from the Floppy Disk Container page to have links to the email or toon it's from and links to the game itself. DBK! 15:35, 27 January 2006 (UTC)

The floppy disk container page already does have links, its in the "Appearances" column, also as for your caption thing, I don't quite catch what you are talking about, captions are just short blurbs about the pic or a line that was used in that scene. I R F 16:06, 27 January 2006 (UTC)
Example: Image:Blue Hair 1-Up.PNG. We need to have captions more like that, and as for the floppy disks, I meant like a link to the Wikipedia article on the game shown on the disk. DBK! 16:12, 27 January 2006 (UTC)
I see I R F 16:35, 27 January 2006 (UTC)
Not all images need captions.--H*Bad 05:37, 24 July 2006 (UTC)
If the line under the image on the image's page is what you're talking about, that's not the caption. That's the summary, and there's already a project here for that. Thy Not Dennis (t/c) 12:38, 25 April 2009 (UTC)
You've replied to a three-year-old thread, just so you know. — It's dot com 19:46, 25 April 2009 (UTC)
That would explain why it's in this section. Sorry, I didn't notice. Thy Not Dennis (t/c) 20:33, 27 April 2009 (UTC)

Music Video Visuals

When it comes to music videos, the visuals are nearly half the cartoon, yet only the lyrics are listed. "[Insert Toon's Name Here] Visuals" pages need to be added for every music video, similar to this one.

Kobe Problem

Figure out a way to fix the Kobe problem discussed here.

Fixed as of 17:28, 5 May 2005 (UTC). The solution is explained on the talk page.

TBC G4techTV Interview - 01 Aug 2003

Due to the success of pages like TMBG Concert - 25 Sep 2004 and Screen Savers Interview - 24 Jan 2005, we bring you Pulse Interview - 1 Aug 2003, a new page for the "Pulse" video interview available for download on the Links page.

It would be brilliant if somebody would do this.
P.S. Please sign your posts. — InterruptorJones[[]] 14:00, 9 Feb 2005 (MST)

I have since completed the entire transcript of this interview - so this can probably be "refactored" or removed entirely from Projects. Right now, I would appreciate if others would check my work for accuracy as a few more eyes will catch the errors that I most inevitably made. For the record, I intentionally omitted many instances of the word "Uh" spoken by Matt and Mike as they don't contribute to the interview. However, there likely are some "on the record" types who insist transcripts be as accurate a possible - feel free to include them if you feel compelled to. --The Paper 16:15, 2 Mar 2005 (MST)

Splitting Fun Facts

Any toon, game- any article with many fun facts needs to be split into the categories found in HRWiki:Standards.

Release Dates

I've noticed that a lot of Toons and E-mails now have 'release date' in bold at the top of the page, with an accompanying date. I really like this feature, but it only goes back so far. Until now. With the recent use of the Live Journal website, I have managed to compile a mostly complete list of updates, going back until late 2001. (It gets sketchy there.) So anyways, if anyone wants to go over those new past updates pages, and add the release dates to the many Toons, emails, etc., that would be much appreciated. Thanks. [[User:Thunderbird L17|⇔Thunderbird⇔]] 02:59, 25 Feb 2005 (MST)

Tying Updates Together

I'm kinda afriad to do this, because they all have some kinda notoc thing or something on the pages, I don't know what they do, and am too scared I'll mess it up. So can somebody, somehow, tie all the updates pages, (2005, 2004, 2003, 2002, and 2001) all together? Either just expand the disclaimers at the tops of all of them, or maybe even make a new page with all of them on there or something? I dunno, it's up to you, but they really should be linked to somehow, now that they're all doneish. [[User:Thunderbird L17|⇔Thunderbird⇔]] 18:05, 25 Feb 2005 (MST)

I made a template that we could use; what do you guys think? Kilroy/talk[[]] 18:54, 25 Feb 2005 (MST)
I like it.—StrongstarRunbad 18:58, 25 Feb 2005 (MST)
So do I, it's always annoying when I try to add a new 2005 update, I have to go into the code to find the other page that I CAN edit and everything. If we add this to all 4 pages, It'll be way easier to add an update, and navigate. Count this a vote for yes.

[[User:Thunderbird L17|⇔Thunderbird⇔]] 11:54, 27 Feb 2005 (MST)

That template rocks. Most certainly yes. →[[User:FireBird|FireBird]]

Running Times

It appears that at least tomstiff, possibly others, have begun adding 'Running Time' to many toons, expanding on the section that includes Date. I think this feature is almost as important and useful as date, so if anyone would like to add running times to the various e-mails and toons, I think they would apprecate a bit of help. [[User:Thunderbird L17|⇔Thunderbird⇔]] 20:37, 7 Mar 2005 (MST)

Check all emails to date and they all have the running times I R F 17:56, 26 January 2006 (UTC)

TBC at SxSW

  • Page: SXSW Panel - 14 Mar 2005
  • The guys from HomestarRunner.com talk about their cartoons, their five years on the Internet, and show you a bunch of stuff you have never seen; including footage that they just shot at SXSW, like, today even. Puppet versions of their characters will no doubt stop by and insult you or your family. You can ask the boys questions and they will do their best to provide informative and clever answers. High fives for everyone!
The Brothers Chaps made an appearance at SxSW. There is tons and tons of info out there on this, since the kind of people who attend blogger conferences are typically bloggers. See Google and Technorati for many writeups. There are also a bunch of photos at Flickr. (Though be sure to get permission for any photos used.)
Note that there seems to be a bit of content from NYU Talk - 1 Mar 2005.

Introducing a new Interwiki link

homestarrunner.com links

I just set up a new interwiki link that I think will make things super-easy around here (though I shant take the credit, it was Jones' idea). From now on, when you want to build a link to the official Homestar Runner site, use

[[HR:sbemail.htm|Strong Bad Email]]

instead of

[http://www.homestarrunner.com/sbemail.htm Strong Bad Email]

It's that simple. JoeyDay (Talk) 15:23, 21 Mar 2005 (MST)

All links to homestarrunner.com should be changed to the new interwiki-type shortcut format, since now with MediaWiki 1.4 all external links have a rel="nofollow" attribute. For information on "nofollow", please see this Google article. -- Tom 14:19, 3 Apr 2005 (MDT)
Actually, that was my idea when we were moving to MediaWiki :P - furrykef (Talk at me) 08:21, 26 Apr 2005 (UTC)
I think you had a similar idea. -- Tom 20:42, 26 Apr 2005 (UTC)
That's not what I was talking about at all. I was talking about Interwiki, exactly the way Joey did it. I don't know if that discussion actually took place on this wiki or not, though. Of course, it's not important anyway. :) - furrykef (Talk at me) 12:53, 27 Apr 2005 (UTC)

Forum links

There's another new interwiki link: Forum

Example: [[Forum:1226|forum thread re: "montage"]] becomes forum thread re: "montage".

Again, it's just that simple. — It's dot com 23:11, 7 Aug 2005 (UTC)

I'm on it. -Polly 00:14, 8 Aug 2005 (UTC)

Fan Stuff List

I'm trying to get all the Fan Stuff Items onto the Fan Stuff page. #1 - 10 are already there, if anybody could do a few I'd appreciate it. --Gafaddict 13:10, 29 Mar 2005 (MST)

Sightings

The Sightings page has some terrible grammar and spelling and is altogether very cluttered. The whole page needs to be cleared out. →FireBird

I think Sightings should be split into various page like TV Sightings, Comic Sightings etc. That nobody has to sift through a million "this webcomic made a reference" sightings to get to interesting ones. Aurora the Homestar Coder 16:59, 29 Apr 2005 (UTC)

Food

I recently added a new article, Food , because there are something like 30 different food articles which aren't connected. I didn't have enough time, though, to write much or make a very extensive list. Please help out. I also added a Cuisine section to the Free Country, USA page.

- Anonymous

Lists like you are thinking of making are generated by our category system. See Category:Food and drinks. Also, I left a comment on the talk page regarding the merits of that article. -- Tom 15:44, 4 May 2005 (UTC)

Things to Merge


Track Information Template

I'm trying to get all the pages related to the tracks on the Strong Bad Sings CD to use the Template:Track information in the "Detailed Information" section, rather than everything being typed out. You can see the template in action on the page for The System Is Down. --Gafaddict 18:03, 3 Jul 2005 (UTC)

Easter Egg Character Problem

I've noticed that in toons and emails, the characters that are only seen in easter eggs sometimes have "(easter egg)" following their names on the cast, such as haircut and others don't. -- User:Tompkins

Give an example of the "don't." --Jay (Gobble) 18:39, 7 Sep 2005 (UTC)

Ignored rule

If a character does something while speaking a line of dialogue, or if more description is needed for their manner of speaking or inflection (e.g. if they're singing or whispering) the action (if it is not too long to describe in a few words) can be enclosed in curly braces — { } — and made italic, like this: {goes to the refrigerator}. Note that the curly braces themselves are also italic. Short actions like these do not need to be proper sentences.

The bold rule is probably one of the most ignored rules ever. Go through the various transcripts and you'll see tons of examples of long in-dialogue actions, some of which don't even relate to the speaker. This problem needs to be fixed, but it's way too big for me to do alone. (Here is an extreme example of this problem.) - Joshua 14:18, 17 October 2005 (UTC)

If the rule is so widely ignored, wouldn't that imply that the rule needs review instead of the application of the rule? I'm not saying that modeling should or shouldn't be fixed, but I just want to make sure people don't get over zealous in taking this on. -- Tom 21:03, 17 October 2005 (UTC)
Without meaning to sound ignorant, where or how should the long in-dialogue actions be transcribed? In modeling the actions are quite important to the plot and script, so it would be a fault if they were left out. How else should they be written? -- Michelle Mabelle 12:33 7 April 2006

Image copyright tags

Add appropriate copyright tags to every image on the wiki. Categories and tags can be found through Category:Images by copyright status — User:ACupOfCoffee@

Done! Now verify none were skipped, and that they're all correct. (Some may need more than one) — User:ACupOfCoffee@

TGS template

Took a mixture of Bill's template code from the prexnext template, and some from IDC's code from the sbemailnav template and made {{tgsnav}}. This added a watch button and the issue number being standardized. Some pages had the issue number under the main title, some didn't. I R F 14:57, 27 January 2006 (UTC)

Please proof for error as this is my first time working with a template I R F 14:58, 27 January 2006 (UTC)
To those not in the know: this nav is based out of {{sbenav}}. Discussion for this can be found here. --Stux 16:33, 27 January 2006 (UTC)
Looks great! I guess this can go in the "completed" section now? --Stux 16:40, 27 January 2006 (UTC)
The only question that I have, for which I could find an answer in the original discussion, did we decide finally on the watch link being there or is there a chance that people want it in the middle? I R F 17:15, 27 January 2006 (UTC)

Lappy Email Template

Ok, to make creating the Lappy email boxes easier, I created a template. You type the subject, then the email (click edit to see proper way). Template:Lappyemail is the name. Here's an example:

Template:Lappyemail

Tell me if you think it's easier!

Bluebry 23:52, 30 January 2006 (UTC)

Navigation templates

This project dicussion originated from the Talk:Strong_Bad_Email/Archive_2#Navigation_template discussion.

Toon Type Status worked on by Templates used
Big Toons Image:Wiki_tick.png completed I R F thanks to Venusy for some fixes. {{toonnav}}
Shorts Image:Wiki_tick.png completed Bluebry
I R F
{{toonnav}}
Powered by The Cheat not going to complete because too many PBTC pages are shared with email pages I R F N/A
Puppet Stuff Image:Wiki_tick.png completed I R F {{puppetnav}}
Holiday_Toons Image:Wiki_tick.png completed I R F {{toonnav}}
Marzipan's Answering Machine Version Image:Wiki_tick.png completed Bill
Stux
{{mamnav}}
Strong Bad Email Image:Wiki_tick.png completed It's dot com
Lapper (talk)
Stux
Bill
{{sbenav}}
Teen Girl Squad Image:Wiki_tick.png completed I R F {{tgsnav}}
Intros Image:Wiki_tick.png completed was already done {{Succession box}}
Character Videos Image:Wiki_tick.png completed I R F {{charnav}}
Main_Pages Image:Wiki_tick.png completed I R F {{mainnav}}

Suggestions

As for the character video, why not just do one for each main characters? DBK! 03:26, 30 January 2006 (UTC)

I second that. --Stux 03:47, 30 January 2006 (UTC)

Main Page Nav Template

This conversation was moved from Talk:Main_Pages#Main_Page_Nav_Template.

Does anyone think we need a navigation template for the main pages like we have for the Toons, TGS Issues, Answering Machines and SBEmails? You know, like, if you were on Main Page 5, there would be arrows at the top of the screen pointing to Main Pages 4 and 6. Just a thought. I thought it would be prooty awexome because the main pages pages go in sequential order. Any opinions on how stupid and/or borderline mental that sounded? Has Matt? (talk) 00:16, 1 February 2006 (UTC)

I, personally, don't think it's a bad idea. It's looked good so far. --Stux 02:43, 1 February 2006 (UTC)
Great idea are you doing that one? If not I don't mind I just don't want us both doing it at the same time. I R F 14:38, 1 February 2006 (UTC) I was thinking something like this:
go to Main Page 1 Main Page 23 Main Page 2
Right now I am not doing it so feel free to work on that. However, I was wondering about the secondary main pages such as this one that do not have a number assigned to them. The current form of {{mainnav}} does not allow for listings of such pages. As for the "go to Main Page X" tag, it might be slightly long, but the only other option i was thinking of was "go to Main Page" which isn't that much shorter. So that should be adequate I guess. You may have to alter the nav so that you have to type: {{mainnav|main1.html|Main Page 23|Main Page 2}} in order to handle secondary pages. In this case, the use of a generic navigation template (there should be one out there somewhere -- SBEmail talk perhaps?) would be better. --Stux 17:42, 1 February 2006 (UTC)
That was quick work! Hopefully the comment above won't set you back ... much. Anyway I just wanted to note that the blank space to the left of the nav makes me a little "uncomfortable". I don't like having that big gap between the title and the first line of text. Oh! I know... I think i know how to fix it and i'll fix it in the first main page only... gotta eat lunch and get to work! --Stux 17:52, 1 February 2006 (UTC)
My solution is not going to work. I'll have to look at it later. --Stux 17:54, 1 February 2006 (UTC)
I don't think those egg pages need to be lumped in with the rest of them. They are eggs and as such are not in order like the rest of them. It would not be in the list of main page that users would be looking normally (which is what the nav is made for; easier access to HRWIKI knowledge). I don't think the goal of the navigation buttons are to link every article in every area. IF we decide those main pages get nav button to, I say nav them JUST with each other keeping them seperate from the ither main pages I R F 18:00, 1 February 2006 (UTC)
That <big>IF</big> comment makes sense (I just wanted to paste the code). If we take the Strong Bad Emails as precedent (and TGS), the DVD emails and NQSB emails don't have anything currently and are separated from the real emails. I'll looks at the template formatting soon. --Stux 18:40, 1 February 2006 (UTC)
Ok I fixed the spacing issue. I also added a list of the templates we're using. I will add a cat to them soon. --Stux 18:52, 1 February 2006 (UTC)

Help with Shorts Template

I signed up for the shorts template. Is it okay to have 4 of {{{X}}} these in there? Bluebry 03:36, 30 January 2006 (UTC)

I created it, um... Template:shortnav. Tell me what you think. Here's an emaple:


Toon Category: Shorts
watch Commandos in the Classroom Strong Bad is a Bad Guy
Bluebry 03:40, 30 January 2006 (UTC)
What if we changed it to Template:toonnav, which would be a generic template. We don't really need the "Short:" identifier. — It's dot com 03:42, 30 January 2006 (UTC)
Umm, okay, but this isn't for big toons. Shorts. Bluebry 03:45, 30 January 2006 (UTC)
Oh oh oH! I get it! Good idea. Sure. moving! Bluebry 03:46, 30 January 2006 (UTC)
Mov'd! Template:toonnav Bluebry 03:48, 30 January 2006 (UTC)
Cool. But, now that I think about it, are the toons considered to be in an order? Wouldn't this be sufficient? — It's dot com 03:50, 30 January 2006 (UTC)
Well, if they're in the order on the TV guide. Bluebry 03:51, 30 January 2006 (UTC)
That's how I did the example. Bluebry 03:52, 30 January 2006 (UTC)

Links to be fixed

TriviaTime

Please help add interesting questions to JoeyDay's TriviaTime.

DVD info on certain toons

All toons and emails that have been released on a DVD need to have a template noting that it's on a DVD. Like this: {{dvd|Everything Else, Volume 2}}

Finished it. Thanks Trey56 for doing the strong bad emails. Okay, bye. TheYellowDart(t/c)

TV Time Codes

I've noticed the 3-digit codes on the TV Time menu. I would like to put this code on every 'toon that can be accessed from the TV Time menu. I've already started this, in the article for more armies. Swarthily,

Bubs Concession Stand

I mean, Superfield Credit Union

I'm glad you're willing to help out, but I'm not so sure that's a good idea. The information is already on the Toons page, and it's more relevant there than to the toons themselves. — It's dot com 15:43, 12 July 2007 (UTC)
Actually, I like the idea. The codes often relate to the toon in some way and are often funny. — Defender1031*Talk 01:44, 3 August 2007 (UTC)
Which is why we explain them on the toons page. But the codes are a specific part of the TV guide, and aren't really that relevant to the toons themselves. As such, noting them on each and every toon article would not really give more insight to the respective toons. On the other hand, noting them all in one long list, as we currently do, is most appropriate. — It's dot com 01:50, 3 August 2007 (UTC)

Underscores

As anyone who has been to Recent Changes in the past few days has probably seen, I've been making a massive effort toward removing underscores from links. It has been brought to my attention that some of these edits have not necessarily been the will of the community and I should have brought it up before starting the project. I will admit that some very good suggestions have been made (like marking them all as minor edits so they could be easily hidden in RC (which I was not aware of when I began)). And some opinions have come out that suggest that a consensus should be reached before these types of edits continue. My philosophy was that all double-bracket links were worth changing from underscores to spaces. Double-bracket links include: [[Internal Links]], [[Wikipedia:]], [[Image:]], [[HR:]], [[Mirror:]], etc. If you have an opinion as to whether or not any of these should be left with underscores, please reply to this message. OptimisticFool 22:05, 20 November 2007 (UTC)

For anything other than an Internal Link, why does it matter? —BazookaJoe 22:12, 20 November 2007 (UTC)
I support this in general, although I should point out that as long as an underscore isn't showing where it's not supposed to, then there's no technical reason to make a specific edit to change it. In other words, I often remove underscores, but it's usually a piggyback with another, more substantial edit. I do think, however, that we should leave underscores in HR and Mirror links, as the files to which they point actually have underscores in the names (and even though a similar case could be made for image links, I think those look better with spaces). — It's dot com 22:14, 20 November 2007 (UTC)
I agree with It's dot com. --Mario2.PNG Super Martyo boing! 22:19, 20 November 2007 (UTC)
I'm confused. If there's no technical reason for spaces rather than underscores, then why do it? Why come Image:Homestar Runner.png is better than Image:Homestar_Runner.png? —BazookaJoe 22:44, 20 November 2007 (UTC)
No real reason. Aesthetics, mainly. I personally think that internal links with spaces are easier to read than those with underscores. — It's dot com 22:47, 20 November 2007 (UTC)
That's cool. So I guess unless we are dealing with strongbad email.exe vs. strongbad_email.exe, then it's not really "worth changing," as OptimisticFool stated, unless you like it better aesthetically and are piggybacking it on another edit. Well, it's certainly not worth spending hours focusing on. —BazookaJoe 23:03, 20 November 2007 (UTC)

Main Character Categories

I recently made categories for the main characters. Can anyone think of any reason why we shouldn't have this? If you don't think we should, then could you explain why all the Coach Z and Bubs character variations are listed as Main Characters but nobody else's is? Stev0 15:05, 23 December 2010 (UTC)

I like this and don't know why we haven't had it before. Now that there are categories for the main characters, we should clean out the Main Characters category. For example, now that there is a category for Bubs, The Thnikkaman should be only in his category, not the main characters category too. — It's dot com 22:11, 28 December 2010 (UTC)
That's exactly the reason I created the categories in the first place. However, the Bubs and Coach Z variations are in those boxes, which I forgot how to edit. Stev0 05:07, 29 December 2010 (UTC)
There, I think I've got it all cleaned up. — It's dot com 21:08, 29 December 2010 (UTC)
I was going to move this to the completed section then I realized that the characters category also could use some cleanup. I'll see if I can work on that a little later on. --Stux 01:42, 28 February 2017 (UTC)
This work was completed in 2018. --Stux 08:39, 28 January 2021 (UTC)
Personal tools