Follow TV Tropes

Following

History Administrivia / TLPGuidelines

Go To


Added DiffLines:

* Similar to not rogue or stealth launching a trope, it's also frowned upon to rogue-discard or stealth-discard a draft, especially if there's still ongoing discussion on the draft itself and/or the sponsor is actively working on it. Regardless of how many bombs a draft has, discarding it before it finishes discussion is simply ''rude''. Another problem is people not adding a reason when they discard something, which can lead to confusion and a lack of transparency, so please try and explain your reasoning before you hit that button. Discarding issues are not as severe as launching issues, as the drafts can more easily be restored, but too many instances of ignoring this guideline can earn you a suspension.


* Administrivia/AGuideToEasyLaunchingOfYourTLP, for more information on the launching process.

Added DiffLines:

Don't use the TLP to propose new Administrivia pages. If you believe there is the need of another one, ask the mods, or take it to the [[https://tvtropes.org/pmwiki/conversations.php?topic=0000000000000000000000f3 Wiki Talk]].


"TropeLaunchPad", usually abbreviated to [=TLP=], and formerly known as "You know, that thing where..." or '''[=YKTTW=]''', is used for spit-balling new tropes.

[=TLP=] is a tool that is here to help make a good article. It will help you catch some errors before they are made, give you a chance to get some wider perspective that may not have occurred to you, determine [[Administrivia/DoWeHaveThisOne if your suggestion already has a page here]], and get some good examples and perhaps a catchy name for the trope. That's it!

Keep in mind that Works pages, for a new show, film, anime, comic, what have you, don't need to go through [=TLP=]. [[Administrivia/WorksPagesAreAFreeLaunch Just go ahead and make those]] (unless you need the extra help).

to:

"TropeLaunchPad", usually abbreviated to [=TLP=], TLP, and formerly known as "You know, that thing where..." or '''[=YKTTW=]''', is used for spit-balling new tropes.

[=TLP=] TLP is a tool that is here to help make a good article. It will help you catch some errors before they are made, give you a chance to get some at a wider perspective that may not have occurred to you, perspective, determine [[Administrivia/DoWeHaveThisOne if your suggestion already has a page here]], and if all goes well get some good examples and perhaps a catchy name for the trope. That's it!

Keep in mind that Works pages, for a new show, film, anime, comic, what have you, don't need to go through [=TLP=]. TLP. [[Administrivia/WorksPagesAreAFreeLaunch Just go ahead and make those]] (unless those]], but feel free to use the TLP if you think you need the extra help).
help.



There are three main stages to the [=TLP=] process, each of which is explained in more depth below:
# Creating the [=TLP=], in which a single contributor proposes a new trope with a brief writeup and invites the comments of everyone else.
# The reply stage, where the various tropers add suggestions and examples, and discuss the possible page with the creator.
# Finally, the ascendance of the draft from the [=TLP=] system. There are two options for how this is done.

to:

There are three main stages to the [=TLP=] TLP process, each of which is explained in more depth below:
# Creating the [=TLP=], TLP, in which a single contributor proposes a new trope with a brief writeup and invites the comments of everyone else.
# The reply stage, where the various tropers add suggestions and examples, and discuss the possible page breadth and of the page-to-be with the creator.
# Finally, the ascendance progression of the draft from the [=TLP=] TLP system. There are two options for how this is done.paths possible.



** The Discard, used to terminate a [=TLP=] that was determined to not be viable.

to:

** The Discard, used to terminate a [=TLP=] TLP that was determined to not be viable.



!!Some general notes on how [=TLP=] works:
* The tick marks indicate new posts. The word "new" next to a tick indicates a new [=TLP=].
* If bizarre things start happening, don't worry. When you reload the page they ''usually'' work themselves out. Be patient and keep trying.
* If a post has more than one reply, but the replies don't show up, click the "show replies" button until they show up.
* If you put a link to a picture in your post, it might not be rendered. Use small images or text links to the picture.
* Like everything else on the wiki, you can edit anything you see, including the [=TLP=] and the comments on it. However, the name next to the text displayed will be that of the last person to edit it. It's bad form to edit over someone else's comments, so don't do it unless you feel you absolutely have to (like to fix a markup that is breaking the discussion).
* As with everywhere else, please try to put a bit of work into your [=TLP=]. Good spelling and grammar aren't just for the final writeup; they help people understand you and make them more likely to care about what you have to say. A poorly written [=TLP=] is likely to get fewer comments, which means it'll get fewer examples, will get less contribution, and is more likely to end up on the cut list. The same goes for comments; if your comment makes no sense, don't expect to see your example in the final write-up.
* Do ''not'' put a picture in a reply. It will just screw up the formatting. The original post will handle them fine, but replies should just link to pictures.

