Administrivia / Tips Worksheet

This article lists the edit tips that are displayed automatically above the editor while editing. The first section lists those which are currently active, and below that there is also an area to suggest new ones.

Reminder: Don't add or remove things in this section. It doesn't do the installation, it is just a list of what is already installed. There is a section below this one for ideas and suggestions.

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.
1. 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, a person who doesn't talk about themselves with 'I' or 'this troper', or get in arguments with themselves, and instead just corrects errors they might have made earlier without drawing attention to them.
2. 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.
3. 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.
4. "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.
5. If you're using a third bullet point, take a moment to think about what you're typing and where it should go.
6. Be sure this example isn't here already.
7. Want to share your opinion on a work? Try writing a review!
8. A trope can't be "partially subverted" any more than someone can be "partially pregnant". If it isn't played straight and it isn't quite subverted, check the Playing with a Trope page to see which one it is.
9. An example that is almost completely spoilered out doesn't work very well as an example.
10. 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 Word Cruft in this example."
11. Did you just catch an error? Be sure to fix it rather than just pointing it out.
12. 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.
13. 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.
14. Got a spoiler you want to hide? Take a look at our Spoiler Policy, and consider whether the spoiler is really needed.
15. Memes don't automatically make things wittier. Resist the urge to shoehorn one in.
16. More than one page-top quote just gets in the way. Use the Quotes page for the rest.
17. 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 Word Cruft, overused to the point of being irritating. Just tell us the fun stuff to know.
18. The articles aren't a chatroom. Do not put 'LOL' or emoticons in your edits.
19. Please read Example Indentation in Trope Lists as early and as often as possible.
20. If an example is poorly written or overlooks something important, change the example. Commentary in sub-bullet points, parentheses and "however, …" digressions clutters the page.
21. A paragraph should not start with "actually", "YMMV", "wrong", "incorrect", "you mean", "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.
22. "You" when referring to the reader, or the player of a video game — sure, you're allowed to do that. "You" when referring to the text above you — Bad Thing!
23. Go look it up when you want to mention multiple distinct items at once; we'll still be here when you get back. Better that than writing "happened in The Honeymooners, or possibly Fringe".

Suggested tips to install: (should be similar in length and style to existing tips)

Formatting and style:

Grammar

• Poor grammar makes for a degraded reading experience; horrible grammar may get deleted outright. Have a look at Tips on Grammar 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, the part of a pencil that makes marks or a front position.
• "Then" and "than" are not the same word. "Then" is for something relating to a time frame, e.g., "I jousted back then" or "And then he died." "Than" is used for comparisons, such as "Bob has more Steve Carell bobblehead memorabilia than Alice" or "I bet I can eat more churros in one sitting than you!"
• When referring to a character whose gender is canonically unclear (whether due to Character Customization or Ambiguous Gender), the singular "they" is your friend. Constructs like "(s)he" just look weird.

Manual Of Style

• Both American and Commonwealth Spellings are fine. If you're American and come across an entry which has spellings used in the Commonwealth (or vice versa) leave the words which aren't spelled your way alone, as "correcting" them could lead to an Edit War. Remember, when it comes to American versus Commonwealth English, the rule is first come, first served.
• 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 Get Help With English Thread before editing the page.

Formatting, Interface, Punctuation, and Structure

• 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 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 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.
• Remember to close your parentheses.
• Italic, bold, and italic and bold coding does not work inside of a Pot Hole. 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 Pot Hole 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.)
• HTML markups (<i>italics</i>, <b>bold</b>, <a href="some website">link</a>, etc.) do not work on the wiki, so don't put them in.
• 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.
• 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.
• Learn the Text-Formatting Rules. Don't use the external link markup for internal links.
• 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 Justice League, it should either be WesternAnimation.Justice League, Film.Justice League 2017 or one of the other options, 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.
• If you are using a word filter/netnanny, or any program that censors or replaces words, turn it off while editing, as it will possibly accidentally edit the article. Nobody likes seeing words accidentally erased or replaced.
• If you're writing a word that contains CamelCase, but it's not a WikiWord, use the notation [=WikiWord=]. Unless the word you're writing is an initialism, in which case don't use it at all; there's no need for potentially-alienating esoteric jargon.
• Links to hosted images from TinyPic, Photobucket, or unofficial manga scans are not recommended, as images from there are often deleted. Our image uploader or imgur are recommended.

