What Would You Like to See in the Next CSS Cookbook Edition?

I’ve begun working on the next edition of the CSS Cookbook.

In late 2006, the second edition of the CSS Cookbook came out. Even though not every book is perfect, I felt I did what I set out to do in making a solid edition. Almost twice the size of the first edition, the second edition features more CSS-based solutions and tutorials. Heck, it even made Best Web Design Book of the Year with only months to spare.

With the new edition I already have in mind what I would like to add in the new edition: revised recipes, more CSS3-based approaches, and, yes, HTML5.

When writing books, I always try to envision what a Web developer or designer would like to have in their hands. Often times, this is easy since the person I’m writing the book for is often me.

Like the case when I made my Web Design Mousepad. I made it for me, but was humbled and flattered to find out that other people wanted one of their own desk, too.

But there’s always something I leave out that would be a good idea to include–and when you are close to the end of pushing out a book, adding almost any new material becomes hard. Therefore, I thought it would be a good idea to toss this question to you:

What would you like to see included in the new edition of the CSS Cookbook?

5 thoughts on “What Would You Like to See in the Next CSS Cookbook Edition?

  1. I see a big push towards base templates for layout these days. I’ve used the 960-grid system several times and found it to be extremely useful.

    I remember your first book had several recipes on creating single-column, two-column and multi-column approaches. It would be great to see you take it up one more level and write recipes using bullet proof layout systems such as 960, one that can be used and re-used on any project as your blueprint foundation for creating a page.

  2. I’d love to see some thoughts on CSS organization, tips on how to write your CSS so it’s easy to find things when you need to tweak ’em later. Also, the advantages of separating out different CSS functions into different files. That kind of thing.

  3. @Eric Including some sort of recipe on CSS framework is in place. In the second edition we already talk about the foundation on which CSS frameworks are based– guess we need to take it to the next logical step for the new edition 🙂

    @Justin I always try to look for ways to code with the fewest amount of markup and avoid div-itis and class-itis. At least, that’s my goal when I write recipes.

    @Chris Spurgeon I go back and forth on that issue–but I will give it some thought. I definitely think that’s an issue that should be addressed more in the next edition. Thanks for the suggestion.

Leave a Reply

Your email address will not be published. Required fields are marked *