Amazing milestone for a website

We have reached 10 years old, a fair age for any website. Actually the domain was registered in October 2002, the site started with the CSS Generator and I added the forum in March 2003. October 2002 So we are actually closer to 10.5 years old. I would like to thank all the people who have been involved, specially the moderators who keep this place running when I leave it in auto pilot mode.

Open Letter to Spammers

Hi there,

Before you post please consider something. We, that is the people that make tech forums like this one viable and useful for the community, keep them alive and provide a little of our experience, and time for free, really do not appreciate people taking advantage of them for what they think is possibly useful SEO gaming, we have to deal with the threads created, wasting our time and more importantly taking the time we may spend helping someone with a genuine need and chucking it away dealing with the utter drivel you post.

HTML5 anchor name & target

An named anchor, so you could target section of the page, like jump to content, used to be

<a name="content"></a>
notice no href.
You could access it in a link prefixing the name with a '#' like
<a href="#content">Jump to content</a>
This is still supported by browsers but no longer valid HTML5.

"" wrote:

The name attribute is obsolete. Consider putting an id attribute on the nearest container instead.

Or you could add '#content' without the quotes to the end of the url in the browsers address bar.

Clearfix and Browser support

When I first wrote about what's known as the Clearfix technique in 2004, I knew it was going to be useful. It was to solve a problem that previously required us to add extra markup to the page. I had no idea it would still be used in one of it's many forms in most CMS and a large percentage of all websites 8 years later.

Browsers have come a long way since then, most of the browser versions we had to support are not even thought of these days.

Debugging CSS problems

Use a valid doctype and validate your markup and styles.
This will help you find out if something as simple as a typo or an unclosed element is causing the problem.

Test in other browsers
Browsers have different base styles and varying support for CSS properties. Knowing in which browsers the problem occurs, make it easier to find a solution. Your problem may be a browser not implementing a CSS property.


Syndicate content