Example Formatting

• Please stick to the following format when adding examples:

* WikiWord: Because this example contains Wiki Words.

• Pages with a lot of long lists of examples in various media, or where one or two media have a lot of examples, should be folderized rather than using small caps headers for the media types.
• 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. See Example Indentation.
• 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.

Spoilers

• Our 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 given away by their length or context.
• Do not put links or Wiki Words inside spoilers. This will result in people accidentally clicking said link when they select the spoilered text to read it.
• ^{Spoiler—click to reveal} Yes, we want to reduce abuse of spoiler font. But we don't want it all replaced with the note markup, because that doesn't change the problem.
• 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.
• 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.

Writing:

Consistent Voice

• Basically, try your best to ensure that the page you're editing looks like it's been written by the same person.
  • So I shouldn't ask 'myself' questions, as if the article were a conversation?
    • Exactly. This is bad and we shouldn't be doing it.

Please Elaborate and Be Specific

• The description is the place for describing the general uses of the trope. Examples that aren't from a specific work aren't examples. Don't just write "all X 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.
• Weblinks Are Not Examples. 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 make sense to non-fans. Describe motives, causes, and effects rather than throwing around bare character names and episode numbers. While it's good form to Pot Hole the trope behind the reference (e.g., In the climax of the Alpha mission, Bob resorts to using the Omega Spark), make sure that it's still understandable without the potholes to someone unfamiliar with the series.
• Examples in trope pages should actually mention the name of the work — a Pot Hole isn't enough. If they don't, not only are they less readable, they won't show up in page search, which can cause repeat examples.
• If you're going to claim Word of God, find and link to where they said that - if you can't, at least determine where and when it's from. Otherwise, people will suspect that it originated from some random webpage's "rumors" section. You don't have to write up a bibliography, but at least make it possible for readers to verify it for themselves.
• Don't just say "In one episode of show X…" — give us the episode title. If you don't remember it, look up an episode guide. If the show doesn't give titles to individual episodes, use the season number or the year the episode was first broadcast.

Administrivia and other tips with accompanying pages

• Tropes Are Tools. Your favorite work isn't going to get any cooler for being mentioned on a trope page, so don't add it unless it belongs.
• If you feel that a page needs a sharp, snappy explanation, make one yourself at the Laconic Wiki. 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 Trope Decay, it's extensively poorly written — take it to the Trope Repair Shop. If you think it absolutely does not belong, then bring up the possibility of taking it to the Cut List.
• Is there something about the way the site is run that bugs you? Bring it up in the "Wiki and Forums" section of the TV Tropes Forum — politely and with a minimum of hostility, please!
• Looking for some way to be helpful? Check out Pages Needing Wiki Magic and List of Shows That Need Summary.
• Don't use phrases that are in the Permanent Red Link Club (I Am Not Making This Up, So Yeah, This Troper). They've been sent there for a reason.
• Follow the Rule of Cautious Editing Judgment: 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 Trope Namer or if it was almost the Trope Namer or if there were extensive arguments on TV Tropes about it. We already have a page detailing trope renamings, so you don't need to memorialize the fallen trope name.
• Avoid adding subjectives on an article's main page unless they happen in-universe. It is now policy that these items go on subpages.
• Keep from throwing in links to Sinkholes. Typing in a style like Buffy Speak is fine, but it's Not an Example of the trope.
• No Lewdness, No Prudishness. If a work contains sexuality, just state the facts. Don't gush about that stuff, but don't pretend it doesn't exist, either.

