I’m with the moose on this one…. I haven’t had the chance to look at the annotated CSS, but when I first started with WP, it would have been nice to have. I am a geek by trade. I deal with this kind of stuff day in and day out. But if you were to ask me how to get rid of the bullets in a list, I would have told you to remove it from a UL and separate each item with BR tags…. but that isn’t the best way to do it, especially when trying to make things semantically correct. I work with this stuff all the time, but that doesn’t mean I know it all. I still need it spoonfed to me from time to time. I applaud NM for the time he took to make the doc. The CSS is probably where most of the customization happens in WP.
As for WP beeing a geeks only “toy”…. I hardly think so. It is so open, and so easy to cusatomize, any one who is willing to learn a little bit of CSS and take a little time to play with WP shouldn’t have any problems creating something all their own. Ever try to build a template for a Blog*Spot website? Now there’s a challenge.
But, wyou know what? I’m just a gnome. What do I know?
TG
If the devs wanted to spoonfeed us they’d write some kind of manual, but they trust us to be able to work everything out ourselves.
Anonymous, meet the wiki. Wiki, meet anonymous. For somebody who claims to be among the WordPress “elite,” you don’t seem to know much about the WordPress community.
Actually the wiki illustrates my point exactly. It’s written mainly by users, not the devs. Users who’ve managed to work everything out for themselves. It’s not a dev-created manual, it’s a user-written resource. Any community capable of writing its own manual is elite in my book.
Will,
Actually, there is quite a bit of content in there that is written by devs.
Welcome to open source, where if you want something – you do it yourself. 🙂
Hmm…if I have to do this myself, then I’m screwed. Off to blog*Spot I go… 🙂
I don’t think that’s a good characterization of open source, it’s more a prejudice. Alex is joking anyway, but just so people don’t get the wrong idea. 🙂
Of course part of the beauty of open source is that you can do it yourself, or pay someone to hack the source. Can you do that with Outlook or Winamp?
Yes, that was said “tongue in cheek” – sorry for any confusion.
Well, here’s the thing: the developers aren’t being paid to create wordpress… so would you prefer that they spend their free time implementing new features, or writing a manual? And it’s not like everyone in the world is pitching in on the manual… it’s pretty much being led up by a few individuals who have become the quasi-official “doc writers”…
Would all the people who want a manual, please raise your hands?
