cotonti.com : HTML in core - total css-ing

Kort

Нд, 08 Бер 2009 17:42:43 -0000

Using

would cause a lot of redundant HTML-code. This post is about lists mostly, and it would be more logical to simply assign a class to a list (ul) in a skin. This way skinmaker will have much more flexibility and the code will be cleaner.

jslowik

Пт, 27 Лют 2009 05:27:32 -0000

CSS is wonderful. Absolutely yes.

GHengeveld

Пт, 27 Лют 2009 05:18:20 -0000

You could ofcourse give the images a class, so users can use

.someimgclass { display:none; }

(or visibility:hidden, whatever is preferred).

musiconly

Пт, 27 Лют 2009 02:55:55 -0000

In that case, I vote YES

medar

Thu, 26 Лют 2009 18:38:51 -0000

Yes, it is. Standart Cotonti css classes.

musiconly

Thu, 26 Лют 2009 17:38:49 -0000

I think I've seen this in Joomla.

You have like standard CSS file with every CSS class which is used for everything in system.
Basically, it looks something like this :

/*Joomla Stuff*/
.com_heading {}
.com_subhead {}
.prev_bt {}
.next_bt {}

If this is what you're trying to say, I vote yes

medar

Thu, 26 Лют 2009 16:43:36 -0000

Now our core output many html which not customizable. Often this elements no need on some sites. Example - arrows and forum pictograms. Now they are displayed as follows:

I propose replace it by this:

In which case we will be able to flexibly adjust the display by css. For example for arrow up:

.arrow-up { background: url(img/system/up.png) no-repeat; padding-right: 13px; text-decoration: none; }

I also propose set unique css-class for each html-element in core output. This will set the display in skin (width of input fields etc) more flexible and helps solve many "html-in-core" problems, without many small tpl-files.