[TYPO3-content-rendering] TYPO3-project-content-rendering Digest, Vol 49, Issue 1

Mike Gutzschhahn info at mikeg.de
Fri May 13 12:42:21 CEST 2011


Hello Riccardo

i'm as well interested in modifying the html and css output
since the huge amount of div, classes and ids weren't that helpful
and as well reduce the performance.

At the user group meeting in Mannheim (GER) we had a little chat about that.
Regarding to your topics, there're already some solution:

1. Reduce the number of classes
A nice how to you'll find at : http://sebastiaandejonge.com/blog/articles/2010/january/26/typo3-page-output-optimization/
Got this and a lot of other suggestions via google "typo3 minimize html output"

2. Avoid some inline styles
I prefer the extension script merger. That handle all inline style very nicely
and you don't have to customize each single installed extension.
http://typo3.org/extensions/repository/view/scriptmerger/current/

3. "Better structure"
I know that over- or rewritng the extensions html output is possible. But it's quite a mess
to update your modifications after the extension was updated. I heard that there're two
thoughts/directions which will be developed. One as we've now and a very simple
and puristic html and css output – but i haven't seen something about this yet …

Hope this helped you.


Kind regards
Mike

Am 13.05.2011 um 12:00 schrieb typo3-project-content-rendering-request at lists.typo3.org:

> Send TYPO3-project-content-rendering mailing list submissions to
> 	typo3-project-content-rendering at lists.typo3.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-content-rendering
> 
> or, via email, send a message with subject or body 'help' to
> 	typo3-project-content-rendering-request at lists.typo3.org
> 
> You can reach the person managing the list at
> 	typo3-project-content-rendering-owner at lists.typo3.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of TYPO3-project-content-rendering digest..."
> 
> 
> Today's Topics:
> 
>   1. Upgrading CSS Styled Content - some ideas (Riccardo De Contardi)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 13 May 2011 11:05:33 +0200
> From: Riccardo De Contardi <riccardo.decontardi at bhuman.it>
> Subject: [TYPO3-content-rendering] Upgrading CSS Styled Content - some
> 	ideas
> To: typo3-project-content-rendering at lists.typo3.org
> Message-ID:
> 	<mailman.1.1305277541.31255.typo3-project-content-rendering at lists.typo3.org>
> 	
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> Hello everybody; first of all let me introduce myself: my name is 
> Riccardo De Contardi and I'm a not-so-long course TYPO3 user and 
> integrator ;)
> 
> I've started a similar topic on the group "TYPO3 English" and I've been 
> suggested to move it to this group instead, so... here I am! (And 
> forgive me for a bit of cross-posting ;))
> 
> I'd like to discuss with you the possibility to somehow "simplify" the 
> current CSS Styled Content HTML and CSS rendering. In detail:
> 
> - could it be possible to reduce the number of classes ?
> - could it be possible to avoid some inline styles (style="width:etc")?
> - if you set captions for images, the  HTML that arranges images becomes a
> dl/dt/dd structure; as far as I know, there are screen readers, like JAWS
> that speak an "=" between the term and its definition, so:
> <dl><dt><img src="typo3temp/myimage.png" alt="alt of the
> image"></dt><dd>caption of the image</dd></dl>
> 
> Would be spoken as:
> 
> "alt of the image = caption of the image"
> 
> I think this should be confusing for the users (and... if there is no alt?
> ? = caption of the image??? );
> 
> so... could it be better to use the plain ul/li structure (plus 
> surroinding the caption with a <span>)?
> 
> 
> Here are some interesting links related to this topic:
> 
> http://pmob.co.uk/pob/centred-float.htm
> (could avoid the sum of widhts in ?Above, center? and "Below, center" - 
> I suspect these are the only cases in which they are somehow mandatory: 
> for all the other options the float:left or float:right is sufficient to 
> set the width of the container)
> 
> http://www.sohtanaka.com/web-design/css-overflow-property-quick-tip/
> (could avoid the <div style=?margin-left:XXXpx;?> in ?Beside text, left? 
> and ?Beside text, right?)
> 
> Also this could be interesting:
> http://blog.mozilla.com/webdev/2009/02/20/cross-browser-inline-block/
> 
> (maybe whith this it could be possible to use a single "list" instead of 
> a "list" for each row)
> 
> Thank you all for your patience and best regards; I hope hearing from 
> you soon!
> 
> -- 
> 
> --------------------------------------------
> Riccardo De Contardi ? TYPO3 Certified Integrator
> B Human Srl - www.bhuman.it <http://www.bhuman.it>
> Via Canzio, 15 - 20131 Milano
> TEL +39-02-20.23.271 - FAX +39-02-20.240.561
> --------------------------------------------
> 
> 
> ------------------------------
> 
> _______________________________________________
> TYPO3-project-content-rendering mailing list
> TYPO3-project-content-rendering at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-content-rendering
> 
> End of TYPO3-project-content-rendering Digest, Vol 49, Issue 1
> **************************************************************



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