Forum Home
Press F1
Thread ID: 33399	2003-05-15 06:11:00	Setting up Website	lovelee (1294)	Press F1

Post ID	Timestamp	Content	User
144358	2003-05-15 06:11:00	Hmmmm .. I used to think I had a grasp on this .. but I find USER FRIENDLY aint quite so USER FRIENDLY !! I ahve designed our webpage ... and we have bought our domain etc ... I have had no end of trouble getting it up and running ... now I find that the pages have to be saved *relatively* in publisher to be able to link one to another ... can anyone tell me how or where I find this option .. also .. if I have several topics on a page and i wish for each to link to a diff page .. how is that accomplished ??????	lovelee (1294)
144359	2003-05-15 06:15:00	Well the links are easy... You should be able to select the text you want hyperlinked, right click on it, click HyperLink and just enter the page you want it to go to. From there just select some more text and do exactly the same - this will hyperlink the different topics to your different pages CyberChuck	cyberchuck (173)
144360	2003-05-15 06:33:00	ok, for a beginner in website building, I recommend you take a serious look at w3school's html tutorials (www.w3schools.com). Publisher doesnt output the tidiest or intercompatible/standards based code, so "alternative" browsers such as opera, mozilla etc may have problems displaying your pages as you intend them.. whereas if you just stick to plain standard code, then all browsers should have no problems at all... validator.w3.org (http://validator.w3.org) is also a valuable tool in ensuring standards compliance. Now, relative linking if I recall correctly goes along the lines of this: you link "relative to the root" for internal links... so for example you have the following pages: index.html contents.html me.html myfriend.html A common mistake among beginners is to create absolute links. So on your index.html page you might have links to say: www.domain.co.nz/contents.html www.domain.co.nz/me.html www.domain.co.nz/myfriend.html as an example the link will look like this in code: My Friend (www.domain.co.nz/myfriend.html) The problem with this is what-if you move from say .co.nz to .com? Or from domain.co.nz to anotherdomain.co.nz? the links wont work as you intended them to... so you use relative linking. On your index.html, your links point to: contents.html me.html myfriend.html as an example the link will look like this in code: My Friend (myfriend.html) now lets say you have an image stored in images/. We'll call it picture.jpg. With an absolute link it would come out as www.domain.co.nz/images/picture.jpg which in code will look like: www.domain.co.nz/images/picture.jpg but again, what if you move hosts or change your site around considerably? Instead you will want to use the relative link: images/picture.jpg which in code will look like: images/picture.jpg So when the browser or whatever goes to look for the resource, it looks relative to the root (think of your file structure as a tree.. the root is where everything is based, each folder is a branch and each file is a leaf... for example on your computer c:\ is the root, c:\windows\ is a branch and c:\windows\somefile.txt is a leaf - A very basic description but this post is getting long winded enough) The point is you use relative linking for simplicity, tidiness/efficiency of code and for consistency. So finally, rule of thumb: For internal resources (other pages, images, files etc hosted on the same site) use relative linking For external resources (links to pages, images, files etc hosted on other sites) use absolute linking Hope this hasnt confused you too much, I'm certain others will gladly clarify	whetu (237)
144361	2003-05-16 07:14:00	OK Whetu .. I think I get most of that .. My problem now is ... I am not sure how to or where to put in contents.html etc ..... Do i create another folder in public.html ? Or do I go *up one level* ... and create a folder/page named contents.html ????	lovelee (1294)
144362	2003-05-16 08:04:00	your file structure is really up to you.. I was always traditionally trained to just throw all the html files into a folder and all the images into an images folder... so for example on a small site the root would look like: (i'll use an asterisk to indicate a folder) *images/ (all images stored in here) index.html contact.html aboutus.html etc etc but with larger sites you'd group information into folders.. so for a personal site for a family for example: *mum/ (all html files stored in here) *mum/images/ (all images required for mum's html files in here) *dad/ (all html files stored in here) *dad/images/ (all images required for dad's html files in here) *son/ (all html files stored in here) *son/images/ (all images required for son's html files in here) *daughter/ (all html files stored in here) *daughter/images/ (all images required for daughter's html files in here) index.html main.html whatever.html and then other resources that werent images would get their own folders.. things like css, other media etc however other people have been taught differently.. another method I've seen used is to create a folder for every page eg: *index_files/ (any resources like images for index.html goes in here) index.html *contactus_files/ (any resources like images for contactus.html goes in here) contactus.html *welcome_files/ (any resources like images for welcome.html goes in here) welcome.html which will seem perfectly logical to those people who are taught that way, but seems messy to me (especially when it comes to coding your pages) oh.. another hint for relative linking - you can go up a level by using ../ so for example if you are in a folder and you want to go up a level to get a resource you can use that.. for example we'll use the family site example... Let's say you are coding index.html for daughter/ and you want to get something in the root/images/ folder.. simply use ../images/picture.jpg What happens then is when the browser is rendering the page, it sees "../" and goes up one level in the directory structure, and then goes into the images folder (or whatever folder you define) I'm not quite sure that I'm following you.. we're having a bit of a miscommunication I think... >>My problem now is ... I am not sure how to or where to put in contents.html etc ..... >>Do i create another folder in public.html ? Or do I go *up one level* ... and create a folder/page named contents.html ???? As I have no idea on how you have organised your directories I cant really advise or guess appropriately... Can you describe what pages you've got and how you want them to be linking to each other? again, hope I havent confused you too much if at all...	whetu (237)
144363	2003-05-16 09:01:00	whetu- that is so nicely put. :D :D i'm impressed that you even included the alt tags which most people/wysiwyg editors leave out.	tweak'e (174)
144364	2003-05-16 23:46:00	Whetu .. would you please contact me on my email .. lovelee@xtra.co.nz That is if you would be prepared to assist me .. Ohhh and if you are broad minded !! Leigh	lovelee (1294)
144365	2003-05-17 00:22:00	thanks tweak'e :D I used to exclude them.. my attitude was "bah! IE has the majority so I'll just code for that" I didnt care that my sites showed like crap in mozilla Then I actually got some formal HTML training and the tutor's anal retentiveness rubbed off on me.. now I code html to standards and wont really be happy until it all validates nicely... my coding is WAY tidier now too, which is far easier to read and figure out, which is especially handy for troubleshooting.. which is a habit I should have picked up when I did my programming papers *rolls eyes*	whetu (237)
144366	2003-05-17 00:23:00	lovelee.. i'll send you an email when i get home from work (www.weltec.ac.nz)	whetu (237)
144367	2003-05-17 03:14:00	Some of the instructions you guys are giving are extremely general... unfortunately Publisher (assuming you are referring to M$ Publisher) has a very very proprietary way of arranging all the links and content of a web-site... It will create a somewhat bizarre directory structure to store all the content in aside from the index page. One of my clients uses it and it is really not good for webdev - the source code for her index.html is 500kb on it's own without any images.	whiskeytangofoxtrot (438)
1 2