Alan Coopersmith wrote:
O'Reilly's Safari online book service has a "Rough Cuts" preview of their upcoming "Even Faster Web Sites" book [1] that I've been reading lately through Sun's Safari subscription - it has several tips on CSS optimization, but really points to the Mozilla document as the source to read on what's faster or slower: https://developer.mozilla.org/en/Writing_Efficient_CSSI've thought it would be interesting to look at the OpenSolaris sites with the various tips from that book and it's predecessor in mind, but it's probably only worthwhile to do so with the new design, and not worry about the one going away.
Yes, not really worth doing until the new stuff is in place.
If community members saw things that could be improved, what's the best way to report them? I know I've filed bugs before in bugster & bugzilla that don't seem to have even got a "Yes, we saw that you filed this, but aren't going to do that right now" response.
Bugzilla is the best place. We have a product set up for auth ('auth'), we will have to set one up for the XWiki install as well, for the moment the 'website' product is probably the best place.
We are in the process of building a web service that will be used to serve all the common OSO components such as headers, footers, CSS & icons, called 'Chrome'. The individual webapps such as XWiki, SCM, Auth etc will all get their common bits from there, so we can change (say) the site-wide CSS by changing chrome and redeploying it rather than having to change each application individually. The source of chrome will be available on src.opensolaris.org, so if people want to tinker they will be able to grab a copy from the repo.
-- Alan Burlison -- _______________________________________________ website-discuss mailing list [email protected]
