Instead of modifing
customer/home.tpl You can add the links to the
skin1/help.tpl
This avoids what looks like a
(but is actually the <table>)
You can also, I assume, make a label in langauges on the provider section so the label for this section changes with the language. But your content on those pages will be in the language you wrote it in. I am thinking you could
add a text in languages for each file you create
ex about_us.tpl would contain
Code:
{ include file="location.tpl" last_location="About Us"}
{capture name=dialog}
{$lng.txt_about_us}
# I believe this is teh correct syntax
# but will need to match whatever you call the content.
{/capture} { include file="dialog.tpl" title="About Us" content=$smarty.capture.dialog
extra="width=100%"}