Is there an issue? Send a MessageReason:
per edit requests thread
Changed line(s) 1,2 (click to see context) from:
2.0 is the name of a planned overhaul of the Wiki/TVTropes database and page handling systems.
to:
2.0 is the name of a planned overhaul of the Wiki/TVTropes Website/TVTropes database and page handling systems.
Is there an issue? Send a MessageReason:
None
Deleted line(s) 242 (click to see context) :
* DeaderThanDisco: How to handle that page?
Is there an issue? Send a MessageReason:
None
Changed line(s) 190 (click to see context) from:
* It checks whether the entry text contains Administrivia/WordCruft, ThisTroper and other problem items. Needs a configuration function.
to:
* It checks whether the entry text contains Administrivia/WordCruft, ThisTroper Administrivia/FirstPersonWriting and other problem items. Needs a configuration function.
Changed line(s) 198,199 (click to see context) from:
# It checks whether the entry text contains Administrivia/WordCruft, ThisTroper and other problem items. Needs a configuration function.
to:
# It checks whether the entry text contains Administrivia/WordCruft, ThisTroper Administrivia/FirstPersonWriting and other problem items. Needs a configuration function.
Is there an issue? Send a MessageReason:
None
Changed line(s) 190 (click to see context) from:
* It checks whether the entry text contains WordCruft, ThisTroper and other problem items. Needs a configuration function.
to:
* It checks whether the entry text contains WordCruft, Administrivia/WordCruft, ThisTroper and other problem items. Needs a configuration function.
Changed line(s) 198,199 (click to see context) from:
# It checks whether the entry text contains WordCruft, ThisTroper and other problem items. Needs a configuration function.
to:
# It checks whether the entry text contains WordCruft, Administrivia/WordCruft, ThisTroper and other problem items. Needs a configuration function.
Is there an issue? Send a MessageReason:
None
Changed line(s) 266 (click to see context) from:
* SugarWiki and DarthWiki
to:
* SugarWiki SugarWiki/SugarWiki and DarthWikiDarthWiki/DarthWiki
Is there an issue? Send a MessageReason:
None
Changed line(s) 22 (click to see context) from:
* {{Natter}} would be diverted into comment threads, making it much less likely to be inserted into the article body.
to:
* {{Natter}} Administrivia/ConversationInTheMainPage would be diverted into comment threads, making it much less likely to be inserted into the article body.
Is there an issue? Send a MessageReason:
None
Changed line(s) 138 (click to see context) from:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances, plus setting banners) and "RealLife examples allowed?" (implements Administrivia/NoRealLifeExamplesPlease)
to:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, Administrivia/ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances, plus setting banners) and "RealLife examples allowed?" (implements Administrivia/NoRealLifeExamplesPlease)
Is there an issue? Send a MessageReason:
Per edit requests thread
Changed line(s) 140 (click to see context) from:
* Title: One for each page, is created during page creation and only moderator editable afterwards. It contains the appearance of the article title (similar to a CustomTitle).
to:
* Title: One for each page, is created during page creation and only moderator editable afterwards. It contains the appearance of the article title (similar to a CustomTitle).Administrivia/CustomTitle).
Is there an issue? Send a MessageReason:
None
Changed line(s) 30 (click to see context) from:
[[folder:URLs]]
to:
Is there an issue? Send a MessageReason:
None
Changed line(s) 1,2 (click to see context) from:
2.0 is the name of a planned overhaul of the TVTropes database and page handling systems.
to:
2.0 is the name of a planned overhaul of the TVTropes Wiki/TVTropes database and page handling systems.
Is there an issue? Send a MessageReason:
Definitively too much opposition to put in the core concept - moving to "questions"
Deleted line(s) 16 (click to see context) :
* Integrated voting feature for sections like Quotes, Images, and Moments.
Changed line(s) 272 (click to see context) from:
* Votes on images and quotes?
to:
* Votes on images Integrated voting feature for sections like Quotes, Images, and quotes? Moments.
Is there an issue? Send a MessageReason:
None
Changed line(s) 3,4 (click to see context) from:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database", it will need to be Unicode compatible. Also, there will be different languages available with their own alphabet for translation purposes. All pages of the same trope or work will automatically link to the crosslanguage (identified as "same page ID, different language ID") versions thereof.
to:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called In technical terms, the wiki will be constructed from "relational database", it will need to be database" elements rather than unstructured text.
Other design goals are Unicodecompatible. Also, there will be different languages available with their own alphabet for translation purposes. compatibility and integrated multi-language/translation support. All pages of the same trope or work will automatically link to the crosslanguage cross-language (identified as "same page ID, different language ID") versions thereof.
Other design goals are Unicode
Changed line(s) 7,8 (click to see context) from:
[[folder:Core concept]]
* This system allows pages to be generated dynamically and thus according to troper preferences.
* This system allows pages to be generated dynamically and thus according to troper preferences.
to:
[[folder:Core concept]]
Concept]]
*This system allows pages The wiki structure will move from flat text objects that are analyzed by a parser to a relational, data-driven system.
* Articles, article components, and individual examples will be structured data elements.
* Pages will be generateddynamically dynamically, allowing alternative views, sorting, filtering, and thus according to troper preferences.pagination, which can be controlled by individual user preferences (e.g. number of examples displayed per page).
*
* Articles, article components, and individual examples will be structured data elements.
* Pages will be generated
* Integrated comment sections that permit conversations to be attached to any wiki element, but still viewed at the main article level.
* Integrated voting feature for sections like Quotes, Images, and Moments.
* Integrated voting feature for sections like Quotes, Images, and Moments.
Changed line(s) 16,17 (click to see context) from:
* Many editing rules (e.g natter or Administrivia/WhatGoesWhereOnTheWiki) will be enforceable by the software rather than by hand.
* This would allow pages to be filtered, sorted and grouped dynamically, also allowing for pagination of long pages.
* This would allow pages to be filtered, sorted and grouped dynamically, also allowing for pagination of long pages.
to:
* Many editing rules (e.g natter Administrivia/ExampleIndentationInTropeLists or Administrivia/WhatGoesWhereOnTheWiki) will be enforceable by the software rather than by hand.
*This {{Natter}} would be diverted into comment threads, making it much less likely to be inserted into the article body.
* There will no longer be a need to hard-split articles, as pagination, filtering, and grouping would allowpages a given article to be filtered, sorted and grouped dynamically, also allowing for pagination handle any amount of long pages.content.
*
* There will no longer be a need to hard-split articles, as pagination, filtering, and grouping would allow
Changed line(s) 19,20 (click to see context) from:
* Articles would no longer be at hardcoded text [=URLs=]; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
* Article subpages would no longer be hardcoded but rather based on the user’s filtering selection. Certain types of subpages could have predefined style/layout.
* Article subpages would no longer be hardcoded but rather based on the user’s filtering selection. Certain types of subpages could have predefined style/layout.
to:
* Checks that rely on "diffs", such as spam filtering, text-replacer detection, and so on, can be applied only to a user's individual edits, not to the entire body of each article.
* Articles would no longer be athardcoded hard-coded text [=URLs=]; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
* Article subpages would no longer behardcoded hard-coded but rather based on the user’s filtering selection. Certain types of subpages could have predefined style/layout.
* Articles would no longer be at
* Article subpages would no longer be
Changed line(s) 38,45 (click to see context) from:
* id Article ID. If found and valid, this will generate an exclusive result.
* title (t) Article title. This will generate a fuzzy query against the title repository.
* type Article type. Allows all page types.
* medium (m) Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) Genre. Reference against genre index, smart enough to understand nesting.
* author (a) Author. Reference against Creator articles related to work page.
* year (y) Publication year.
* title (t) Article title. This will generate a fuzzy query against the title repository.
* type Article type. Allows all page types.
* medium (m) Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) Genre. Reference against genre index, smart enough to understand nesting.
* author (a) Author. Reference against Creator articles related to work page.
* year (y) Publication year.
to:
* id -- Article ID. If found and valid, this will generate an exclusive result.
* title (t) -- Article title. This will generate a fuzzy query against the title repository.
* type -- Article type. Allows all page types.
* medium (m) -- Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) -- Genre. Reference against genre index, smart enough to understand nesting.
* author (a) -- Author. Reference against Creator articles related to work page.
* year (y) -- Publication year.
* title (t) -- Article title. This will generate a fuzzy query against the title repository.
* type -- Article type. Allows all page types.
* medium (m) -- Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) -- Genre. Reference against genre index, smart enough to understand nesting.
* author (a) -- Author. Reference against Creator articles related to work page.
* year (y) -- Publication year.
Changed line(s) 47,54 (click to see context) from:
* subpage (sub) Subpage -- could be YMMV, WMG, Characters, or any supported subpage filter.
* filter (f) Synonym for subpage.
* sort (s) Sort -- choose from sort options (alpha, date added, date modified)
* group (grp) Group -- choose grouping: medium, genre, trope category, etc.
* page (p) Page number in a paginated article.
* length (l) Number of examples listed on each page.
* view (v) Read (default), Edit, Comments, Images, Quotes, History
* filter (f) Synonym for subpage.
* sort (s) Sort -- choose from sort options (alpha, date added, date modified)
* group (grp) Group -- choose grouping: medium, genre, trope category, etc.
* page (p) Page number in a paginated article.
* length (l) Number of examples listed on each page.
* view (v) Read (default), Edit, Comments, Images, Quotes, History
to:
* subpage (sub) Subpage -- Subpage: could be YMMV, WMG, Characters, or any supported subpage filter.
* filter (f) -- Synonym for subpage.
* sort (s)Sort -- Sort: choose from sort options (alpha, date added, date modified)
* group (grp)Group -- Group: choose grouping: medium, genre, trope category, etc.
* page (p) -- Page number in a paginated article.
* length (l) -- Number of examples listed on each page.
* view (v) -- Read (default), Edit, Comments, Images, Quotes, History
* filter (f) -- Synonym for subpage.
* sort (s)
* group (grp)
* page (p) -- Page number in a paginated article.
* length (l) -- Number of examples listed on each page.
* view (v) -- Read (default), Edit, Comments, Images, Quotes, History
Changed line(s) 56,68 (click to see context) from:
http://tvtropes.org/wiki/search.php?id=3885774
Resolves uniquely to The Lord of the Rings, Literature
http://tvtropes.org/wiki/search.php?title=The%20Lord%20of%20%the%20Rings
Finds multiple hits, shows disambiguation or franchise landing page if available.
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&a=Tolkien
Titles without spaces are acceptable in [=URLs=], so are partial names of authors. This will resolve to the LOTR book article.
http://tvtropes.org/wiki/search.php?id=3885774&grp=tropecategory&l=50
This will return the LOTR article with 50 examples per page, grouped by trope category (plot, character, production, etc.)
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&y=1954&v=Comments
This will return the LOTR literature article in the Comments view.
http://tvtropes.org/wiki/search.php?t=BigBad&type=trope
This will find the Big Bad trope article.
Resolves uniquely to The Lord of the Rings, Literature
http://tvtropes.org/wiki/search.php?title=The%20Lord%20of%20%the%20Rings
Finds multiple hits, shows disambiguation or franchise landing page if available.
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&a=Tolkien
Titles without spaces are acceptable in [=URLs=], so are partial names of authors. This will resolve to the LOTR book article.
http://tvtropes.org/wiki/search.php?id=3885774&grp=tropecategory&l=50
This will return the LOTR article with 50 examples per page, grouped by trope category (plot, character, production, etc.)
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&y=1954&v=Comments
This will return the LOTR literature article in the Comments view.
http://tvtropes.org/wiki/search.php?t=BigBad&type=trope
This will find the Big Bad trope article.
to:
Changed line(s) 74 (click to see context) from:
**[=URLs=] with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
to:
Changed line(s) 76 (click to see context) from:
** [=URLs=] with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
to:
Changed line(s) 78 (click to see context) from:
** This will match one of the publication dates of the original LOTR books and so will resolve to the literature page.
to:
Changed line(s) 80 (click to see context) from:
** This will recognize the ‘edit’ keyword asking for the page to be shown in edit mode.
to:
Changed line(s) 82 (click to see context) from:
** This will find the Lord of the Rings literature article, open it to the Characters view, and drill down to the tropes associated with the character Legolas.
to:
Changed line(s) 84,85 (click to see context) from:
** This will arrive at (a) the work-agnostic general article for the character Legolas, (b) a disambiguation page showing all matching character articles, (c) the Lord of the Rings character, Legolas, if there is only one such entry.
to:
Changed line(s) 107 (click to see context) from:
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences in alphabetized form. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples.
to:
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences in alphabetized form. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples. \\
Changed line(s) 124 (click to see context) from:
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic. Automatically formatted.
to:
* Laconic: One per page, can be created during page creation or elsetime, afterwards, displays a laconic. Automatically formatted.
Changed line(s) 127,128 (click to see context) from:
* Self Demo: A free form page, sort of an equivalent to description. Allows bullet points.
* Settings: One of each exists for each page/article and is created during page creation. It applies crosslanguage. By default only editable by moderators, it includes all per-page settings:
* Settings: One of each exists for each page/article and is created during page creation. It applies crosslanguage. By default only editable by moderators, it includes all per-page settings:
to:
* Self Demo: Self-Demo: A free form page, sort of an equivalent to description. Allows bullet points.
* Settings: One of each exists for each page/article and is created during page creation. It appliescrosslanguage.cross-language. By default only editable by moderators, it includes all per-page settings:
* Settings: One of each exists for each page/article and is created during page creation. It applies
Changed line(s) 145 (click to see context) from:
** A "cascading lock" (which does not imply a plain lock!) tells the addelement function to not permit to add elements that feature the metadata (elementtype"work+trope combination).
to:
** A "cascading lock" (which does not imply a plain lock!) tells the addelement function to not permit to add elements that feature the metadata (elementtype"work+trope (elementtype+work+trope combination).
Is there an issue? Send a MessageReason:
Adding item
Added DiffLines:
* Compare/Contrast element? See [[http://tvtropes.org/pmwiki/posts.php?discussion=14556697700A23839500 thread]].
Is there an issue? Send a MessageReason:
None
Changed line(s) 200 (click to see context) from:
# Each element can be edited (during the save process, unedited elements are not alterated) and has checkboxes allowing for actions (e.g "Delist", "Put into Maintenance mode" or "Move", equivalent to the element action buttons).
to:
# Each element can be edited (during the save process, unedited elements are not alterated) altered) and has checkboxes allowing for actions (e.g "Delist", "Put into Maintenance mode" or "Move", equivalent to the element action buttons).
Is there an issue? Send a MessageReason:
None
Changed line(s) 19 (click to see context) from:
* Articles would no longer be at hardcoded text URLs; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
to:
* Articles would no longer be at hardcoded text URLs; [=URLs=]; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
Changed line(s) 27,28 (click to see context) from:
All other wiki URLs, other than to static objects like AskTheTropers, will be treated as database queries. These queries will contain parameter elements that identify the search terms. Certain parameter elements will also modify the display of the article, such as sorting, filtering, subpage display, etc.
to:
All other wiki URLs, [=URLs=], other than to static objects like AskTheTropers, will be treated as database queries. These queries will contain parameter elements that identify the search terms. Certain parameter elements will also modify the display of the article, such as sorting, filtering, subpage display, etc.
Changed line(s) 34 (click to see context) from:
Complex URLs
to:
Complex URLs[=URLs=]
Changed line(s) 55 (click to see context) from:
Examples of complex URLs:
to:
Examples of complex URLs:[=URLs=]:
Changed line(s) 61 (click to see context) from:
Titles without spaces are acceptable in URLs, so are partial names of authors. This will resolve to the LOTR book article.
to:
Titles without spaces are acceptable in URLs, [=URLs=], so are partial names of authors. This will resolve to the LOTR book article.
Changed line(s) 69,72 (click to see context) from:
Friendly URLs
The wiki parser should also understand URLs submitted in a more reader friendly format, using fuzzy logic to handle them. Rather than using parameter elements, forward slashes will separate terms that will be fed to a search engine.
Examples of friendly URLs and handling:
The wiki parser should also understand URLs submitted in a more reader friendly format, using fuzzy logic to handle them. Rather than using parameter elements, forward slashes will separate terms that will be fed to a search engine.
Examples of friendly URLs and handling:
to:
Friendly URLs
[=URLs=]
The wiki parser should also understandURLs [=URLs=] submitted in a more reader friendly format, using fuzzy logic to handle them. Rather than using parameter elements, forward slashes will separate terms that will be fed to a search engine.
Examples of friendlyURLs [=URLs=] and handling:
The wiki parser should also understand
Examples of friendly
Changed line(s) 74 (click to see context) from:
**URLs with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
to:
Changed line(s) 76 (click to see context) from:
** URLs with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
to:
** URLs [=URLs=] with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
Is there an issue? Send a MessageReason:
None
Changed line(s) 3,4 (click to see context) from:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database", it will need to be Unicode compatible.
to:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database", it will need to be Unicode compatible.
compatible. Also, there will be different languages available with their own alphabet for translation purposes. All pages of the same trope or work will automatically link to the crosslanguage (identified as "same page ID, different language ID") versions thereof.
Changed line(s) 128 (click to see context) from:
* Settings: One of each exists for each page/article and is created during page creation. By default only editable by moderators, it includes all per-page settings:
to:
* Settings: One of each exists for each page/article and is created during page creation. It applies crosslanguage. By default only editable by moderators, it includes all per-page settings:
Changed line(s) 149 (click to see context) from:
* Revert: A moderator button which allows older versions of an element to be restored, to prevent
to:
* Revert: A moderator button which allows older versions of an element to be restored, restored.
* Translate: Applies toprevent all elements save for Settings, it allows elements to be translated in different languages while forking the element. It automatically assigns the correct language ID while keeping the page ID(s) identical. It needs to check that no elements are created for tropes whose descriptions weren't yet translated in the given language.
* Translate: Applies to
Changed line(s) 167 (click to see context) from:
A way to have Edit Notices for pages meeting particular criteria?
to:
A way to have Edit Notices for pages meeting particular criteria?criteria? They would replace the standard edit tips on the pages concerned.
A way to merge one page ID into another. This is a moderator tool that works irreversibly to reassign elements from one page ID to another. Useful to handle translation goofs as well as duplicates.
A way to merge one page ID into another. This is a moderator tool that works irreversibly to reassign elements from one page ID to another. Useful to handle translation goofs as well as duplicates.
Added DiffLines:
[[folder:Troper permissions]]
* Global moderator: They have all the non-wiki tools as well as the ability to grant and revoke local moderator status on a per language basis.
* Local moderator: Assigned per language domain, they have the ability to (un)lock and (un)delete elements as well as to edit them in the locked and view them in the deleted state. They are limited to their assigned language domain.
[[/folder]]
* Global moderator: They have all the non-wiki tools as well as the ability to grant and revoke local moderator status on a per language basis.
* Local moderator: Assigned per language domain, they have the ability to (un)lock and (un)delete elements as well as to edit them in the locked and view them in the deleted state. They are limited to their assigned language domain.
[[/folder]]
Added DiffLines:
* Crosslanguage links?
Added DiffLines:
* Language specific bans?
Is there an issue? Send a MessageReason:
None
Added DiffLines:
* Examples will automatically appear on both work and trope pages, making Administrivia/{{Crosswicking}} superfluous.
Is there an issue? Send a MessageReason:
None
Changed line(s) 119,122 (click to see context) from:
* Analysis: Several per page, can be created by an addelement function.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" a page.
* Example: These contain example text and are connected each to a trope and a work. They can be flagged with PlayingWithATrope, potentially also through the markup.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" a page.
* Example: These contain example text and are connected each to a trope and a work. They can be flagged with PlayingWithATrope, potentially also through the markup.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic.
to:
* Analysis: Several per page, can be created by an addelement function.
function. Allows bullet points.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" apage.
page. Allows bullet points.
* Example: These contain example text and are connected each to a trope and a work. They can be flagged with PlayingWithATrope, potentially also through themarkup.
markup. Also, there will optionally be two versions of the example text, for work page and trope page.
* ImageLinks: Several per page, allow links to image [=URLs=]. Need a dedicated addImageLinks function.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic. Automatically formatted.
* PlayingWith: For tropes, allows a formatted list of PlayingWith elements.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" a
* Example: These contain example text and are connected each to a trope and a work. They can be flagged with PlayingWithATrope, potentially also through the
* ImageLinks: Several per page, allow links to image [=URLs=]. Need a dedicated addImageLinks function.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic. Automatically formatted.
* PlayingWith: For tropes, allows a formatted list of PlayingWith elements.
* Self Demo: A free form page, sort of an equivalent to description. Allows bullet points.
Changed line(s) 128 (click to see context) from:
* Stinger: One for each page, is an optional element that can be added. Each page can only have one visible stinger element.
to:
* Stinger: One for each page, is an optional element that can be added. Each page can only have one visible stinger element. Formatted like a quote.
Changed line(s) 137 (click to see context) from:
* Delist: Available for everybody on examples, quotes and Analysis, it hides the element from queries, thus also from example and quote lists. A banner named "Element X was delisted by Y on date Z for reason: A" appears above the element. It generates an entry both in the edit history of the element and the troper in question.
to:
* Delist: Available for everybody on examples, ImageLinks, quotes and Analysis, it hides the element from queries, thus also from example and quote lists. A banner named "Element X was delisted by Y on date Z for reason: A" appears above the element. It generates an entry both in the edit history of the element and the troper in question.
Changed line(s) 143,144 (click to see context) from:
* Move: For quote, Analysis, example elements, it allows one to change the trope or work the element is associated with.
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted".
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted".
to:
* Move: For quote, Analysis, ImageLinks, example elements, it allows one to change the trope or work the element is associated with.
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". Allowed everywhere delisting is allowed.
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". Allowed everywhere delisting is allowed.
Changed line(s) 146,148 (click to see context) from:
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted".
Some markups may be allowed only in particular sections. Direct links to elements are excluded from search engines.
Some markups may be allowed only in particular sections. Direct links to elements are excluded from search engines.
to:
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted".
deleted". Allowed everywhere deletion is allowed.
Some markups may be allowed only in particularsections.elements. Direct links to elements are excluded from search engines.
Some markups may be allowed only in particular
* Creator pages?
* Customizability of the example section header?
* DeaderThanDisco: How to handle that page?
* DeaderThanDisco: How to handle that page?
Deleted line(s) 221,222 (click to see context) :
* How to handle creator pages?
* How to handle indexing?
* How to handle indexing?
* ID thing creates some hairy problems if a page is cut then recreated (say, for having insufficient examples) ... examples would become disconnected from the new page. Basically, how the createarticle function for works would "catch" already existing examples for that work.
* Indexes and Categories?
* Media categories?
* Merge ID function?
* Merge ID function?
* Recap pages?
* Red links?
* Red links?
* Tagging: Characters? See also [[http://tvtropes.org/pmwiki/posts.php?discussion=14478420050A97600200&page=5#108 here]].
* Translations: [[http://tvtropes.org/pmwiki/posts.php?discussion=14509679370A24783300&page=1 One proposal]], another exists.
* Translations: [[http://tvtropes.org/pmwiki/posts.php?discussion=14509679370A24783300&page=1 One proposal]], another exists.
Changed line(s) 241 (click to see context) from:
* How to work with Recap, ImageLinks, Timeline, Fanworks and Useful Notes.
to:
* How to work with Recap, ImageLinks, Timeline, Timeline and Fanworks and Useful Notes. namespace pages.
* Watchlist.
* Watchlist.
Added DiffLines:
* ZCE rule exemption?
Is there an issue? Send a MessageReason:
None
Changed line(s) 3,4 (click to see context) from:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database"
to:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database"
database", it will need to be Unicode compatible.
Changed line(s) 31,32 (click to see context) from:
All articles should have a human-readable default URL that contains all the information needed to uniquely disambiguate it. The wick component (everything after http://tvtropes.org/wiki) would be used in the editor instead of the ID to avoid confusion.
to:
* All articles should have a human-readable default URL that contains all the information needed to uniquely disambiguate it. The wick component (everything after http://tvtropes.org/wiki) would be used in the editor instead of the ID to avoid confusion.
Changed line(s) 34,35 (click to see context) from:
The expanded destination URL will look something like http://tvtropes.org/wiki/search.php. May have synonyms.
to:
* The expanded destination URL will look something like http://tvtropes.org/wiki/search.php. May have synonyms.
Changed line(s) 37,44 (click to see context) from:
id Article ID. If found and valid, this will generate an exclusive result.
title (t) Article title. This will generate a fuzzy query against the title repository.
type Article type. Allows “trope”, “work”, “character”, “admin”, etc.
medium (m) Medium. Reference against medium index, smart enough to understand nesting.
genre (g) Genre. Reference against genre index, smart enough to understand nesting.
author (a) Author. Reference against Creator articles related to work page.
year (y) Publication year.
title (t) Article title. This will generate a fuzzy query against the title repository.
type Article type. Allows “trope”, “work”, “character”, “admin”, etc.
medium (m) Medium. Reference against medium index, smart enough to understand nesting.
genre (g) Genre. Reference against genre index, smart enough to understand nesting.
author (a) Author. Reference against Creator articles related to work page.
year (y) Publication year.
to:
* id Article ID. If found and valid, this will generate an exclusive result.
* title (t) Article title. This will generate a fuzzy query against the title repository.
* type Article type. Allows“trope”, “work”, “character”, “admin”, etc.
all page types.
* medium (m) Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) Genre. Reference against genre index, smart enough to understand nesting.
* author (a) Author. Reference against Creator articles related to work page.
* year (y) Publication year.
* title (t) Article title. This will generate a fuzzy query against the title repository.
* type Article type. Allows
* medium (m) Medium. Reference against medium index, smart enough to understand nesting.
* genre (g) Genre. Reference against genre index, smart enough to understand nesting.
* author (a) Author. Reference against Creator articles related to work page.
* year (y) Publication year.
Changed line(s) 46,53 (click to see context) from:
subpage (sub) Subpage -- could be YMMV, WMG, Characters, or any supported subpage filter.
filter (f) Synonym for subpage.
sort (s) Sort -- choose from sort options (alpha, date added, date modified)
group (grp) Group -- choose grouping: medium, genre, trope category, etc.
page (p) Page number in a paginated article.
length (l) Number of examples listed on each page.
view (v) Read (default), Edit, Comments, Images, Quotes, History
filter (f) Synonym for subpage.
sort (s) Sort -- choose from sort options (alpha, date added, date modified)
group (grp) Group -- choose grouping: medium, genre, trope category, etc.
page (p) Page number in a paginated article.
length (l) Number of examples listed on each page.
view (v) Read (default), Edit, Comments, Images, Quotes, History
to:
* subpage (sub) Subpage -- could be YMMV, WMG, Characters, or any supported subpage filter.
* filter (f) Synonym for subpage.
* sort (s) Sort -- choose from sort options (alpha, date added, date modified)
* group (grp) Group -- choose grouping: medium, genre, trope category, etc.
* page (p) Page number in a paginated article.
* length (l) Number of examples listed on each page.
* view (v) Read (default), Edit, Comments, Images, Quotes, History
* filter (f) Synonym for subpage.
* sort (s) Sort -- choose from sort options (alpha, date added, date modified)
* group (grp) Group -- choose grouping: medium, genre, trope category, etc.
* page (p) Page number in a paginated article.
* length (l) Number of examples listed on each page.
* view (v) Read (default), Edit, Comments, Images, Quotes, History
Changed line(s) 72,84 (click to see context) from:
http://tvtropes.org/wiki/LordOfTheRings
URLs with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
http://tvtropes.org/wiki/LordOfTheRings/film
URLs with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
http://tvtropes.org/wiki/LordOfTheRings/1955
This will match one of the publication dates of the original LOTR books and so will resolve to the literature page.
http://tvtropes.org/wiki/LordOfTheRings/edit
This will recognize the ‘edit’ keyword asking for the page to be shown in edit mode.
http://tvtropes.org/wiki/Literature/LordOfTheRings/Characters/Legolas
This will find the Lord of the Rings literature article, open it to the Characters view, and drill down to the tropes associated with the character Legolas.
http://tvtropes.org/wiki/Characters/Legolas
This will arrive at (a) the work-agnostic general article for the character Legolas, (b) a disambiguation page showing all matching character articles, (c) the Lord of the Rings character, Legolas, if there is only one such entry.
URLs with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
http://tvtropes.org/wiki/LordOfTheRings/film
URLs with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
http://tvtropes.org/wiki/LordOfTheRings/1955
This will match one of the publication dates of the original LOTR books and so will resolve to the literature page.
http://tvtropes.org/wiki/LordOfTheRings/edit
This will recognize the ‘edit’ keyword asking for the page to be shown in edit mode.
http://tvtropes.org/wiki/Literature/LordOfTheRings/Characters/Legolas
This will find the Lord of the Rings literature article, open it to the Characters view, and drill down to the tropes associated with the character Legolas.
http://tvtropes.org/wiki/Characters/Legolas
This will arrive at (a) the work-agnostic general article for the character Legolas, (b) a disambiguation page showing all matching character articles, (c) the Lord of the Rings character, Legolas, if there is only one such entry.
to:
Changed line(s) 86,90 (click to see context) from:
It should be possible to enter queries without a title element; this would be interpreted as an index search.
http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
Both of these queries will enumerate all works in the Fantasy genre and the Literature medium published between 1950 and 1959.
http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
Both of these queries will enumerate all works in the Fantasy genre and the Literature medium published between 1950 and 1959.
to:
* It should be possible to enter queries without a title element; this would be interpreted as an index search.
** http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
** http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
* Both of these queries will enumerate all works in the Fantasy genre and the Literature medium published between 1950 and 1959.
** http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
** http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
Changed line(s) 100,101 (click to see context) from:
RealLife will be a special work page, with additional restrictions.
to:
RealLife will be a special work page, with additional restrictions.
restrictions. These page types are hard coded and cannot be changed.
Changed line(s) 106 (click to see context) from:
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples.
to:
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences.preferences in alphabetized form. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples.
Changed line(s) 121 (click to see context) from:
* Example: These contain example text and are connected each to a trope and a work.
to:
* Example: These contain example text and are connected each to a trope and a work. They can be flagged with PlayingWithATrope, potentially also through the markup.
Changed line(s) 127 (click to see context) from:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances) and "RealLife examples allowed?" (implements Administrivia/NoRealLifeExamplesPlease)
to:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances) appearances, plus setting banners) and "RealLife examples allowed?" (implements Administrivia/NoRealLifeExamplesPlease)
Changed line(s) 133,134 (click to see context) from:
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some of them will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
* Delete: Available for moderators on most elements save for Settings and Title, it automatically hides the element text and its history behind a splash page "Element X was deleted by Y on date Z for reason: A" for anyone who isn't a moderator. It generates an entry both in the edit history of the element and the troper in question. This element is automatically excluded from queries.
* Delete: Available for moderators on most elements save for Settings and Title, it automatically hides the element text and its history behind a splash page "Element X was deleted by Y on date Z for reason: A" for anyone who isn't a moderator. It generates an entry both in the edit history of the element and the troper in question. This element is automatically excluded from queries.
to:
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some of them will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
fallbacks. All such functions generate an entry both in the edit history of the element and the troper in question.
* Change Play: For examples, it allows the Playing With status of an example to be changed.
* Edit: Obvious.
* Delete: Available for moderators on most elements save for Settings and Title, it automatically hides the element text and its history behind a splash page "Element X was deleted by Y on date Z for reason: A" for anyone who isn't a moderator. It generates an entry both in the edit history of the element and the troper in question. This element is automatically excluded from queries.
* Change Play: For examples, it allows the Playing With status of an example to be changed.
* Edit: Obvious.
* Delete: Available for moderators on most elements save for Settings and Title, it automatically hides the element text and its history behind a splash page "Element X was deleted by Y on date Z for reason: A" for anyone who isn't a moderator.
Changed line(s) 136 (click to see context) from:
* Lock: Done by moderators .It generates an entry both in the edit history of the element and the troper in question.
to:
* History: Obvious.
* Lock: Done bymoderators .moderators. It generates an entry both in the edit history of the element and the troper in question.
* Lock: Done by
Changed line(s) 141,142 (click to see context) from:
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". It generates an entry both in the edit history of the element and the troper in question.
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted". It generates an entry both in the edit history of the element and the troper in question.
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted". It generates an entry both in the edit history of the element and the troper in question.
to:
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". It generates delisted".
* Revert: A moderator button which allows older versions of anentry both in the edit history of the element and the troper in question.
to be restored, to prevent
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "notdeleted". It generates an entry both deleted".
Some markups may be allowed only inthe edit history of the element and the troper in question. particular sections. Direct links to elements are excluded from search engines.
* Revert: A moderator button which allows older versions of an
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not
Some markups may be allowed only in
[[folder:Other functions]]
The "New Edits" function needs to be filterable on per-element and per-action (e.g Delete) basis. And perhaps per troper - having two different functions for edit lists is rather pointless.
Related To pages:
* Element ought to be assessed individually by the Related To page. In other words, the page would no longer list wicks on a per-article basis, but on a per-elements one.
* It also should link to the edit page for each section linked to.
* A function to remove "ghost wicks" from there.
* Wicks should be listed by element and page type, not by alphabet.
* There are other requests in various threads, which can be found in the forum search "related" - of course, some might not be feasible for performance reasons.
A function to rename tropers may be desirable, it will need a system in the backend.
A way to have Edit Notices for pages meeting particular criteria?
[[/folder]]
The "New Edits" function needs to be filterable on per-element and per-action (e.g Delete) basis. And perhaps per troper - having two different functions for edit lists is rather pointless.
Related To pages:
* Element ought to be assessed individually by the Related To page. In other words, the page would no longer list wicks on a per-article basis, but on a per-elements one.
* It also should link to the edit page for each section linked to.
* A function to remove "ghost wicks" from there.
* Wicks should be listed by element and page type, not by alphabet.
* There are other requests in various threads, which can be found in the forum search "related" - of course, some might not be feasible for performance reasons.
A function to rename tropers may be desirable, it will need a system in the backend.
A way to have Edit Notices for pages meeting particular criteria?
[[/folder]]
* It checks whether the entry text contains WordCruft, ThisTroper and other problem items. Needs a configuration function.
Changed line(s) 153,154 (click to see context) from:
Aside from standard editing, there are functions associated with elements. Aside from standard edit bans, special bans may apply to both. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
* It needs to check whether the submitted element clashes with a "cascading lock", and reject it if it clashes and is submitted by a non moderator.
* It needs to check whether the submitted element clashes with a "cascading lock", and reject it if it clashes and is submitted by a non moderator.
to:
Aside from standard editing, there are functions associated with elements. Aside from standard edit bans, special bans may apply to both. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
*fallbacks. In the following order:
# For all elements, it needs to check whether they have at least one page they are attached to.
# For examples, it needs to check whether the trope exists; the work existing is not so important.
# It needs to check whether the submitted element clashes with a "cascading lock", and reject it if it clashes and is submitted by a nonmoderator.moderator.
# It checks whether the entry text contains WordCruft, ThisTroper and other problem items. Needs a configuration function.
One idea is to have addexample be only linked from trope pages, to force people to read the description. Also, maybe having a function that can convert free-form text into structured elements is useful. Perhaps reuse the Conversion script?
*
# For all elements, it needs to check whether they have at least one page they are attached to.
# For examples, it needs to check whether the trope exists; the work existing is not so important.
# It needs to check whether the submitted element clashes with a "cascading lock", and reject it if it clashes and is submitted by a non
# It checks whether the entry text contains WordCruft, ThisTroper and other problem items. Needs a configuration function.
One idea is to have addexample be only linked from trope pages, to force people to read the description. Also, maybe having a function that can convert free-form text into structured elements is useful. Perhaps reuse the Conversion script?
* Adaptations and franchises, how to make a hierarchy of them.
* Substitute for commenting out elements?
* Substitute for commenting out elements?
* Createpage restrictions for Administrivia?
* "Curator" user right?
* "Curator" user right?
Changed line(s) 189 (click to see context) from:
* Discussion
to:
* DiscussionDiscussion as well as whether to put a link to it on edit forms
* Laconic as hovertext?
* Meta information: Authors, Genres, Publication for works and Trope Attributes (e.g Appearance Trope, not the same thing as Trope Types in "Settings"). Some could be tied to particular example types in the addexample function.
* Old histories: AKA the old edits by troper, page histories and "combined history". These should be archived in watch-only mode, linked from the appropriate new pages.
* Meta information: Authors, Genres, Publication for works and Trope Attributes (e.g Appearance Trope, not the same thing as Trope Types in "Settings"). Some could be tied to particular example types in the addexample function.
* Old histories: AKA the old edits by troper, page histories and "combined history". These should be archived in watch-only mode, linked from the appropriate new pages.
* Post-expand article size: How many elements of how much length can be parsed before pagination.
* Rotation of images
* Sandbox namespace
* Selective deletion: The deletion system should apply to edit reasons as well, hiding them from non-moderators but still displaying to staff (with the red border and note as mentioned under Deletion, as well as the ability of restoring). Maybe such a system could apply to old versions of elements, hiding the history entries around the deleted version. Same stipulations as before regarding visibility to staff, red border and note/un-deletion ability.
* Sandbox namespace
* Selective deletion: The deletion system should apply to edit reasons as well, hiding them from non-moderators but still displaying to staff (with the red border and note as mentioned under Deletion, as well as the ability of restoring). Maybe such a system could apply to old versions of elements, hiding the history entries around the deleted version. Same stipulations as before regarding visibility to staff, red border and note/un-deletion ability.
* SugarWiki and DarthWiki
Changed line(s) 200 (click to see context) from:
* Votes on images and quotes?
to:
* Examples for nonexistent works
* Votes on images andquotes?quotes?
* How to work with Recap, ImageLinks, Timeline, Fanworks and Useful Notes.
* Votes on images and
* How to work with Recap, ImageLinks, Timeline, Fanworks and Useful Notes.
Is there an issue? Send a MessageReason:
None
%%
%% When adding new elements here, remember to update other sections. Especially per element functions!
%%
%% When adding new elements here, remember to update other sections. Especially per element functions!
%%
Changed line(s) 122 (click to see context) from:
** "Global lock" (elements associated with that article are only moderator editable), "Google ads" (for whether to display Google ads), "Fake redlink" (overriding the blue link colour for [=URLs=] pointing at the article)
to:
** "Global lock" (elements associated with that article are only moderator editable), "Google ads" (for whether to display Google ads), "Fake redlink" (overriding the blue link colour for [=URLs=] pointing at the article)article), "Funky markup" (allowing text colours and strikethrough), "Spoiler tags" (whether to allow spoiler tags on associated elements to work)
Changed line(s) 131 (click to see context) from:
*
to:
* Delete: Available for moderators on most elements save for Settings and Title, it automatically hides the element text and its history behind a splash page "Element X was deleted by Y on date Z for reason: A" for anyone who isn't a moderator. It generates an entry both in the edit history of the element and the troper in question. This element is automatically excluded from queries.
* Delist: Available for everybody on examples, quotes and Analysis, it hides the element from queries, thus also from example and quote lists. A banner named "Element X was delisted by Y on date Z for reason: A" appears above the element. It generates an entry both in the edit history of the element and the troper in question.
* Lock: Done by moderators .It generates an entry both in the edit history of the element and the troper in question.
** A plain lock does prevent non-moderators from modifying the element in question.
** A "cascading lock" (which does not imply a plain lock!) tells the addelement function to not permit to add elements that feature the metadata (elementtype"work+trope combination).
** A button to simultaneously perform "delete" and "cascading lock" - "salt"? - is also good.
* Move: For quote, Analysis, example elements, it allows one to change the trope or work the element is associated with.
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". It generates an entry both in the edit history of the element and the troper in question.
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted". It generates an entry both in the edit history of the element and the troper in question.
* Delist: Available for everybody on examples, quotes and Analysis, it hides the element from queries, thus also from example and quote lists. A banner named "Element X was delisted by Y on date Z for reason: A" appears above the element. It generates an entry both in the edit history of the element and the troper in question.
* Lock: Done by moderators .It generates an entry both in the edit history of the element and the troper in question.
** A plain lock does prevent non-moderators from modifying the element in question.
** A "cascading lock" (which does not imply a plain lock!) tells the addelement function to not permit to add elements that feature the metadata (elementtype"work+trope combination).
** A button to simultaneously perform "delete" and "cascading lock" - "salt"? - is also good.
* Move: For quote, Analysis, example elements, it allows one to change the trope or work the element is associated with.
* Relist: It automatically creates a clone of a delisted element (including its history) but set to "not delisted". It generates an entry both in the edit history of the element and the troper in question.
* Undelete: It automatically creates a clone of a deleted element (including its history) but set to "not deleted". It generates an entry both in the edit history of the element and the troper in question.
Changed line(s) 134,135 (click to see context) from:
[[folder:Save page actions]]
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
to:
[[folder:Save page element edit actions]]
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks. Edit pages are accessible by an unique URL addon to the element ID URL.
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks. Edit pages are accessible by an unique URL addon to the element ID URL.
* For examples, it checks that the trope exists
* For examples, it checks that the example text is sufficiently long
* For examples, it checks that the example text is sufficiently long
* It needs to check whether the submitted element clashes with a "cascading lock", and reject it if it clashes and is submitted by a non moderator.
Changed line(s) 143,155 (click to see context) from:
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* Discussion
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* Spoilers
* Troper pages
* Votes on images and quotes?
* Wicks: Current standard link to URL or internally replaced with an ID?
* WMG and Headscratchers
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* Discussion
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* Spoilers
* Troper pages
* Votes on images and quotes?
* Wicks: Current standard link to URL or internally replaced with an ID?
* WMG and Headscratchers
to:
* Connecting article ID with an URL or several
* Decide on how
# Access to
* Discussion
* How
* How
# The form allows one to
* How to handle character pages?
* Images: Markup things or individual elements?
* Spoilers
* Troper pages
* Votes on images and quotes?
* Wicks: Current standard
# Saving the query generates a list of elements, each of them displayed in edit mode. The initial page contains as many elements as can be a) loaded by a browser and b) as can be saved in one go without causing server lag. If too large, the list should be paginated with
* WMG
# Each element can be edited (during the save process, unedited elements are not alterated) and
# Each page has a Save button and an edit reason input box. Saving causes all the elements be modified if they were edited or some action was selected, using the input edit reason. The other pages part of the paginated query can be edited/modified afterwards (the save affects only the elements on a particular pagination, not all queried elements).
Added DiffLines:
[[folder:Convert]]
Presumably, we'll write a script that will go through all current wiki articles and convert them into the new database structure. For a substantial percentage of articles, there will be markup that an automated parser is not able to understand. How shall we deal with this problem?
The proposal:
* Don't convert everything all at once. Instead, the new and old designs will run parallel for a while.
* Articles will be, over time, entered (automatically or manually?) into a transport queue.
* The agent driving the queue will come up with a "confidence" value indicating how much of the content was successfully converted.
* Articles over a certain confidence value will get converted automatically.
* Articles below this confidence value will be flagged for user attention.
* Articles in the queue should be automatically locked to (a) prevent data conflicts, (b) encourage editors to participate in the conversion process.
* User attention would involve any/all of:
** Cancelling the conversion to spend more time cleaning the article.
** Correcting the article's destination (example: subpages merging with main article, proper medium tags for works, etc.).
** Fixing markup in the article that is not recognized by the parser.
* When an article is converted, the existing article is removed from view, automatically redirects to the new article, and generates a HTTP 301 code for referrers.
** The old content should be archived in case a reversion (or re-conversion) is needed.
** The old history and discussion pages would be archived in a read-only mode.
* Converted articles would contain an "unconverted markup" section that would show any markup that was not successfully transported.
* In the conversion queue, prioritize high level docum
[[/folder]]
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* Discussion
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* Page creation: When to trigger it
* Administrivia/PermanentRedLinkClub: How to enforce it?
* Administrivia/PermanentRedLinkClub: Allow examples from works in there?
* Report function
* Spoilers
* Troper pages
* Votes on images and quotes?
* Wicks: Current standard link to URL or internally replaced with an ID?
* WMG and Headscratchers
[[/folder]]
Is there an issue? Send a MessageReason:
None
[[folder:URLs]]
Article linking (URL construction and querying)
In the new system, an article will have an internal ID value that forms its permanent URL. Examples: http://tvtropes.org/wiki/3885774 = The Lord of the Rings, Literature. http://tvtropes.org/wiki/549437 = Big Bad.
All other wiki URLs, other than to static objects like AskTheTropers, will be treated as database queries. These queries will contain parameter elements that identify the search terms. Certain parameter elements will also modify the display of the article, such as sorting, filtering, subpage display, etc.
A “human friendly” URL will contain textual parameter elements separated by slashes, which the parser will take a “best guess” at, returning the element with the highest probability if there are insufficient secondary matches, or a list of elements that the user must choose from if the ambiguity is above a certain threshold.
Human-readable default URL
All articles should have a human-readable default URL that contains all the information needed to uniquely disambiguate it. The wick component (everything after http://tvtropes.org/wiki) would be used in the editor instead of the ID to avoid confusion.
Complex URLs
The expanded destination URL will look something like http://tvtropes.org/wiki/search.php. May have synonyms.
Search parameters may include any of the following:
id Article ID. If found and valid, this will generate an exclusive result.
title (t) Article title. This will generate a fuzzy query against the title repository.
type Article type. Allows “trope”, “work”, “character”, “admin”, etc.
medium (m) Medium. Reference against medium index, smart enough to understand nesting.
genre (g) Genre. Reference against genre index, smart enough to understand nesting.
author (a) Author. Reference against Creator articles related to work page.
year (y) Publication year.
Presentation parameters may include any of the following:
subpage (sub) Subpage -- could be YMMV, WMG, Characters, or any supported subpage filter.
filter (f) Synonym for subpage.
sort (s) Sort -- choose from sort options (alpha, date added, date modified)
group (grp) Group -- choose grouping: medium, genre, trope category, etc.
page (p) Page number in a paginated article.
length (l) Number of examples listed on each page.
view (v) Read (default), Edit, Comments, Images, Quotes, History
Examples of complex URLs:
http://tvtropes.org/wiki/search.php?id=3885774
Resolves uniquely to The Lord of the Rings, Literature
http://tvtropes.org/wiki/search.php?title=The%20Lord%20of%20%the%20Rings
Finds multiple hits, shows disambiguation or franchise landing page if available.
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&a=Tolkien
Titles without spaces are acceptable in URLs, so are partial names of authors. This will resolve to the LOTR book article.
http://tvtropes.org/wiki/search.php?id=3885774&grp=tropecategory&l=50
This will return the LOTR article with 50 examples per page, grouped by trope category (plot, character, production, etc.)
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&y=1954&v=Comments
This will return the LOTR literature article in the Comments view.
http://tvtropes.org/wiki/search.php?t=BigBad&type=trope
This will find the Big Bad trope article.
Friendly URLs
The wiki parser should also understand URLs submitted in a more reader friendly format, using fuzzy logic to handle them. Rather than using parameter elements, forward slashes will separate terms that will be fed to a search engine.
Examples of friendly URLs and handling:
http://tvtropes.org/wiki/LordOfTheRings
URLs with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
http://tvtropes.org/wiki/LordOfTheRings/film
URLs with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
http://tvtropes.org/wiki/LordOfTheRings/1955
This will match one of the publication dates of the original LOTR books and so will resolve to the literature page.
http://tvtropes.org/wiki/LordOfTheRings/edit
This will recognize the ‘edit’ keyword asking for the page to be shown in edit mode.
http://tvtropes.org/wiki/Literature/LordOfTheRings/Characters/Legolas
This will find the Lord of the Rings literature article, open it to the Characters view, and drill down to the tropes associated with the character Legolas.
http://tvtropes.org/wiki/Characters/Legolas
This will arrive at (a) the work-agnostic general article for the character Legolas, (b) a disambiguation page showing all matching character articles, (c) the Lord of the Rings character, Legolas, if there is only one such entry.
Search and Indexing
It should be possible to enter queries without a title element; this would be interpreted as an index search.
http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
Both of these queries will enumerate all works in the Fantasy genre and the Literature medium published between 1950 and 1959.
Note that some degree of prioritization is implied in the “fuzzy” searches; it will be necessary to rank indexes higher than tropes and works, for example.
[[/folder]]
Article linking (URL construction and querying)
In the new system, an article will have an internal ID value that forms its permanent URL. Examples: http://tvtropes.org/wiki/3885774 = The Lord of the Rings, Literature. http://tvtropes.org/wiki/549437 = Big Bad.
All other wiki URLs, other than to static objects like AskTheTropers, will be treated as database queries. These queries will contain parameter elements that identify the search terms. Certain parameter elements will also modify the display of the article, such as sorting, filtering, subpage display, etc.
A “human friendly” URL will contain textual parameter elements separated by slashes, which the parser will take a “best guess” at, returning the element with the highest probability if there are insufficient secondary matches, or a list of elements that the user must choose from if the ambiguity is above a certain threshold.
Human-readable default URL
All articles should have a human-readable default URL that contains all the information needed to uniquely disambiguate it. The wick component (everything after http://tvtropes.org/wiki) would be used in the editor instead of the ID to avoid confusion.
Complex URLs
The expanded destination URL will look something like http://tvtropes.org/wiki/search.php. May have synonyms.
Search parameters may include any of the following:
id Article ID. If found and valid, this will generate an exclusive result.
title (t) Article title. This will generate a fuzzy query against the title repository.
type Article type. Allows “trope”, “work”, “character”, “admin”, etc.
medium (m) Medium. Reference against medium index, smart enough to understand nesting.
genre (g) Genre. Reference against genre index, smart enough to understand nesting.
author (a) Author. Reference against Creator articles related to work page.
year (y) Publication year.
Presentation parameters may include any of the following:
subpage (sub) Subpage -- could be YMMV, WMG, Characters, or any supported subpage filter.
filter (f) Synonym for subpage.
sort (s) Sort -- choose from sort options (alpha, date added, date modified)
group (grp) Group -- choose grouping: medium, genre, trope category, etc.
page (p) Page number in a paginated article.
length (l) Number of examples listed on each page.
view (v) Read (default), Edit, Comments, Images, Quotes, History
Examples of complex URLs:
http://tvtropes.org/wiki/search.php?id=3885774
Resolves uniquely to The Lord of the Rings, Literature
http://tvtropes.org/wiki/search.php?title=The%20Lord%20of%20%the%20Rings
Finds multiple hits, shows disambiguation or franchise landing page if available.
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&a=Tolkien
Titles without spaces are acceptable in URLs, so are partial names of authors. This will resolve to the LOTR book article.
http://tvtropes.org/wiki/search.php?id=3885774&grp=tropecategory&l=50
This will return the LOTR article with 50 examples per page, grouped by trope category (plot, character, production, etc.)
http://tvtropes.org/wiki/search.php?t=LordOfTheRings&y=1954&v=Comments
This will return the LOTR literature article in the Comments view.
http://tvtropes.org/wiki/search.php?t=BigBad&type=trope
This will find the Big Bad trope article.
Friendly URLs
The wiki parser should also understand URLs submitted in a more reader friendly format, using fuzzy logic to handle them. Rather than using parameter elements, forward slashes will separate terms that will be fed to a search engine.
Examples of friendly URLs and handling:
http://tvtropes.org/wiki/LordOfTheRings
URLs with a single text object will assume a title search. This will resolve to a disambiguation page or a franchise landing page.
http://tvtropes.org/wiki/LordOfTheRings/film
URLs with two components will assume one to be the title and the other to be an author, genre, type, medium, or year keyword. This will find two hits: the Bakshi animated film and the Jackson live action film, and generate a disambiguation.
http://tvtropes.org/wiki/LordOfTheRings/1955
This will match one of the publication dates of the original LOTR books and so will resolve to the literature page.
http://tvtropes.org/wiki/LordOfTheRings/edit
This will recognize the ‘edit’ keyword asking for the page to be shown in edit mode.
http://tvtropes.org/wiki/Literature/LordOfTheRings/Characters/Legolas
This will find the Lord of the Rings literature article, open it to the Characters view, and drill down to the tropes associated with the character Legolas.
http://tvtropes.org/wiki/Characters/Legolas
This will arrive at (a) the work-agnostic general article for the character Legolas, (b) a disambiguation page showing all matching character articles, (c) the Lord of the Rings character, Legolas, if there is only one such entry.
Search and Indexing
It should be possible to enter queries without a title element; this would be interpreted as an index search.
http://tvtropes.org/wiki/search.php?genre=Fantasy&medium=Literature&year=1950-1959
http://tvtropes.org/wiki/Fantasy/Literature/1950-1959
Both of these queries will enumerate all works in the Fantasy genre and the Literature medium published between 1950 and 1959.
Note that some degree of prioritization is implied in the “fuzzy” searches; it will be necessary to rank indexes higher than tropes and works, for example.
[[/folder]]
Changed line(s) 23 (click to see context) from:
When asked to render an URL, the wiki software would first attempt to resolve it to a unique ID. If it cannot, it would present the user with a disambiguation prompt. Each article has an ID associated with it that is "occupied" during article creation. This ID connects all elements belonging to this article, when a page is parsed a query calls all these elements and the parser assembles the final HTML. This HTML may be cached so that it doesn't need to be re-parsed with each request. Several types exist, all with particular element types that can be associated with them:
to:
When asked to render an URL, the wiki software would first attempt to resolve it to a unique ID. If it cannot, it would present the user with a disambiguation prompt. Each article has an ID associated with it that is "occupied" during article creation. This ID connects all elements belonging to this article, when a page is parsed a query calls all these elements and the parser assembles the final HTML. This HTML may be cached so that it doesn't need to be re-parsed with each request. Several types exist, all with particular element types that can be associated with them:
RealLife will be a special work page, with additional restrictions.
Changed line(s) 50 (click to see context) from:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances)
to:
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances)appearances) and "RealLife examples allowed?" (implements Administrivia/NoRealLifeExamplesPlease)
Changed line(s) 52 (click to see context) from:
* Title: One for each page, only moderator editable is created during page creation. It contains the appearance of the article title (similar to a CustomTitle).
to:
* Title: One for each page, is created during page creation and only moderator editable is created during page creation.afterwards. It contains the appearance of the article title (similar to a CustomTitle).
Changed line(s) 55,62 (click to see context) from:
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* WMG and Headscratchers
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* WMG and Headscratchers
to:
* Connecting article ID
Aside from standard editing, there are functions associated with
* Decide on how
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* WMG
*
Added DiffLines:
[[folder:Save page actions]]
Aside from standard editing, there are functions associated with elements. They are all subject to locks and edit bans. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
* It checks any added links that they resolve to an unique function
[[/folder]]
[[folder:Createpage and createlement actions]]
Aside from standard editing, there are functions associated with elements. Aside from standard edit bans, special bans may apply to both. Some functions will be assisted with AJAX (e.g ) but there will be non-scripting fallbacks.
[[/folder]]
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* Discussion
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* Spoilers
* Troper pages
* Votes on images and quotes?
* Wicks: Current standard link to URL or internally replaced with an ID?
* WMG and Headscratchers
[[/folder]]
Is there an issue? Send a MessageReason:
None
Changed line(s) 3 (click to see context) from:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects.
to:
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects. Each of these objects is editable and has a history associated with it, similar to how pages work today. It is also called "relational database"
[[foldercontrol]]
[[folder:Core concept]]
* This system allows pages to be generated dynamically and thus according to troper preferences.
* Indexing, media tags, and other meta-data expressed as relationships.
* Relationships between wiki objects in code rather than in text.
[[/folder]]
[[folder:Purpose]]
* Tropes and works are now identified by an ID rather than by their name, which should facilitate renames.
* Many editing rules (e.g natter or Administrivia/WhatGoesWhereOnTheWiki) will be enforceable by the software rather than by hand.
* This would allow pages to be filtered, sorted and grouped dynamically, also allowing for pagination of long pages.
* Actions (e.g editing, cutting) can be done now on a per-object basis without the need to apply them to the whole page.
* Articles would no longer be at hardcoded text URLs; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
* Article subpages would no longer be hardcoded but rather based on the user’s filtering selection. Certain types of subpages could have predefined style/layout.
[[/folder]]
[[folder:Article/Page]]
When asked to render an URL, the wiki software would first attempt to resolve it to a unique ID. If it cannot, it would present the user with a disambiguation prompt. Each article has an ID associated with it that is "occupied" during article creation. This ID connects all elements belonging to this article, when a page is parsed a query calls all these elements and the parser assembles the final HTML. This HTML may be cached so that it doesn't need to be re-parsed with each request. Several types exist, all with particular element types that can be associated with them:
* Administrivia (Just a description element)
* Trope.
* Work.
Then the wiki would gather all the relational elements of the article and assemble them.
* The displayed title would be the Title element identified.
* The header would contain a set of controls to visit its related sub-elements. For example, if an article has an associated Analysis text element, it would be available to click on. This is similar to current buttons. The header would contain an automatically generated subpage filter for examples. For example, if there are any examples on a work article linked to tropes flagged as YMMV, then those would not appear on the main article display, but instead there would be a “YMMV” filter available to select.
* For articles that are parents (they index child articles, as a trope index, author index, etc.; they have child relationships such as a franchise with sub-works or a serial work with episode/volume articles), a list of child articles will be displayed. This should be collapsible and sortable. Some form of control over the organization of the list may be useful, as would some form of nesting.
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples.
(Note: Discuss how/whether to automatically folderize work articles.)
* Examples would be automatically indented as appropriate. When more than one example for a trope/work is present, the nested examples should be organized by the relationship hierarchy (see below for more).
* At the top of the examples section, sorting and filtering controls would be present. Possible sorts: alphabetical, by medium (for trope articles), by trope category (for work articles), by character (for work articles), by date added, etc.
* In the footer of the article, additional [=URLs=] would be shown along with the Stinger text element, if present.
[[/folder]]
[[folder:Objects, also named "elements"]]
Each of these is created either during page creation or by an addelement function. Individual elements each have an ID that cannot be reused. They have a history page and an edit page associated with them.
* Analysis: Several per page, can be created by an addelement function.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" a page.
* Example: These contain example text and are connected each to a trope and a work.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic.
* Quote: Formatted like quotations, these hold quotes. Each is attached to a trope ''or'' work.
* Settings: One of each exists for each page/article and is created during page creation. By default only editable by moderators, it includes all per-page settings:
** "Global lock" (elements associated with that article are only moderator editable), "Google ads" (for whether to display Google ads), "Fake redlink" (overriding the blue link colour for [=URLs=] pointing at the article)
** For works, "Published" (for DarthWiki/UnpublishedWorks, disables crosswicks)
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances)
* Stinger: One for each page, is an optional element that can be added. Each page can only have one visible stinger element.
* Title: One for each page, only moderator editable is created during page creation. It contains the appearance of the article title (similar to a CustomTitle).
[[/folder]]
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* WMG and Headscratchers
[[/folder]]
----
[[foldercontrol]]
[[folder:Core concept]]
* This system allows pages to be generated dynamically and thus according to troper preferences.
* Indexing, media tags, and other meta-data expressed as relationships.
* Relationships between wiki objects in code rather than in text.
[[/folder]]
[[folder:Purpose]]
* Tropes and works are now identified by an ID rather than by their name, which should facilitate renames.
* Many editing rules (e.g natter or Administrivia/WhatGoesWhereOnTheWiki) will be enforceable by the software rather than by hand.
* This would allow pages to be filtered, sorted and grouped dynamically, also allowing for pagination of long pages.
* Actions (e.g editing, cutting) can be done now on a per-object basis without the need to apply them to the whole page.
* Articles would no longer be at hardcoded text URLs; rather, the parser would take a submitted URL and treat it as a database query, looking up the closest match. Disambiguation and prioritization would be automatic.
* Article subpages would no longer be hardcoded but rather based on the user’s filtering selection. Certain types of subpages could have predefined style/layout.
[[/folder]]
[[folder:Article/Page]]
When asked to render an URL, the wiki software would first attempt to resolve it to a unique ID. If it cannot, it would present the user with a disambiguation prompt. Each article has an ID associated with it that is "occupied" during article creation. This ID connects all elements belonging to this article, when a page is parsed a query calls all these elements and the parser assembles the final HTML. This HTML may be cached so that it doesn't need to be re-parsed with each request. Several types exist, all with particular element types that can be associated with them:
* Administrivia (Just a description element)
* Trope.
* Work.
Then the wiki would gather all the relational elements of the article and assemble them.
* The displayed title would be the Title element identified.
* The header would contain a set of controls to visit its related sub-elements. For example, if an article has an associated Analysis text element, it would be available to click on. This is similar to current buttons. The header would contain an automatically generated subpage filter for examples. For example, if there are any examples on a work article linked to tropes flagged as YMMV, then those would not appear on the main article display, but instead there would be a “YMMV” filter available to select.
* For articles that are parents (they index child articles, as a trope index, author index, etc.; they have child relationships such as a franchise with sub-works or a serial work with episode/volume articles), a list of child articles will be displayed. This should be collapsible and sortable. Some form of control over the organization of the list may be useful, as would some form of nesting.
* In the examples section (if that section is not hidden by mod control), up to [X] examples would be shown based on defaults and/or the user’s preferences. If more than [X] examples are present, pagination controls would appear. Folders would appear for tropes based on the medium categories of the works linked to its examples.
(Note: Discuss how/whether to automatically folderize work articles.)
* Examples would be automatically indented as appropriate. When more than one example for a trope/work is present, the nested examples should be organized by the relationship hierarchy (see below for more).
* At the top of the examples section, sorting and filtering controls would be present. Possible sorts: alphabetical, by medium (for trope articles), by trope category (for work articles), by character (for work articles), by date added, etc.
* In the footer of the article, additional [=URLs=] would be shown along with the Stinger text element, if present.
[[/folder]]
[[folder:Objects, also named "elements"]]
Each of these is created either during page creation or by an addelement function. Individual elements each have an ID that cannot be reused. They have a history page and an edit page associated with them.
* Analysis: Several per page, can be created by an addelement function.
* Description: One per page, contains the description text and is created during page creation. Deleting a description is what "cuts" a page.
* Example: These contain example text and are connected each to a trope and a work.
* Laconic: One per page, can be created during page creation or elsetime, displays a laconic.
* Quote: Formatted like quotations, these hold quotes. Each is attached to a trope ''or'' work.
* Settings: One of each exists for each page/article and is created during page creation. By default only editable by moderators, it includes all per-page settings:
** "Global lock" (elements associated with that article are only moderator editable), "Google ads" (for whether to display Google ads), "Fake redlink" (overriding the blue link colour for [=URLs=] pointing at the article)
** For works, "Published" (for DarthWiki/UnpublishedWorks, disables crosswicks)
** For tropes, "Trope" (AudienceReaction, ExampleSectionectomy, FlameBait, Trivia, Trope, UsefulNotes; each controls the appearance and induces filtering in default appearances)
* Stinger: One for each page, is an optional element that can be added. Each page can only have one visible stinger element.
* Title: One for each page, only moderator editable is created during page creation. It contains the appearance of the article title (similar to a CustomTitle).
[[/folder]]
[[folder:Open questions]]
* Connecting article ID with an URL or several
* Decide on how to handle languages.
* How to handle creator pages?
* How to handle indexing?
* How to handle character pages?
* Images: Markup things or individual elements?
* WMG and Headscratchers
[[/folder]]
----
Is there an issue? Send a MessageReason:
None
Added DiffLines:
2.0 is the name of a planned overhaul of the TVTropes database and page handling systems.
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects.
The key concept is that where nowadays pages are each one database object, in the future system they will instead be assembled from many database objects.
