<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.3//EN" "http://www.wapforum.org/DTD/wml13.dtd">
<wml>
 <!-- page name="designtools"-->
 <template>
  <do optional="false" label="Back" type="prev">
   <prev/>
  </do>
 </template>
 <card ordered="true" newcontext="false" id="choosetool">
  <do optional="false" type="options" label="Next">
   <go enctype="application/x-www-form-urlencoded" method="get" sendreferer="true" href="html.wml#html"/>
  </do>
  <!-- h1 -->
  <h1>Choose a web design tool that supports separate templates</h1>
  <p>When selecting a web design tool, make sure that it supports creating site templates that are stored in separate files, which can be downloaded and cached separately by client browsers. Many web design tools apply the templates to every single web page before the pages are published. An application server might be apply site templates to every page it sends, which takes more time on the server and can more than double the size of the pages being sent to the client. If you are already using a web design tool or application server that works this way instead of sending its templates to the client as separate files, you will probably want to <a href="/internet/xml/templates.wml">create separate templates</a> yourself, unless your web server bandwith is free and you don't mind the longer page load times. The only disadvantage is that by putting the common elements of your web pages in a separate file, the web pages might not be quite WYSIWYG in the design tool; you will need to open the files in a web browser to see the pages as they would look on the actual site. </p>
  <p align="left">
   <a href="html.wml#html">Next: Page 2</a>
   <br/>
   <a href="index.wml">Back Up: Web</a>
   <br/>
  </p>
 </card>
</wml>
