Separating Javascript from HTML

[domino1]

Is there an easy way that the javascript that gets included on all the catalog pages can be separated out into an external file? That way each page can just reference the external file instead of loading the scripts individually. My thinking is that this may help to improve the keyword density of a page and improve its content to code ratio.

[NormanRouxel]

That's what happens for the larger JavaScript files. E.g. actiniccore.js, actinicextras.js and the section tree files. There should only be small chunks of JavaScript in most generated pages.

Norman

[domino1]

Thanks Norman.

Out of interest, why isn't all of the js located in these external files?

[Mike Hughes]

Note that when search engines look at the keyword density they only look at content (i.e. stuff that's visible to the user). Not code.

So there's no real penalty to having some bits of javascript on the page other than a little bit of loading time. (a tiny, tiny, tiny difference even on dial up).

Mike

[garyhay]

Just as an add on to the above.

I would steer clear of having a log on box on every page as the code used for it is like a mini novel.