 |
 |
 |
You will probably want to make your changes directly to the Custom HTML template file as we have done in this tutorial.
If you have a long series of changes, you might want to add one change at a time to the Custom HTML template file, testing the results after each change.
As a shortcut during development, you can run the template file itself in the browser to see the results, rather than regenerate the Deployment Wizard output files. For example, in this tutorial, we could run sstemplate.html in the browser to see the results. When you have completed and tested all the changes, then regenerate the Deployment Wizard output files.
Another approach is to make the changes directly to the proximate output file. Test each change separately by running the proximate HTML output file in a browser. When you are satisfied that the change works as you had intended, move the change from the proximate HTML output file to your custom HTML template file, and regenerate your Deployment Wizard output files. Then go on to make and test the next change.
Remember to keep backup copies!
|
|
|
|