[TYPO3-dev] Master Style 4 Typo3

[Johannes Reichardt]

Hi Kasper,

great to hear you share that idea, if this is the right time and the 
right place we could discuss what is needed.

My supersimple idea in detail:

a default and small "typo3.css" which is right next to the index.php, 
containing a very conservative and simple style without backgrounds.

for example:

body {
	font-familiy:arial,helvetiva,sans;
	font-size:12px;
	color:#00000;
}
h1 {
	display:inline;
	font-size:18px;
}
header1 {
	font-size:16px;
}
.tdlist1 {
	background-color:#ffffff;
}
.tdlist2 {
	background-color:#eeeeee;
}
.error {
	color:#ff0000;
}

thats pretty much nothing but should cover (along with a few more 
styles) 95% of the styling that is needed. If there is something more 
the extension requests to update the typo3.css OR to include its own 
stylesheet wherever it is used (and not everywhere ;)

So this along with no other default styles in typo3 and extensions would 
make things really easy.

What else should be taken care of?

- Johannes


> 
> This idea is also on my heart. I haven't looked in detail on what the  
> Content Rendering Schemes are but for version 4.5 I hope that  
> defining a long lasting CSS strategy that can be used globally for a  
> site and affecting all extensions (complying with it) will be a major  
> point.
> 
> - kasper
> 
> 
> On Feb 21, 2006, at 2:20 , Johannes Reichardt wrote:
> 
>> Hey there!
>>
>> Its late and my eyes are already burning after more than 12 hours
>> non-stop computing but nevertheless i would like to share an idea that
>> just came into my mind:
>>
>> How about a "masterstyle" for Typo3?
>>
>> Let me explain.
>>
>> Right now every extension tends to introduce its own new styles - new
>> backgrounds of tds, new font classes, new margins and paddings and so
>> on. Even worse all that oldschool font tags in the template. We all  
>> know
>> the process of going through myriads of configuration places like the
>> constant editor, the default template, the stylesheet or even the
>> extension code itself for example. And after that your style is  
>> stil not
>> really "consistent" and you have a huge mess with tons of different
>> stylesheets and oldschool tags.
>>
>> That really sucks big time.
>>
>> So how about a concept that gently invites extension developers to use
>> predefined styles of the mastertemplate which comes along with a clean
>> typo3 install? So we have by default styles for the body, tds,  
>> borders,
>> errors etc.. and also for table lists, headers and so on. That way  
>> a lot
>> of other things could be removed (like typoscript styling etc...) and
>> you still would keep complete flexibility overall.
>>
>> If you want to style your extension differently than just prepend
>> "ext_key" to the style and you use a whole own extension style. Or you
>> just add a few "styling exceptions" in the mastertemplate and off  
>> you go.
>>
>> The point is to develop a template that is not too huge but still  
>> covers
>> most cases in a usual typo3 installation. That template should be
>> publicitly known and used as much as possible.
>>
>> In the end it wouldn´t be just a dream but rather reality to install a
>> typo3 page out of the box in 30 minutes and completly style it along
>> with its extensions in another 30 minutes. And even better: You can
>> change things quickly without looking up tons of places anymore!
>>
>> Actually i´m afraid there is already a concept like this and just gets
>> not used enough or i misunderstood it - if so please ignore this  
>> mail or
>> explain it to me, otherwise i would be glad to get comments on this  
>> idea.
>>
>> Clean styles are the future! (Says a square-eyed-man ;)
>>
>> - Johannes
>>
>> _______________________________________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> 
> 
> - kasper
> 
> "A contribution a day keeps the fork away"
> -------------------------------
> kasper2006 at typo3.com | +45 20 999 115 | skype: kasperskaarhoej |  
> gizmo: kasper_typo3
> 
> 
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>