WordPress for happy campers
Sometime ago I worked at a rather well-regarded summer camp for children interested in science, technology, and engineering. It was by and large a positive experience, and none of what I am about to raise pertains to that programme alone. Any camp run by university students will undergo a lot of staff turnover year to year, with comparably less turnover in the boys and girls who show up every summer because (as their parents attest) they don’t want to go outside. At DiscoverE, the instructors had an instrumental role in planning the day camps on offer, but broadly speaking the schemes were adapted from the successes of previous years with minor modifications.
For computer camps, that sense of inherited continuity can be crippling in ways that aren’t obvious at first sight. Consider a standard offering of computer instruction today: an introduction to building websites. When kids look at websites, they dream about making their own—and they pattern their imaginations after what they see, not what is practical. The instructors have to teach them how to do this, in a rudimentary sense, in a severely limited timeframe with a minimum of confusion and drudgery.
Most quick-and-dirty website instruction, right up to the community-college level, will adopt one of two solutions. Both of them are holdovers from a decade ago. On one hand you can teach hand-coded HTML, which is how we grizzled warriors learned the ropes when we braved the jungles of GeoCities to hang our(selves on) <marquee>
lights. But you don’t do that to kids today, certainly not within a week; it’s demoralizing to start with an empty canvas, teaching it ends up in a mire of copy-and-paste, and the youngsters don’t value minimalism like we do. Besides, you’ll only end up showing them how to write bad code that doesn’t validate, since there’s no way in holy hell you’re covering CSS.
Introductory website courses thus swing to the other extreme: proprietary WYSIWYG site-builders like Dreamweaver. This is a terrible idea, for two major reasons (among others):
- Campers want to take their work home with them when the week is through and continue chipping away. To do this, they have to pressure their parents to obtain a product that isn’t priced for individual amateurs and certainly not for kids, a fraction of which will ever see use. As much as I love Adobe, I have an ethical problem with this, especially as I do not consider piracy a legitimate workaround to the high cost of software licenses. It ends up being either a de facto endorsement of a commercial product or a de facto endorsement of piracy.
- These tools are not for beginner sites. Years ago, nobody serious about websites used WYSIWYG editors; they had a dreadful reputation for generating messy code, non-compliant with standards and a pain to fine-tune. Dreamweaver has improved considerably, but it is a professional tool for business purposes more than personal use, best left to the people who know the nuts and bolts of web design and use it for mock-ups or speeding up their workflow. If you don’t know what you’re doing, the interface is bewildering and problems are hard to spot and fix—and children break things in the most fascinating and creative ways.
Don’t get me wrong: I don’t think Dreamweaver wrecked my camp. The kids had fun, the parents offered their compliments, the instructors didn’t go too crazy, and whoever planned the course that year did an admirable job considering how they stuck to what I think is a fundamentally broken orthodoxy of how to introduce 9-to-11-year-olds to making websites. I’m saying computer camps can do better.
I propose that crash courses in website building teach WordPress. Here’s why.