CSS3

Since i’ve started with my CSS3 preview pages, i’ve had the same question at least 10 times already: why do browsers prefix CSS3 features? It seems so weird, when both WebKit and Firefox have border-radius implemented, you have to write two lines for it to work in both browsers.

The Opacity declaration sets how opaque an element is. An opacity value of 1 means the element is fully opaque; an opacity value of 0 means an element is not at all opaque, i.e. fully transparent.

Just a short note to let you all know that i’ve switched the feed to a FeedBurner feed, it should work automatically, if it does not please tell me in the comments. I’ve switched it because FeedBurner can give some pretty cool stats on feeds, which could be useful in the future.

Hello, I’m the third member of the new CSS3.info team. My name’s Peter Gasston and I’ve been working as a web developer for six years, currently as Creative Developer for a design agency in London (I would provide a link to their site but I’m still rebuilding it). I’m a passionate advocate of web standards and my dream would be to see either Internet Explorer embracing standards, or everyone else embracing a different browser.

I write for a number of blogs on a number of subjects; my most relevant would be my geek blog, where I get to talk about all the stuff I like that’s not necessarily mainstream. Like many projects of mine, it’s in constant development.

I’m excited about the new features of CSS3 because they might finally help us to get rid of ‘tag soup’ in our code; no more four-layer nested divs to create curves, for example, and many less ids and classes required to hook our CSS to. My enthusiasm is only slightly dampened by the fact that it will be many years before we reach that stage.

Im the second blogger/author to be added to css3.info and I’m extremely excited. I have become much more involved with CSS and Web Standards based design over the past year, then I ever thought I would be. I dove head first into a new project that started in October ’05 at dLife.com where we converted dLife.com from a regular table driven website supported by a shoddy CMS called OpenCMS, to a more agile ruby based backend with a css-based front-end design.

I would say at this point, dLife.com is 50-60% of being complete, but there is so much more to learn. The site is about 5,000+ pages, so there is still much to be done to get this site really cranking. My team and I are also learning ruby on rails, which is still a very new technology which nobody knows quite where it will go.

At the same time, I hope I can help other web designers/developers learn more about whats to come for CSS3. Joost and I are very excited to put together a great resource dedicated to CSS3.

I’ve started css3.info three days ago, and already it got dugg, became a del.icio.us popular url, and was in furl.net’s top 10 :). Now it’s time to start expanding this site. Starting today, all the blogging i did on joostdevalk.nl/blog about CSS3 will be moved here, and others will join me.

At least one new blogger will be introducing himself somewhere this week, perhaps even tonight. We will be blogging some CSS news, and write articles about CSS usage and webdesign in general. We do NOT intend to copy other CSS news sites, there are enough CSS news sites out there.

A next step in this evolving project will be to add CSS3 compatibility tables, and other interesting news. Do tell us what you’d like to see, and mail me or comment here if you want to join this new community.

You might have noticed that some of the ads on the site are gone. People were complaining about it, and even calling this a “Made for Adsense” site. That, it is not, and I’m even thinking about other ways to finance this site, so that it can go “adless”.