Board Thread:Consensus Track/@comment-27797856-20160328140628/@comment-27797856-20160329203243

I'm suggesting removing them to avoid repetitive portrayal of information, not because I dislike them. I made it pretty clear that my intention is to expand the ability section, not to remove features, but you keep ignoring that.

"Consensus" is a word that can be used very loosely here: To start with, your templates were implemented against the consensus in the first place. (But please, let's not get off topic, it's not the time nor the place for angst...)

Can you name other wikis that focus on manga material that use collapsible tables nowadays? Then the entire argument about Narutopedia would be null and void. The wikis for the most popular manga nowadays don't use the collapsible tables at all: eg. Fairy Tail, Magi, Attack on Titan, even the predecessor - Soul Eater (which is what we should strive to be in the first place).

Gou is asking for testing time and he has the full right to ask that. It's a new feature that allows us, mainspace editors, to edit more efficiently and not pick straws and use repetitive information to make ability sections longer so that we could fit in a single picture.

If anything, we can write the quo as Image Policy guidelines; Saru perfectly enforces them, so there wouldn't be much of an issue.

Not that your opinion doesn't matter, Sajuuk, of course it does but on top of the fact that you mentioned in the chat that you had zero interest in the topic combined with your lack on mainspace editing (which is what this consensus is directed towards) doesn't put much value in your words: Every wiki functions differently, every experience is different.

Edit: I think we're focusing more on removing the collapsible tables, which shouldn't be the focus of our discussion.

Picture fights happen. So what? That doesn't mean that pictures have to be stripped from the wiki entirely. We need longer sections and if this way allows us to achieve that, we should strive for it. If we come up with a better solution in the future, we'll go with that.