Here is an interesting thought I had…

It might be very useful if you could have two different sets of code for one template. For example, what if I wanted my “regular” index template and my “event coverage” index template?

Right now (I think) I would have to create a second template called, say, index_event_coverage and load the event coverage code into there. Then, when I needed that template to be the index, I would need to rename index to index_regular and then rename index_event_coverage to index. Then, when the event was done, I would need to reverse that.

But what if a template could have two fields (or more if the user wants, similar to weblog custom fields) and you could give each field a name. Then, you could go in and switch which field was active.

So, using myself as ex example. I could have our standard index template. Then, when we are covering E3, we could have our pre-loaded E3 index page go active, and when it is over, change back. Then when it is time for CES, do the same thing, but with our CES template “field”.

This would be awesome for times when you know a template will need to be changed in advance, and you know what content will need to be on that template - or how it would need to be laid out, etc.

Could even help with working on a redesign. You could have a second field in all your templates once all the coding is done, and then set them all to go active tomorrow night at midnight, all at the same time.

Am I making sense here?

drusoicy - 07 July 2008 01:37 PM

It might be very useful if you could have two different sets of code for one template.

I don’t think that’s feasible, to be honest. Also, potentially very confusing.

For example, what if I wanted my “regular” index template and my “event coverage” index template?

You use two templates. Note that your “index” template could consist of nothing but

Takes 5 seconds to change that to

So, using myself as ex example. I could have our standard index template. Then, when we are covering E3, we could have our pre-loaded E3 index page go active, and when it is over, change back. Then when it is time for CES, do the same thing, but with our CES template “field”.

So use:

Oh, I like it. So basically, instead of coding out the index template, you code out “sub” template, and in the index, just have the embed of the appropriate template that is needed?

You could probably define a few more variables, re-use the HTML header or the doctype or whatever, but yes, in general terms that’s it. It’s a technique I have used a couple of times with some success.