new domain arrived.....
Friday, December 28, 2007
first thing first.. u need to put ns for DNS pointing to your domain, because we used Exabyte, we can access our domain manager to change by our own DNS services. Here the capture screen of domain manager,
*/ps
To have your domain resolve correctly, please use ns1.everydns.net, ns2.everydns.net, ns3.everydns.net, and ns4.everydns.net as your domain's nameservers in your registrar's whois database. Without that, none of your records will resolve properly. (NS1 is in San Diego, while NS2 is in San Jose, NS3 is in the Netherlands, and NS4 is in Washington, D.C.)
here the solution... u need to go here and register DNS services for free everydns.net
after u register and login with your username and password
then add your domain e.g. openportalsolution.net and add the setting like screen below,
next, go to your blogger.com and edit the domain setting,
after that, we need to check our DNS pointing... by using cache check from everyDNS
and the result is......
and your domain is ready... try this blog.openportalsolution.net
Labels: everyDNS.net, free DNS service forever
First step towards html.
Saturday, December 22, 2007
- We will use notepad as our first step of making webpage.
- Open a notepad file and save as test.html in desktop.
- Click right mouse to edit this html files.
- Insert html open and close tag i.e. <html> </html>.
- In the html tag we need to make head tag and body tag.
- Head tag <head> </head>.
- Body tag <body></body>.
- In the header tag we will put title tag.
- Title tag <title></title>.
- In the body we will put any thing that we want to put i.e. table, picture, video, music, and many more.
This is the html coding that we can use for our studies:
<html>
<head>
<title>Testing html</title>
</head>
<body>
Put anything you want here.
</body>
</html>
Just copy and paste this coding to make the test.html file.
5-Meta Command
Tuesday, December 18, 2007
Search Engine... What's That?
A search engine is a program that takes key words from you, searches a database of Web pages, and gives you back a list of pages that might be helpful. Yahoo is a search engine, as is Webcrawler. If you'd like to see a list and a half of search engines and learn how to use them straight from your own page -- see my tutorial So, You Want A Searchable Database, Huh?.
When you submit your page to a search engine, or "register" the page as Net-heads like to say, you are asking the people who keep the page to place your page's text into a huge database. Yahoo's database was well over 3 million pages, last I heard.
When you use the search engine, you enter "keywords." Let's say you were interested in deep-sea fishing. You'd enter those words. The database would be searched and would return any pages containing those words.
When you register a page, some search engines ask you to enter a few keywords. What you are allowed to offer is limited. Wouldn't it be nice if you could send the search engine a page that has all the keywords written out in the HTML text? This way you could make the search engine's job a lot easier and get your page brought up onto the screen a lot more often.
What You Can Do With Meta Commands
There are three things (in terms of search engines) that I know of:- Offer Keywords to the search engine.
- Offer the name of the computer software, herein known as the "Generator", you used to make the page (it helps).
- Offer a description to use when your page is displayed.
--Some search engines do not show descriptions, so this won't work on all engines. - Offer the author's name.
- Offer a copyright statement.
- Offer an expiration date so the search engine's database stops bringing your page up after a certain time as passed.
Let's remember that you are playing against a search engine here. You will play by its rules, not the other way around. These items will not work on all search engines, but will be successful on most.
Offering Key Words
Follow this format:
<META NAME="keywords" CONTENT="big,ugly,stupid,Baltimore,Ravens,fan">
Sorry, Ravens fans. I like whom I like and I can't change for anyone. I grew up in Cleveland. No jokes! See what I did? I offered keywords, all separated by a comma. No space. Some servers don't like an added space and may not bring up the page because the space is seen as part of the word. Offer words in the format above.
ALSO some servers will bring up one page over others because the keyword appears more than once in the page. So, why not offer 10 or 12 of each of the keywords you are using? Huh? Why not? That would work, right?
No! That's spamming! And search engines hate it. Do not type multiple keywords like, "Browns,Browns,Browns,Browns,etc.". If you do, you'll probably be stricken from the search engine's database. They're real picky about that kind of stuff. Play fair. You can put in a ton of keywords. Just make them all different.
One more thing...don't put in false keywords. That can also get you kicked off the search engines. We all know that Yahoo! is one of the most visited sites on the Web. If you put "yahoo" in your keywords yet that has nothing to do with your page, that's not good. Play fair.
Offering Your Page Generator
I don't get this one, but I always put it in anyway. It's another thing the search engine can use to isolate your page. It's simply the program you used to make your page. This is what mine always looks like:
<META NAME="Generator" CONTENT="HTMLpad">
Use it in good health.
Offering a Description of Your Page
If you use search engines to any great extent, you no doubt have seen the ones that return the title of the page and then something like the first 25 words. Most of the time, the text makes no sense. Wouldn't it be great if you could tell the search engine what description to place on the search-results page? Yes, it would!
(It's a sign the mind is starting to go when you keep answering your own questions.)
Here's the format:
<META NAME="description"
CONTENT= "Come to my page please!">
...pretty self-explanatory.
Author, Copyright, Expire, Etc...
These follow the basic format as above. Here they are.
- <META NAME="author" CONTENT= "Some Body">
This tells search engines who wrote the document. - <META NAME="copyright" CONTENT="Copyright © 2001">
This tells search engines the copyright. - <META NAME="expires" CONTENT="15 September 2000">
This automatically expires the document in the search engine's database. - <META NAME="DISTRIBUTION" CONTENT="global">
The page will go global - <META NAME="REVISIT-AFTER" CONTENT="15 days">
Have the Search Engine revisit the site to possible relist. - <META NAME="ROBOTS" CONTENT="all">
Use all the bots to list the site!
Where Do I Place These On My Page?
Somewhere close after the TITLE commands, but still between the HEAD tags. Make sure your page's title comes first as that is the first item many search engines use -- Webcrawler does this. Also, when you submit a page to a search engine, don't put something in the title that is different from the rest of the page. It may be clever, but it's messing up the search for your information. Change it on your server, but be sure to submit a copy that is done correctly.
What If I've Already Submitted the Pages?
What to do now depends on the search engine people. Many will only take a submission once. Some might take updates, but those are last on their list of priorities.
I've Never Submitted a Page to a Search Engine. How Do I Do It?
There are a couple of ways. You could drop by the search engines (there's a pretty full list of them here) and follow their link that reads, "submit URL" or words to that effect.
There are also sites on the Net that will allow you to submit to many at the same time. Submit It! is by far the best. It's not a hard process. In fact, it's kind of fun to get all those e-mail messages from these big companies telling you your work was cool enough to be used in their database.
What's even cooler is going to a search engine and looking up your own page.
Thanks for coming by...
4-Head Commands
The conversation went downhill from there.
Actually we're both right. Here's a very basic HTML document format. You've seen this example 100 times, I'm sure.
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
Displays in browser window
</BODY>
</HTML>
It wasn't until the advent of JavaScript and META commands that I even cared what they did. This is all true. When I teach HTML in a classroom, I do not incorporate the HEAD commands until after the students learn to manipulate text with bold, italic, and other types of commands.
I'm sure that statement is right now driving someone out of his or her skull. Again, I say... what would you tell students who are just being introduced to the language what those commands do? Header commands are a great part of HTML. I know that now. But I still think they are to be taught separately, as something to incorporate rather than something that's required.
I don't know why I told you that... I guess I just love sharing with you people. So, let's get started.
What The <HEAD> Commands Actually Do
The HEAD commands do three things:
- They contain information regarding the document.
This data does not appear in the browser window when the page is loaded. The data is mainly used for helping search engines with page descriptions, browsers with base domains, and other data not generally regarded as display content. - They separate the page into two distinct sections.
Ever go into a page that won't load, but somehow the title is up there? It's inside the HEAD commands. - They are loaded first and what is included between them is run first by the browser.
Here's the first section in a little more depth:
Information Regarding The Document
TITLE Commands
This is the most popular command to appear between the HEAD commands. It places text within the color bar at the very top of the browser.
I must say I liked it before the newer version browsers placed their name after the TITLE text. That did not used to be the case. It was just text you wrote. Plus if you wrote a lot of TITLE commands, they would all be compiled one after the other. You could have animation in the blue bar at the top. It was great. The newer browsers don't go for more than one TITLE command these days.
Geez, I'm starting to sound like Dana Carvey's Grumpy Old Man. We had lots of TITLE commands. And that's the way I likes it! ...Sorry.
At this point in time, we'll begin constructing the fully functioning HEAD command extraordinaire.
<HEAD>
<TITLE>Big Fat Head Commands</TITLE>
</HEAD>
META Commands
I have a full tutorial just on META Commands and what they do. Here, I'll quickly outline some of the more popular ones.
- <META NAME="keywords" CONTENT="key,word,key,word">
This offers key words to the search engines that use them in their searches. - <META NAME="description" CONTENT="Great page! Come see!">
This offers a description of the page for search engines that use them. - <META NAME="generator" CONTENT="Notepad">
This tells search engines what program was used to create the document. - <META NAME="author" CONTENT="Some Body">
This tells search engines who wrote the document. - <META NAME="copyright" CONTENT="Copyright © 1997 Me">
This tells search engines... blah, blah, blah. - <META NAME="expires" CONTENT="15 September 2000">
This automatically expires the document in the search engine's database.
Adding these commands, our Super Duper Head command section grows to this:
<HEAD>
<TITLE>Big Fat Head Commands</TITLE>
<META NAME="keywords" CONTENT="key,word,key,word">
<META NAME="description" CONTENT="Great page! Come see!">
<META NAME="generator" CONTENT="Notepad">
<META NAME="author" CONTENT="Some Body">
<META NAME="copyright" CONTENT="Copyright © 1997 Me">
<META NAME="expires" CONTENT="15 September 2000">
</HEAD>
The Base HREF Command
The Base HREF instructs the browser to use a path as a basis for all links and images on its page. Here's the basic format:
<BASE HREF="HTTP://www.htmlgoodies.com/">
The command acts as a reference for the remainder of the page. When you use the Base HREF, whatever you place between its quotes will be added in front of any links you write. For example:
I write the link:
<A HREF="page.html">
Since my document employs the Base HREF command, the link now becomes http://www.htmlgoodies.com/page.html.
I have yet to adopt the Base HREF command because of the setup of my pages. I include page jumps a lot. If I use a Base HREF, then the page jump only works on the server. If the document is on my hard drive, then it won't jump because the Base HREF command won't stop adding the domain to the links and images. However, when the page is posted to the Net, it tends to reload the page with the entire domain attached rather than just jumping to the page section I want. I don't use it, but I can see why one would use it. If your page happens to be reposted off of your server, then all of the images would point back at the original source of the images.
Let's continue making our Super Duper HEAD command section:
<HEAD>
<TITLE>Big Fat Head Commands</TITLE>
<META NAME="keywords" CONTENT="key,word,key,word">
<META NAME="description" CONTENT="Great page! Come see!">
<META NAME="generator" CONTENT="Notepad">
<META NAME="author" CONTENT="Some Body">
<META NAME="copyright" CONTENT="Copyright © 1997 Me">
<META NAME="expires" CONTENT="15 September 2000">
<BASE HREF="HTTP://www.htmlgoodies.com/>
</HEAD>
Parts Two and Three
Above I said that the Head commands break the page into two distinct sections and also are loaded and run first. Where that comes into play is where you have a script of some sort. Let's take JavaScript, for example.
If you place your JavaScripts in the HEAD commands then they will be run first before the remainder of the page loads. Usually this is the case when the JavaScript has two parts, a script, and then something that calls for that script to place an object on the page. The Image Flip tutorial is a good example of this.
The purpose of separating the script from the element that calls for it is to speed the use. The script is already running by the time the call is made for its services.
As for separating the document into two parts, it is often possible that two entities won't run together. Again, two JavaScripts, for example. Placing one inside the HEAD commands and the other inside the BODY commands tends to separate them enough to calm the fight. Often, they then both run.
Adding a JavaScript to our Super Duper HEAD command section, we get this:
<HEAD>
<TITLE>Big Fat Head Commands</TITLE>
<META NAME="keywords" CONTENT="key,word,key,word">
<META NAME="description" CONTENT="Great page! Come see!">
<META NAME="generator" CONTENT="Notepad">
<META NAME="author" CONTENT="Some Body">
<META NAME="copyright" CONTENT="Copyright © 1997 Me">
<META NAME="expires" CONTENT="15 September 2000">
<BASE HREF="HTTP://www.htmlgoodies.com/>
<SCRIPT LANGUAGE="JavaScript">
</SCRIPT>
</HEAD>
Ah, but it goes on. It is now possible to use these things called Cascading Style Sheets to help pretty up your pages for all. They go in the Head commands, too.
Add them in the recipe and you get the finished product:
<HEAD>
<TITLE>Big Fat Head Commands</TITLE>
<META NAME="keywords" CONTENT="key,word,key,word">
<META NAME="description" CONTENT="Great page! Come see!">
<META NAME="generator" CONTENT="Notepad">
<META NAME="author" CONTENT="Some Body">
<META NAME="copyright" CONTENT="Copyright © 1997 Me">
<META NAME="expires" CONTENT="15 September 2000">
<BASE HREF="HTTP://www.htmlgoodies.com/>
<SCRIPT LANGUAGE="JavaScript">
</SCRIPT>
<STYLE>
</STYLE>
</HEAD>
Well, there it is. The ultimate HEAD section of an HTML document. Of course, all of that is not needed, but it can't hurt to add it. You'll be helping search engines and some users of your site. I've altered the program I sometimes use to include the six meta commands above already. I'm not so sure about the Base HREF command yet though....
Enjoy!
3-HTML Declaration
The command:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
That's a strange looking thing, huh? It's called an "HTML Declaration." Basically it's declaring what version of HTML the browser is to use when reading this document. It also tells the viewer, if they care to look. It's long, but rather easy to understand. Here's what it means:
- !DOCTYPE HTML PUBLIC proclaims this is an HTML document type that can be read by public browsers.
- -//W3C represents the HTML organization that denotes what HTML commands are to be used and what are not. You can visit their WWW page at http://www.w3.org and read about HTML until your brain is full.
- //DTD HTML 3.2 stands for Document Type Description HyperText MarkUp Language (version) 3.2.
- //EN means the document will be written in the English language.
If you were attempting to write HTML using the commands set aside in HTML 4.0, then you would change the header above from 3.2 to 4.0. Now, I'm not talking browsers here. I am talking version of HTML. Again, if you'd like to read about new and older versions of HTML and what makes them different, go to http://www.w3.org. 4.0 is out and there are reams of paper on what it will do.
My assumption is that once you read this, you will right away ask if you need to hurry and put the command on your pages. I don't have a good answer for you there. I knew that would come up so I contacted my brain trust of HTML people. One said yes, one said no, the other said to do it if you remember. Not exactly the consensus of answers I was looking for.
So, do you use it? Yes. I do on every page now. I started putting it on when I first learned about it. Some of my very early pages do not have the command and I'm in no real hurry to get it on them. Mainly because the pages use very early, and very basic, commands that do not belong to a higher version of HTML. Besides, if you do not have a declaration, I've been told the default is the highest HTML version. I would not be doing myself any good by altering the page.
I'll give you a couple rules of thumb that one of the HTML big-heads told me. If you're using META commands or plan to use HTML validators... use the declaration.
2-Set Up Your First Site
Putting A Site Together
Lately, I've been getting a lot of email asking about setting up a site with numerous internal pages. For example, let's say you create a homepage. We'll call it homepage.html.
You then create three more pages:
- links.html (A page of your favorite links)
- photos.html (A page of your favorite photos)
- story.html (A page with one of your best stories)
At the moment they are just sitting on your hard drive (or floppy disc) and now you want them to become a site. Homepage.html will offer links to the three other pages. That'll be your first site. Good. Now, how do you do it?
The HREF Links
First off, I'm assuming you already have a place to post these pages.
So, now you have a place for your files. This "place" you have been given is actually a small section of a hard drive on a server somewhere. In computer terms, you have a directory where you can place your files. Think of this directory like an equal to a floppy disc. It's a contained area where the pages, and all the images that go on those pages will be housed.
This is important to remember when you're writing the links that will connect these four pages together.
In Site vs. Off Site Links
You've probably already read through Primer Four - Creating Links. If not - give it a once over pretty soon. It'll give you the basic format of a link. Now let's talk about the pages you'll link to.
First off, let's attach to a page outside of your site. Here's the basic format:
<A HREF="http://www.htmlgoodies.com">Click Here</A>
Note the address above is a full URL. ("URL" stands for Universal Resource Locator. It's a fancy way of saying "web address") It starts with that http thing and ends with that .com deal. It's a full address.
Now let's look at what I call an internal link. This is a link that stays within your own site. One of your pages is calling for another one of your pages. We'll say this is a link from your homepage.html to links.html. Remember that from above? Here's the format:
<A HREF="links.html">Click Here</A>
Notice I'm only calling for the page, without the full address attached. Why? Well, because I don't need it. To make the point a little stronger, let's look at the directory structure of web addresses.
Directory Structure
For the sake of continuing this discussion, and because I love to hear myself talk, let's take this little fantasy of mine a bit further. You purchase an account on a server called www.joeserver.com. When you sign up for your account, you choose the login "schmoe". This means that, most likely, your email address will be schmoe@joeserver.com and your web site address will be http://www.joeserver.com/~schmoe. The little squiggly line thing (~) is called a tilde. It tells the server, "There is one directory on this server called 'schmoe'- find it."
When you use your File Transfer Protocol (FTP) program to upload files to your new server, you will upload into the directory that was set aside for you - in this case, schmoe.
So you upload your homepage.html page into your directory. The address of that page is now http://www.joeserver.com/~schmoe/homepage.html.
See the slash I added and then the name? I do that because the homepage.html page is now inside your directory called schmoe.
Think of a directory structure as one item being inside of a larger item. For example, a word is inside of sentence, is inside of a paragraph, is inside of a page, is inside of a chapter, is inside of a book. If this were written in directory structure format, it would look like this:
Book/chapter/page/paragraph/sentence/word
It gets smaller as you move to the right, each is inside the previous. Take this URL for example:
http://www.server.com/users/pages/ohio/joe.html
In that URL, the page "joe.html" is inside a directory called Ohio, is inside a directory called pages, is inside a directory called users, is on a server called server.com.
That's why the page homepage.html is at the end of the address above. Make sense?
Internal Links
Now we put together a site in your own directory. Once again, you have a homepage called "homepage.html" and three sub-pages that you want to link to from homepage.html. They are "links.html," "photos.html," and "story.html". First off, you need to to FTP, or "upload" all four pages to your directory. Now, here's the first link on homepage.html that will call up your links.html page.
<A HREF="links.html">Click Here</A>
Notice I am only calling for the page by its name. I am not using the full address.
Now, I could use the full address. There's no reason why I couldn't. If you followed along with the discussion above, you'll remember that since the file was uploaded into the schmoe directory, its full address would be http://www.joeserver.com/~schmoe/links.html. So why not use it?
To Use Full URL, Or Not To Use Full URL
If you are linking to a page off of your site, then you must use the full URL. The reason is that you are leaving your own directory. In fact, the chances are really good that you are leaving your server all together. Because of that, you need to offer your HREF command the full address to the new site.
But when you're staying within your own site, as we are above, you need only call for the page name. You see, your directory is a closed home for all of your pages. If you only call for a page or an image through its name minus the full address, what happens is that the server looks for the page or the image inside the same home that houses the page that called for it. In other words, servers will search a page's home directory by default. That's good to know when you create your links. It means you only have to use the page's name minus the full URL.
What If I Do Use The Full URL?
Always playing the rebel, huh? The answer is that your internal links might run slower. You see, if you use the full address, what happens is that when your user clicks on a link, a full search process begins. First the server is located, next the directory is located, then the page is located. Whereas, if you use only the name, the search is already at its destination. The server simply searches itself. Slick, huh?
The Home Page Links
So what is written onto homepage.html to link the pages together? This:| <A HREF="links.html">Click Here for My Favorite Links</A> <A HREF="photos.html">Click Here for My Photos</A> <A HREF="story.html">Click Here for My Best Story</A> |
Basic HTML: tags
Sunday, December 9, 2007
HTML works in a very simple, very logical, format. It reads like you do, top to bottom, left to right. That's important to remember. HTML is written with TEXT. What you use to set certain sections apart as headings, subtitles, bold text, underlined text, etc is a series of tags.
Think of tags as making your structure. Let's say you want a heading. You will put a tag at the exact point you want the heading to start and another tag where you want the heading to stop. If you want just a word to be emphasized, you will place a start emphasis tag at the beginning of the word and an end emphasis tag at the end of the word. Is this making sense so far?
Tag Format
All tag (I sometimes call them command) formats are the same. They begin with a less-than sign: < and end with a greater-than sign: >. Always. No exceptions. What goes inside the < and > is the tag. Learning HTML is learning the tag to perform whatever command you want to do. Here's an example:
The tag for a paragraph is "p". That makes sense.
For example:
<p>Joe</p>
In the old HTML standards, we used to use B for bold, and I for italics, etc. With the latest standards it is now accepted practice to separate content from presentation - by which we mean you set out the structure of your document in HTML, and control how it displays using a CSS file (more on this later!)
This means we can mark our keywords using strong and em tags, which have the same effect, but comply with the latest standards.
<strong>Joe</strong> and <em>Burns</em>
- <strong> is the beginning strong tag.
- "Joe" is the word being affected by the <strong> tag.
- </strong> is the end strong tag. Notice it is exactly the same as the beginning tag except there is a slash in front of the tag command.
- This is what the strong tags above produced: Joe Nice, huh?
Q. Is the end tag for other commands simply the begin tag with the added slash?
A. Yup.
Q. Will the tags show up on my page?
A. No. As long as your commands are inside the < and > marks, the tag is used to alter the text, but the actual code is hidden from the viewer.
Q. Do I use capitals or lower case? I've seen people using both.
A. In HTML, the browser doesn't care. However, should you move on to XHTML, they will have to be lower case.
Q. Must everything have a tag to show up on the page?
A. No. If you just type in text, it'll show up. But it will not have any special look.
Q. What if I forget to add the end tag or forget to add the slash to the end tag command?
A. That's trouble, but easy-to-fix trouble. It will be obvious if you've not placed an end tag when you look at the document in your browser. The entire document will be affected after the point where you forgot the end tag. Just go back into the document, add the slash, and reload the document into the browser.
Q. Do all HTML tags require both a begin and end tag, like above?
A. No. There are exceptions to the rule, but let's stay on the ones that do require both tags to work for now. Moving along...
The majority of HTML tags do require both an open and a close tag (a begin and end tag). Most are very easy to understand because the tag is obvious. Here are a few and what they do to text:
| Affect | Code | Code Used | What It Does |
Strong | Strong | <strong>Bold</strong> | Bold |
Emphasis | em | <em>Italic</em> | Italic |
Paragraph | p | <p>Paragraph</p> | Plain |
Note: the strong and em tags are normally found inside a paragraph. There is a technical reason for this which we'll cover later.
Can I Use Two Tags at Once?
Yes. Just make sure to begin and end both. Like so:
<strong><em>Strong and emphasis</em></strong> gives you Bold and Italic
If you do use multiple tags to alter text, make a point of not getting the end tags out of order. Look at this:
<strong><em>Strong and emphasis</strong></em>
In terms of format, the example above is not correct. The end tags are out of order in relation to the start tags.
Follow this rule:
Always set the beginning and end tags at the same time, always placing them on the farthest end of the item being affected.
Here, again, is the example above in correct form:
<strong><em>Strong and emphasis</em></strong>
Notice the strong tags are on the far ends. Next in line are the emphasis tags. Just keep setting commands at the farthest ends each time you add them and you'll stay in good form.
The open and close tag format dominates the majority of the available HTML tags, but there are tags that stand alone. Here are two useful ones:
| tag | What It Does |
<HR> | This command gives you a line across the page. (HR stands for Horizontal Reference.) The line right above the words "Single tags" was made using an <HR> tag. |
<BR> | This BReaks the text and starts it again on the next line. Remember you saved your document as TEXT so where you hit ENTER to jump to the next line was not saved. In an HTML document, you need to denote where you want every carriage return with a <BR>. |
So, here we go... you're going to write your first HTML page using what you have learned above plus a few other items. And these other items are important to every page you will ever write. Why? Because they will be on every page you ever write.
For a properly formed document, you need a 'doctype'. For example:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
This tells the browser exactly what version of html you are using. Whilst this won't make any difference to you early on, when you get into CSS and positioning it will have a huge impact, so get into good habits now to avoid the problems later!
You will always have this tag: <HTML>
That makes sense. You are denoting that this is an HTML document.
Your next tags will always be these: <TITLE> and </TITLE>
See the very top of this page? I mean way up top. Above the FILE -- EDIT -- VIEW menus. The colored bar up there. Right now it reads "Basic HTML: tags" That's the title of the page and that's what you are denoting here. Whatever you put between these two tags will show up in the title bar way at the top.
Finally, you'll end every page you write with this tag: </HTML>
Get it? You started the page with HTML and you will end the page with /HTML. That makes sense again.
I want you to play around with these commands. Just remember that HTML reads like you do, top to bottom, left to right. It will respond where you place the start tag and stop where you place the end tag. Just make sure your tags are within the < and > items.
Here's a sample page to show you what I mean for you to do tonight:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>My first HTML document</title>
</head>
<body>
<p>Hello <strong>world!</strong><p>
<br>
<p>This is my very first HTML page.<p>
</body>
</html>
Click here to view the sample page.
Notice I only used the tags I showed you on this page. Yes, it's a simple page, but you're just starting out. Notice the <HTML> and </HTML>. Notice the <TITLE> and </TITLE>. See how there's a beginning and end tag when I alter the text and that the P and BR commands are used to go to new lines?
Look at the program above and then what it produced. Look at the source code when you open the page. See how the HTML tags denoted where text was affected? Good! I knew you would. Now go! Go into the world -- or at least to your text editor -- and create. Follow the instructions in HTML Primer #1 to help you save and then display your first HTML page.
You Can Do This!
New lectures...
Thursday, December 6, 2007
I start with the basic of web pages that is the .html files.
this basic is for beginner who want to learn the web page making.
I make the simple html code first.
The tag.
The tag is for the html to works even not in the server field.
the first tag is <> for opening and< / x > for closing.
This is important for us to make the html files.
the x you can put html for html coding to works.
