If you are going to be building a database, odds are you are going to be presenting data in a number of ways. If you are running a multilingual site, you cannot avoid the issue. You are going to be dealing with multiple templates. The two basic Manila templates will be insufficient.
You have a number of options to choose from. They do require you use manilaFixer.
The first method requires you to:
Proper practice implies having a good ordering of your stories and pictures. Outliners are the perfect analogy here. You can define paths which nest pages according to their meanings (continent/country/region/province/city). By using the site structure, you can attribute once a template (say to country) and all the nested pages will inherit that attribute. & you can stop worrying about assigning a template value...
To run the auxiliary templates in this mode, you need to
Words of Caution:
Yours truly likes to use the HTML non-breaking space command in templates. If you do to, be aware that you cannot use such a technique with auxiliaryTemplates from manilaFixer as the template data is rendered thus & n b s p ; become a space in the template then when the browser renders it, no matter how many spaces you have in there, it will sum it up into one blank. This means the following special characters of HTML are unusable: ensp; emsp; thinsp; zwnj; zwj; lrm; rlm;
You'll have to use transparent gifs instead.
Very important Hint:
When building a template, in the header section, make sure that your title tag opens with a capital 'T', as such: <Title>... or you'll get messy things at the top of your rendered page...
a Manila gotcha..