Add a New Page

  • Determine URL (path) and HTML <title> for page.

    [Note]Note

    No directory need be made for a new Level 4 page. They will always be placed in the same subdirectory as their "parent" Level 3 page.

  • Determine appropriate Page Layout (/mlnmdev/SiteHTML/PgLayouts/pl06.html for Level 4).

    (Has column for Nav4 on left part of content body zone; has no "related" zone for Highlights (no Highlights used on Level 4 pages, typically).

    [Note]Note

    Page Layout pl06a.html is to be used for very short pages. It suppresses the use of the background page image (helix).

  • Create /util/buildlist.xml entry for page.

  • Create BusinessML module(s) for page.

  • Modify Nav4 module (if applicable)

    A single Nav4 module is shared by all sibling Level 4 pages. E.g.

    				/rd/cardiovascular/candidates/mln519.asp
    				/rd/cardiovascular/candidates/cab2.asp 
    				etc.
    				

  • No site navigation graphics needed.

  • Determine URL (path) and HTML <title> for page.

  • Make a new directory for the new Level 2 page: > mkdir mynewdir {ENTER}. (all lowercase)

    [Tip]Tip

    Make the directory in four locations: Development Area (/mlnmdev/htdocs); Development Website (/Inetpub/stage8080/); Staging Website (/Inetpub/stage80/); and Production Website (at Rackspace (forthcoming)).

    As noted above, think about the best directory name (see Level 3 for an example).

  • Devise the three-letter code you will use for this (sub)-section (e.g. 'dir'). Consult the list of three-letter codes in this documentation to ensure it has not already been used.

    At Level 2, the code is used in naming several artifacts: Nav2 HTML snippets, image filenames, etc.

  • Determine appropriate Page Layout (/mlnmdev/SiteHTML/PgLayouts/pl05.html also used for Level 2).

    (Has no "related" zone for Highlights (no Highlights used on Level 2 pages, typically) (If you want to create Highlights for a page, you need to use Page Layout 1.)

    [Note]Note

    As above, Page Layout pl05a.html is to be used for very short pages. It suppresses the use of the background page image (helix).

  • Create /util/buildlist.xml entry for page.

  • Create BusinessML module(s) for page.

  • Modify /BusinessML/NAV2.xml entry to include new <NavItem> as child to existing Nav2 grouping element (e.g. <Nav2 sitesection="rad">).

    [Note]Note

    If any new Level 3 pages come beneath this Level 2 page, follow instructions above re: their addition.

  • New site navigation graphics are required (Nav2s are images).

    C:\mlnmdev\htdocs\images\nav\ 
    NAV2_1rad_2crd_off.gif
    NAV2_1rad_2crd_in.gif 
    NAV2_1rad_2crd_on.gif 
    NAV2_1rad_2crd_ro.gif 
    ("roll-over" is identical to "on", therefore the additional graphic is not actually used)
    				 

    "Page SubHeader" graphics:

    C:\mlnmdev\htdocs\images\pghdrs\ 
    pgsubhdr_1rad_2crd.gif
    pgsubhdr_1rad_2eng.gif 
    pgsubhdr_1rad_2inf.gif 
    ... 
    pgsubhdr_1xxx_2none.gif
    (blank white SubHeader "none"; used for all ("xxx") Level 1 Headers)
    					 

  • Determine URL (path) and HTML <title> for page.

  • Make a new directory for the new Level 1 page: > mkdir mynewdir {ENTER}. (all lowercase)

    [Tip]Tip

    Make the directory in four locations: Development Area (/mlnmdev/htdocs); Development Website (/Inetpub/stage8080/); Staging Website (/Inetpub/stage80/); and Production Website (at Rackspace (forthcoming)).

    As noted above, think about the best directory name (see Level 3 for an example).

  • Devise the three-letter code you will use for this section (e.g. 'dir'). Consult the list of three-letter codes in this documentation to ensure it has not already been used.

    At Level 1, the code is used as part of naming many artifacts: Nav1 HTML snippets, Nav2 HTML snippets, image filenames, etc.

  • Determine appropriate Page Layout (/mlnmdev/SiteHTML/PgLayouts/pl01.html used for Level 1).

    (Has "related" zone for Highlights on right-hand side of content body.)

    [Note]Note

    Page Layout pl01a.html is to be used for very short pages. It suppresses the use of the background page image (helix).

  • Create /util/buildlist.xml entry for page.

  • Create BusinessML module(s) for page.

  • Modify /BusinessML/NAV1.xml entry to include new <NavItem> as child to the Nav1 container element (<Nav1>).

    [Caution]Caution

    There must be at least one (really, more) new Level 2 pages to go beneath this new Level 1 page. To add them, follow instructions above re: their addition.

  • Modify /BusinessML/NAV2.xml entry to include new Nav2 grouping element (e.g. <Nav2 sitesection="xyz">).

    Further modify NAV2.xml to provide the children <NavItem>s to the new Nav2 grouping element, for the new children Level 2 page(s).

  • New site navigation graphics are required (Nav1s are images).

    C:\mlnmdev\htdocs\images\nav\ 
    NAV1_1rad_off.gif
    NAV1_1rad_ro.gif 
    NAV1_1rad_on.gif 
    NAV1_1rad_in.gif 
    ("on" is identical to "in", therefore the additional graphic is not actually used) 

    "Page Header" graphics:

    C:\mlnmdev\htdocs\images\pghdrs\ 
    pghdr_1rad.gif
    pghdr_1rad_photos.jpg