to:

!!Some general notes on how [=TLP=] TLP works:
* The tick marks indicate new posts. posts are highlighted in a brighter, bolder blue than the other drafts.
*
The word "new" next code around the TLP doesn't always do what it's supposed to a tick indicates a new [=TLP=].
*
do. If bizarre things start happening, happen,[[note]]One you'll want to be on guard for is the save button of the draft being hidden or not loading at all.[[/note]] don't worry. When you reload the page they ''usually'' work themselves out. Be patient and keep trying.
* If Proposed pages are judged by a post has system of (green) hats and (red) bombs. Hats are in support of the page being launched as-is, and bombs represent a more than one reply, but the replies don't show up, click the "show replies" button until they show up.
* If you put
negative judgement, such as that a link to a picture in your post, draft shouldn't launch, or that it might not should be rendered. Use small images or text links to the picture.
discarded.
* Like everything else on the wiki, you can edit anything you see, including the [=TLP=] and the comments on it. However, the name next to the text displayed will be that of the last person to edit TLP draft, no matter who sponsors it. It's bad form proper to leave a post explaining what you did if you edit over someone else's comments, draft, however, so don't do it unless you feel you absolutely have to (like to fix a markup that is breaking the discussion).
sponsor knows what they are working with.
* As with everywhere everything else, please try to put a bit of work into your [=TLP=].TLP. Good spelling and grammar aren't just for the final writeup; they help people understand you and make them more likely to care about what you have to say. A poorly written [=TLP=] TLP is likely to get fewer comments, which means it'll get fewer examples, will get less contribution, and is more likely to end up on the cut list. The same goes for comments; if your comment makes no sense, don't expect to see your example in the final write-up.
* Do ''not'' put Take note that while unusual characters can be displayed no problem on regular pages, they cannot be added to [=TLPs=]. Instead, they'll be displayed by a picture in a reply. It line of regular characters that will just screw up get longer and longer every time you save. So for the formatting. The original post will handle duration of the TLP, avoid unusual characters and add them fine, but replies should just link to pictures.
if need be once the trope is launched.



!!Creating a [=TLP=]:

The first stage of the process: click the "Launch a New Trope" button, then enter your working title, a laconic one-sentence description of your trope[[note]]Referred to as the Trope Laconic Title. It's kind of a [[NonIndicativeName non-indicative term]] right now, which tends to lead a lot of clueless newbies into typing in a title where the laconic description would normally go.[[/note]], and your writeup in the text boxes that will appear. Once you're done, click the "send" button.

When creating a new [=TLP=], you should aim to give a good idea of the trope that everyone can understand, preferably with a few examples of your own to make the concept clear. Try and make sure it's something anyone can comment on and understand. Nothing is completely Administrivia/SelfExplanatory. Try to explain it without resorting to "Like [some other trope] except for...". The description of one trope should not require detailed knowledge of half-a-dozen other tropes to understand. Explain how it relates to other tropes, though.

to:

!!Creating a [=TLP=]:

TLP:

The first stage of the process: click the "Launch a New Trope" button, button then enter your three things.
* Your
working title, title: Ostensibly the title you'll want to launch the trope under, but it may also be descriptive while you ask around for a good title. You can change the working title as often as you want, which means you can also use it to leave messages such as when you're planning to launch and requests for more examples.
* A
laconic one-sentence description of your trope[[note]]Referred trope, referred to as the Trope Laconic Title. It's kind of a [[NonIndicativeName non-indicative term]] right now, which tends to lead a lot of clueless newbies into typing in a title where the laconic description would normally go.[[/note]], and your writeup Note that you can submit a trope without adding a description, ''but'' this means that no edits that you make will be saved. You can always add the laconic title after the fact in the box beneath the title box.
* Your writeup: This should be prepared in a text editor, from which you copy&paste it into
the text boxes box that will appear. appear.
Once you're done, click the "send" button.