How To Write An Example

• It's better to understate an example than exaggerate it. Do not use either at the expense of clarity.
• A Pot Hole to the extent of "look, I made a reference" or "Get it? Get it?" can really take the fun out of the joke. Save them for situations where the reader will actually go "huh, I don't get it".
• Please remember that English is a lot of tropers' second language, so they won't be able to appreciate the wordplay that seems so obvious to you. A brief explanation or even a link to the expression you're referring to is much appreciated.
• Brevity Is Wit. Nobody wants to read a Wall of Text if they don't have to.
• 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, well…
• Don't shoehorn. If you have a work or trope you want to Entry Pimp, make the effort to find the proper 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. If necessary, copy the current page quote in an example if that's the best way to illustrate it - that way, 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 Pot Hole or buried three lines deep.

TV Tropes 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 Holes.
• Don't pothole because you know how to, much less because you kind of know how to. Do it if (and only if) it either helps explain something or adds something of substance.
• People who edit only make up around 1% of all traffic. This means that about 99% of traffic is from non-editing readers. Try to keep this in mind when editing.
• When linking to pages such as Big "NO!", Flat "What", or "No. Just… No" Reaction, 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 Flat "What" when describing something that you find weird but did not make anyone In-Universe say "What").

Hyperbole In Examples

• DON'T Emphasize EVERYTHING!!! WHEN EVERYTHING HAS EMPHASIS, NOTHING IS EMPHASIZED!!!
• Use bold, italics, and ESPECIALLY CAPS sparingly - and this includes exclamation points! Especially multiple ones!!!! Additionally, don't combine them unless you have a very good reason (and how impressed you are with an example isn't a good reason). People can read an example and understand the weight of it just fine in plain formatting.
• 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 up to eleven and brilliant hyperbole going Beyond the Impossible is the single absolute epitome of sheer pure annoyance, and gets old incredibly fast. Yeah. THAT IS ALL.
• The examples list isn't a competition. Adding sugary adverbs and Pot Holes doesn't automatically make your example "better".
• Subversions are specifically for a trope that's clearly set up to happen but then doesn't. It is not the cooler term for "aversion".
• Don't swear just for the sake of it. The idea is to keep all of the pages objective (to an extent), and foul language solely as emphasis betrays that goal.
• Don't insult the reader. Telling a person they "have no soul" or "are inhuman" because they aren't as affected by something as you only serves to make the example more annoying, not more powerful.
• Deconstructions and subversions are not automatically more interesting because they are "brutal" or "cruel."
• We know you want to put your "Ew" for Nausea Fuel, "Aww" or "D'aww" for Heartwarming Moments, "*shudder(s)*" for Nightmare Fuel scenes, and "*sob*" or "*sniff*" for Tear Jerkers, but remember that not everybody agrees with you.
• Sometimes, a troper might feel the need to address a character/person/work/company. Seriously, troper, why do you feel you need to do so? Don't you know that they're likely not going to read what you're writing?

Best Practices For Page Longevity

• Refer to things elsewhere on the wiki only if you have to — even things on the same page. Things like page quotes, page images, Trope Namers, and nearby examples are all liable to change. If/when they do change, any writing that refers to them will cease to make sense.
• Avoid wording that will become dated. The "latest" happenings won't be as "recent" in a month or so. If it's necessary to establish a time frame for something, use a name, an episode number, or something that clearly shows when something was made.
• 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 make sure that what you're adding is likely to be in the final release. For instance, if something has been confirmed to be in the work, just say it's in the work instead of "it's confirmed that…".
• When making a Wild Mass Guess about something that might happen in a future entry in an ongoing series, don't guess that it will happen in the very next entry unless you legitimately think it's going to be that specific one. Otherwise, even if you meant that it'd just happen sometime in the future, people will call it Jossed if it doesn't happen in that specific entry.

