<p>If you have a number of templates in the same part of an article — I'm thinking here mostly of navboxes at the bottom of pages — it's a good idea to keep it super simple. Just listing them at the bottom of a page is a good idea, like this: </p>

{{template 1}}
{{template 2}}
{{template 3}}

<p>Though that's probably the best idea — because other editors can see precisely what's on the page — it <i>might</i> be a good idea to template all those templates together, and then put a <i>single</i> template on the bottom of the page. Whichever way you go, though, you want to make sure — particularly if your templates go the whole width of the page — that they are not in any kind of table structure. </p><p>Recently, at the A.F.C. Wimbledon page i cane across this code: </p>

{{A.F.C. Wimbledon}}
{| class="toccolours" style="margin:0 auto; width:47em;"
{{Football League Two}}
|}

<p>Though this could be made to work, it's wholly unnecessary to put it within a table structure. Indeed, doing so created problems, largely because <span style="font-family:monospace;">{{Football League Two}}</span> didn't have a pipe (|) in front of it, and was therefore not on a row of its own. (And there were other issues within <span style="font-family:monospace;">{{Football League Two}}</span> itself.) </p><p>Instead, it's a much better idea just to do this: </p>

{{A.F.C. Wimbledon}}
{{Football League Two}}

<p>Nothing fancy, nothing complicated. Just one template right after the other. And you should also make sure that <span style="font-family:monospace;">{{Football League Two}}</span> doesn't create a table, either. It's just not necessary, and it opens you up to a lot of syntax errors that can wreck a page's design. </p><p>In short, keep it simple, and be very wary of any template which includes sub-tempaltes that contain the words "start" or "end". Templates like <span style="font-family:monospace;">{{fs start}}</span> and <span style="font-family:monospace;">{{fs end}}</span> create table structures, but because they're not explicit on the template or article page, you're never immediately sure what their code is. I know that this kinda code is present all over Wikipedia, but remember that Wikipedia has teams of editors who specialise in templates. You don't have that luxury here, so it's best to keep the top and bottom of a table on the same page or template as the body of the table. It just makes diagnosing problems a <i>lot</i> quicker! </p>