I wanted to keep Allteria for the ancient brethren, so I changed Allandria to Stallandria. Again, I lived with the name for a time. Then, Stallandria started bugging me; the resemblance to Stalingrad was too great.

I changed the name again, this time to Eldlandria. Choosing names should be simple, but it can be challenging to find names that aren’t widely used in other fiction or have some unintended associations.

I had built websites in the past, but was not really a huge fan of designing for the web. The problem, at least in the past, was that in order to layout HTML effectively you had to use invisible tables. Inside those would go more invisible tables. I never like using tables as a method of layout, but eventually got used to it for the few sites I had made.

A modern web site uses CSS (Cascading Style Sheets) to control the look and layout of a website instead of building ugly tables. I have to admit that I didn’t clue into what CSS was the first few times I came across it. I thought it was for controlling fonts, and that was about it. Later I found zengarden, and saw what could really be done with CSS.

I decided I should re-learn how to build a web site, so I bought books on the subject and read them. Now that I have a few of them, I’ve noticed that most come in two main flavors: How to code (HTML and CSS) and How to plan and design a website. There’s a fair amount of crossover, but they’ll each have their main focus. I’m sure there’s some tomes out there that fully cover both, but I imagine they’re thick like a phone book.

Here are some of the books I’ve gotten on either HTML/CSS or Designing a Website: (Regardless of the book’s focus, they all say to drop the tables for layout and use CSS.)

By Jennifer Niederst Robbins

One of the first books I read. Pretty thorough with regards to teaching the main concepts and requirements behind HTML and CSS. For example, shows you how to create sections within your HTML and move them around through CSS.

by Richard Quick

I kind of felt self conscious about buying a how to book with a monkey on the front, but I got it anyway. It’s a good book that’s not too long, and has some good content. It talks about the many components of a web site, planning, navigation, etc. It didn’t tell me a lot that I didn’t already know, but served as a good reminder here and there. Like all good web books, it tells you to use bread crumbs wherever possible to enhance navigation.

By Christopher Schmitt

More of a reference book, I read about the first half before getting bored. It’s a good book to have if you need to understand or make something work in CSS.
Talks about web typography, images, page elements, links and navigation, layouts and more.

By Rob Huddleston

Not a bad buy, but I bought it well into development, and didn’t really need it as much as I thought I’d use it.

I do think that the visual examples are a good way to learn.

by Paul McFedries

I got this one for some of the later chapters, like finding a web host. A good design book with lots of information.

By Matthew MacDonald

Again, I bought this one for the chapters on what to do once you have a website. Quite readable.

In a future Post I will try and talk about some of the specific concepts that I’ve come across while figuring out how to build a web site.