As your friendly neighborhood Admin Team, the gang here at TVTropes HQ is always working to improve the site.
Many of those improvements begin with suggestions posted right here, on the Community Wishlist. Is there a feature you really want on TVTropes? Post it.
Is there something we could be doing better? We want to know. Do you think we look fat in these pants? We were totally afraid of that. See a bug? Report it.
Important things to know:
- We're all about that content-creation life! The top contenders for our attention are ideas that'll create more content, like the video uploading feature, or speed up launching new pages. On the flip side, design or layout tweaks won't be our top priority.
- Help us dig through the goldmine of old wishlist items! If you have an old request gathering dust or spot one you're totally on board with, give it a bump and a like. There's a treasure trove of 6+ years' worth of ideas just waiting to be rediscovered. Items without enough love may not make the cut and will be closed.
- Was your wishlist item locked up without an explanation? It was most likely disapproved or just too big of a task versus the benefit it would ultimately have. Time is precious, and we want to focus on updates with the biggest bang for the buck. Don't be discouraged though! We appreciate every idea and we're always listening.
Make a Tech Wish:
openGive subpages Darth Wiki skin
He Panned It, Now He Sucks! is now on Darth Wiki per TRS, so it’s subpages should probably have the Darth Wiki skin.
Edit: They should have the Flame Bait banner too.
Edited by LymantriaopenCut invalid sandboxes
At present there are two sandboxes on this wiki with spaces in front of their names. I presume both of them were made before such page names were made invalid. These sandboxes still technically exist on the site, but attempting to access either of them produces an error.
Can the admins cut both sandboxes, please?
openAllow replacement of your own approved video with a better version without deleting the whole thing.
There are at least a few video examples of mine I want to replace with a higher quality version, but well, since they have so many votes on them and some of them are nostalgic to me due to them being some of the first ones I have uploaded and I don’t want to lose all that. Additionally, it would be easier than having to get it approved again. Some of them also didn’t have a higher quality version I could find at the time, and now I would like to fix that. I hope I explained it well as I genuinely tried my best here to explain it.
Edited by Pokemon439openReverse-flagging tool to stop revenge-reporting
Moderators could have access to a checkbox/button which disables the "This page may violate the Content Policy" checkbox in the report page dialog, to be used for pages which have already been reviewed.
So for a page like Cuties (which has been revenge-reported three times within twenty four hours by now-bounced users), the idea is that simply ticking the box would stop the revenge-reporting entirely.
Relevant discussion starts here.
openInclude hypen to special characters
Boop-Oop-a-Doop was made despite hypens in wikiword being forbidden, and we also have a list at Hyphenated Titles. I was wondering if an empty page has hypens in the wikiword, allow editing existing pages for now, but block creating a new page.
openCustom message on pages in the PermanentRedLinkClub
Right now pages in the Permanent Redlink Club use the default "no page yet" message that invites people to create them.
To reduce the confusion and make the situation absolutely clear to readers, there should be a custom message for these pages.
Edited by henke37openAutomatically follow a discussion page when following a page
It would be handy and help promote the use of discussion pages if following a wiki page automatically added its discussion page to your watchlist, since otherwise you'd have to remember to follow the discussion page separately to be notified of new discussion on your watchlist.
You could still choose whether to follow just the wiki page or just the discussion page, same as under the current system, it's just that the discussion page would be an "opt out" option when following the wiki page, rather than an "opt in" option.
openMessage on Headscratchers/ discussion pages
I often see inexperienced editors post headscratchers on the discussion page for Headscratchers/ rather then the page itself
I've see mods replying that they should add it to the page since that is where better for organizing, visibility (other editors look more at the page then), etc, etc
So at the top of Headscratchers/ discussion page could be a short bolded message like "Discussion pages are for problems with the page itself, if you want to post a headscratcher please click on the edit page and add it to page itself" just to give them a friendly poke in the right direction
Edited by jormis29openHeadscratchers tutorial
Something like the title idk. I don’t know how to “reply” to people on Headscratchers, I want to answer someone’s questions but I don’t really know how, just make a tutorial for Headscratchers (like how to make questions and reply, that’s about it)
openCustom titles for namespaces used by other languages
For foreign languages, sometimes the correct form of a namespace includes accented characters. Example:
- The Portuguese equivalent namespace for WesternAnimation is BrAnimaçãoOcidental.
- However, the wiki doesn't support special characters in namespaces.
- Due to this, the namespace must be BrAnimacaoOcidental, but it's incorrect.
It's even worse for languages that doesn't use the Latin alphabet.
While we don't get the major update for enabling multi-lingual support for good, I'd like to have a way for setting a custom title for namespaces, like the one we already have for pages.
openWikiword request reasons
Considering unilateral changes aren't too uncommon and get overlooked, I wonder if it'd help to add a "reason" field to Custom WikiWord Request. Modifying the title from a default one is understandable, but changing an already confirmed custom title probably should require some explanation for the mod to judge.
openAdd comment field to Custom WikiWord Requests
I often feel it would be helpful for the mod if users could provide context for why they want to add or change a custom Wikiword title. For example, I may want to change Zero-Approval Gambit to 0% Approval Gambit and let the mod know that it's because it would better align with 0% Approval Rating. Or I want to provide a link to an official source.
It could look something like this:
Edited by eroock
openAdd "Unlaunched" trope as a common edit reason
The rogue/stealth edit reason has been added lately, but when I was cleaning up links from a trope that was unlaunched for unadressed issues (The unlaunched trope's draft), I might think it needs a companion piece or maybe even merge as "Unlaunched" when it comes to unaddressed issues other then being rogue or stealth launched.
openFurther forum improvements
Just throwing a suggestion for future reference. The fixed forum search is good, but could have improved uses:
- Filter to search by forum title only and remove duplicate results (different posts from the same thread), letting users find specific threads, with results giving the opening post.
- Filter to search by posts only, excludes matching with a thread title, just brings up posts where the query is present.
Also, since forum search uses posts text as previews, it may be more helpful to just show the post's user and/or date for visibility, especially since sorting by date is an option by there's no indication which date the posts are posted.
open"Click to see context" also for new entries
We now have a feature to see where an edit to a lower-hierarchy entry belongs via the "Click to see context" button. However, this feature does not work for new entries where it would be equally important to see the context.
openImproved Video Example Features
I would like to see some features added to Video Examples, including: -Subtitles for deaf or hard-of-hearing tropers. -Spoiler Blur/Mute for Video Examples that are spoilers or graphically violent (this means Video Examples won't get rejected for these two reasons), and the blur/mute can be removed either by double-clicking on the video or by signing into TV tropes and turning on "show spoilers", similar to how spoilers in the Trope texts are hidden behind a white-out mark. -The ability to create a Video Examples page for a trope that doesn't currently have one, as opposed to uploading the Video Example for another trope and using the new trope as a secondary trope. -The ability to suggest edits to a Video Example description, sources, and secondary tropes for a Video Example uploaded by someone else.
openMake a TLP draft have its launch button disabled for 7 days before it's launched or nuked
In my opinion, 3 days is too short for a TLP draft to be launched. In some cases, some tropers insist on launching it once the 3 day limitation is lifted without addressing lingering issues. For me, a TLP draft needs 7 days to cook.
Edited by alnair20aug93
Eight years ago, ~SatoshiBakura made a wish for different site colors, which ~kory closed last year, saying we should make a second thread to vote on color changes. Since I'm running a custom stylesheet, I experimented with some colors and I found some that looked good. (All strings preceded by "#" are HTML hex color codes.)
Note: Most of what I wrote is similar to what Satoshi wrote, with some minor fixes for color specifications and stuff like that. I know TV Tropes was redesigned in 2018, so if you see stuff no longer relevant, point it out to me and I'll delete it.
Corollary: I did look at some old 2016/17-era pages on the Wayback Machine, so these colors shouldn't be too screwed up. Also, note that I will post screenshots to demonstrate what I am thinking once more people have seen this post.
Font change
Font: Open Sans (the font I currently run on my userstyle). I'm biased, though. I'll run a comparison and show the screenshots in a bit.Normal Pages
Grey headers: Make them blue (either #004aab, #00204a, or #00306f).As Satoshi said, the primary color of the site is (or used to be) blue.
Negative space: Make it light blue (either #00484d or #00124d).
Footers: Same color as the grey headers (either #004aab, #00204a, or #00306f).
YMMV Pages:
Top header: Make it dark blue (same color as the new headers). Alternatively, make it orange (#ab5f00) again.Grey header: Make it dark blue or orange (#ab5f00). The gray button (formerly green) is OK, I think.
Space around text: Not sure what Satoshi meant by this in 2016.
Negative space: Make it dark grey or light orange (#ff710087)?
Footer: Same color as top header.
Links: Should be orange (#ab5f00 or #ba4500?) when highlighted. (Alternatively, you could make them all orange, but...)
Subpage tabs: The proposal in 2016 was to "make the outlines orange and the words dark blue." I believe that meant the fill for the subpage buttons should be orange and the words dark blue, so, say, #ffb938 for the buttons and #00008d for the words? Alternatively, if we wanted the blue aesthetic, we could do dark blue for the buttons and orange for the wording.
Sugar Wiki:
Top header: In 2016, the proposal would have made the top header blue-green and the "random" button yellow. However, given that the appearance of the website has been updated, something like this might work (#990053 for the header bars). We don't need to worry about the "random" button.Bluish green headers: Not applicable to the 2018-era design.
Negative space: Make it lighter pink.
Links: Should be pink when highlighted. (Alternatively, you can make them all pink, but...)
Nightmare Fuel:
Top header: Make it dark red (#8b0000). Make the red "random media" button black.Space around text: Again, not sure what Satoshi meant or whether its applicable.
Negative space: Make it grey.
What say you?