When creating a new [=TLP=], TLP, you should aim to give a good idea of the trope that everyone can understand, preferably with a few examples of your own to make demonstrate the concept clear.concept. Try and make sure it's something anyone can comment on and understand. Nothing is completely Administrivia/SelfExplanatory. Try to explain Explain it without resorting to "Like [some other trope] except for...". The description of one trope should not require detailed knowledge of half-a-dozen other tropes to understand. Explain how it relates to other tropes, though.



* Before creating your [=TLP=], try to make sure we don't already have it. See Administrivia/FindingATrope for more help with this. If you think we might have the trope but still can't find it, just put Administrivia/DoWeHaveThisOne in your new [=TLP=] -- someone will probably call you out on it.

to:

* Before creating your [=TLP=], try to make sure TLP, investigate if we don't already have it. See Administrivia/FindingATrope for more help with this. If you think we might have the trope but still can't find it, just put Administrivia/DoWeHaveThisOne in your new [=TLP=] TLP -- someone will probably call you out on it.



* We have a number of other useful StockPhrases to use on [=TLP=]. See PredefinedMessages.
* Try as hard as you can to avoid AudienceReactions and other [[YMMV.HomePage YMMV]] items. More often than not, they just lead to arguments.
* If your trope slides down the page without getting any replies, you might want to give it a Administrivia/TLPBump. There are two ways of doing this: Edit the entry (click on the little pencil icon at the top of the entry, whose location tends to vary depending on which web browser you use) and enter "save changes" without making any changes, which will automatically bump the [=TLP=] to the top of the stack without adding new replies. Or just add a new reply. Don't overdo the bumping, especially not content-less bumping, however!
* If you find that we already have your trope, or if you reconsider the [=TLP=], discard it by launching it (see below) to Administrivia/DiscardedTLP. This is usually, but not always, left to the person who created the trope to do.

to:

* We have a number of other useful StockPhrases to use on [=TLP=].TLP. See PredefinedMessages.
* Try as hard as you can to avoid Avoid AudienceReactions and other [[YMMV.HomePage YMMV]] items. More often than not, they just lead to arguments.
* If your trope slides down the page without getting any replies, you might want to give it a Administrivia/TLPBump. There are two ways of doing this: Edit the entry (click on the little pencil icon at the top of the entry, whose location tends to vary depending on which web browser you use) and enter "save changes" without making any changes, which will automatically bump the [=TLP=] TLP to the top of the stack without adding new replies. Or just add a new reply. Don't overdo the bumping, especially not content-less bumping, however!
* If you find that we already have your trope, or if you reconsider the [=TLP=], TLP, discard it by launching it (see below) to Administrivia/DiscardedTLP. This is usually, but not always, left to the person who created the trope to do.



* A page is easier to read if the examples are sorted by category, so create a folder for each medium which examples of the trope fall into; that way, as the page grows it'll remain organised. Don't make empty folders or headings, though, since they just waste space.






Hit the "Show Drafts" button on a given [=TLP=][[note]](protip: you can open a [=TLP=] in a new browser tab if you want)[[/note]] and scroll to the bottom. Click "Reply". Enter what you have to say into the box, then press "Send". When a new reply is entered, the [=TLP=] will be bumped to the top of the page.

Replying to a [=TLP=] is a form of WikiMagic: it's how a page gains examples, content and sometimes a better name. Browsing [=TLP=] and adding your comments is how a [=TLP=] becomes a trope. When the [=TLP=] is launched, it's the launcher's responsibility to read through the comments and add the examples to the page. There is a tool on the Discussion created when the trope is launched to help with this, "Show All Markup" will provide a copy of the [=TLP=] and replies that can be copy-n-pasted.

* When giving an example from an obscure source, mention the type of media it is from. Most page launches are structured with categories for the examples rather than dumping all the items in a list, meaning the person launching has to know where the examples are from in order to put them in the right place in the writeup. It's not necessary with more well-known examples, and the example itself often makes it clear, but if the source is more obscure, it again helps the launcher to add "(anime example)" or something. Err on the side of caution.
* Style your examples so that the launcher doesn't have to work hard to put them in the article. The very best way to add an example is to format it in the style of an example as it would be on the final page, complete with markup. It saves the launcher time, as they can just copy and paste the code, and it will be your own contribution ending up in the page rather than being rewritten.
* Just as nothing is completely Administrivia/SelfExplanatory, no example is so well-known that no description is needed. An example that consists entirely of "Series... Just, Series." or "One Word: Series" isn't very informative or interesting.

