About 20 years ago, I made a website with the free hosting service Angelfire for a class project. It wasn’t my first HTML project, but it was the first time the scope went beyond AOL Instant Messenger away message formatting.
Writing that paragraph, by the way, made me feel super old.
The challenge to webwork back then was that everything was hand-coded. You wanted to write a paragraph? Well
<p>Make sure to wrap it in a < p > tag or else your text won't wrap.</p>
If you wanted any of that text to be bold, you had better make sure to put a <b> tag in there. Need your page background to be something other than white? While, that <body> tag is going to need some style declarations.
It was a pain in the butt, and I was glad those days were over. I like to get under the hood every now and then, but if I’m writing HTML, it’s because it’s an output of some javascript or php.
Anyway, fast forward to this week, and I find myself writing this

That’s part of a Pardot landing page. Creating a landing page template in Pardot is a good idea, and it’s something I would have taught my students to do if my classes ever had the time to get into CRM tools. But, creating a template is basically an HTML-only job. There are no page builders or other resources, and it is a ton of fun.
I mean, I’m building this landing page template for a single job right now: a page promoting the company’s booth at an event later this year. But, I hate doing more work than I need to, and creating a fresh page for every event would be mind-numbingly awful. There’s too much room for error, and if I find myself simply copy/pasting what worked in the past and adjusting a few bits of text, then I might as well have a template.
I see enough of these events coming in the future that it’s worth getting the design right the first time.
Templates and Learning
But Matt, you say, “pardot-region” isn’t a standard DOM object property.
That’s right. It’s part of the internal Pardot logic. Pardot supports {{handlebar notation}} for functions, and I’m wondering if I can use those to template out template components. That would really make things easier over time. For now, I’m stuck hand coding everything again and—while it is fun and it’s bringing back warm memories—that’s taking some time.
There is a benefit to hand-coding it, though. I’m new enough to the company that I need to learn a lot of style and branding standards: what colors do we use for different contexts and elements, how should web pages look, do we have standards for different text lengths or formatting, etc.
Back in my teaching days, I’d often teach template writing first in a course where document design and structure was a focus. Before we ever touched content creation, we dealt with the form the content would take. It forced students to explicate every rule they will need to follow when creating a document, which made it a lot easier to offer revision advice when they didn’t format things correctly.
“You said an equation in an IEEE paper has to be formatted following these rules. Your equation looks different. Why?”
I’m feeling the same benefit now. Many communications from METER begin with a bold clause, then transition to that grey, unbold text style. The Pardot region for text doesn’t allow formatting, though, so I can’t wing it whenever I have to fill in a template. I’ve had to define every rule, accounting for every possible bit of formatting I might want in the future, and I’ve had to think ahead to how large text blocks or images might be when they hit the page, since some of the layout rules assume elements of a specific width or maximum height.
Man, I miss Angelfire.
