Board Thread:New Features/@comment-20644-20170522203248/@comment-28083312-20170529174103

Technobliterator wrote: And none of them respond to the content at all. It's just "q_q customization going away", then whining about a slippery slope and how customization makes wikis special. I'm fairly sure Fandom Staff know that that's the case, but as the thread stated, there are very clear reasons why CSS and JS, as well as fourth/fifth level navigations, do not make sense anymore (btw, it's extremely easy to make a font for a wiki and use CSS to prevent the font affecting the top nav or the bottom of pages). The content, if you cared to read it again, was “X, Y, Z practices (basically extended navs) cause reader frustration & drive readers away & standard experiences drive views up”. That’s fine, totally understandable, but if you’d noticed, most of the replies begrudgingly accept that JS is barred but are asking why CSS is a problem. Fandom said that disrupting the usual functionality causes issues for readers; I accept that. What I don’t accept, & what Fandom has not explained, is how custom CSS disrupts the usual functionality. THAT is the crux of what people are asking after which you have either studiously ignored or reduced to mewling, childish bickering because you didn’t find it convenient to address it. Technobliterator wrote: Of course not, but do you not see how, when you fail to interpret the other point of view… Oh please. You’re the one who’s talking past everyone, while we’ve acknowledged Fandom’s points about JavaScript & are simply asking after CSS. Technobliterator wrote: …and basically rage post about customization just because of the removal of one feature, you will rarely ever receive a response? This is standard Community Central practice, they flip out over the removal any tiny customization feature lost, even if they demonstrate very clearly how said feature is actually a detriment to the wiki, and entitled users complain about "no, we'd rather keep it and drive readers away, also remove all ads and let us remove the Fandom banner". Again, as SuperRobot9338 said, they nor you have demonstrated how CSS is the problem. I agree that viewership is important & that’s why I’m more than happy to let JS go in this instance, but CSS doesn’t disrupt that. There’s no sense in removing it. In fact, if the lower Wiki is heavily unique, then the Header would clash with the Wiki below & admins would either be forced to adapt the Wiki to the Header or live with an eyesore. The Header being cut off from CSS is more far-reaching than you say. Technobliterator wrote: After this, they collectively barrage a thread with dozens of responses (often including flaming), whine about some "corporate dystopia" in which Fandom has control over everything, and turn around and claim they have "community support" and that therefore staff should give into their (often unreasonable) demands. Not a few hours ago you compared everyone’s legitimate complaints to irrational children, yet you have the audacity to complain about flaming. Have your cake or eat it. As for the Community Support bit; if Fandom didn’t want democracies insisting on their rights, then they shouldn’t have encouraged & propagated the notion that Wikis are ruled by their communities. Either it’s true or it isn’t, but saying it is true while acting like it isn’t won’t exactly discourage these events from happening. Technobliterator wrote: It's happened every time for the past few years and it's why I wish Fandom didn't even announce things to Central and just went ahead and made the changes anyway. You're not going to get any constructive feedback here. There is a difference between a void of constructive criticism & willfully discarding it. You & I both know that you, I, other Councilors, & users on the blog have mentioned other things they wanted in the headers (an option to replace the wordmark or remove it, separate theme designer controls for its color, a dropdown on the Discuss button containing links to specific categories, cascading CSS, et cetera). You know this, for you have been involved in these conversations! How about you stop sweeping everyone who disagrees with you under the rug & actually consider their statements? Even if the others are “whining,” they are still worth your ear because these are the people who work their butts off to make the best of their communities just like you do, & thereby provide revenue to Fandom & make Fandom a greater place. They’re complaining about the loss of CSS because it follows a trend of removal, because it restricts their community expression, & because it’s important to them.