[TYPO3-content-rendering] Divide css_styled_content in multiple templates to rid ourselves of the compat versions

Susanne Moog typo3 at susannemoog.de
Tue Dec 2 18:19:47 CET 2008


Franz Koch schrieb:
> Hi,

> shouldn't we take the opportunity and remove all the outdated 
> HTML4-Markup and provide a clean and accessible XHTML version of CSC 
> that can be used by default without rewriting major parts to get a clean 
> output? Just like suggested in the tutorial on T3CON?
> 
> I don't see why we should keep that outdated stuff - who is using it 
> anyway nowadays?
> 
> We could:
> - drop the useless wraps around headlines and make them clean h-tags
> - remove useless css-classes like <p class="bodytext"> (you can address 
> those p-tags with nested CSS selectors)
> - do we really need to show the prefixComments by default?
> - do we really need all those csc-bulletlist and whatever classes?
> - make forms more styleable and accessible and use ol/ul (there already 
> was a discussion about that - but I can't remember in which group)
> - integrate a up2date MULTIMEDIA component (damn - that one is really 
> outdated)
> - ...

I agree to all your points but I would do it bit for bit. Let's first 
get rid of the compat version conditions and then start on the next 
point on the list as it's easier to split work and really get things in 
the core. I think if we try to do everything at once at the end nothing 
will be really finished (and yes I am a pessimist ;) ).

Short question about prefix comments: what sense do they make anyway? I 
always disable them and I'm still waiting for the moment I'll think "oh, 
a prefix comment would be exactly what I need now!".

Regards,

Susanne


More information about the TYPO3-project-content-rendering mailing list