Board Thread:New Features/@comment-24739709-20150518230347/@comment-24409505-20150607215746

EternalLocket wrote: I've only used CSS on a wiki once or twice, and from what I remember, the response time is not great. So, on top of not allowing regular users the ability to style a template from the original wiki they're on. Adding the styling to the CSS has a bit of a delay.

I'm sorry for being nitpicky, but I think there are some serious misunderstanding here as to what CSS means. It's not just this reply from EternalLocket, but the way many other users responded earlier.

From Wikipedia:
 * Cascading Style Sheets (CSS) is a style sheet language used for describing the look and formatting of a document written in a markup language.

Somehow people describe it like it's some additional tool or feature that people can choose to use (like the Theme Designer) and that has a bad response time. It's not. It's a style sheet language. You don't "add styling to the CSS" (like it's a tool), you style with CSS (the language). When you say you "style a template" within the template page, then you are in fact styling with CSS in the template. Anything you place within  is CSS. Any other way you style things in your template, you most likely do that with CSS.* So if you say you used CSS only once or twice, then that's most likely false. You use it every time you change the styling in the template. And the so-called bad response time? You do use CSS within your template, and yet there's no delay! The "delay" has nothing to do with CSS (the language) at all.

What people are actually talking about is the attachment of CSS into a separate stylesheet as opposed to including it inline in a template. When CSS is served from an external file, it is cached by your browser for performance (in case you didn't get: this is a good thing, as web pages load much faster), but the consequence of caching is that the CSS changes may not show its effects instantly for you (anyone else who didn't have the files cached yet could see the changes without delay).

* Unless you still use the deprecated HTML tags like ...

EternalLocket wrote: From what I can tell, it doesn't register separate tabs correctly, images in templates-or the wiki in general- appear larger than they're meant to be- regardless of what size is set for it, it doesn't register the styling for- not just the template- but the wiki in general.

[...] Are images and styling going to be fixed afterwards? For images, is that a coding problem on the individual wiki's side? Not sure what you mean with "separate tabs". Problems with "images appearing larger in all templates or the wiki in general" don't seem to have anything to do with the new infoboxes, the same with "styling for the wiki in general".