No edit summary |
mNo edit summary |
||
Line 129: | Line 129: | ||
{{Forum post |
{{Forum post |
||
− | |I honestly have no idea why we favored one way over the other to begin with ''or'' how the conflict arose in the first place (I made the first alterations toward what is currently the Creature/Location template way back in 2010 and I just don't recall what my exact reason was). But like Moviesign said it is relatively easy to change: all we'd need to do is either tell the infobox cell to |
+ | |I honestly have no idea why we favored one way over the other to begin with ''or'' how the conflict arose in the first place (I made the first alterations toward what is currently the Creature/Location template way back in 2010 and I just don't recall what my exact reason was). But like Moviesign said it is relatively easy to change: all we'd need to do is either tell the infobox cell to align toward the right or leave it blank (which would align it to the left). |
All that needs to be figured out is basically which we prefer.|[[User:Niirfa-sa|Niirfa-sa]] ([[User talk:Niirfa-sa|talk]]) 05:14, October 17, 2014 (UTC)}} |
All that needs to be figured out is basically which we prefer.|[[User:Niirfa-sa|Niirfa-sa]] ([[User talk:Niirfa-sa|talk]]) 05:14, October 17, 2014 (UTC)}} |
Revision as of 05:15, 17 October 2014
Use the following template for a nicely presented post:
{{Forum post|Write your message here!|~~~~}}
- I think it was mentioned somewhere that the tabber thing doesn't work on mobile devices. I have no idea what this looks like viewed on a phone.
- The infobox changes size dynamically when tabs contain different amounts of content. This may cause the text of an article to re-flow around the box (at least I hope it does, rather then overlap) which could lead to some ugly situations on any given page.
- Putting an infobox inside an infobox makes the text very small. The CSS will probably have to be adjusted so the text isn't so tiny. Oh, and to remove the extra border.
- We may have to make the infobox wider to accommodate the extra padding (which results in lost width) that the tabber puts in.
- It makes a messy template even messier, but damn if that isn't cool.
What do you think, sirs?
Right, now it looks fine in the Oasis skin: the infobox width remains fixed; the length changes, but the text readjusts. In Monobook, however, the width changes and the Basic Information box spills out of the tabber box.
It doesn't work at all in Mobile: no tabs, every edition is shown, 5e, 4e, 3e, 2e, 1e, all at once with a lot of different rows. They're not even labelled by edition.
Does it really need the extra infobox inside? Are the raw tables of before a problem?
I'd rather the infobox wasn't made wider, as the article space is already quite narrow in the Oasis skin, and that would affect the layout of some pages.
Okay, we need to make a decision before I put the effort into adding tabs to our infoboxes. Assuming that it will not work on mobile devices or in monobook for the foreseeable future, should we make this change? I can mitigate the problem for mobile devices by adding a section header for each edition so that the content will at least be divided up for them and look pretty much like the infoboxes look now. Everybody will see the dividers regardless of their viewing platform, unless the CSS has a way to make the distinction between mobile and non-mobile.
I wish Wikia was still maintaining Monobook. It's vastly cleaner, faster, and easier to use than Oasis, and it's my default. But Oasis is the default for everybody who comes to the wiki, and I imagine most members use it now anyway. For that reason, I'd say go ahead. We should use our best features to greet the most users, and that's Oasis.
Infoboxes in Monobook have been bent for a long time: alignment grids are stretched and tables are all spaced out. It's probably a problem specific to Monobook, and I've gotten used to it being funky. Monobook is the probably the domain of stubborn old editors like me, and will probably be removed one day. The Mobile skin, meanwhile, always looks like crap; putting edition headings is sufficient to solve that problem.
We probably should default to the latest edition tab, where there is information present for it.
I'm not planning to add any more color palettes and I think the ones I've worked out at the moment are pretty contrasty (I've actually increased the contrast between the text and the background color to some degree). But if it's still too hard to read I'll look into altering them further.
Other than stylistic stuff, I'm also planning to differentiate the planar creature templates a little bit more in the future, adding a few inputs that are relevant only to creatures from a certain kind of plane or possibly removing some which aren't relevant. I haven't gotten around to that yet though, as my main priority ATM has been adding new material from the 5th edition Player's Handbook.
The conflict is at its most obvious when using the alignment grid, which when placed inside an infobox doesn't follow either guideline by default but instead it's own internal direct to float left or right. I tried disabling the float directive so that it would instead go where the rest of the text does but it doesn't work that way - without a float directive it floats naturally to the left, which makes it out of place in right-aligned templates.
Basically, what it comes down to is do we want infobox cells to be aligned toward the right or the left?
- It requires less coding. Unless told otherwise, infobox cells default to left alignment because that's the way that text normally aligns on English-language websites. As a result, right alignment is something that must be explicitly coded, whereas left alignment is inferred.
- I think it looks neater. With right alignment, there's a large amount of white space in the middle and there's also a tendency for long lines of text like lists to look a bit weird, because the text moves away from the right rather than from the left as is typical in English.
- Nearly all other wikis use left-alignment (including several of our sister wikis like the Baldur's Gate Wiki or the Eberron Wiki). As a general rule I look to other wikis as a model for aesthetics and styling.