Spring website

[AF]

and why are all the headings prefixed by bullet characters?

H1 should be bigger than h2, instead what we have is h2 has more dots than h1, lolwut?

Add more padding/margins around headers, make h1 bigger, h2 a little bigger, h3 the same, and italicize h4.

Proper padding underneath <p> tags too

Code: Select all

p { margin-bottom: 10px; }

No stupid header text shadow, it should look the same everywhere, and no Bold text, if the text was styled properly none of it would be necessary

And why has the table of contents been shunted tot he top with its background removed hovering over the page overlapping with bits of it too? If this is a joke that someones decided to pull or they actually think it looks fine, *facepalm* it looks horrific, like someone has torn out half the code for it and forgot to put it back.

[Forboding Angel]

Changes are being made to the spring wiki css, however, I have noticed something:

Springnew.php

- $s .= "<div id='article' style='width:738px; overflow: hidden;'><br />";
+ $s .= "<div id='article'><br />";

What response do I give to this and any mention of this tag in the wiki pages themselves be they a wiki page or the template assembling it?

no no no no nO NO NO NO NO NO NOOOOOO NOOOO

NEVER use <br>, especially for formatting and layout purposes. This small br will look slightly different on eveyr browser and its unsemantic and means css changes require php changes to change interfering markup.

it would be far better to simply add #article { padding-top:10px; } or something along those lines

php makes content
html marks up content
css styles and lays out the content
javascript builds functionality ontop

It's worth noting that the <br /> tag will look the same on firefox and IE8. IE6 and 7 bugger it up something awful though.

[AF]

You should never need to use the <br> tag in the first place. Use <p>text</p> instead, and let the css sort out spacing.

[FLOZi]

<br/> owns your ridiculous face

[AF]

Id like to purchase it back, I have many cheeseburgers

[aegis]

feel free to correct spring's wiki styling to something sane

guess what, it also uses epic inline tables for layout.

[Forboding Angel]

Depends on whether random newlines can be added via the editor or not. Sometimes <br /> is absolutely necessary. Or you can always go the hacky way and use <p>&nbsp;</p>

[aegis]

pressing enter in mediawiki works well enough.

[AF]

<br> is unnecessary, it should never appear in markup, purely css styling should suffice, any html markup should be structural, it should not be directly used for formatting purposes.

[Forboding Angel]

That isn't always the case AF. But this is a silly thing to argue about. Is that you restyling the wiki? Looks fanfuckintastic!

[AF]

That isn't always the case AF. But this is a silly thing to argue about. Is that you restyling the wiki? Looks fanfuckintastic!

• No it is JK
• Readability has not increased
• Text is still cramped as hell
• <BR> should never be used and if it is necessary then your not using the markup properly.
• Tables of contents are still shunted up in the corner, so they arent visible, stretch the page past 1024px and the table of contents jumps out of the page and into the top right corner with no background overlaid over the rest of the page
• More unnecessary markup e.g. <h1><span>text</span></h1>

I would work on this website, but in the past reason has fallen to fads and gimmickery, as such there is no incentive to invest when that effort is unlikely to even be used.

[Forboding Angel]

I think it's a lot more readable. It's a fucking wiki! What do you expect? Wiki's dont exactly lend themselves to the most layout friendly thing around.

About about br. <p>&nbsp;</p> Does the exact same thing. DId I meantion that arguing about br is retarded? Also, your taking xhtml standards a little too seriously buddy , yes a good thing to follow, but if you have to deviate a little bit, the world isn't going to fall apart.

Span tags are valid xhtml if they are used on line elements. Now, if they are used on every line element in order to style something (in other words, if all your headers and subheaders and titles are wrapped in a <span>), ur doin it rong, that's css territory, but if you're styling a single line of text that needs to be different from any of the rest then there is nothing wrong with that.

[jK]

That isn't always the case AF. But this is a silly thing to argue about. Is that you restyling the wiki? Looks fanfuckintastic!

• No it is JK
• Readability has not increased
• Text is still cramped as hell
• <BR> should never be used and if it is necessary then your not using the markup properly.
• Tables of contents are still shunted up in the corner, so they arent visible, stretch the page past 1024px and the table of contents jumps out of the page and into the top right corner with no background overlaid over the rest of the page
• More unnecessary markup e.g. <h1><span>text</span></h1>

I would work on this website, but in the past reason has fallen to fads and gimmickery, as such there is no incentive to invest when that effort is unlikely to even be used.

you are an evil man -_-

[AF]

All the headings are, although this appears to be a quirk of the template and media wiki if anything.

However the wiki has not become more readable. Cues have been added to cover up the lack of readability, aka signposts in a dump, but no improvement to basic readability. May I note that the error in the table of contents is still present?

As for br and the like, I am not referring to the xhtml standards. I see references to the br tag all over the place in the web design world. It is 'unsemantic' and generally a pain.

I could go into a huge list of horrific problems that increase processing time at the server end and browser end, cross-browser issues, dodgy javascript, css, html markup, a tonne of unoptimized stuff, and blatant overuse of bandwidth (mobile broadband? mobile phones?).

I can fix these, quite a number of people on this forum can, but why should we? There is no incentive.