Ordinary Human Language

by Brian Crane

Some Thoughts on HTML Export

HTML export functions exactly the same way as my other examples, and yet for many of us, I think it’s harder to do.

This isn’t however because the process of making templates for the web is harder. It’s not.

No, it’s harder because Tinderbox isn’t (and doesn’t aim to be) an iWeb replacement. It works from templates you provide.

What this means is that, as with the other examples I’ve shown, you need to write a sample of the output. And to do this for the web, you need to be able to write a sample page in HTML.

Once that sample is written, making a web page is no harder than turning your sample into a temple by replacing specific values with ^value()^.

For most of us “web export” doesn’t mean a single page though. It means a site, probably with a variety of pages. To create that output, you’ll probably need a variety of templates. Creating them involves the hard work of figuring out how to write samples for all of them. And Tinderbox won’t help you with this.

What Tinderbox will help you with is the donkey work such as inserting and maintaining the links in the exported files. If you had to do this (and all kinds of other stuff) directly with HTML, you’d go crazy. But Tinderbox has tons export code that automates this work and makes it manageable.

…but still…you have to be able to write the samples to get started…

For what it’s worth, HTML and CSS aren’t hard and you don’t even really have to know them to use them. You can work from a book. That’s what I did with this site. So the challenge of a web export isn’t an overwhelming one. But to does require you to write the samples that become templates…

This is my two cents.

Take it for what it’s worth.

Back to the example list

Posted July 8, 2017