Make Edit Love, Not Edit War

• Whenever you delete content, explain yourself in either the edit reason box or the discussion page. Conversely, if some piece of content is suddenly gone, check both the edit history and the discussion page for an explanation. This helps avoid Edit Wars and can make good faith editing easier to tell apart from vandalism.
• If you decide to rewrite a trope description or an example for a trope, salvage the good points from the earlier version. There's no reason to throw away all the work that went into it.
• If you have to change the page image or quote, link to the old one from the corresponding Image Links Wiki or Quotes Wiki entry (and start one if necessary). There will always be people who liked it, so be nice and save them the searching time.
• Trying to revert an edit made by someone that has "moderator" next to their name in a page's history is a bad idea - they likely made a change for a reason. Unless you have a very good reason for reverting their edit, you're likely making things worse.
• YMMV sections are for describing the different ways to look at a work, not for making rulings about which ones are right and which ones are wrong. 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 Edit War.
• If a trope, audience reaction, etc. is repeatedly added and/or removed on a page, you should leave an edit-only visible marker (%% Markup) to prevent it from being added or removed again. Remember to include an explanation for why that item does or does not fit.
• Don't use the note markup to correct mistakes, fix the mistake itself. Remember, Repair, Don't Respond.
• Editing just to change spelling or add in the Oxford Comma is fine if it's done for consistency. Editing grammar/punctuation that's an actual, accepted way of writing, or changing it simply "because it's wrong" (when it's clearly not) is not fine. And neither is "correcting" Commonwealth English if you're American, or vice versa.

Interoperability In New Examples and Wiki Magic

• When you mention a work, try to make it a link if you think there's any chance it could have a page. Even if it doesn't have one yet, it may get one later.
• When you add trope examples for your favorite work, consider helping the Wiki Magic 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 Wiki Magic 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 it (provided it has at least three examples). If it's for a trope that's at a different name, either change the link or create a redirect. If it's for anything else, remove it.
• Planning to remove or replace a main page quote or image? See if there are any paragraphs or examples that need to be fixed because they rely on the reader seeing the quote or image in question for reference. If you don't want to read the whole article, a CTRL+F for "picture", "image", and/or "quote" will usually catch everything.

Accurate Trope Identification

• Tropes are often similar and sometimes have Subtropes 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 Exactly What It Says on the Tin. Read the actual trope description before you base an example or Pot Hole on the title alone.
• An example might not actually be an example of the trope it's listed as, but it's probably an example of something. Try to find the right trope and move it there before deleting it outright.
• Remember, these are lists of tropes. Artists, Creators, and/or Useful Notes aren't tropes and shouldn't be treated as a trope or listed in the trope list. If it's interesting enough to mention, put it in the main article.
• Tropes can have their definitions changed and/or usage restrictions placed on them, so make sure you're checking up on the trope pages every now and then if you frequently add a particular trope.

Other

• Fanon theories are not canon theories, so make sure that what you are posting on any of the Fridge pages is not based solely on assumptions.
• Both good and bad writing inspire more writing like it. Be the change you want to see in TV Tropes and fix every bad example you see. Just because bad writing's all over the place doesn't mean you have to produce more of it.
• When writing in a work's main namespace, stay focused on the actual work. Fan speculation, Audience Reactions, Shipping and the like should remain in the work's YMMV tab.
• Don't mention other, unrelated works in examples for no reason. Someone having the same name as a character from your favorite show or the usage of a trope reminding you of your favorite show doesn't mean that a reference will mean anything to anyone else. Lines like "As in [show]…" or "not to be confused with…" should be avoided unless it is legitimately possible to mix the two works up.
• Using the # sign is much easier than writing "episode" every single time. Try it out!
• Don't bring fan arguments into examples that aren't about fanon.
• Don't Pot Hole 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! In fact, linking to it at all is considered bad practice.
• Real Life examples are especially prone to being useless noise and natter fuel. If there is even the slightest doubt to its relevance, coherence, ability to be described in a way that adheres to the Rule of Cautious Editing Judgment, or anything else about it, then it's best to leave it out.
• When writing examples or even tropes, remember that TV Tropes isn't just for people with your interests. 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 create a new work page and are changing the page type, do not check "does indexing". That is only used for turning a page into an index.
• When indexing a work page, make sure to create the work page before adding it to the index page. The index won't update if you add a page that doesn't exist yet.
• 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 works the way you want it to. While it's true that Wiki Magic dictates whatever mistake you miss will be corrected eventually, please be courteous and save yourself (or somebody else) the effort of an extra edit.
• Try not to edit when you are 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.
• Page quotes should more-or-less work out of context. If a quote needs more than a couple of words explaining the setting, it's probably bad. If the explanation is longer than the quote itself, it's definitely bad. Put it in the Examples section where it belongs. Alternatively, consider if the explanation is even necessary; if the quote is snappy and can illustrate the trope without the full context, there's nothing wrong with leaving details out.
• Emphasis cruft. Just… emphasis cruft. Padding Zero Context Examples with dull repetition since forever, and how! Super annoying and PRLC'd, so don't do it. Just don't. That's all.
• You don't need to say "Oh, and (insert X here)" unless you want to be informal. Oh, and you can easily describe what you want to without it.
• Inviting people to guess something can be unnecessary, so try to guess if you should do it or not (hint - you shouldn't).
• Quotes subpages are fun places to be, but they can risk becoming overstuffed. If the page is getting long, have a think about whether your example will add something to the page or will pad it with more of the same. It's probably welcome on the Main page either way.
• Even if you are American, try to avoid Americentrism in your entries. Instead, unless you are writing an entry for a work which is set in the USA, or a page which has strong cultural ties to that country, try to keep the writing culturally neutral. The same (with the appropriate nationality substituted) applies to anyone from other countries.

Issues of "Political Correctness"

• TV Tropes is not interested in letting people publicly upload their offensive views pertaining to race, nationality, gender, gender identity, disabilities, and/or sexual orientation.
• While TV Tropes is intolerant of any bigotry on the site, we are also not interested in leaning into Political Overcorrectness. This means don't remove anything that might be offensive towards a certain group, especially if that group has already stated that they don't mind it.
• Use your common sense; don't say something that you know is offensive. If you have to ask yourself if what you're saying is offensive, then others will also question it, and you're better off either keeping it to yourself or wording it better.
• Don't use slurs unless you are directly quoting a work, or if is appropriate within the context of the article. If you are quoting or paraphrasing a work, please clarify that the slurs are used in-universe.
• If you are speaking about the issue of some form of Values Dissonance or Unfortunate Implications, be sure to voice your opinion in an intelligent manner, and describe what in the work could be seen as offensive - even if the work's blatantly offensive, there are people out there who might not have heard of it.
• When it comes to presenting topics pertaining to religion, try to write from a secular point of view, as not everyone believes in the same god as you (or in any god at all). Additionally, don't write from the perspective that all religions (or any specific ones) are silly superstitions.
• TV Tropes has a fairly progressive mindset on issues pertaining to homosexuality. Don't write from the mindset that anything "gay" is "gross", don't use "gay" to mean anything inherently negative, and don't treat same-sex romance as something that's automatically inappropriate for children or a case of Getting Crap Past the Radar.^note  The only exceptions are if it involves situations that would also be inappropriate with an opposite-sex couple, or the radar is known for only allowing opposite-sex romance.
• When writing about a Transgender creator, use their current name and pronouns even if you're talking about them pre-transition. If they have any works for which they were credited under their former name, that name may be included in a labelnote, as in "Alice Smith ^note credited as Bob Smith prior to transitioning." This helps to keep the information on the wiki accurate while avoiding openly deadnaming trans individuals.

---