Starting with an earlier post called I don’t want templates, I want HTML-making shortcuts, I’m slowly exploring the idea of the final HTML in web programming coming not from an HTML template, but from programming shortcuts. It seems ridiculous, I’ll bet. But Eric Meyer’s new post on Structural Naming reminded me why this makes sense.
I do believe, VERY much, in the idea of separating business-logic from presentation-logic. (Some call it model-view-controller. Whatever.)
But when HTML moves towards structural naming, it really is more like creating XML, where it’s the programmer’s job to output solid, valid, structually-marked-up data. NO layout, NO colors, NO fonts, just data….
…and it’s not the designer’s job to get that data into structural and valid HTML. Therefore it’s not a good time to be using separate template systems meant just for designers.
Once the HTML is created, then it’s the designer’s job to use a CSS stylesheet to make that structural data look how they want.
I may be totally wrong with this, but in a few weeks I’m going to try to put this vague idea into practice, and letcha know how it goes.