Sub - Page best practices

Report · Jan 19, 2009

My site has a main index.cfm template which loads "sub-pages" (say #content, #navbar, etc)

What if anything should I put in the header of the subpages??? Specifically, below is in my index.cfm (most put there by DW automatically) but for the pages which (are NOT designed to be seen independently of the .index) what should/need be used?

FWIW, heretofore I have put nothing save comments at the top of subpages BUT have recently been compelled to move SOME css into the subpages (rather than all in the index.cfm css link) and thus need to have at least a <head><style type="text/css"> . . . </style></head> area (plus I then have put in a body tag as well).

But I have noticed that when doing so some of the DW code highlighting does not work (i.e. divs won't stay blue, cfouputs won't stay red etc). even when they seem to my eye to be proper.

Thanks in advance for any and all comments,

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" " http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=" http://www.w3.org/1999/xhtml">

<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

Report · Jan 19, 2009

If you sub pages get rendered in frames, they should have their own doctype, html, head, and body tags. Otherwise, they should not have any. They should be somewhere between the body tags of the main page.

Report · Jan 19, 2009

Report · Jan 20, 2009

Thanks to you both. Follow up though, as I understand it the css page(s) are loaded and saved into browser cache. My single CSS link/page is however getting quite long.

What are your thoughts on breaking it up into separate pages (obviously with 2+ links in the index.cfm header) -- both for manageability and for specificity (i.e. I have six slightly differing #content Divs)?

I know I can devolve down to in-line CSS on each of the different divs (and think I am correct in saying that neither a link to an external CSS page and/or <style> definition on a sub page is possible) . . .

Report · Jan 20, 2009

quote:

Originally posted by: ProjectedSurplus
Thanks to you both. Follow up though, as I understand it the css page(s) are loaded and saved into browser cache. My single CSS link/page is however getting quite long.

What are your thoughts on breaking it up into separate pages (obviously with 2+ links in the index.cfm header) -- both for manageability and for specificity (i.e. I have six slightly differing #content Divs)?

Sounds like extra work with no accmplishment.

Report · Jan 20, 2009

> What are your thoughts on breaking it up into separate pages (obviously with 2+ links in the index.cfm header) -- both for manageability and for specificity (i.e. I have six slightly differing #content Divs)?

You can break it up, it won't hurt anything. Do it by category (like nav.css, header.css, body.css, common.css) or something else.

> btw, part of why I set out on this possible goose chase is that I had hoped to be able during editing to preview in the browser the subpages independently of the index.cfm (ie if I preview only the subpage then there is no css link and hence no formatting)

I don't code the same way as you, so I can't provide any recommendation here. I don't use a WYSIWYG editor like Dreamweaver.

>Presumably these (duplicate) body tags are similarly redundant/non-conforming so is there an easy alternative (code or site to read)?

<script language="Javascript/1.0">
document.SignInForm.password.focus();
</script>

Report · Jan 20, 2009

quote:

<script language="Javascript/1.0">
document.SignInForm.password.focus();
</script>

does not seem to work. Am I missing something (note I am putting the script on a "sub-page" insofar as depending on which of these subpages is shown the cursor will go to a different form element).

I googled ( http://www.webdeveloper.com/forum/showthread.php?t=8846) which refers to a
<body onload="placeCursor()"> in addition to the script:
<script type="text/javascript">

function placeCursor(){
document.formName.fieldName.focus();
}

</script>

Report · Jan 20, 2009

That will work more reliably. Just need to ensure that you're not defining more than one placeCursor() function.

Report · Jan 20, 2009

btw, part of why I set out on this possible goose chase is that I had hoped to be able during editing to preview in the browser the subpages independently of the index.cfm (ie if I preview only the subpage then there is no css link and hence no formatting)

thoughts on whether I am just chasing my tail here :)?

Report · Jan 20, 2009

also, to put the cursor into the appropriate form onLoad I have <body> tags per:

<body onLoad="document.SignInForm.password.focus();">

Presumably these (duplicate) body tags are similarly redundant/non-conforming so is there an easy alternative (code or site to read)?