Hmm... I need to find out myself. I don't know what is the answer to that question. I'll do some poking around and get back to you if I got an answer. You should email the people at iPage as they probably know..
Yah, I know thats why I cant put a background, but I want to know if theres a way I can change it so I can have my repeated side image mix with a backgrond...
Wait. YOu already did. The way you did it, you can have the OTHER cell have a background, so then you get the repeating image in one cell, and the sidebar in another!..
Do not use tables, tables are the most complex of all regular html code structure and should not be used for positioning elements on webpages. You will want to use a div most likely, one for your sidebar and one for the main content, something along these line:.
In your CSS:.
Div.sidebar {.
Position: absolute;.
Left: 0;.
Top: 0;.
Width: 200px;.
Height: 100%;.
Background-image:url(rustsheet.jpg);.
Background-repeat:repeat-y;.
Z-index: 2;.
}.
Div.main{.
Position: absolute;.
Left: 0;.
Top: 0;.
Width: 100%;.
Height: 100%;.
Background-image:url(yourotherimage.jpg);.
Z-index: 1;.
Padding-left: 220px;.
}.
In your html page:.
<div class="sidebar">.
Your sidebar content.
</div>.
<div class="main">.
Your main content.
</div>..
I would have to beg to differ there Kevin. Tables are not to bad and think they are a great way to lay a iPage site out. There are drawbacks but I think the pros far outweigh any cons..
I would say tables are very easy to learn... but the trick is not to rely on them too much or make them too convoluted..
Only a thought, not saying Kevin is wrong, just that I take a different view...
K I think I will try what Kevin suggested, I dont know how to make tables, so if Kevins thing doesnt work, then I guess I will have to learn the tables. but thanx alot guys for all the help..
Please don't beg, it makes you look pathetic.
Tables are not supposed to be used for positioning elements on webpages anymore, it's been recommended that webdesigners get away from tables for maybe 4 years now. Once you free yourself from the table design model and use the box design model you will never go back to tables except for what they are meant to be used for, to display tableized data..
Nuff said...
Beg... me beg... never... those are fighting words Sir. Pistols at dawn?.
I agree with you in the most part. However the performance of many browsers leaves a lot to be desired. Tables are IMHO fairly robust and easy to use. It is very easy to design a page this way as well. Using posistioning can be a royal pain in the ass at the best of times..
I also find it hard to visualise design this way as well. Maybe practice will get me better at seeing design from a pixel perfect point of view in time..
I also find it easier to come back to a table layout design to make changes. Table code has a certain flow about it that is easy to understand. Give me a posistioned based equivalent to read and visualise... and I have a killer head ache..
In time who knows... now count to ten and no turning before the count is up...
What do I put in "your side bar content" and "Your main content"? the image I want to put on my sidebar content is called Scrathnews.jpg and the image I want to put for "your main content" is called metalfloor.jpg ..
I want to know what I would type to atacht those jpegs to the content places...
Type those names in place of the example names..
Just try it; save the file and hit reload on the browser...
I already tried that,.
<div class="sidebar">.
Scrathnews.jpg.
</div>.
<div class="main">.
Rustsheet.jpg.
</div>.
And it didnt work...
The images don't go in the DIVs, they go in the CSS stylesheet code, just as in the post three above here..
Make sure that the images are in the same folder as the HTML file [as well as the same folder as the the CSS file (if you use external CSS files that is)]...
K, that really confuses me. My mind cant comprehend what you mean there Giz sorry...