My doorjamb hates you

I can already tell that this particular entry is probably going to get me in trouble. So, let me sit down with a cup of hot chocolate and my comfortable Friday-night-slobbing-around-the-house clothing and just tell you like it is. You know, the kind of talks your mother used to have with you when you were too young and too stupid to understand that just because Aunt Bertha was really really fat didn't mean that you were allowed to come right up to her in front of her and her thirteen grandchildren to tell her that she was fat. On her birthday, no less.

So, say you write fairly regularly on a personal site for a couple of years, and you start picking up readers. Say you do something interesting and unusual with your site—say, making it skinnable. Then let's say that since your friends are fairly vocal and active in the open source community, you get the notion that maybe you're not the only person who would be interested in skinning a website. So what do you do? You make your code available, and you take a good bit of time and write up a tutorial to explain how it all works, and then you sit back, rather amused, to watch the results.

Oh, blast, we've gone from a hypothetical story into the meat of the situation in only two paragraphs. Oh, well. I never said I was the master of subtlety, did I?

Let me tell you—it's amusing. I never expected more than ten people to ever show an interest in skinning a website. While not extremely technical (case in point: I managed to do it), you have to admit, it's not something that should ever appeal to the regular Joe Schmoes who just want to put together a website so that they can post to it when they find something new and appealing on the web.

Now, here's the part where I get up from the computer and go bang my head against the nearest doorjamb: when the heck did this bizarre little idea for my site suddenly become the cool thing to do to a weblog?

Okay, okay, I admit it. It's flattering to check the site stats and see that people find the tutorial interesting and useful, and to get email from people who have managed to skin their own sites. But the converse is … amusing, to say the least.

It's hard to completely suppress a chuckle when I follow up on a referer and see someone writing along these lines about the tutorial: "But it's HARD. Why is the tutorial so long? Isn't there an easier way?"

(At which point I cock my head to the side, arch an eyebrow, and say to myself, "You want to do the equivalent of maintaining multiple websites, combined on a single site…and you want to do something that requires a combination of a server-side language and cookies… Let me get this straight: you want to have multiple, completely different layouts, and you want all this to be plugged into your site and working properly within fifteen minutes?")

Then, suddenly, it all comes back to me, and I remember why doing web design professionally restarted my collegiate antacid habit.

