[TYPO3-dev] CSC and ContentRendering Team

[Georg Ringer]

Steffen Ritter wrote:
> Denyer Ec schrieb:
>> many 3rd party extensions rely on the CSC markup structure for correct
>> operation. I'd hope none *depend* on it, but my instincts say
>> otherwise.

Sure some of my extensions depend on csc because I need to put sometimes 
my code just in between. ;)

IMO this is not a big problem to change because most of the extensions 
in this area are developed activly.

> Many do... Look at all lightbox stuff, ringer extensions, frame 
> extensions etc. they are based on changing ts code of csc.

I still don't know how I should feel about getting a kind of synonym ;)

Extensions like rgaccordion are more like a container of some lines of 
TS, js and css files. This can easly be adopted.


> - We also should provide a css set using as less classes as possible - 
> but meaningful names.

absolutly a +1
This can be also the other way round: Add an extra cleaning TS which 
deletes all the not needed class names and so on.

I really don't have a problem with a 2nd improved static ts template of 
csc which can be added to every new project. Old projects can just use 
the old csc.

I don't need any radio button but of of course some help for all type of 
  users how to work with the new features and a changelog.

Is there a place we could share the snippets we use everytime because I 
don't like to use the mailinglist for that. Maybe forge or the wiki?

Georg