to:

Hit Click the "Show Drafts" button link on a any given [=TLP=][[note]](protip: TLP, [[note]](protip: you can open a [=TLP=] TLP in a new browser tab if you want)[[/note]] and scroll to the bottom. Click "Reply". Enter what you have to say into the box, then press "Send". When a new reply is entered, the [=TLP=] TLP will be bumped to the top of the page.

Replying to a [=TLP=] TLP is a form of WikiMagic: it's how a page gains examples, content and sometimes a better name. Browsing [=TLP=] TLP and adding your comments is how a [=TLP=] TLP becomes a trope. When the [=TLP=] TLP is launched, it's the launcher's responsibility to read through the comments and add the examples to the page. There is a tool on the Discussion created when the trope is launched to help with this, "Show All Markup" will provide a copy of the [=TLP=] TLP and replies that can be copy-n-pasted.

* When giving an example from an obscure source, example, mention the type of media it is from. Most page launches are structured with categories for the examples rather than dumping all the items in a list, meaning the person launching has to know where the examples are from in order to put them in the right place in the writeup. It's not necessary with more well-known examples, and the The example itself often makes it clear, but if the source is more obscure, it again helps the launcher to add "(anime example)" or something. Err on the side of caution.
* Style your examples so that the launcher doesn't have to work hard to put them in the article. The very best way to add an example is to format it in the style of an example as it would be on the final page, complete with markup. It saves the launcher time, as they can just copy and paste the code, code into the draft, and it will be your own contribution ending up in the page rather than being rewritten.
* Just as nothing is completely Administrivia/SelfExplanatory, no example is so well-known that no description is needed. That's called a Administrivia/ZeroContextExample. An example that consists entirely of "Series... Just, Series." or "One Word: Series" isn't very should explain ''how'' it's an example; otherwise, it's neither informative or interesting.nor verifiable.



* However, if you don't think the proposed is a trope, is too subjective, should be [[Administrivia/LumperVsSplitter lumped]] with something else, or otherwise doesn't deserve to be a page, ''go ahead and say so''. Far better to nip a bad page in the bud than have to deal with a site cluttered up with Administrivia/TheSameButMore articles and subjective Administrivia/{{natter}}. If the original poster disagrees, that person will state his/her case. There can be an open discussion about it; use constructive criticism as much as possible, since that helps both the page and its contributors improve.
* When proposing that an existing trope is the same or in some other way related, do not post only the trope name, and especially not in '''bold''' text. That is a Administrivia/ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.


to:

* However, if you don't think the proposed is a trope, is too subjective, should be [[Administrivia/LumperVsSplitter lumped]] with something else, or otherwise doesn't deserve to be a page, ''go ahead and say so''. Far better to nip a bad page in the bud than have to deal with a site cluttered up with Administrivia/TheSameButMore articles and subjective Administrivia/{{natter}}. If the original poster disagrees, that person will state his/her case. There can be an open discussion about it; use constructive criticism as much as possible, since that helps both the page and its contributors improve.
* Going along with the above, when adding a hat or bomb, it's helpful to explain ''why'' you felt the draft deserved it. Keep in mind that hats are intended to be "launch now" votes but are, in practice, given for a variety of reasons, and bombs are typically used as meaning both "discard" and "needs work before launching", so hats and bombs with no explanation can be quite confusing and stressful for a sponsor. Please let them know if there's any problems they need to work on, or if you think the draft is genuinely ready to be launched. It helps a lot, and is just more polite than refusing to discuss.
* When proposing that an existing trope is the same or in some other way related, do not post only the trope name, and especially not in '''bold''' text. That is a Administrivia/ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] TLP and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.

one.



!!What a [=TLP=] should contain at the end:

To determine if [=TLP=] is a trope, try to eventually include as much as possible described below in the header before examples:

to:

!!What a [=TLP=] should contain at the end:

!!Ways to strengthen your TLP:

To determine if [=TLP=] your TLP is a trope, try to eventually include as much as possible described below in the header before examples:



* Current trope life cycle status: How seriously is the trope taken nowadays? It can be still a trope taken seriously; it can be a DiscreditedTrope when a trope is considered a cliché; it can be a DeadHorseTrope where parodies and {{Lampshade Hanging}}s far outnumber straight examples; it can be an UndeadHorseTrope when, despite being mocked a lot, it's still used straight; it can be a ForgottenTrope when it's not used at all; and it can be a DeadUnicornTrope when the trope was rarely, if ever used straight at all.

to:

* Current trope life cycle status: How seriously is the trope taken nowadays? It can be still a trope taken seriously; it can be a DiscreditedTrope when a trope is considered a cliché; it can be a DeadHorseTrope where parodies and {{Lampshade Hanging}}s far outnumber straight examples; it can be an UndeadHorseTrope when, despite being mocked a lot, it's still used straight; it can be a ForgottenTrope when it's not used at all; and it can be a DeadUnicornTrope when the trope was rarely, if ever used straight at all.all.

If you're sponsoring a draft and need help with something that would otherwise make the draft unlaunchable, you should let people know you need the help. Some ways of doing this are to make a note in the title, laconic, or top of the draft itself, [[note]]these can be formatted in parenthesis or brackets labeled as notes, if you want to ensure better visibility[[/note]] posting about it in the comments, or even making a post [[https://tvtropes.org/pmwiki/posts.php?discussion=mrrv0lfphb29fvme6ofumrj0&page=1 on the TLP workstation thread]]. Otherwise, a miscommunication may lead people to believe you aren't aware of or don't intend to fix the issues on the draft, so remember to speak up if your draft needs help you can't personally provide for it.



Go to the [=TLP=] and click "show draft". Scroll down to the bottom of the page and click the "Launch" button. (This will not appear until the [=TLP=] is [[Administrivia/ThreeRulesOfThree three days old]].) Add the title, and click "Launch" again. This will launch the [=TLP=] to the wiki page put in the title, and a link to the [=TLP=] discussion will automatically be added to that page's Discussion. Go to the page itself, click "Edit page", add the writeup and examples, and link them up.

to:

Go to the [=TLP=] and click "show draft". Scroll down to the bottom of the page TLP and click the "Launch" button. (This will not appear until the [=TLP=] it is [[Administrivia/ThreeRulesOfThree three days old]].old]] and has five hats.) Add the title, and click "Launch" again. This will launch the [=TLP=] TLP to the wiki page put in the title, and a link to the [=TLP=] TLP discussion will automatically be added to that page's Discussion. Go to the page itself, click "Edit page", add the writeup and examples, and link them up.
Discussion.



You can write all the markup yourself, or copy the TropeEntryTemplate and edit the content. Copying and pasting the entries directly from the [=TLP=] is best, if contributors have formatted their examples properly.

Launching a trope is the most demanding part of the [=TLP=] process. If the replies have been helpful, it'll be much easier. This is the final page, and it should be complete, concise and well formatted. A page so well written nobody else will feel a need to edit the body text is something to be proud of.

* The best way to determine if a [=TLP=] is ready to be launched is to see if the draft has a net 5 hats- five more tropers think it's ready to launch (added a hat) than think it should be discarded (added a bomb).
* If the [=TLP=] lacks hats and you don't know why, you can make a comment to ask what is missing.

to:

You can write all the markup yourself, or copy the TropeEntryTemplate and edit the content. Copying and pasting the entries directly from the [=TLP=] is best, if contributors have formatted their examples properly.

Launching
Creating a trope launchable draft is the most demanding part of the [=TLP=] TLP process. If the replies have been helpful, it'll be much easier. This is the final page, and it should be complete, concise and well formatted. A page so well written nobody else will feel a need to edit the body text is something to be proud of.

* The best default way to determine if a [=TLP=] TLP is ready to be launched is to see if the draft has a net 5 hats- five hats; that is to say, five more tropers think it's ready to launch (added a hat) than think it should be discarded (added a bomb).
bomb). The software will allow a launch when there's five hats total, regardless of the net count, and so it's the launcher's responsibility to ensure it's five hats net ''and'' that those five hats net actually signify quality.
* If the [=TLP=] TLP lacks hats and you don't know why, you can make a comment to ask what is missing.