Oh, I dunno, I suppose I could probably go back and rewrite things to try to make it simpler. Cut it down to six or eight pages, take out all the commentary, and make it really dry, dull, and boring. (Like every other tutorial I've attempted to slog through.)

Don't get me wrong. I'm not bashing the people who are trying to learn something new, nor those who are willing to give things an honest try before they contact me. But there are some people who have contacted me in the past six months who have really and truly just wanted me to tell them how to do it—wanted to have the end result without putting in the time and effort to understand what it takes to get there. There comes a point when you want to email these people back and say, "Look. If you don't understand what the tutorial's talking about, maybe it's not the right thing to try to do with your site?"

(With that paragraph, I've probably scared off at least six people and generated at least one hateful post on someone else's weblog. Life's terrible, isn't it?)

But now, suddenly, it appears that this skinning your weblog thing has become a Cool Thing To Do To Your Site, and as a result we've moved past the people who are probably technically ready to handle this sort of thing and moved into the realm of the folk who are simply doing it because someone else they've spotted in the Great Weblog Herd[tm] is doing it.

(Note to self: "great weblog herd." I need to remember this. There's got to be an entry in this somewhere.)

Just so you know: my doorjamb hates you. As a result of the severe abuse it's encountered lately, it has presented me with a list of demands, not the least of which is that I am to cease and desist smacking my forehead into it at regular intervals. Would you believe it wants a masseuse, too? Something about compensation for pain and suffering. Outrageous, I tell you, outrageous.

Just for all this, I think I'll go back and rewrite my tutorial in Tagalog. My original idea, Icelandic, is probably not obscure enough.

…and for the guy who wanted to know why I was such a priss and wouldn't write code for him: I tell you what. You come over and feed my spouse and take care of my life for a day or two, and I'll write your code for you.

In the meanwhile, you're stuck with Tagalog.

For the rest of you, good luck with the tutorial. I hope you find it useful. Just go easy on the list of demands when you email me, eh?

all tags: 

Comments

I've got something to say about this. This is to all the people who are having trouble following the tutorial. Just stop, take a deep breath. Now, just drop it—go out and learn more about the internet. Build your site, maintain it, and then try to do a major design change. Go figure out how PHP works. And then come back to it. Honestly, that's the best way, and the only way you'll learn anything about it. Or maybe I can put this in a different way (and here I'm only speaking my opinion, not necessarily Amy's). If you really think this is cool, but have absolutely no coding experience or knowhow to make it work, then follow the advice I gave up there. Spend some time learning HTML. Learn how code works—it's logical and a lot of the time like following a recipie. You can't add the eggs and salt together, bake it for 15 minutes at 375, and then add the rest of the ingredients. Write out in english what you want your code to do, and then translate the english into working code. If you can't say what you want, step by step, in english, then you can't do it on a computer. So now that you have your steps, go through them one by one and figure out how to do them. If they're complicated steps, break them down into simpler ones. Even the first one is putting the text "Welcome to my webpage" in the title bar, figure them all out one at a time. Then put them together. Once you have enough experience working with HTML and/or other kinds of logical, structured code, then you'll be able to understand the tutorial better. If you want a really cool web page, that's the way to get one. I've made about 6-8 really, really shitty web pages before I made my current one. Expect to do the same, and don't worry about having a crappy web page. Get a design in your head and make it. Just don't tell anyone about your web page for a while and it's okay—no one will see it so you don't have to be embarassed. The only way to learn this stuff is to do it. If you're looking for a book to help you. . . Hmm. I don't know any good current books on HTML per se. I do know that the O'Reilly book on Cascading Style Sheets is invaluble—You'll want that even if you don't know what to do with it yet. Do google searches on different things you want to learn about—chances are, someone's made a useful tutorial online. All of that stuff is good if you actually care about doing things right and having fun with it. BUT. . . . if you're just a lazy fuck, go out and get a work ethic. Get off your virtual ass and put some effort into it. If you believe that the world is going to take care of you, think again.

Yep, I've gotta have this entry bookmarked. I hardly need tell you why. =) *hug*

John's got a pretty decent point, actually, about the recipe bit. The actual skinning part isn't that difficult: cut the layout away from the content, call it with PHP, and create a page that lets you switch between different layouts. The problem is that if that's all you do, you're going to chunk it all in frustration about a month later. Something will break, or you'll want to remove a layout, and suddenly you can't figure out which files are which and where the various bits for each skin are...and you end up hosing the entire thing in disgust and going back to one layout. To do skinning the right way -- that is to say, to do skinning in a maintainable way -- you have a lot of prep work that needs to be done before you ever even add another layout. Anyone who tells you differently hasn't had their eyes opened by maintaining a very large personal site with 14 very different layouts. If you are not prepared to do the maintenance work that skinning requires, skinning isn't for you. Period. I wish I could impress that on more people.

It's truly disappointing (and annoying) how many are plagued by this idea that everything should be dumbed down so anyone can do anything. When your parents said you could do anything they meant you could do anything with work, thought, and the desire to learn and do, not just sit on your butt and have it handed over. Kudos to you my dear for speaking your mind!

i might just add that the mentality of people who want everything easy is fostered and nurtured by Microsoft...

I wondered when you'd want to explode about this, dearie. :)

I fully endorse the post and above comments. coding is laborious and logical. To do it correctly, you MUST begin at the begining... and in terms of websites, that means learn some HTML, grok CSS, make some ugly websites, learn from your mistakes and gain a gestalt understanding of how these things are put together, and more importantly, maintaned. As for "some good books on HTML", you should flip through a couple in your local bookstore, start with the O'Reilly ones, which may be a tad intimidating, or seem to technical, but they DO walk you through everything. Again, it is not a simple task that can be mastered in 24 hours. In terms of a reference, I rely on http://www.blooberry.com/indexdot/html/index.html for my HTML, and http://www.blooberry.com/indexdot/css/index.html for CSS. They are current and comprehensive. When something funky is going on -- it can usually be found within those pages.

Hello. I was referred to this tutorial from a friend, alex (athenae.nu, asperia.net etc etc). I just wanted to say thank you for the tutorial (really easy to understand) and thank you especially for this post. I love it. It _is_ sad that website features become trendy instead of being unique (another example is the tag board), although I must admit I am a slave to the trends as much as the next webmaster, I can't stand it when people won't put any effort in. Er, I meant to say something poignant, but I give up. Thanks for the tutorial and insights. Laura