Re: php.net layout with CSS-P

From: Date: Wed, 23 Jul 2003 10:29:48 +0000
Subject: Re: php.net layout with CSS-P
References: 1 2 3 4 5 6  Groups: php.mirrors 
Request: Send a blank email to php-mirrors+get-19487@lists.php.net to get a copy of this message
Hi! I generally worked to make the stuff work with XHTML 1.0 Transitional, as most of our (non manual) pages are already valid XHTML 1.0 Transitional. I have tried to validate the frontpage as XHTML 1.0 Strict, as I have seen some "strange" invalid parts, like that input fields shuold be in some container, which I was absolutely anaware of. Though it seems there will be little to add to the pages to make them XHTML 1.0 Strict compliant, if someone is ready to do so. Most of these changes cannot be done with applying changes to the current site however, a new CVS branch is needed for this, and a test site (xhtml.php.net ?), until we can make things work. It is also important, that whatever we do with the environment of manual pages, those are not XHTML compliant as they are generated as SGML files with our old DSSSL sheets currently. This will of course be solved with Livedocs. But for now, the test site should not print an XHTML doctype on top of manual pages, as they are not XHTML pages at all. Most of the generated code now on php.net is XHTML Transitional compliant. I have also removed some tables in favor of <div>s and some CSS formatting to make some advance in this field. There are some advancements in this field which are doable without starting a new branch (like putting the user notes into <div>s instead of tables). As Rasmus, I would be very happy to see a clean and clear XHTML based php.net in the future. I think it is critical for a web language to present itself as ready for the modern challenges. We know of course that PHP is ready, but presenting it with it's webpage can boost it's "marketing" IMHO. Using CSS, I would also like to avoid the separate requests for printer friendly manual pages, as we can simply apply a different CSS to the same page, and make it printable easily. We can also provide an optional sheet which makes the top menu part a bit less high (satisfying Derick :), so the content would rule on most of the page, instead of the domination of the navigation. Goba

« previous php.mirrors (#19487) next »