History Main / TipsWorksheet

13th Mar '14 10:02:40 AM SeptimusHeap
Is there an issue? Send a Message
! Installed: Don't add or remove things in this section. It doesn't ''do'' the installation, it is just a list of what has been installed. There is a section below this one for ideas and suggestions. [numlist:0] # Remember to use the discussion page for questions. They don't go in the article. Just click that discussion button at the top of every page. # The idea is to make articles in Main look like they were written by the same person. A person with a good sense of humor, who doesn't talk about themself with 'I' or 'this troper', or get in arguments with themself, and who just corrects errors they might have made earlier without drawing attention to them. # Use spoiler tags when you really need them, but it would be even better if you could manage to write your example without bringing up the sensitive information. # If you feel the need to preface your example with "Not really an example but..." you know in your heart it's not an example. Don't add it. # "I can't believe no-one mentioned X yet!" Except, you did just now, so that won't mean anything in a moment. Write your example like it's been there forever and we won't tell a soul it wasn't. # If you're using a third bullet point, take a moment to think about what you're typing and where it should go. # Be sure this example isn't here already. # Want to share your opinion on a work? Try [[TVTropesReviews writing a review]]! # A trope can't be "partially subverted" any more than a woman can be "a little bit pregnant." If it isn't played straight and it isn't quite subverted, check the PlayingWithATrope page to see which one it is. # An [[spoiler:example]] that [[spoiler:is almost completely spoilered]] out doesn't [[spoiler:work very well]] as [[spoiler:an]] example. # Here is an example of word cruft: "Don't forget, actually, as a matter of fact, what really happened is that there's far too much WordCruft in this example." # Did you just catch an error? [[Administrivia/RepairDontRespond Be sure to fix it rather than just pointing it out]]. # We are not interested in whether or not something is or was popular. Whether or not it was liked has nothing to do with tropes. # No matter how popular your favorite show is, there are even more people out there who didn't see it. Listing your example as "Show X! Just... Show X" doesn't work. Always explain ''how'' Show X is an example. # Got a spoiler you want to hide? Take a look at our [[Administrivia/HandlingSpoilers Spoiler Policy]], and consider whether the spoiler is really needed. # Memes don't automatically make things wittier. Resist the urge to shoehorn one in. # More than one page-top quote just gets in the way. Use the Quotes page for the rest. #You are not reminding people of what they know. You are relating something they might not know. Things like "Don't forget", "Remember...", and "Lest we forget" are WordCruft, overused to the point of being irritating. Just tell us the fun stuff to know. # The articles aren't a chatroom. Do not put 'LOL' or emoticons in your edits. # Please read Administrivia/ExampleIndentationInTropeLists as early and as often as possible. [/numlist] !! Ideas/Discussion !!!Tips for suggesting tips: * Installed Tip #6 applies here, too: '''''Be sure that what you are suggesting isn't here already.''''' * Don't just tell people what ''not'' to do. Tell them what they should do instead. * Administrivia/BrevityIsWit. If you've written a paragraph, skip to the '''end''', get to the '''point''', and that summary is your '''tip'''. Check if the rest is covered by an {{Administrivia}} link. !!!Suggested tips to install: [[AC:Consistent Voice]] * If an example is poorly written or overlooks something important, ''[[Administrivia/RepairDontRespond change]]'' the example. Commentary in [[Administrivia/ConversationInTheMainPage sub-bullet points]], [[ParaBombing parentheses]] and [[ThreadMode "however, ..." digressions]] clutters the page. * A paragraph should not start with "actually", "YMMV", "wrong", "incorrect", "you mean", "[[JustifyingEdit to be fair]]", "not really", or anything of the sort. You're writing an article. Articles can provide different viewpoints, but they do not contradict themselves. * No "I." Period. (Full stop) * "You" when referring to the reader -- sure, you're allowed to do that. "You" when referring to the text above you -- Bad Thing! [[AC:Please Elaborate and Be Specific]] * Neither "And ''how''!", "Full stop", or "Nuff said" give enough information to someone who hasn't seen/read a work. They should not be used as complete examples. * Go look it up; we'll still be here when you get back. Better that than writing "happened in ''TheHoneymooners'', or possibly ''Series/{{Fringe}}''." * The description is the place for describing general uses of the trope. Examples that aren't from a specific work ''aren't examples''. Don't just write "all anime ever" -- give us specifics. * Don't add examples of works in which you assume a trope occurs, or expect it to occur; only add an example of the trope actually occurring. * Don't just drop a bare URL for an off-site link into an example, especially as the only thing ''in'' the example. It's better to make it a pothole for some relevant trope page. * Write in a way that will [[FanMyopia make sense to non-fans]]. Describe motives, causes and effects rather than throwing around bare character names and episode numbers. It's good form to PotHole the trope behind the reference (e.g., ''In the climax of the [[ProlongedPrologue Alpha mission]], [[TheLancer Bob]] resorts to using the [[DangerousForbiddenTechnique Omega Spark]]''). * Examples in trope pages should actually mention the ''name of the work'' -- a PotHole isn't enough. If they don't, not only are they less readable -- they won't show up in page search, which will cause repeat examples. * If you're going to claim WordOfGod, back it up, or at least determine where and when it's from. Otherwise people will suspect [[GodNeverSaidThat it originated from some tripod webpage's "rumors" section in 1997]]. You don't have to write up a bibliography, but at least make it possible for readers to verify it for themselves. [[AC: Spoilers]] * Our [[Administrivia/HandlingSpoilers Spoiler Policy]] in a nutshell: Don't bring up spoilers if you don't have to. If you do, make the writing legible to someone who won't highlight the spoilers and make sure they're not [[Administrivia/SelfFulfillingSpoiler given away by their length or context]]. * Do not put links or WikiWords inside spoilers. This will result in people accidentally clicking said link when they select the spoilered text to read it. * [[labelnote:Spoiler--click to reveal]]Yes, we want to reduce abuse of spoiler font. But we don't want it all replaced with the [[Sandbox/NotesAndLabelNotes note markup]], because that doesn't change the problem.[[/labelnote]] * ''Don't'' spoiler tag the name of the work you're spoiling, or the name of the trope that's the spoiler. It doesn't help at all. ** Exception: Character pages. Stating that a trope turns out to apply to ''someone specific'' may be enough of a spoiler to warrant whiting out. Exercise your judgment. * If a work is short enough that you could reasonably fit all of it in an example (for example, jokes), you don't have to use spoilers. After all, if the reader reached the spoilered-out part in your example, it means they reached the point where learning the twist wouldn't count as being spoiled. [[AC:Administrivia and other tips with accompanying pages]] * TropesAreNotGood. Your favorite work isn't going to get any cooler for being mentioned on this page. Don't add it unless it belongs. * If you feel this page needs a sharp snappy explanation, make one yourself at the LaconicWiki. Change the /Main/ part of the URL to /Laconic/ and edit the page. * If you think there's a problem with a trope -- e.g. it's too specific, it's being misunderstood, it's suffering TropeDecay, it's extensively poorly written -- take it to the TropeRepairShop. If you think it absolutely does not belong, bring up the possibility of taking it to the CutList. * Is there something about the way the site is run that bugs you? Bring it up -- politely, and with a minimum of hostility -- in the "Wiki and Forums" section of the TVTropesForum. * Looking for some way to be helpful? Check out NeedsWikiMagicLove and ListOfShowsThatNeedSummary. * Don't use the kind of phrases that are in the Administrivia/PermanentRedLinkClub (IAmNotMakingThisUp, SoYeah, ThisTroper). They've been sent there for a reason. * Follow the RuleOfCautiousEditingJudgment: don't add examples that are going to get people riled up. * Avoid referring to wiki-specific trivia in examples. Nobody cares if an example used to be the TropeNamer or if it was almost the TropeNamer or if there were extensive arguments on TVTropes about it. We already have [[Administrivia/RenamedTropes a page]] detailing trope renamings, so don't feel like you need to memorialize the fallen trope name. * Avoid adding [[YMMV.HomePage subjectives]] on an article's main page. It is now policy that these items go on subpages. * Keep from throwing in links to Administrivia/{{Sinkhole}}s. Typing in a style like BuffySpeak is fine, but it's NotAnExample of the trope. * Administrivia/NoLewdnessNoPrudishness. If a work contains sexuality, state the facts and don't gush; but on the other hand don't whitewash it either. [[AC:Administrivia/HowToWriteAnExample]] * Favor understatement over exaggeration. Do not use either at the expense of clarity. * A PotHole to the extent of "HEY LOOK I MADE A REFERENCE" or "LOLZ I MADE A FUNNY" [[DontExplainTheJoke can really take the fun out of the joke]]. Save them for potential "huh, I don't get it" situations. * However, please remember that English is a lot of tropers' second language, who won't be able to appreciate the word play that seems so obvious to you. A brief explanation, or even a link to the expression you're referring to, is often much appreciated. * Administrivia/BrevityIsWit. Nobody wants to read a WallOfText. * If you've finished a complete sentence with a full thought, you can complete it and start a new one, and you don't have to keep adding to the sentence and leave it open at the end, because, [[SelfDemonstratingArticle well...]] * Don't [[SquarePegRoundTrope shoehorn]]. If you have a work or trope you want to EntryPimp, make the effort to find pages where it belongs. * Don't respond to an example with another example from a different work. Each example should be under its own work entry. * Don't ask, "Does this belong here?" in the main page. Use your best judgment and be bold. If you really, truly can't decide, ask on the discussion page. * Don't refer to "the page quote" in an example. The page quote can change, and the person changing it probably won't notice that your example now needs to be updated. It's OK to copy the current page quote in an example, if that's the best way to illustrate it, and then your example won't be broken if the page quote changes. * The source of an example should be explicit near the beginning of the example. It does no good to have the source work hidden in a PotHole or buried three lines deep. [[AC:TVTropes lingo]] * The trope description or example you're writing might be someone's first experience of TV Tropes. Favor clear language over catchy jargon and clever {{Pot Hole}}s. * Don't {{pothole}} because you '''can''', much less because you kind of can, barely; do it if (and '''only''' if) it explains something or adds something.'' * People who edit make up just over 1% of all traffic. That is, about 99% of traffic are non-editing readers. Try to keep this in mind when editing. * When linking to pages such as BigNo, FlatWhat or NoJustNoReaction, make sure the trope happens in the scene you're describing, and '''not''' just in your description of said scene (for example, don't link to BigNo because something made ''you'' say "NOOO!", or to FlatWhat when describing something that is weird to you but did not make the InUniverse ''characters'' say "What"). [[AC:Hyperbole In Examples]] * '''''[[AllBlueEntry DON'T]] [[EmphasizeEverything EMPHASIZE EVERYTHING]][[WantonCrueltyToTheCommonComma !!!]] [[BoldInflation WHEN EVERYTHING HAS EMPHASIS,]] [[TheIncredibles NOTHING IS EMPHASIZED!!!]]''''' * Use '''bold''', ''italics'' and CAPS judiciously; especially don't combine them unless you have a very good reason that doesn't involve how impressed you are of the example. People can read an example and understand the weight of it just fine in plain formatting without your "help". * Don't pitch your example. ''Good LORD'', don't pitch your example! Where to begin? Suffice it to say, wading through oh so much masterful emphasis taken UpToEleven and brilliant hyperbole going Beyond The Impossible is the ''single absolute epitome'' of sheer pure annoyance, and gets old ''incredibly'' fast. [[DarthWiki/HowNotToWriteAnExample Yeah.]] THAT IS ALL. * The examples list isn't a competition. Adding [[SugarWiki sugary]] adverbs and {{Pot Hole}}s doesn't make your example "better". * [[NotASubversion "Subversion" is not the cooler version of "aversion"]]. * [[PrecisionFStrike Don't swear just]] [[ClusterFBomb for the sake of it.]] The idea is to keep the pages objective to an extent, and foul language as emphasis betrays that goal. * Don't [[ComplainingAboutPeopleNotLikingTheShow insult the reader]]. Telling a person they "have no soul" or "are inhuman" because they aren't affected by something the way you are serves only to make the example more annoying, not more powerful. * Deconstructions and subversions are not more interesting because they are "brutal" or "cruel". [[AC:Grammar]] * Poor grammar makes for a degraded reading experience; ''horrible'' grammar may get deleted outright. Have a look at TipsOnGrammar to at least get the most common blunders out of the way. * Write out your sentences. Just because there exists an acronym for some commonly used phrase doesn't mean that everyone will recognize what it means. * "Because" is much better than "due to the fact that". * Ending punctuation is a good thing. No, brackets do not count. They're not going to show up on the example page. When in doubt, ''punctuate.'' * "It's" is only short for "it is" or "it has". "Its" means "belonging to it". If you're not sure which one you should use, try replacing the word with "it is" or "it has"; if the sentence no longer makes sense, then you probably want "its". * The past tense of the verb "lead" is "led", not "lead". The noun "lead" is the heavy metal in car batteries, and (mistakenly) in pencils. * "Then" and "than" are not the same word. [[AC:Manual Of Style]] * Both Administrivia/AmericanAndCommonwealthSpellings are fine. * Work titles go in ''italics''. Installment titles go in "quotes". ** For music, album titles go in ''italics''. Song titles go in "quotes". * Need help with English? Consider posting in the [[http://tvtropes.org/pmwiki/posts.php?discussion=b9tcd2k65789p1pglrd92nvr&page=19#472 Help With English Thread]] before editing this page. [[AC: Formatting, Interface, Punctuation, and Structure]] * Forgotten how to do some markup trick? There's a ''Show Markup Help'' button, just a bit above and to the right of the editing box. * The [=-->=] markup is for inserting quotes, not for adding bullet points. * When using the [=-->=] markup, the number of dashes should be ''one more'' than the current number of asterisks in the current bullet point. * If you want to continue text at the current bullet point's level of indentation after a quote or other line breaking feature, you can use the [="::"=] markup to do so; use one more colon (":") than there are asterisks in the current bullet point. * Before you hit "save", proofread your entry and/or hit "preview" at the bottom left of the page. There's no need to rush, and no need to keep [[SerialTweaker re-editing the page]] as you or others find the mistakes after the fact. * "’", "", "�", "?", and generally weird symbols where they do not belong are likely formatting errors caused by incompatible character encoders. Use [[http://www.unicodetools.com/unicode/utf8-to-latin-converter.php this utf8-to-latin-converter]] to fix them. If the characters above show up as normal characters for you, try to avoid using apostrophes, accented characters, or quote marks. * Please stick to a consistent format when adding examples. Most pages use the following format: ::@@[=* WikiWord: Because this example contains Wiki Words.=]@@ :: Some pages use a hyphen, and some put examples in parentheses after the trope name, but ''all'' pages (are supposed to, and should be fixed if they don't) pick one and stick to it. * Remember to close your parentheses. * Italic, bold, and italic and bold coding does not work inside of a PotHole. If you want to bold or italic ''and'' link something, place the coding outside the link, like so: [=''[[PotHole This is a link]]''=] If you want to make a PotHole with emphasis on ''part'' of it, rewrite the pothole. * To make a link out of several words, you don't need to use [=CurlyBrackets=]. Just use CamelCase to make it into a WikiWord. (Unless you want the link to include lowercase words, e.g. ''LordOfTheRings''.) * HTML markups (italics, bold, link, etc.) do not work on the wiki, so don't put them in. * Pages with a lot of long lists of examples in various media, or where one or two media has a lot of examples, should be folderized rather than using small caps headers for the media types. * If an image is interfering with bullet points, move it to the right with [=[[quoteright:]]=]. * In Character pages, rather than putting the actor/voice actor of the character into the tropes list, instead place it in quote form directly under the character's name. * Using a redirect to go to a page that is also a redirect doesn't work. Link directly to where the link should ''really'' go. * Each work's example should have a single bullet all to its own. If you want to start talking about another show, start a new single bullet. ** Second-level bullets are for other examples from the same or related works, not for corrections (which should be made directly to the example), discussion (which should go on the discussion page), or {{Justifying Edit}}s (which should be kept to yourself). * When a trope gets renamed, if you want to go through the pages for works which list that trope and change the links to the new name, great. But if you do so, please put the new trope name in its correct alphabetical position in the list rather than leaving it exactly where it is and just changing the name. ** Or simply removing the line containing the old name regardless of any indented sidenotes it may have. * Learn the Administrivia/TextFormattingRules. Don't use the external link markup for internal links. * If you want to add information to an example, just add the information. That's not what bullet points are for. * Don't write new examples in blank paragraphs that divide the categories. You need to hit the "enter" button on your keyboard before you write a new example. * If a trope you were editing has folders, just ''please'' don't write under the [[/folder]] part when adding a new example. * Don't link to disambig. pages. If you do get linked to a disambig. page, go back to the page it was on, figure out which link it's referring to and fix it. Don't link to just ''BattlestarGalactica'', it should either be Series.BattlestarGalacticaClassic or Series.BattlestarGalacticaReimagined depending on which you are referring to. * Please make sure you are namespacing works. For example [=Series/DoctorWho=] or [=WesternAnimation/MyLittlePonyFriendshipIsMagic=]. It helps with ambiguity as well. [[AC:Best Practices For Page Longevity]] * Refer to things elsewhere on the wiki only if you have to -- even things on the same page. Page quotes, page images, {{Trope Namer}}s, nearby examples and so on are all liable to change, and when they do any writing that refers to them ceases to make sense. * [[Administrivia/ExamplesAreNotRecent Avoid wording that will become dated]]. "The latest" happenings won't be so "recent" in a month or so. If it's necessary to establish a time frame for something, use a name, an episode number or the like. * When discussing a work that has not been released yet, it will save future editors time if you pretend that it already has been released. Just be sure that what you're adding is likely to be in the final release. [[AC:Make Edit Love, Not Edit War]] * Whenever you delete content, explain yourself in the edit history page (via the edit reason) or the discussion page. Conversely, if some piece of content is suddenly gone, first check both these places for an explanation. This prevents {{Edit War}}ring and helps tell good faith editing from vandalism. * If you decide to rewrite a trope description or an example, salvage the good points from the earlier version. There's no reason to just throw away all the work that went into it. * If you have to change the page image or quote, link the old one from the corresponding ImageLinksWiki or QuotesWiki entry, respectively (start one if necessary). There will always be people who liked it, so be nice and save them the searching time. * Trying to edit war with someone with "moderator" next to their name in a page's history is a Very Bad Idea. * [[YMMV.HomePage YMMV]] sections are for describing the different ways to look at a work, not for [[Administrivia/RightingGreatWrongs making rulings about which is the right one]]. If your agenda can't play nice, it's not welcome. * If you must correct something someone has written, do just that, and no more. Write a polite, brief note in the edit reason field, and do ''not'' refer to the whole thing on the page itself. * If an example becomes contentious, direct people to the Discussion page to thrash it out in more detail there. This is the best way to stop a budding EditWar. * If a trope, audience reaction, etc. is put repeatedly on some page and does not fit, you should leave an edit-only visible marker ([=%%=] Markup) to prevent it from being added again. Include an explanation for why that item does not fit. * Don't use the note markup to correct mistakes. Administrivia/RepairDontRespond. [[AC:Interoperability In New Examples and WikiMagic]] * When you mention a work, try to make it a link, at least if you think there's any chance it could ever warrant a page. Even if it doesn't have a page here yet, it may get one later. * When you add trope examples for your favorite work, consider helping the WikiMagic along by adding that work as an example on the trope page. * Adding a page on a work? It's a good idea to add at least a few examples of tropes the work uses for the WikiMagic to act on. * Found a broken link? Do your part and fix it. If it's for a work you're familiar with, make a quick page for WikiMagic; if it's for a trope that's at a different name, either change the link or [[Administrivia/NeedsARedirect create a redirect]]; if it's to a trope that doesn't exist or an external page that can't be found, remove it. * Planning to remove or replace a main page quote or image? Take care -- there may be paragraphs or examples which will need to be fixed, because they rely on the reader seeing the quote or image in question for reference. If you can't be bothered to read the whole article, a CTRL+F for "picture", "image" and "quote" will usually catch everything. [[AC:Accurate Trope Identification]] * Tropes are often similar and sometimes have {{Subtrope}}s that deal with more specific situations. Read the description and see if you're really adding the example in the best place before posting it. * Not every trope name is ExactlyWhatItSaysOnTheTin. Read the actual trope description before you base an example or PotHole on the title. * An example might not actually be an example of the trope it's listed as, but it's probably an example of ''something''. Consider moving it to the right trope rather than deleting it outright. * Remember, these are list of ''tropes''; just because an artist/creator has an article here doesn't make them a trope, and just because they appear in a work doesn't mean they go in the trope list. If it's interesting enough to mention, put it in the main article. * If you commonly add examples of a certain trope, check that trope's main page every now and again, as they can commonly have their definitions changed and/or have usage restrictions placed on them. [[AC:Other]] * Fanon theories are not canon theories, so make sure what you are posting on the Fridge pages are not a conclusion you drew from shipping or other assumptions. * Both good and bad writing inspire more writing like it. Be the change you want to see in TVTropes and fix every bad example you see. If bad style is all over the place, that's no excuse for producing ''more'' of it. * While writing in the main namespace, stay focused on the actual work. [[EpilepticTrees Fan speculation]], AudienceReactions, {{Shipping}}-[[ShippingGoggles induced]] wishful thinking and the like should go in the YMMV tab. * Don't mention other unrelated works in examples. Just because someone has the same name as a character from your favorite show or comic doesn't mean you should say "not to be confused with..."; and just because a particular usage of a trope really reminds you of your favorite show doesn't mean it will be meaningful to anyone else. "As in [show]..." should be avoided. * Use the # sign instead of writing "episode" every single time. It's so much easier. * Don't bring fan arguments into examples. * Don't PotHole things to the page you're already on. No one reading a page needs to be linked to that page; they're already reading it! Adding these potholes just makes people hover over more words for literally no reason. In fact, even [[Administrivia/LinkingToAnArticleWithinTheArticle linking it at all]] is probably bad. * From our experience, RealLife examples are ''especially'' prone to being useless noise and Administrivia/{{natter}} fuel. If there is even the slightest doubt as to its relevance, its coherence, your ability to describe it in a way that adheres to the next section of this page and the RuleOfCautiousEditingJudgement, or anything else about its inclusion, don't put it in. * When writing examples or even tropes, please remember that TV Tropes isn't just for people with your interests. Please do not put walls of text about the physics of a trope or get angry when other people don't also know what color socks Alice was wearing on ''Your Favorite Show''. * If you created a new work page and are changing the page type, do NOT check "does indexing". That was used for ''turning a page into an index only''. * '''The Preview Button is your friend'''. There's no rush to adding to or editing a trope or works page, so make sure everything you wanted to put in actually works the way you want it to. It is also true that WikiMagic dictates whatever mistake you miss will be corrected eventually, but please be courteous. Save yourself (or somebody else) the effort of an extra edit, and try to catch mistakes before you hit that "Save" button. * Try not to edit angry or under the influence. We feel for your bad day, or need to relax, but be careful not to take out your bad day on other people in edit reasons or make edits you may regret (or not even remember making) later. [[AC: Issues of "Political Correctness"]] * TV Tropes is not interested in letting people publicly upload their [[UnfortunateImplications offensive views]] pertaining to race, nationality, gender, or sexual preference. * TV Tropes is also ''not'' interested in playing PoliticalCorrectnessGoneMad. Use the following points as a guide: ** First off, use your common sense. Don't say something you know is offensive. If you have to ask yourself if it is, then so will others, and you're better off keeping it to yourself, or wording it better. ** Don't use slurs unless you are quoting the work, or if is appropriate within the context or the article. Again, [[DepartmentOfRedundancyDepartment use your head here]]. ** If you are speaking about the issue of some form of ValuesDissonance, MoralDissonance, or UnfortunateImplications, be sure to voice your opinion in an intelligent manner. Don't just say "X work is racist/sexist/homophobic." Say something more like "X work has [issue X], which some could find offensive." Even if the work has very blatant examples of UnfortunateImplications (or sometimes, unfortunate ''explications''), clarify what they are rather than simply blurting it out. ** When it comes to presenting topics pertaining to religion, try to write from a secular point of view. Not everyone believes in the same god as you, not everyone believes in god at all. Write from a secular point of view, but not from the perspective that all religion (or the particular one that you don't like) [[OutgrownSuchSillySuperstitions is a silly superstition]] either. ** When addressing issues pertaining to [[HoYay homoerotic]] [[LesYay undertones]], [[BoysLove actual gay romances]], or [[QueerAsTropes issues pertaining to "gayness" as a whole]], err on the side of caution. TV Tropes has a fairly progressive mindset on these subjects, and is not interested in playing HeteronormativeCrusader. This means: *** Do not write from the point of view that anything "gay" is "gross." *** If a work contains same-sex romance, that in and of itself doesn't make it inappropriate for children, unless it involves situations that would also be inappropriate with an opposite-sex couple. It's not GettingCrapPastTheRadar either, unless the radar is known for normally allowing only opposite-sex romance. *** '''Do not''' use the word "gay" or any similar phrase to mean "stupid," "annoying," or anything else inherently negative. *** Again, don't use slurs unless you are quoting a work, and it is appropriate within the context of ''why'' you are quoting it. In this case it's best to clarify that it was done in-universe. ** [[RuleOfThree Use your head]]. * Do NOT use "and how!" In your edits. %% %% Did you read ALL the other suggested tips first? %% !Direct Responses To Installed Tips * The one on "partially subverted" should include a link to NotASubversion. In fact, you should have to confirm that you've read NotASubversion before you can save an edit that uses the term. ** And a Partial Subversion is possible, if only part of the trope is subverted. *** Perhaps. But in practice "partially subverted" almost always means either "used straight, but I like the show and I think [[TropesAreTools tropes are bad]]" or occasionally "{{subverted}}, but I don't like the show and don't think it's clever enough to play with tropes like that."[[note]]I myself am always brought up short whenever I see a certain particularly insipid family sitcom -- not a subgenre that flees insipidity even at its best -- listed as subverting a trope, and I like to think I know better.[[/note]] *** It probably is true that a trope can be partially subverted that way. If so, we can't have the tip directly stating the opposite. How about changing it into one of those that tell what that really means and for people to think before they say that? *** An hour ago I was a firm believer in partial subversion as "complex trope with only some parts subverted". However, [[http://tvtropes.org/pmwiki/posts.php?discussion=13077448910A09200100&page=1 this discussion]] explained it to me. In short, a complex trope rarely has every single part subverted, so almost all subversions would be partial. Thus, the term is redundant and undesirable. I suggest this edit[[note]]The word "quite" was removed because that implies a continuum of subversion rather than a binary distinction, which is the whole point of the Tip. Also the part after "PlayingWithATrope page" was removed for length since it's not strictly unnecessary.[[/note]]: --->A trope can't be "partially subverted" any more than a woman can be "a little bit pregnant." Complex tropes with only one part subverted are still simply "subverted". If it isn't played straight and it isn't subverted, check the PlayingWithATrope page. *** Really, there are two misuses of "partially subverted" there, so it could be split into two Tips. The first one would remain as it is now (or maybe without the "quite" -- see note above). The second would be something like this, although perhaps this misuse is rare enough that it's not worth it: --->Most subversions of a complex trope only involve a couple of its multiple parts. That doesn't make it a "partial subversion". **** Also, "optional" elements (those using "often" or similar words) do not subvert the trope even if that element is subverted, since the situation still fits the trope after the subversion. It's simply an alternate version of the trope. *** In any case, all of these issues should be addressed on NotASubversion or SubvertedTrope. ** Some uses of "partially subverted" seem to be confused with ZigZaggingTrope. Maybe suggest people look at that entry too? *** Perhaps a pothole could be added, but basically that's already found on the PlayingWithATrope page, so probably not worth adding to the Tip length. * Possible amendment to tip #5: "If you're using 4 or more bullet points, take a moment to think about whether what you're typing needs to be there at all." * In response to tip 17: Slap yourself if you write in "That is all." If that actually is all, you don't need to write any more. Most likely, though, there is more and you need to give more detail. Elaborate before [[ThreadMode someone writes in to ask for clarification]]. * Corollary to #3: Administrivia/ExamplesAreNotArguable. If you're using words like, "arguably", "probably", or "to some", it's most likely NotAnExample. Don't add it. * Reformulation of the first uninstalled tip: "Needless to say" nothing. If it was needless to say, you wouldn't be saying it. * Corollaries to #13: If you feel the example If you do post a link to an outside source, describe it if you can. Links come and go very freely, ''especially'' on Website/YouTube, and an entry like "This video" or "This picture" is very likely to become useless. ** Sometimes your example may seem to describe itself, such as listing a celebrity as an example of a physical quality like LanternJawOfJustice. That doesn't mean that everyone has that person's image in mind, so either make sure that their appearance is easy to find, or, better yet, provide an example yourself. * On #6: If your browser has a find feature, use it (ctrl+F or F3 on Firefox, Opera, IE, Chrome). Makes long alphabetized lists way easier to handle. * I saw something on Administrivia/LinkingToAnArticleWithinTheArticle. Should I pothole that? ** You mean the one about putting a PotHole to a page on itself? Yeah, that's closely related. In fact, I just did it myself. ----
to:
! Installed: Don't add or remove things in this section. It doesn't ''do'' the installation, it is just a list of what has been installed. There is a section below this one for ideas and suggestions. [numlist:0] # Remember to use the discussion page for questions. They don't go in the article. Just click that discussion button at the top of every page. # The idea is to make articles in Main look like they were written by the same person. A person with a good sense of humor, who doesn't talk about themself with 'I' or 'this troper', or get in arguments with themself, and who just corrects errors they might have made earlier without drawing attention to them. # Use spoiler tags when you really need them, but it would be even better if you could manage to write your example without bringing up the sensitive information. # If you feel the need to preface your example with "Not really an example but..." you know in your heart it's not an example. Don't add it. # "I can't believe no-one mentioned X yet!" Except, you did just now, so that won't mean anything in a moment. Write your example like it's been there forever and we won't tell a soul it wasn't. # If you're using a third bullet point, take a moment to think about what you're typing and where it should go. # Be sure this example isn't here already. # Want to share your opinion on a work? Try [[TVTropesReviews writing a review]]! # A trope can't be "partially subverted" any more than a woman can be "a little bit pregnant." If it isn't played straight and it isn't quite subverted, check the PlayingWithATrope page to see which one it is. # An [[spoiler:example]] that [[spoiler:is almost completely spoilered]] out doesn't [[spoiler:work very well]] as [[spoiler:an]] example. # Here is an example of word cruft: "Don't forget, actually, as a matter of fact, what really happened is that there's far too much WordCruft in this example." # Did you just catch an error? [[Administrivia/RepairDontRespond Be sure to fix it rather than just pointing it out]]. # We are not interested in whether or not something is or was popular. Whether or not it was liked has nothing to do with tropes. # No matter how popular your favorite show is, there are even more people out there who didn't see it. Listing your example as "Show X! Just... Show X" doesn't work. Always explain ''how'' Show X is an example. # Got a spoiler you want to hide? Take a look at our [[Administrivia/HandlingSpoilers Spoiler Policy]], and consider whether the spoiler is really needed. # Memes don't automatically make things wittier. Resist the urge to shoehorn one in. # More than one page-top quote just gets in the way. Use the Quotes page for the rest. #You are not reminding people of what they know. You are relating something they might not know. Things like "Don't forget", "Remember...", and "Lest we forget" are WordCruft, overused to the point of being irritating. Just tell us the fun stuff to know. # The articles aren't a chatroom. Do not put 'LOL' or emoticons in your edits. # Please read Administrivia/ExampleIndentationInTropeLists as early and as often as possible. [/numlist] !! Ideas/Discussion !!!Tips for suggesting tips: * Installed Tip #6 applies here, too: '''''Be sure that what you are suggesting isn't here already.''''' * Don't just tell people what ''not'' to do. Tell them what they should do instead. * Administrivia/BrevityIsWit. If you've written a paragraph, skip to the '''end''', get to the '''point''', and that summary is your '''tip'''. Check if the rest is covered by an {{Administrivia}} link. !!!Suggested tips to install: [[AC:Consistent Voice]] * If an example is poorly written or overlooks something important, ''[[Administrivia/RepairDontRespond change]]'' the example. Commentary in [[Administrivia/ConversationInTheMainPage sub-bullet points]], [[ParaBombing parentheses]] and [[ThreadMode "however, ..." digressions]] clutters the page. * A paragraph should not start with "actually", "YMMV", "wrong", "incorrect", "you mean", "[[JustifyingEdit to be fair]]", "not really", or anything of the sort. You're writing an article. Articles can provide different viewpoints, but they do not contradict themselves. * No "I." Period. (Full stop) * "You" when referring to the reader -- sure, you're allowed to do that. "You" when referring to the text above you -- Bad Thing! [[AC:Please Elaborate and Be Specific]] * Neither "And ''how''!", "Full stop", or "Nuff said" give enough information to someone who hasn't seen/read a work. They should not be used as complete examples. * Go look it up; we'll still be here when you get back. Better that than writing "happened in ''TheHoneymooners'', or possibly ''Series/{{Fringe}}''." * The description is the place for describing general uses of the trope. Examples that aren't from a specific work ''aren't examples''. Don't just write "all anime ever" -- give us specifics. * Don't add examples of works in which you assume a trope occurs, or expect it to occur; only add an example of the trope actually occurring. * Don't just drop a bare URL for an off-site link into an example, especially as the only thing ''in'' the example. It's better to make it a pothole for some relevant trope page. * Write in a way that will [[FanMyopia make sense to non-fans]]. Describe motives, causes and effects rather than throwing around bare character names and episode numbers. It's good form to PotHole the trope behind the reference (e.g., ''In the climax of the [[ProlongedPrologue Alpha mission]], [[TheLancer Bob]] resorts to using the [[DangerousForbiddenTechnique Omega Spark]]''). * Examples in trope pages should actually mention the ''name of the work'' -- a PotHole isn't enough. If they don't, not only are they less readable -- they won't show up in page search, which will cause repeat examples. * If you're going to claim WordOfGod, back it up, or at least determine where and when it's from. Otherwise people will suspect [[GodNeverSaidThat it originated from some tripod webpage's "rumors" section in 1997]]. You don't have to write up a bibliography, but at least make it possible for readers to verify it for themselves. [[AC: Spoilers]] * Our [[Administrivia/HandlingSpoilers Spoiler Policy]] in a nutshell: Don't bring up spoilers if you don't have to. If you do, make the writing legible to someone who won't highlight the spoilers and make sure they're not [[Administrivia/SelfFulfillingSpoiler given away by their length or context]]. * Do not put links or WikiWords inside spoilers. This will result in people accidentally clicking said link when they select the spoilered text to read it. * [[labelnote:Spoiler--click to reveal]]Yes, we want to reduce abuse of spoiler font. But we don't want it all replaced with the [[Sandbox/NotesAndLabelNotes note markup]], because that doesn't change the problem.[[/labelnote]] * ''Don't'' spoiler tag the name of the work you're spoiling, or the name of the trope that's the spoiler. It doesn't help at all. ** Exception: Character pages. Stating that a trope turns out to apply to ''someone specific'' may be enough of a spoiler to warrant whiting out. Exercise your judgment. * If a work is short enough that you could reasonably fit all of it in an example (for example, jokes), you don't have to use spoilers. After all, if the reader reached the spoilered-out part in your example, it means they reached the point where learning the twist wouldn't count as being spoiled. [[AC:Administrivia and other tips with accompanying pages]] * TropesAreNotGood. Your favorite work isn't going to get any cooler for being mentioned on this page. Don't add it unless it belongs. * If you feel this page needs a sharp snappy explanation, make one yourself at the LaconicWiki. Change the /Main/ part of the URL to /Laconic/ and edit the page. * If you think there's a problem with a trope -- e.g. it's too specific, it's being misunderstood, it's suffering TropeDecay, it's extensively poorly written -- take it to the TropeRepairShop. If you think it absolutely does not belong, bring up the possibility of taking it to the CutList. * Is there something about the way the site is run that bugs you? Bring it up -- politely, and with a minimum of hostility -- in the "Wiki and Forums" section of the TVTropesForum. * Looking for some way to be helpful? Check out NeedsWikiMagicLove and ListOfShowsThatNeedSummary. * Don't use the kind of phrases that are in the Administrivia/PermanentRedLinkClub (IAmNotMakingThisUp, SoYeah, ThisTroper). They've been sent there for a reason. * Follow the RuleOfCautiousEditingJudgment: don't add examples that are going to get people riled up. * Avoid referring to wiki-specific trivia in examples. Nobody cares if an example used to be the TropeNamer or if it was almost the TropeNamer or if there were extensive arguments on TVTropes about it. We already have [[Administrivia/RenamedTropes a page]] detailing trope renamings, so don't feel like you need to memorialize the fallen trope name. * Avoid adding [[YMMV.HomePage subjectives]] on an article's main page. It is now policy that these items go on subpages. * Keep from throwing in links to Administrivia/{{Sinkhole}}s. Typing in a style like BuffySpeak is fine, but it's NotAnExample of the trope. * Administrivia/NoLewdnessNoPrudishness. If a work contains sexuality, state the facts and don't gush; but on the other hand don't whitewash it either. [[AC:Administrivia/HowToWriteAnExample]] * Favor understatement over exaggeration. Do not use either at the expense of clarity. * A PotHole to the extent of "HEY LOOK I MADE A REFERENCE" or "LOLZ I MADE A FUNNY" [[DontExplainTheJoke can really take the fun out of the joke]]. Save them for potential "huh, I don't get it" situations. * However, please remember that English is a lot of tropers' second language, who won't be able to appreciate the word play that seems so obvious to you. A brief explanation, or even a link to the expression you're referring to, is often much appreciated. * Administrivia/BrevityIsWit. Nobody wants to read a WallOfText. * If you've finished a complete sentence with a full thought, you can complete it and start a new one, and you don't have to keep adding to the sentence and leave it open at the end, because, [[SelfDemonstratingArticle well...]] * Don't [[SquarePegRoundTrope shoehorn]]. If you have a work or trope you want to EntryPimp, make the effort to find pages where it belongs. * Don't respond to an example with another example from a different work. Each example should be under its own work entry. * Don't ask, "Does this belong here?" in the main page. Use your best judgment and be bold. If you really, truly can't decide, ask on the discussion page. * Don't refer to "the page quote" in an example. The page quote can change, and the person changing it probably won't notice that your example now needs to be updated. It's OK to copy the current page quote in an example, if that's the best way to illustrate it, and then your example won't be broken if the page quote changes. * The source of an example should be explicit near the beginning of the example. It does no good to have the source work hidden in a PotHole or buried three lines deep. [[AC:TVTropes lingo]] * The trope description or example you're writing might be someone's first experience of TV Tropes. Favor clear language over catchy jargon and clever {{Pot Hole}}s. * Don't {{pothole}} because you '''can''', much less because you kind of can, barely; do it if (and '''only''' if) it explains something or adds something.'' * People who edit make up just over 1% of all traffic. That is, about 99% of traffic are non-editing readers. Try to keep this in mind when editing. * When linking to pages such as BigNo, FlatWhat or NoJustNoReaction, make sure the trope happens in the scene you're describing, and '''not''' just in your description of said scene (for example, don't link to BigNo because something made ''you'' say "NOOO!", or to FlatWhat when describing something that is weird to you but did not make the InUniverse ''characters'' say "What"). [[AC:Hyperbole In Examples]] * '''''[[AllBlueEntry DON'T]] [[EmphasizeEverything EMPHASIZE EVERYTHING]][[WantonCrueltyToTheCommonComma !!!]] [[BoldInflation WHEN EVERYTHING HAS EMPHASIS,]] [[TheIncredibles NOTHING IS EMPHASIZED!!!]]''''' * Use '''bold''', ''italics'' and CAPS judiciously; especially don't combine them unless you have a very good reason that doesn't involve how impressed you are of the example. People can read an example and understand the weight of it just fine in plain formatting without your "help". * Don't pitch your example. ''Good LORD'', don't pitch your example! Where to begin? Suffice it to say, wading through oh so much masterful emphasis taken UpToEleven and brilliant hyperbole going Beyond The Impossible is the ''single absolute epitome'' of sheer pure annoyance, and gets old ''incredibly'' fast. [[DarthWiki/HowNotToWriteAnExample Yeah.]] THAT IS ALL. * The examples list isn't a competition. Adding [[SugarWiki sugary]] adverbs and {{Pot Hole}}s doesn't make your example "better". * [[NotASubversion "Subversion" is not the cooler version of "aversion"]]. * [[PrecisionFStrike Don't swear just]] [[ClusterFBomb for the sake of it.]] The idea is to keep the pages objective to an extent, and foul language as emphasis betrays that goal. * Don't [[ComplainingAboutPeopleNotLikingTheShow insult the reader]]. Telling a person they "have no soul" or "are inhuman" because they aren't affected by something the way you are serves only to make the example more annoying, not more powerful. * Deconstructions and subversions are not more interesting because they are "brutal" or "cruel". [[AC:Grammar]] * Poor grammar makes for a degraded reading experience; ''horrible'' grammar may get deleted outright. Have a look at TipsOnGrammar to at least get the most common blunders out of the way. * Write out your sentences. Just because there exists an acronym for some commonly used phrase doesn't mean that everyone will recognize what it means. * "Because" is much better than "due to the fact that". * Ending punctuation is a good thing. No, brackets do not count. They're not going to show up on the example page. When in doubt, ''punctuate.'' * "It's" is only short for "it is" or "it has". "Its" means "belonging to it". If you're not sure which one you should use, try replacing the word with "it is" or "it has"; if the sentence no longer makes sense, then you probably want "its". * The past tense of the verb "lead" is "led", not "lead". The noun "lead" is the heavy metal in car batteries, and (mistakenly) in pencils. * "Then" and "than" are not the same word. [[AC:Manual Of Style]] * Both Administrivia/AmericanAndCommonwealthSpellings are fine. * Work titles go in ''italics''. Installment titles go in "quotes". ** For music, album titles go in ''italics''. Song titles go in "quotes". * Need help with English? Consider posting in the [[http://tvtropes.org/pmwiki/posts.php?discussion=b9tcd2k65789p1pglrd92nvr&page=19#472 Help With English Thread]] before editing this page. [[AC: Formatting, Interface, Punctuation, and Structure]] * Forgotten how to do some markup trick? There's a ''Show Markup Help'' button, just a bit above and to the right of the editing box. * The [=-->=] markup is for inserting quotes, not for adding bullet points. * When using the [=-->=] markup, the number of dashes should be ''one more'' than the current number of asterisks in the current bullet point. * If you want to continue text at the current bullet point's level of indentation after a quote or other line breaking feature, you can use the [="::"=] markup to do so; use one more colon (":") than there are asterisks in the current bullet point. * Before you hit "save", proofread your entry and/or hit "preview" at the bottom left of the page. There's no need to rush, and no need to keep [[SerialTweaker re-editing the page]] as you or others find the mistakes after the fact. * "’", "", "�", "?", and generally weird symbols where they do not belong are likely formatting errors caused by incompatible character encoders. Use [[http://www.unicodetools.com/unicode/utf8-to-latin-converter.php this utf8-to-latin-converter]] to fix them. If the characters above show up as normal characters for you, try to avoid using apostrophes, accented characters, or quote marks. * Please stick to a consistent format when adding examples. Most pages use the following format: ::@@[=* WikiWord: Because this example contains Wiki Words.=]@@ :: Some pages use a hyphen, and some put examples in parentheses after the trope name, but ''all'' pages (are supposed to, and should be fixed if they don't) pick one and stick to it. * Remember to close your parentheses. * Italic, bold, and italic and bold coding does not work inside of a PotHole. If you want to bold or italic ''and'' link something, place the coding outside the link, like so: [=''[[PotHole This is a link]]''=] If you want to make a PotHole with emphasis on ''part'' of it, rewrite the pothole. * To make a link out of several words, you don't need to use [=CurlyBrackets=]. Just use CamelCase to make it into a WikiWord. (Unless you want the link to include lowercase words, e.g. ''LordOfTheRings''.) * HTML markups (italics, bold, link, etc.) do not work on the wiki, so don't put them in. * Pages with a lot of long lists of examples in various media, or where one or two media has a lot of examples, should be folderized rather than using small caps headers for the media types. * If an image is interfering with bullet points, move it to the right with [=[[quoteright:]]=]. * In Character pages, rather than putting the actor/voice actor of the character into the tropes list, instead place it in quote form directly under the character's name. * Using a redirect to go to a page that is also a redirect doesn't work. Link directly to where the link should ''really'' go. * Each work's example should have a single bullet all to its own. If you want to start talking about another show, start a new single bullet. ** Second-level bullets are for other examples from the same or related works, not for corrections (which should be made directly to the example), discussion (which should go on the discussion page), or {{Justifying Edit}}s (which should be kept to yourself). * When a trope gets renamed, if you want to go through the pages for works which list that trope and change the links to the new name, great. But if you do so, please put the new trope name in its correct alphabetical position in the list rather than leaving it exactly where it is and just changing the name. ** Or simply removing the line containing the old name regardless of any indented sidenotes it may have. * Learn the Administrivia/TextFormattingRules. Don't use the external link markup for internal links. * If you want to add information to an example, just add the information. That's not what bullet points are for. * Don't write new examples in blank paragraphs that divide the categories. You need to hit the "enter" button on your keyboard before you write a new example. * If a trope you were editing has folders, just ''please'' don't write under the [[/folder]] part when adding a new example. * Don't link to disambig. pages. If you do get linked to a disambig. page, go back to the page it was on, figure out which link it's referring to and fix it. Don't link to just ''BattlestarGalactica'', it should either be Series.BattlestarGalacticaClassic or Series.BattlestarGalacticaReimagined depending on which you are referring to. * Please make sure you are namespacing works. For example [=Series/DoctorWho=] or [=WesternAnimation/MyLittlePonyFriendshipIsMagic=]. It helps with ambiguity as well. [[AC:Best Practices For Page Longevity]] * Refer to things elsewhere on the wiki only if you have to -- even things on the same page. Page quotes, page images, {{Trope Namer}}s, nearby examples and so on are all liable to change, and when they do any writing that refers to them ceases to make sense. * [[Administrivia/ExamplesAreNotRecent Avoid wording that will become dated]]. "The latest" happenings won't be so "recent" in a month or so. If it's necessary to establish a time frame for something, use a name, an episode number or the like. * When discussing a work that has not been released yet, it will save future editors time if you pretend that it already has been released. Just be sure that what you're adding is likely to be in the final release. [[AC:Make Edit Love, Not Edit War]] * Whenever you delete content, explain yourself in the edit history page (via the edit reason) or the discussion page. Conversely, if some piece of content is suddenly gone, first check both these places for an explanation. This prevents {{Edit War}}ring and helps tell good faith editing from vandalism. * If you decide to rewrite a trope description or an example, salvage the good points from the earlier version. There's no reason to just throw away all the work that went into it. * If you have to change the page image or quote, link the old one from the corresponding ImageLinksWiki or QuotesWiki entry, respectively (start one if necessary). There will always be people who liked it, so be nice and save them the searching time. * Trying to edit war with someone with "moderator" next to their name in a page's history is a Very Bad Idea. * [[YMMV.HomePage YMMV]] sections are for describing the different ways to look at a work, not for [[Administrivia/RightingGreatWrongs making rulings about which is the right one]]. If your agenda can't play nice, it's not welcome. * If you must correct something someone has written, do just that, and no more. Write a polite, brief note in the edit reason field, and do ''not'' refer to the whole thing on the page itself. * If an example becomes contentious, direct people to the Discussion page to thrash it out in more detail there. This is the best way to stop a budding EditWar. * If a trope, audience reaction, etc. is put repeatedly on some page and does not fit, you should leave an edit-only visible marker ([=%%=] Markup) to prevent it from being added again. Include an explanation for why that item does not fit. * Don't use the note markup to correct mistakes. Administrivia/RepairDontRespond. [[AC:Interoperability In New Examples and WikiMagic]] * When you mention a work, try to make it a link, at least if you think there's any chance it could ever warrant a page. Even if it doesn't have a page here yet, it may get one later. * When you add trope examples for your favorite work, consider helping the WikiMagic along by adding that work as an example on the trope page. * Adding a page on a work? It's a good idea to add at least a few examples of tropes the work uses for the WikiMagic to act on. * Found a broken link? Do your part and fix it. If it's for a work you're familiar with, make a quick page for WikiMagic; if it's for a trope that's at a different name, either change the link or [[Administrivia/NeedsARedirect create a redirect]]; if it's to a trope that doesn't exist or an external page that can't be found, remove it. * Planning to remove or replace a main page quote or image? Take care -- there may be paragraphs or examples which will need to be fixed, because they rely on the reader seeing the quote or image in question for reference. If you can't be bothered to read the whole article, a CTRL+F for "picture", "image" and "quote" will usually catch everything. [[AC:Accurate Trope Identification]] * Tropes are often similar and sometimes have {{Subtrope}}s that deal with more specific situations. Read the description and see if you're really adding the example in the best place before posting it. * Not every trope name is ExactlyWhatItSaysOnTheTin. Read the actual trope description before you base an example or PotHole on the title. * An example might not actually be an example of the trope it's listed as, but it's probably an example of ''something''. Consider moving it to the right trope rather than deleting it outright. * Remember, these are list of ''tropes''; just because an artist/creator has an article here doesn't make them a trope, and just because they appear in a work doesn't mean they go in the trope list. If it's interesting enough to mention, put it in the main article. * If you commonly add examples of a certain trope, check that trope's main page every now and again, as they can commonly have their definitions changed and/or have usage restrictions placed on them. [[AC:Other]] * Fanon theories are not canon theories, so make sure what you are posting on the Fridge pages are not a conclusion you drew from shipping or other assumptions. * Both good and bad writing inspire more writing like it. Be the change you want to see in TVTropes and fix every bad example you see. If bad style is all over the place, that's no excuse for producing ''more'' of it. * While writing in the main namespace, stay focused on the actual work. [[EpilepticTrees Fan speculation]], AudienceReactions, {{Shipping}}-[[ShippingGoggles induced]] wishful thinking and the like should go in the YMMV tab. * Don't mention other unrelated works in examples. Just because someone has the same name as a character from your favorite show or comic doesn't mean you should say "not to be confused with..."; and just because a particular usage of a trope really reminds you of your favorite show doesn't mean it will be meaningful to anyone else. "As in [show]..." should be avoided. * Use the # sign instead of writing "episode" every single time. It's so much easier. * Don't bring fan arguments into examples. * Don't PotHole things to the page you're already on. No one reading a page needs to be linked to that page; they're already reading it! Adding these potholes just makes people hover over more words for literally no reason. In fact, even [[Administrivia/LinkingToAnArticleWithinTheArticle linking it at all]] is probably bad. * From our experience, RealLife examples are ''especially'' prone to being useless noise and Administrivia/{{natter}} fuel. If there is even the slightest doubt as to its relevance, its coherence, your ability to describe it in a way that adheres to the next section of this page and the RuleOfCautiousEditingJudgement, or anything else about its inclusion, don't put it in. * When writing examples or even tropes, please remember that TV Tropes isn't just for people with your interests. Please do not put walls of text about the physics of a trope or get angry when other people don't also know what color socks Alice was wearing on ''Your Favorite Show''. * If you created a new work page and are changing the page type, do NOT check "does indexing". That was used for ''turning a page into an index only''. * '''The Preview Button is your friend'''. There's no rush to adding to or editing a trope or works page, so make sure everything you wanted to put in actually works the way you want it to. It is also true that WikiMagic dictates whatever mistake you miss will be corrected eventually, but please be courteous. Save yourself (or somebody else) the effort of an extra edit, and try to catch mistakes before you hit that "Save" button. * Try not to edit angry or under the influence. We feel for your bad day, or need to relax, but be careful not to take out your bad day on other people in edit reasons or make edits you may regret (or not even remember making) later. [[AC: Issues of "Political Correctness"]] * TV Tropes is not interested in letting people publicly upload their [[UnfortunateImplications offensive views]] pertaining to race, nationality, gender, or sexual preference. * TV Tropes is also ''not'' interested in playing PoliticalCorrectnessGoneMad. Use the following points as a guide: ** First off, use your common sense. Don't say something you know is offensive. If you have to ask yourself if it is, then so will others, and you're better off keeping it to yourself, or wording it better. ** Don't use slurs unless you are quoting the work, or if is appropriate within the context or the article. Again, [[DepartmentOfRedundancyDepartment use your head here]]. ** If you are speaking about the issue of some form of ValuesDissonance, MoralDissonance, or UnfortunateImplications, be sure to voice your opinion in an intelligent manner. Don't just say "X work is racist/sexist/homophobic." Say something more like "X work has [issue X], which some could find offensive." Even if the work has very blatant examples of UnfortunateImplications (or sometimes, unfortunate ''explications''), clarify what they are rather than simply blurting it out. ** When it comes to presenting topics pertaining to religion, try to write from a secular point of view. Not everyone believes in the same god as you, not everyone believes in god at all. Write from a secular point of view, but not from the perspective that all religion (or the particular one that you don't like) [[OutgrownSuchSillySuperstitions is a silly superstition]] either. ** When addressing issues pertaining to [[HoYay homoerotic]] [[LesYay undertones]], [[BoysLove actual gay romances]], or [[QueerAsTropes issues pertaining to "gayness" as a whole]], err on the side of caution. TV Tropes has a fairly progressive mindset on these subjects, and is not interested in playing HeteronormativeCrusader. This means: *** Do not write from the point of view that anything "gay" is "gross." *** If a work contains same-sex romance, that in and of itself doesn't make it inappropriate for children, unless it involves situations that would also be inappropriate with an opposite-sex couple. It's not GettingCrapPastTheRadar either, unless the radar is known for normally allowing only opposite-sex romance. *** '''Do not''' use the word "gay" or any similar phrase to mean "stupid," "annoying," or anything else inherently negative. *** Again, don't use slurs unless you are quoting a work, and it is appropriate within the context of ''why'' you are quoting it. In this case it's best to clarify that it was done in-universe. ** [[RuleOfThree Use your head]]. * Do NOT use "and how!" In your edits. %% %% Did you read ALL the other suggested tips first? %% !Direct Responses To Installed Tips * The one on "partially subverted" should include a link to NotASubversion. In fact, you should have to confirm that you've read NotASubversion before you can save an edit that uses the term. ** And a Partial Subversion is possible, if only part of the trope is subverted. *** Perhaps. But in practice "partially subverted" almost always means either "used straight, but I like the show and I think [[TropesAreTools tropes are bad]]" or occasionally "{{subverted}}, but I don't like the show and don't think it's clever enough to play with tropes like that."[[note]]I myself am always brought up short whenever I see a certain particularly insipid family sitcom -- not a subgenre that flees insipidity even at its best -- listed as subverting a trope, and I like to think I know better.[[/note]] *** It probably is true that a trope can be partially subverted that way. If so, we can't have the tip directly stating the opposite. How about changing it into one of those that tell what that really means and for people to think before they say that? *** An hour ago I was a firm believer in partial subversion as "complex trope with only some parts subverted". However, [[http://tvtropes.org/pmwiki/posts.php?discussion=13077448910A09200100&page=1 this discussion]] explained it to me. In short, a complex trope rarely has every single part subverted, so almost all subversions would be partial. Thus, the term is redundant and undesirable. I suggest this edit[[note]]The word "quite" was removed because that implies a continuum of subversion rather than a binary distinction, which is the whole point of the Tip. Also the part after "PlayingWithATrope page" was removed for length since it's not strictly unnecessary.[[/note]]: --->A trope can't be "partially subverted" any more than a woman can be "a little bit pregnant." Complex tropes with only one part subverted are still simply "subverted". If it isn't played straight and it isn't subverted, check the PlayingWithATrope page. *** Really, there are two misuses of "partially subverted" there, so it could be split into two Tips. The first one would remain as it is now (or maybe without the "quite" -- see note above). The second would be something like this, although perhaps this misuse is rare enough that it's not worth it: --->Most subversions of a complex trope only involve a couple of its multiple parts. That doesn't make it a "partial subversion". **** Also, "optional" elements (those using "often" or similar words) do not subvert the trope even if that element is subverted, since the situation still fits the trope after the subversion. It's simply an alternate version of the trope. *** In any case, all of these issues should be addressed on NotASubversion or SubvertedTrope. ** Some uses of "partially subverted" seem to be confused with ZigZaggingTrope. Maybe suggest people look at that entry too? *** Perhaps a pothole could be added, but basically that's already found on the PlayingWithATrope page, so probably not worth adding to the Tip length. * Possible amendment to tip #5: "If you're using 4 or more bullet points, take a moment to think about whether what you're typing needs to be there at all." * In response to tip 17: Slap yourself if you write in "That is all." If that actually is all, you don't need to write any more. Most likely, though, there is more and you need to give more detail. Elaborate before [[ThreadMode someone writes in to ask for clarification]]. * Corollary to #3: Administrivia/ExamplesAreNotArguable. If you're using words like, "arguably", "probably", or "to some", it's most likely NotAnExample. Don't add it. * Reformulation of the first uninstalled tip: "Needless to say" nothing. If it was needless to say, you wouldn't be saying it. * Corollaries to #13: If you feel the example If you do post a link to an outside source, describe it if you can. Links come and go very freely, ''especially'' on Website/YouTube, and an entry like "This video" or "This picture" is very likely to become useless. ** Sometimes your example may seem to describe itself, such as listing a celebrity as an example of a physical quality like LanternJawOfJustice. That doesn't mean that everyone has that person's image in mind, so either make sure that their appearance is easy to find, or, better yet, provide an example yourself. * On #6: If your browser has a find feature, use it (ctrl+F or F3 on Firefox, Opera, IE, Chrome). Makes long alphabetized lists way easier to handle. * I saw something on Administrivia/LinkingToAnArticleWithinTheArticle. Should I pothole that? ** You mean the one about putting a PotHole to a page on itself? Yeah, that's closely related. In fact, I just did it myself. ----[[redirect:Administrivia/TipsWorksheet]]
13th Mar '14 9:49:05 AM SeptimusHeap
Is there an issue? Send a Message
* Keep from throwing in links to {{Sinkhole}}s. Typing in a style like BuffySpeak is fine, but it's NotAnExample of the trope.
to:
* Keep from throwing in links to {{Sinkhole}}s.Administrivia/{{Sinkhole}}s. Typing in a style like BuffySpeak is fine, but it's NotAnExample of the trope.
16th Jan '14 4:39:53 AM LongLiveHumour
Is there an issue? Send a Message
namespace
* From our experience, RealLife examples are ''especially'' prone to being useless noise and {{natter}} fuel. If there is even the slightest doubt as to its relevance, its coherence, your ability to describe it in a way that adheres to the next section of this page and the RuleOfCautiousEditingJudgement, or anything else about its inclusion, don't put it in.
to:
* From our experience, RealLife examples are ''especially'' prone to being useless noise and {{natter}} Administrivia/{{natter}} fuel. If there is even the slightest doubt as to its relevance, its coherence, your ability to describe it in a way that adheres to the next section of this page and the RuleOfCautiousEditingJudgement, or anything else about its inclusion, don't put it in.
15th Jan '14 8:38:40 AM Someoneman
Is there an issue? Send a Message
* Don't {{pothole}} because you '''can''', much less because you kind of can, barely; do it if (and '''only''' if) it explains something or adds something.
to:
* Don't {{pothole}} because you '''can''', much less because you kind of can, barely; do it if (and '''only''' if) it explains something or adds something.''

to:
* When linking to pages such as BigNo, FlatWhat or NoJustNoReaction, make sure the trope happens in the scene you're describing, and '''not''' just in your description of said scene (for example, don't link to BigNo because something made ''you'' say "NOOO!", or to FlatWhat when describing something that is weird to you but did not make the InUniverse ''characters'' say "What").
30th Dec '13 12:58:18 PM pittsburghmuggle
Is there an issue? Send a Message
to:
* Try not to edit angry or under the influence. We feel for your bad day, or need to relax, but be careful not to take out your bad day on other people in edit reasons or make edits you may regret (or not even remember making) later.
27th Dec '13 4:31:46 PM SciFiMs
Is there an issue? Send a Message
# I can't believe no-one mentioned X yet! Except, you did just now, so that won't mean anything in a moment. Write your example like it's been there forever and we won't tell a soul it wasn't.
to:
# I "I can't believe no-one mentioned X yet! yet!" Except, you did just now, so that won't mean anything in a moment. Write your example like it's been there forever and we won't tell a soul it wasn't.
1st Dec '13 8:20:35 AM LongLiveHumour
Is there an issue? Send a Message
* Avoid referring to wiki-specific trivia in examples. Nobody cares if an example used to be the TropeNamer or if it was almost the TropeNamer or if there were extensive arguments on TVTropes about it. We already have [[RenamedTropes a page]] detailing trope renamings, so don't feel like you need to memorialize the fallen trope name.
to:
* Avoid referring to wiki-specific trivia in examples. Nobody cares if an example used to be the TropeNamer or if it was almost the TropeNamer or if there were extensive arguments on TVTropes about it. We already have [[RenamedTropes [[Administrivia/RenamedTropes a page]] detailing trope renamings, so don't feel like you need to memorialize the fallen trope name.
12th Nov '13 1:18:42 PM Someoneman
Is there an issue? Send a Message
to:
* If a work is short enough that you could reasonably fit all of it in an example (for example, jokes), you don't have to use spoilers. After all, if the reader reached the spoilered-out part in your example, it means they reached the point where learning the twist wouldn't count as being spoiled.
20th Oct '13 4:22:29 AM SeptimusHeap
Is there an issue? Send a Message
Namespace move
* Don't PotHole things to the page you're already on. No one reading a page needs to be linked to that page; they're already reading it! Adding these potholes just makes people hover over more words for literally no reason. In fact, even [[LinkingToAnArticleWithinTheArticle linking it at all]] is probably bad.
to:
* Don't PotHole things to the page you're already on. No one reading a page needs to be linked to that page; they're already reading it! Adding these potholes just makes people hover over more words for literally no reason. In fact, even [[LinkingToAnArticleWithinTheArticle [[Administrivia/LinkingToAnArticleWithinTheArticle linking it at all]] is probably bad.

* I saw something on LinkingToAnArticleWithinTheArticle. Should I pothole that?
to:
* I saw something on LinkingToAnArticleWithinTheArticle.Administrivia/LinkingToAnArticleWithinTheArticle. Should I pothole that?
10th Oct '13 9:23:00 AM Matchstick
Is there an issue? Send a Message
* The description is the place for describing general uses of the trope. Examples that aren't from a specific work ''aren't examples''. Don't just write "all anime ever" - give us specifics.
to:
* The description is the place for describing general uses of the trope. Examples that aren't from a specific work ''aren't examples''. Don't just write "all anime ever" - -- give us specifics.

* Examples in trope pages should actually mention the ''name of the work'' - a PotHole isn't enough. If they don't, not only are they less readable- they won't show up in page search, which will cause repeat examples.
to:
* Examples in trope pages should actually mention the ''name of the work'' - -- a PotHole isn't enough. If they don't, not only are they less readable- readable -- they won't show up in page search, which will cause repeat examples.

* If you think there's a problem with a trope- e.g. it's too specific, it's being misunderstood, it's suffering TropeDecay, it's extensively poorly written - take it to the TropeRepairShop. If you think it absolutely does not belong, bring up the possibility of taking it to the CutList.
to:
* If you think there's a problem with a trope- trope -- e.g. it's too specific, it's being misunderstood, it's suffering TropeDecay, it's extensively poorly written - -- take it to the TropeRepairShop. If you think it absolutely does not belong, bring up the possibility of taking it to the CutList.

* Planning to remove or replace a main page quote or image? Take care - there may be paragraphs or examples which will need to be fixed, because they rely on the reader seeing the quote or image in question for reference. If you can't be bothered to read the whole article, a CTRL+F for "picture", "image" and "quote" will usually catch everything.
to:
* Planning to remove or replace a main page quote or image? Take care - -- there may be paragraphs or examples which will need to be fixed, because they rely on the reader seeing the quote or image in question for reference. If you can't be bothered to read the whole article, a CTRL+F for "picture", "image" and "quote" will usually catch everything.

*** Really, there are two misuses of "partially subverted" there, so it could be split into two Tips. The first one would remain as it is now (or maybe without the "quite" - see note above). The second would be something like this, although perhaps this misuse is rare enough that it's not worth it:
to:
*** Really, there are two misuses of "partially subverted" there, so it could be split into two Tips. The first one would remain as it is now (or maybe without the "quite" - -- see note above). The second would be something like this, although perhaps this misuse is rare enough that it's not worth it:
This list shows the last 10 events of 489. Show all.