Re: php.net layout with CSS-P

From: Date: Tue, 05 Aug 2003 14:09:44 +0000
Subject: Re: php.net layout with CSS-P
References: 1 2 3  Groups: php.mirrors 
Request: Send a blank email to php-mirrors+get-19840@lists.php.net to get a copy of this message
Anybody against the idea of converting some less used pages to use the new header/footer/container divs with CSS-P, and start to experiment this way? There were no replies yet... :( Goba
Hi Davey! I have updated http://goba.hu/phpnet/ to be strict XHTML 1.0 compliant and fully valid CSS (without warnings) on W3C validators. It still looks the same of course and before (plus I have added the container table and the content div to add some padding in the content area). The practical question now is how we can go on with this development. I have continually made the existing pages closer to XHTML Strict compliance, but manual pages are a different matter. They will only get XHTML compliant with the upcoming livedocs (which will be used hopefully by the end of this year on the site exclusively). Till then we can open a different branch in phpweb, but there are practically only three things that are different on standard compliant pages: the header, the footer (which also print out the three column layout) and the style sheet (which need to be replaced to start from scratch and to avoid dealing with incompatible styles). Most of the other things need no modification in the new branch. So it would be sufficient to just add two new functions (header, footer) to the layout.inc file, which will invoke a different CSS file, and start to make the pages one-by-one to be compatible with the new strict compliance requirement and to use the new functions. That is if we start from the least important pages won't add too much problems (reports that the site is not layed out as expected), while give us the most used place to test, the php website. My layout experiment is already ready for pages like the usage, thanks and some other less used ones, where we can experiment with the new solutions without problems. This may seem a bit messy workflow for this transition, but as most of the page content is already XHTML strict compliant, I don't see a need to open a new branch. Opinions? Goba


« previous php.mirrors (#19840) next »