* The main writeup has to be well written, properly formatted, use correct markup and make sense. Make sure you're familiar with the wiki's [[Administrivia/HowToWriteAnExample good style]] and Administrivia/TextFormattingRules. Check the page once it's written; there's nothing wrong with being a SerialTweaker.
* A page is easier to read if the examples are sorted by category, so create a folder for each medium which examples of the trope fall into; that way, as the page grows it'll remain organised. Don't make empty folders or headings, though, since they just waste space.
* It's generally a better idea to write the whole page out in full at once than add it piecemeal, as if someone going through the launches list happens across a half-finished page, they might jump in and finish it themselves. You don't even have to write it out on the wiki - type the page up somewhere else, and enter it all in at once. Make sure you have your writeup copied to the clipboard or somewhere before you hit the "Send" button! There is nothing more frustrating than [[DataVampires losing your beautiful page to a database hiccup]].
* Use the WikiSandbox if you want to get the page perfect before launching.

to:

* Similar to the above rule, '''Do not launch a trope if the discussion is still unresolved.''' If there's people in the comments who have a problem with the title, examples, or the tropeworthiness itself, those people will also not be very happy if you've chosen to launch, anyway. Make sure there's no lingering issues before the trope is launched- this can be done by letting people know you intend to launch, and give them time to voice concerns if they have any. "Stealth" or "Ninja" launching is just as frowned upon as rogue launching is.
* The main writeup has to be well written, be properly formatted, use correct markup markup, and make sense. Make sure you're familiar with the wiki's [[Administrivia/HowToWriteAnExample good style]] and Administrivia/TextFormattingRules. Check the page once it's written; there's nothing wrong with being a SerialTweaker.
* It is good manners but not required to notify others that you are planning to launch a trope soon. Because there's no separate spot for this kind of news, a common tactic is to alter the (laconic) title with something like "(launching 3/11)" or "(final title feedback needed)". If you do this, be short but also clear. "(Launching soon)", for instance, is not clear because "soon" is rather open to interpretation.
* A page is easier to read if TLP takes time. Some launch only two weeks after they're proposed, while others linger for months. There are many factors that influence the examples are sorted by category, so create a folder for each medium which examples length of the trope fall into; that way, as TLP process and you should never rush it (not in the page grows it'll remain organised. Don't make empty folders or headings, though, since they just waste space.
* It's generally a better idea
least because there's also several post-launch matters to write the whole page out in full at once than add it piecemeal, as if someone going through the launches list happens across a half-finished page, they might jump in and finish it themselves. You don't even have to write it out on the wiki - type the page up somewhere else, and enter it all in at once. Make sure you have take care of).

!!After Launching:

You've launched
your writeup copied to the clipboard or somewhere before trope, but you hit the "Send" button! aren't done yet. There is nothing more frustrating than [[DataVampires losing your beautiful page are still several things to a database hiccup]].
take care of:

* Use [[Administrivia/HowToMakeACustomTitle Customise the WikiSandbox title]] if that's needed.
* As mentioned in the general notes, add any unusual characters that
you want to get couldn't during the page perfect before launching.TLP process.



* When you've written up the trope, in order to make sure a trope gets plenty of wicks and is noticed, it helps to go to the example pages and add it there (there's nothing wrong with copy-pasting the example text), a process known as Administrivia/{{Crosswicking}}. This is not mandatory, but all too often a trope page withers and dies because nobody even noticed it was added. A good rule of thumb is that a healthy trope page should have at least 12 wicks; if you absolutely can't get it there, you should probably list it on PagesNeedingWicks. If there are tropes related to the one you launched, add "See also" sections to both tropes. The more pages linked up, the better the WikiMagic flows.
* Create a laconic. To do this, go to the trope's URL window and edit the URL by replacing the word "Main" (which comes right before the trope name) with "Laconic". Edit the resulting page.

to:

