Is there an issue? Send a MessageReason:
Trope was cut/disambiguated due to cleanup
Changed line(s) 1 (click to see context) from:
The official Website/TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the former tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
to:
The official Website/TVTropes trope-naming mantra, [[CatchPhrase [[AuthorCatchphrase signature line]] of the former tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
Is there an issue? Send a MessageReason:
None
Changed line(s) 13 (click to see context) from:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[Administrivia/ThreadMode heading off into tangents]]. So don't add useless WordCruft like "Just to make it perfectly, crystal clear".
to:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[Administrivia/ThreadMode heading off into tangents]]. So don't add useless WordCruft Administrivia/WordCruft like "Just to make it perfectly, crystal clear".
Is there an issue? Send a MessageReason:
Wiki/ cleanup
Changed line(s) 1 (click to see context) from:
The official Wiki/TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the former tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
to:
The official Wiki/TVTropes Website/TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the former tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
Is there an issue? Send a MessageReason:
None
Changed line(s) 13 (click to see context) from:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[Administrivia/ThreadMode heading off into tangents]].
to:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[Administrivia/ThreadMode heading off into tangents]]. So don't add useless WordCruft like "Just to make it perfectly, crystal clear".
Is there an issue? Send a MessageReason:
namespace migration
Changed line(s) 13 (click to see context) from:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[ThreadMode heading off into tangents]].
to:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[Administrivia/JustifyingEdit justifying]] itself or [[ThreadMode [[Administrivia/ThreadMode heading off into tangents]].
Is there an issue? Send a MessageReason:
None
Changed line(s) 3 (click to see context) from:
# The name of a trope should be '''concise''', so long as concision does not conflict with clarity, defined above;
to:
# The name of a trope should be '''concise''', so long as concision conciseness does not conflict with clarity, defined above;
Is there an issue? Send a MessageReason:
None
Changed line(s) 13 (click to see context) from:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[JustifyingEdit justifying]] itself or [[ThreadMode heading off into tangents]].
to:
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[JustifyingEdit [[Administrivia/JustifyingEdit justifying]] itself or [[ThreadMode heading off into tangents]].
Is there an issue? Send a MessageReason:
None
Changed line(s) 12 (click to see context) from:
# An example should '''clearly''' illustrate why it is an example of the trope. [[Administrivia/ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[Administrivia/WeblinksAreNotExamples linking offsite]] and calling it a day.
to:
# An example should '''clearly''' illustrate why how it is an example of the trope. [[Administrivia/ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[Administrivia/WeblinksAreNotExamples linking offsite]] and calling it a day. When writing an example, imagine that your audience is familiar with neither the work nor the trope.
Is there an issue? Send a MessageReason:
None
Changed line(s) 16 (click to see context) from:
Again, the specific order is important. If being funny makes the example unreadable, then stop and get to the point. If an example takes so much text to explain that it takes over the page, ask yourself if it's really an example, or if all those details are really necessary.
to:
Again, the specific order is important. If being funny makes the example unreadable, then stop and get to the point. If an example takes so much text to explain that it takes over the page, ask yourself if it's really an example, or if all those details are really necessary. Above all, an example must be understandable.
Is there an issue? Send a MessageReason:
None
Changed line(s) 1 (click to see context) from:
The official Wiki/TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
to:
The official Wiki/TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the former tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
Is there an issue? Send a MessageReason:
Changed line(s) 6,7 (click to see context) from:
The specific order of these items is very important: Names that fail in clarity will attract misuse more often than names which are overly long (but clear), or so clinically devoid of humor that it [[ThereShouldBeALaw should be a crime]]. It's no mere hyperbole, either, but a proven fact of our TropeRepairShop -- renames are proposed (and evaluated) on the grounds of active misuse or misleading titles more often than any other criterion.
to:
The specific order of these items is very important: Names that fail in clarity will attract misuse more often than names which are overly long (but clear), or so clinically devoid of humor that it [[ThereShouldBeALaw should be a crime]]. It's no mere hyperbole, either, but a proven fact of our TropeRepairShop Administrivia/TropeRepairShop -- renames are proposed (and evaluated) on the grounds of active misuse or misleading titles more often than any other criterion.
Is there an issue? Send a MessageReason:
None
Changed line(s) 1 (click to see context) from:
The official TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
to:
Changed line(s) 12 (click to see context) from:
# An example should '''clearly''' illustrate why it is an example of the trope. [[ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[WeblinksAreNotExamples linking offsite]] and calling it a day.
to:
# An example should '''clearly''' illustrate why it is an example of the trope. [[ZeroContextExample [[Administrivia/ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[WeblinksAreNotExamples [[Administrivia/WeblinksAreNotExamples linking offsite]] and calling it a day.
Is there an issue? Send a MessageReason:
None
Changed line(s) 10,11 (click to see context) from:
The same guideline applies to trope examples.
to:
The same guideline applies guidelines apply to trope examples.
Is there an issue? Send a MessageReason:
None
Added DiffLines:
The official TVTropes trope-naming mantra, [[CatchPhrase signature line]] of the tropes webmaster Tropers/FastEddie, and laconic guidelines of Administrivia/NamingATrope. These are to trope names much as Creator/IsaacAsimov's ThreeLawsOfRobotics are to ArtificialIntelligence:
# The name of a trope must be '''clear''', so that readers can intuitively [[Administrivia/GuessThatTropeDefinition figure out the definition]] at a glance;
# The name of a trope should be '''concise''', so long as concision does not conflict with clarity, defined above;
# The name of a trope should aim for '''witty''', provided it does not conflict with either of the first two.
The specific order of these items is very important: Names that fail in clarity will attract misuse more often than names which are overly long (but clear), or so clinically devoid of humor that it [[ThereShouldBeALaw should be a crime]]. It's no mere hyperbole, either, but a proven fact of our TropeRepairShop -- renames are proposed (and evaluated) on the grounds of active misuse or misleading titles more often than any other criterion.
----
The same guideline applies to trope examples.
# An example should '''clearly''' illustrate why it is an example of the trope. [[ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[WeblinksAreNotExamples linking offsite]] and calling it a day.
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[JustifyingEdit justifying]] itself or [[ThreadMode heading off into tangents]].
# An example should be '''witty''', written in an entertaining and breezy style. This doesn't mean that it should be filled with in-jokes and irrelevant details, but the wiki is best when it's enjoyable to read.
Again, the specific order is important. If being funny makes the example unreadable, then stop and get to the point. If an example takes so much text to explain that it takes over the page, ask yourself if it's really an example, or if all those details are really necessary.
----
# The name of a trope must be '''clear''', so that readers can intuitively [[Administrivia/GuessThatTropeDefinition figure out the definition]] at a glance;
# The name of a trope should be '''concise''', so long as concision does not conflict with clarity, defined above;
# The name of a trope should aim for '''witty''', provided it does not conflict with either of the first two.
The specific order of these items is very important: Names that fail in clarity will attract misuse more often than names which are overly long (but clear), or so clinically devoid of humor that it [[ThereShouldBeALaw should be a crime]]. It's no mere hyperbole, either, but a proven fact of our TropeRepairShop -- renames are proposed (and evaluated) on the grounds of active misuse or misleading titles more often than any other criterion.
----
The same guideline applies to trope examples.
# An example should '''clearly''' illustrate why it is an example of the trope. [[ZeroContextExample Simply mentioning the trope]] is not enough, nor is [[WeblinksAreNotExamples linking offsite]] and calling it a day.
# An example should be as '''concise''' as possible, so as not to look like a WallOfText. A clear sign that you're violating this guideline is when an example starts [[JustifyingEdit justifying]] itself or [[ThreadMode heading off into tangents]].
# An example should be '''witty''', written in an entertaining and breezy style. This doesn't mean that it should be filled with in-jokes and irrelevant details, but the wiki is best when it's enjoyable to read.
Again, the specific order is important. If being funny makes the example unreadable, then stop and get to the point. If an example takes so much text to explain that it takes over the page, ask yourself if it's really an example, or if all those details are really necessary.
----
