All The Tropes:Trope Workshop Guidelines: Difference between revisions

→‎What a Trope Workshop Candidate Should Contain at the End: added "analyze why a trope happens" to the list
(→‎What a Trope Workshop Candidate Should Contain at the End: added "analyze why a trope happens" to the list)
Line 31:
* Popularity through time: A trope should have a clear pattern. Try to include the information about the popularity of the trope through time, when the occurrences of the trope started to raise and when the popularity of the trope reached its peak and if the trope has fallen out of favor. Also pay in mind that a trope can be region-specific (a trope used in works only or mostly in certain countries or regions). For an example, there might be a trope exclusive to Romanian animation. If the examples of the trope are just random occurrences with no clear pattern, it has a danger of belonging to the [[Too Rare to Trope]] category.
* Current [[Trope Life Cycle]] status: How seriously the trope is taken nowadays. It can be still an commonly-used trope, it can be a [[Discredited Trope]] when a trope is considered a cliché, it can be [[Dead Horse Trope]] where parodies and [[Lampshade Hanging]]s far outnumber straight examples, it can be an [[Undead Horse Trope]] when, despite being mocked a lot, is still used straight, it can be [[Forgotten Trope]] when it's not used at all and it can be a [[Dead Unicorn Trope]] when the trope was rarely, if ever used straight at all.
* As mentioned in |[https://fucknotvtropes.tumblr.com/faq the FAQ] at ''[[Fuck No TVTropes]]'', "analyze why a trope happens and not just when it happens". Describe ''why'' it's a trope - what triggers it in-story, what it leads to in-story, what happens when the trope is Enforced or Defied, and so on. Again, a list of examples is not a trope.
* Proper English grammar and usage: It doesn't matter if you hit all the other points above right on the head, if the trope candidate reads like it was written by Google Translate or a dyslexic ten-year-old (or both working together), ''it will '''not''' get launched''. And although wiki admins have been known to step in and do their best to translate trope candidates from whatever they were written in to proper English, it is ''not'' their responsibility to do so -- it is that of the user(s) who want to see the trope candidate go live. If the description is so badly written a reader can't figure out what it means, and/or the examples are so garbled their relevance to the trope cannot even be guessed at, the article has ''failed'' at what it is supposed to do, which is ''communicate clearly and succinctly'' a pattern in storytelling.