We made it a decade! It’s our tenth birthday! 🎉 This is an extra-special one, as we hit those double digits. Each year on July 4th we mark the occasion with a post. In that tradition, allow me to ramble on a bit about the past and present.

The very first post ever on this site was literally a CSS trick. It’s a classic, too. “Header Text Image Replacement”:

.headerReplacement { text-indent: -9999px; width: 600px; height: 100px; background: url(/path/to/your/image.jpg) #cccccc no-repeat; }

Funny, I just used that trick a couple of days ago.

The post is interesting to me for a number of reasons. For one, I certainly didn’t come up with that technique. At the time, I was just learning CSS myself and writing down interesting stuff I’d come across and used in my own work. I think I felt like I learned it a little more deeply by writing it out as an explanation like that.

For another, at the time, I was entirely unaware of where a trick like that fit into CSS history and larger discussions about CSS and semantics and accessibility and all that. A year later, I started getting interested in stuff like that and did stuff like rounded up many possible techniques for image replacement. Ultimately, even making a “museum” for it.

Before I go too much further here, I gotta mention the fact that we just re-opened the shop in honor of this anniversary. We made up some nerdy web related T-Shirts, and would love it if you would pick one up to help support the site:

CSS-Tricks was a WordPress site running on PHP and MySQL back then. Today, it’s… a WordPress site running on PHP and MySQL. Although WordPress was 2.0.1 back then and 4.8 now. PHP was 5.2 then and 7.1 now. MySQL 5.0 then and 5.7 now. All those seem fairly small version bumps for a 10-year span, but really they are quite significant technological advances.

Back then we made sites with HTML, CSS, and JavaScript. These days, sites are… HTML, CSS, and JavaScript.

I try to keep a design history the best I can. Let’s do a little blast-to-the-past of header styles:

This one isn’t to be underestimated: it takes serious work to keep a website running. There is always something that needs to be done.

There is always some bit of software that needs to be updated.

There is always some weird bug that needs attention.

There is always some business opportunity that needs work to get going.

There is always some part of the design that really needs a look.

There is always some SSL certificate to worry about.

There is always some server or DevOps thing to think about.

I have a whole section of my TODO’s called “Site Work” that is full of things I need to get done around here. For example, right this second, I know there are some assets that are loading in a way I don’t want them to and I need to look at it for performance reasons. I’d like to do some stuff with embedded Pens to make them a bit wider by default, but need to be careful not to screw up any layout. I know markdown is behaving weird in the forums for the 692nd time, and that a private forum is showing publicly in a place I don’t want. That’s like 5% of the list!

I shudder to think what would happen if all this work wasn’t done constantly. The site would fall to pieces.

And that doesn’t include what you might actually think is the hard work involved in running a website:

Writing new content

Editing submitted content

Updating old content

Managing the publishing schedule and planning future content

Community management

Promoting and marketing the site

Finding sponsors

Make sure sponsors are happy

Social media

If you do all that work, on both lists, the hope is that you just keep to keep on keeping on. Everyone gets paid for their effort. This is not a hockey-stick growth kind of site. It’s a modest publication.

Speaking of slow growth, that’s the deal:

That’s not representative of just doing the same ol’ same ol’ year in and year out. That’s representative of more and more people working on the site and more and more money being invested back into the site.

One interesting aspect of this is how the bulk of that traffic is generated by search. Of course, I have no problem with that. I’m very happy that this site shows up in search results and can be useful to people that way. At the same time, having an active readership is a very valuable thing. Not just people who show up in search, but people who read the site regularly like they do the news. Definitely a balance there. That’s why we do things like invest in the newsletter, to make sure we have ways to read CSS-Tricks that come to you and are worth your time.

On a personal note, I’m still living in Milwaukee, back here after a 7-month stint in Miami. My fiance Miranda got a job down there at FIU and we took the opportunity to move down, skip the Wisconsin winter, and be close to our Florida friends. I don’t post publicly all that much about personal life stuff, but this will be a huge year for me. The Miami move to and back was big! Miranda and I are getting married this summer! We’re also expecting a baby in the fall! And we’re also planning to move to Oregon in late summer! Crazy times. There almost couldn’t possibly be more going on, especially factoring in all this running multiple businesses stuff and a fairly aggressive speaking schedule this year.

My main focus is CodePen, which has had a tremendous last year. After taking funding, hiring an amazing team, and releasing lots of big stuff, we’ve got ourselves to that wonderful spot all businesses desire: profitability. The roadmap of ideas on CodePen is absolutely never ending. I’ve never felt like we have more work in front of us as strongly as I do right now.

I’d like to give special thanks to all the sponsors that make the site possible. I can’t thank every single one, but I will give a special shout out to Media Temple, who has been a long time sponsor and supporter of CSS-Tricks.

And of course the heartiest of thanks to all you readers, without whom there would be no reason to have a site at all. The discourse that happens here is top notch and I couldn’t be happier to facilitate it. And lastly, as you likely know, this site is by front-end developers for front-end developers, so if you have something to say, feel free to reach out.

See the Pen Conways Fireworks by Ben Matthews (@tsuhre) on CodePen.