Create a Parameter Error Checking Routine
The main reason for building template-driven sites is so that another user can amend the content themselves using Dreamweaver or Contribute without coming to you for small changes and advice - so you need to make the templates as self-explanatory as possible, to avoid having to field lots of queries on which template parameter takes which values, and ending up with just as many questions as you had before!
In this 17-page tutorial, Brad details how he went about a real-life project to intercept incorrect Template Parameter values and display a list of allowed values to prevent the Dreamweaver/Contribute content editors from causing page or Template engine issues using Template MultipleIf Conditional regions. This requires a little more front-end load time (in the sense that you have to actually build the functionality into the template) but provides the content editor with immediate feedback if they input an incorrect value. Be smart and incorporate this into your template development routine and your users will be happier for it.. and so will you!
Read More