* When you've written up the trope, in In order to make sure get a trope gets plenty of wicks and is noticed, it helps to if you yourself go to the example pages and add it there (there's nothing wrong with copy-pasting the example text), a process known as Administrivia/{{Crosswicking}}. This is not mandatory, but all too often a trope page withers and dies because nobody even noticed it was added. A good rule of thumb is that a healthy Every example listed on the trope page should also be listed on the corresponding work page, if we have at least 12 wicks; if you absolutely can't get it there, you one. Character tropes should probably list it go on PagesNeedingWicks.Character Pages if possible, and the same is true for episode-specific tropes and Recap Pages. If there are tropes related to the one you launched, add "See also" sections to both tropes. The more pages linked up, the better the WikiMagic flows.
* Create a laconic. To do this, go to the trope's URL window and edit the URL by replacing the word "Main" (which comes right before the trope name) with "Laconic". Edit the resulting page.



See also Administrivia/AGuideToEasyLaunchingOfYourTLP.

to:

See also Administrivia/AGuideToEasyLaunchingOfYourTLP.also:
* Administrivia/AGuideToEasyLaunchingOfYourTLP, for more information on the launching process.
* The [[https://tvtropes.org/pmwiki/posts.php?discussion=13544789560A75740100&page=1 TLP Crash Rescue thread]], for reporting premature launches and other issues with drafts.
* The [[https://tvtropes.org/pmwiki/posts.php?discussion=mrrv0lfphb29fvme6ofumrj0&page=1 TLP Workstation thread]], for getting help and feedback.


* When proposing that an existing trope is the same or in some other way related, do not post only the TropeName, and especially not in '''bold''' text. That is a Administrivia/ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.


to:

* When proposing that an existing trope is the same or in some other way related, do not post only the TropeName, trope name, and especially not in '''bold''' text. That is a Administrivia/ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.



The first stage of the process: click the "Add a new [=TLP=]" button, enter your working title and your writeup, and click the "send" button.

to:

The first stage of the process: click the "Add "Launch a new [=TLP=]" New Trope" button, then enter your working title, a laconic one-sentence description of your trope[[note]]Referred to as the Trope Laconic Title. It's kind of a [[NonIndicativeName non-indicative term]] right now, which tends to lead a lot of clueless newbies into typing in a title where the laconic description would normally go.[[/note]], and your writeup, and writeup in the text boxes that will appear. Once you're done, click the "send" button.

Added DiffLines:

If you want to create a new redirect, '''don't''' use the TLP. In fact, this is a major cause of TropeLaunchPad duplicates of existing tropes. For redirects, follow instead the [[Administrivia/CreatingNewRedirects instructions here]].


"TropeLaunchPad", usually abbreviated to [=TLP=], and also known as "You know, that thing where..." or '''[=YKTTW=]''', is used for spit-balling new tropes.

to:

"TropeLaunchPad", usually abbreviated to [=TLP=], and also formerly known as "You know, that thing where..." or '''[=YKTTW=]''', is used for spit-balling new tropes.



** [[https://tvtropes.org/pmwiki/posts.php?discussion=13294396280A03925700 YKTTW Backlog Cleanup]], since a lot of [=TLPs=] never see the light of the day.
** [[https://tvtropes.org/pmwiki/posts.php?discussion=mrrv0lfphb29fvme6ofumrj0 YKTTW Workstation thread]] for any help you need on TLP.

to:

** [[https://tvtropes.org/pmwiki/posts.php?discussion=13294396280A03925700 YKTTW Backlog Cleanup]], php?discussion=15518456230A47472000 TLP Discard Project]], since a lot of [=TLPs=] never see the light of the day.
** [[https://tvtropes.org/pmwiki/posts.php?discussion=mrrv0lfphb29fvme6ofumrj0 YKTTW TLP Workstation thread]] Thread]] for any help you need on TLP.


* As with everywhere else, please try to put a bit of work into your [=TLP=]. Good spelling and grammar aren't just for the final writeup; they help people understand you and make them more likely to care about what you have to say. A badly written [=TLP=] is likely to get fewer comments, which means it'll get fewer examples, less contribution and more likely to end up on the cut list. The same goes for comments; if your comment makes no sense, don't expect to see your example in the final write-up.

to:

* As with everywhere else, please try to put a bit of work into your [=TLP=]. Good spelling and grammar aren't just for the final writeup; they help people understand you and make them more likely to care about what you have to say. A badly poorly written [=TLP=] is likely to get fewer comments, which means it'll get fewer examples, will get less contribution contribution, and is more likely to end up on the cut list. The same goes for comments; if your comment makes no sense, don't expect to see your example in the final write-up.


* If your trope slides down the page without getting any replies, you might want to give it a Administrivia/TLPBump. There are two ways of doing this: Edit the entry (click on the little pencil icon at the top of the entry, whose location tends to vary depending on which web browser you use) and enter "save changes" without making any changes, which will automatically bump the [=TLP=] to the top of the stack without adding new replies. Or just add a new reply.

to:

* If your trope slides down the page without getting any replies, you might want to give it a Administrivia/TLPBump. There are two ways of doing this: Edit the entry (click on the little pencil icon at the top of the entry, whose location tends to vary depending on which web browser you use) and enter "save changes" without making any changes, which will automatically bump the [=TLP=] to the top of the stack without adding new replies. Or just add a new reply. Don't overdo the bumping, especially not content-less bumping, however!


* However, if you don't think the proposed is a trope, is too subjective, should be [[Adminstrivia/LumperVsSplitter lumped]] with something else, or otherwise doesn't deserve to be a page, ''go ahead and say so''. Far better to nip a bad page in the bud than have to deal with a site cluttered up with Administrivia/TheSameButMore articles and subjective Administrivia/{{natter}}. If the original poster disagrees, that person will state his/her case. There can be an open discussion about it; use constructive criticism as much as possible, since that helps both the page and its contributors improve.

to:

* However, if you don't think the proposed is a trope, is too subjective, should be [[Adminstrivia/LumperVsSplitter [[Administrivia/LumperVsSplitter lumped]] with something else, or otherwise doesn't deserve to be a page, ''go ahead and say so''. Far better to nip a bad page in the bud than have to deal with a site cluttered up with Administrivia/TheSameButMore articles and subjective Administrivia/{{natter}}. If the original poster disagrees, that person will state his/her case. There can be an open discussion about it; use constructive criticism as much as possible, since that helps both the page and its contributors improve.


* The best way to determine if a [=TLP=] is ready to be launched is to see if the draft has a net 5 hats- five more tropers think its ready to launch (added a hat) than think it should be discarded (added a bomb).

to:

* The best way to determine if a [=TLP=] is ready to be launched is to see if the draft has a net 5 hats- five more tropers think its it's ready to launch (added a hat) than think it should be discarded (added a bomb).


* The best way to determine if a [=TLP=] is ready to be launched is to see if five tropers have given it the Hat symbol, i.e. think that it's ready for launching.

to:

* The best way to determine if a [=TLP=] is ready to be launched is to see if the draft has a net 5 hats- five more tropers have given it the Hat symbol, i.e. think that it's its ready for launching.to launch (added a hat) than think it should be discarded (added a bomb).



* The general rule of launching is to let the person who proposed the trope launch it, unless they specifically said it was Administrivia/UpForGrabs. However, if the original creator stops replying to the discussion, and the trope is all ready to go, it's better to act and launch the trope.

to:

* The general rule of launching is to let the person who proposed the trope launch it, unless they specifically said it was Administrivia/UpForGrabs. However, '''Do not launch a trope if you haven't contributed to the original creator stops replying to draft.''' If you see a good draft that's been inactive for a while, give it a Administrivia/TLPBump and let people weigh in before launching. "Rogue launching", or launching a draft that has unresolved issues without participating in the discussion, is frowned upon, and the trope is all ready to go, it's better to act and launch the trope.may result in a suspension of TLP privileges.


* When proposing that an existing trope is the same or in some other way related, do not post only the TropeName, and especially not in '''bold''' text. That is a ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.


to:

* When proposing that an existing trope is the same or in some other way related, do not post only the TropeName, and especially not in '''bold''' text. That is a ZeroContextExample, Administrivia/ZeroContextExample, and more likely to lead to confusion and conflict than enlightenment -- it cannot be assumed that everyone will read the [=TLP=] and the cited trope the same way. Bold text is commonly used on the internet to infer shouting, which is rude in most conversations and circumstances including this one.



* If you put a link to a picture in your post, it might be rendered. Use small images or text links to the picture.

to:

* If you put a link to a picture in your post, it might not be rendered. Use small images or text links to the picture.

Showing 15 edit(s) of 24

Top

How well does it match the trope?

Example of:

/

Media sources:

/

Report