Maing a quality website ---> Javascript

I'm making a site for my school. I am very good at HTML and using Dreamweaver to make a site. I am using Photoshop to make clean graphics and I am containing my site inside a table that will center itself automatically when opened so that the site wil be compatible with any computer at any resoluion.

I have a top Navigation bar for the site. What code makes the big content cell below the navigation cell link to a site that is already created?

I also want to set up the site so that the Navigation bar will not have to reload and only the large contelt cell in the table will change. I friend suggested that Javascript can do this. I have knowlendge in the code structure and basic functions of Java, but I don't know the actual commands. Suggestions?

 

Log in or Sign up to hide all adverts.

You can accomplish that with CSS, and it takes less effort than html/javascript.

http://csszengarden.com
http://www.w3schools.com/

 

Log in or Sign up to hide all adverts.

Do you mean that a page should load in the content containing cell? Or that the entire cell should be a hyperlink? The former might use the IFRAME tag, DHTML(ie css/js/div tags) or you might approximate it with frames. I'd consider using a plain page unless you have an essential need for a omnipresent menu bar, that kind of thing irks people.

http://mercury.tvu.ac.uk/~lucieh/iframe.htm here is an iframe example.

 

Log in or Sign up to hide all adverts.

I'll have to learn CSS then. I don't have time this evening because I'm about to go somewhere. Can I integrate CSS into HTML? Oh, and I want the page to load inside the cell.

 

I think you mean: making a quality website != javascript.

You can do this with php, asp or any other server-side scripting language.

 

Yes and no. There are 3 types of .css. External, internal and inline. inline is in HTML tags. eg. <table style="blah, blah, blah">Internal resides in the head btw. style tags, whilst external is in a .css file.

 

I think thats a little unfair, what it should really be is:
quality website != incompatible browsers.

Like for instance browsers that alter their standards for the language because of them being intergrated with the Operating System. (Since Javascript was really meant to be both a glue language allowing transitions from HTML to do form parsing etc, and also was suppose to be "Safe" in the sense that nothing could be written to system by it "originally")

There is only so much you can do if you are doing a website "Client-Side" since you have to look at the compatibility of browsers and how they deal with the code as they see it.

As for serverside it's definitely more time and effort, but worthwhile if you get into it.