⚠️ This page has been archived

✅ New page with updated info: ssw.com.au

Home > StandardsInternal > _EmployeeTestArea > LeiXu2 > SSW Web Template
  1. Only edit pages when viewing them on an intranet. If trying to edit pages from external servers you could encounter problems. For more information see Rules to better website administration .

  2. New web pages are to be consistent with the SSW Template. All new pages must also abide by the rules set out in SSW Rules to Better Websites .

  3. Please also read the standard on SSW Branding before you create a new page...

  4. Sample Heading to look like this

  5. Add this Include file for all SSW Products:
    Demonstration Options
    • If you are in Sydney, call today for a free no-obligation demonstration at your office!
    • If you are not in Sydney, please take advantage of our SSW Phone Walkthrough. The SSW Phone Walkthrough is a service where we will call you, anywhere in the world and once you have installed our product we will guide you over the important features of the software. Saves you time, playing around with the software trying to work out all the useful features, please email us today.
  6. <table class="clsSSWTable" cellspacing="2" cellpadding="2" summary="Formatting Table" align="right" style="{width:50%;}">

    When you have tables on your pages use the ssw colours Don't specify these colours in your HTML

    • BAD <table bgcolor=white cellpadding=0 cellspacing=0 width="100%" border=0>
    • GOOD <table class="clsSSWTable" cellspacing="2" cellpadding="2" summary="Tips On How to Show a Table" style="{width:90%;}">

    Don't specify anything your <tr> or <td> tags

    • BAD <tr bordercolor="#cccccc" bgcolor="#cccccc">
    • GOOD <tr>

    When you have large blocks of text, it's important to break up the page to make it visually appealling. Using text boxes like this is a good idea...
  7. When you use named anchors in a table, use meaningful names. When you are sending the URL by email it helps indicate what you are talking about, and in addition, list numbers often change. An anchor like "#13" becomes incorrect when the order changes.
  8. When inserting a table use "class="clsSSWTable""
  9. If your table needs a header column use the <th> tag for the first table row to get the correct formatting in your table.
    Header Column Header Column Header Column Header Column
    varchar, nvarchar pstr @pstrEmail varchar(150)
    int pint @pintContactID int
    bit pbit @bitPrimaryContact bit
  10. When you have tables that are displaying data (like a DataGrid) then use the same clsSSWTable but with a font-size='xx-small' and a couple of other changes to the table tag.
    ProdName Downloads
    Simple Table Documentor 233
    SSW Performance PRO! 155
    SSW SQL Script Wizard 128
    SSW Data Renovator 122
  11. Always write code in the CODE tag...
    1. BAD <font face="Courier New, Courier, mono" size="2">
    2. GOOD <code>Code in Here</code> Details
  12. Close tags that offically need closing eg. <p>, <li>.

    Also close tags such as </br>, </img> as it will make it easier to go to XHTML in the future.

  13. The Header and Footer tags. These are required on all pages so that you only need to keep the main body of the page and the heading html on the aspx page. The heading, menu, side, footer, table structure is all taken care of for you in the includes.

    At the top of your page you must tell the page to use the templates. You do this by inserting these 2 lines:

    1. <%@ Register TagPrefix="SSW" TagName="incBottom" Src="/ssw/Include/incBottom.ascx" %>
      <%@ Register TagPrefix="SSW" TagName="incTop" Src="/ssw/Include/incTop.ascx" %>
    Figure: Include Templates

    Now you can call the header template:

    <SSW:INCTOP id="Inctop" runat="server" PageTitle="SSW Template"></SSW:INCTOP>
    Figure: Calling the Header Template

    At the end of your page you call the footer that will close the table structure and put the footer image on the page:

    <SSW:INCBOTTOM id="incBottom" runat="server"></SSW:INCBOTTOM>
    Figure: Calling the Footer Template

  14. To use this template, you can just copy this file or if you want to include custom backend scripting you will be required to copy 2 files for this template. By default the webpage is using a custom code behind page to populate the side html in the template. When you use this template you have to rename the 2 files so they are similar. This is for ease of maintenance more than anything. E.g. Login.aspx and Login.aspx.vb
  15. You also have to change the Class name. You must pick a totally unique class name than has not been used on the rest of the site. Eg. LoginMaintancePage

    This class name must be changed at the top of the aspx page:

    <%@ Page Language="vb" src="Login.aspx.vb" AutoEventWireup="false" Inherits="SSW. LoginMaintancePage " %>
    Figure: Changing the Class name

    And at the top of the aspx.vb page: Public Class LoginMaintancePage

  16. There are now two methods of placing some HTML in the left hand side bar in the template:

    1. Make a txt file in the same directory called CurrentPagename.txt If this file exists when the page loads, it will display the html in the txt file in the side nav. i.e. If you call the page default.aspx then you will have to make a default.txt file.
    2. If you have a page where the side content changes depending on different query strings on the page then you can enter the URL into the database and when the page loads, it will check the database for that URL and display the corresponding HTML. Eg. If I have a products aspx page (the product is dependant on the query string passed into the page) then I would use this method.

  17. The Nav Bar is edited using by altering the appropriate table in SQL Server on Joey. Then you need to use a special web page on Seal to generate a new static text file from this table.

  18. You should acknowledge any contributers in accordance with standard convention. If you are quoting another author directly you should use direct quotes - for example: As Cameron Shaw says in the SSW Web Template "You should acknowledge any contributers". OR, if you are just referring to another persons idea don't quote the author directly, but mention that it is his idea - for example: Adam Cogan recommends on his site ( www.ssw.com.au ) that every coding company should have a series of rules and standards that every developer must adhere to." Following this standard will ensure we don't get accused of plagiarism.

  19. Finally if you are not sure then see www.w3.org

  20. Acknowledgements

    Always acknowledge your work.