Friday
Misc ApplicationsHTML Basics
CSS was calculated to work with HTML. To take advantage of CSS, you need to know some HTML. As stated in the Preface, we assume most readers have had some exposure to HTML. But, to ensure we all talk about the same thing, we now review the basics of HTML.
Fundamentals
HTML is simple to write. It is essentially a series of fundamentals that define the structure of your document. An element naturally has three parts:
- Start tag
- Content
- End tag
Figure 1.2 illustrates the three parts of an element.
All tags in HTML start with a “<” and end with a “>.” Between these comes the name of the element. In Figure 1.2, the name of the element is SENTENCE. The content of the element is a string of font (but we will soon see that the content of an element can be another element). After that comes the end tag. End tags look like the start tag, apart from they have a “/” (slash) before the element name.
Building a Simple HTML Document
HTML has approximately 30 commonly used fundamentals. SENTENCE isn’t one of them, in fact, SENTENCE isn’t an HTML element at all. We used it as an example to show the basic structure of all fundamentals. Let’s look at a real HTML element:
<HTML></HTML>
In this book, all element names are printed using small-cap letters (for example, BODY). HTML fundamentals are case-insensitive. That is, any combination of uppercase and lowercase letters can be used. Hence, “TITLE,” “Title,” and “title” are all the same. XML, but, is case-sensitive.
One of the fundamentals in HTML is called HTML. The HTML start tag (<HTML>) marks the beginning of an HTML document, and the HTML end tag (</HTML>) marks the end. Everything between these two tags is the content of the HTML element. In the example, nothing is between the start and the end tag. In the next example, we add some content:
<HTML><TITLE>Bach’s home page</TITLE></HTML>
What we added from the last example is marked in bold letters (this is a convention we will use right through this chapter). Unlike the SENTENCE example, the content of the HTML element is not just a string of font – it’s really another element. The TITLE element contains the title of an HTML document. The title of the document we build in this chapter is “Bach’s home page.” Figure 1.3 maps out the two fundamentals we have so far.
Figure 1.3. Diagram of an element.
When a browser displays an HTML document in a window onscreen, the content of the title element generally goes into the title bar of the window. The title bar is at the top of the window. Not more than that is often the browser’s control panel. Further not more than that is the most fascinating part of the browser window: the canvas. The canvas is the part of the window everywhere documents are really showed. See Figure 1.4.
Figure 1.4. The parts of a browser’s window. The top line is the title bar, the large grey area is the canvas. CSS only deals with the content of the canvas.
As you can see, we have yet to place anything in the document that will be showed on the canvas. To have something really show up on the canvas, you must place it in the BODY element. The BODY element is inside the HTML element:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
</BODY>
</HTML>
To make it simpler to see everywhere fundamentals start and end, we show the HTML examples over several lines and indent fundamentals that are inside others. We do this because it makes the code simpler to read. The browser ignores the extra space and the line breaks that separate one line from another.
The content of the HTML element now consists of not one, but two other fundamentals. By themselves, the BODY tags do not add anything to the canvas; we need to give the BODY element some content. Let’s start by adding a first-level bearing to the sample document. The standard HTML tag for a first-level bearing is H1. Here’s the HTML code:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
</BODY>
</HTML>
The title of the document is the same as the first-level bearing. This will often be the case in HTML documents, but it doesn’t have to be.
HTML also has other headings you can use: H2, H3, H4, H5, and H6. The higher the number, the less vital the bearing is. If H1 corresponds to a chapter, H2 is a part, H3 a subsection, etc. Typically, also, the higher the number, the smaller the font size. Here’s the document with a couple of extra headings added:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<H2>Bach's compositions</H2>
<H3>The upright music</H3>
</BODY>
</HTML>
Figure 1.5 shows the bearing levels as they might grow onscreen.
But, we don’t need those two extra headings right now, so we rub out them and add a paragraph of text instead. We do this using the paragraph element, P:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a prolific
composer.
</BODY>
</HTML>
Figure 1.6 shows the new paragraph.
Note that we left out the ending paragraph tag, </P>. Naturally, an element starts with a start tag and ends with an end tag. But, for some HTML fundamentals, the end tag may be omitted. The end tag notifies the browser when the element ends, but in some cases, the browser can figure this out for itself, so the tag is not needed. For example, the P element cannot continue living outside of the BODY element. So, when the browser encounters the BODY end tag (</BODY>), it knows that the P element has also finished. Still, including the P end tag is impeccably legal. HTML specifies that leaving out the </P> has no effect on the way the document is showed.
You can also see that the browser ignored the spaces and line breaks in the source document. Here is only one space between each pair of words and the line breaks are gone.
Next, suppose we want to emphasize a word relative to the surrounding text. Several HTML fundamentals can express this; amongst them, we find STRONG and EM (EM stands for accent). These fundamentals do not say anything about how they are to be showed, but here are some conventions: STRONG fundamentals are naturally showed in bold, and EM fundamentals are showed in italic.
The following code shows the use of the STRONG element:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer.
</BODY>
</HTML>
Figure 1.7 shows how this code is showed.
Notice how the word “prolific” stands out relative to the surrounding text. Also note that although the H1 and P fundamentals start on a new line, the STRONG element continues on the same line everywhere the P element ongoing. H1 and P are examples of block-level fundamentals, while the STRONG element is an inline element. We discuss block-level and inline fundamentals in the next part.
Block-Level and Inline Fundamentals
In the previous part, the STRONG element was placed in the middle of an element, P, while the P and H1 fundamentals both started and finished a line. You can’t insert a P element in the middle of another P or H1 element or vice versa. But, you can insert an element like STRONG in the middle of most other fundamentals. This is because the P and H1 fundamentals are block-level fundamentals, while the STRONG element is an inline element.
- Fundamentals can be divided into three groups:
- Block-level
- Inline
- Hidden
A block-level element is an element that starts and ends a line or, place another way, that has a line break before and after its content. Examples of block-level fundamentals that you’ve seen so far in this chapter are H1 and P.
Element Overview
Confused about the different fundamentals? Don’t worry. Table 1.1 gives you an overview of the most common HTML fundamentals. We’ve introduced you to several of these already and will discuss others before long. We talk about others when appropriate right through the rest of this book and use them in many examples. Also, we recommend that you refer to the table as needed as you work your way through this book. The last column of the table (“Empty? Replaced?”) is clarified later in this chapter.
Amongst the fundamentals that are not included in Table 1.1 are the fundamentals that start forms and tables. Also, the non-standard fundamentals have been left out.
In the next several sections, we add to your repertoire of HTML tags by discussing fundamentals that you can use to start lists, add a horizontal rule, force a line break, and link to text and images.
Comments
Most of your documents will consist of fundamentals. But, you can also insert HTML comments into the document. A comment is anything you want to say about what is vacant on with your document that you don’t want to be showed. The user won’t see the comment on the canvas because browsers ignore comments; that is, they do not show a comment’s contents. Comments can be a helpful way of communicating something about your document to other designers who will see your code.
To ensure that the comment really is not viewable by the user, you enclose it between special strings that the browser will admit as enclosing a comment. You start the comment with the string <!-- and end it with the string -->. (That’s two hyphens in both cases.) Here’s a sample comment:
<!-- CSS is the greatest thing
to hit the Web in view of the fact that hyperlinks -->
Lists
Lists are common in HTML documents. HTML has three fundamentals that start lists:
OL, which makes an prearranged list. In an prearranged list, each list item has a mark that indicates the order, e.g., a digit (1, 2, 3, 4, or I, II, III, IV) or letter (a, b, c, d). In desktop-publishing terminology, prearranged lists are often called numbered lists.
UL, which makes an unordered list. In an unordered list, each list item has a mark that does not indicate order, e.g., a bullet symbol. In desktop-publishing terminology, unordered lists are often called bulleted lists.
DL, which makes a definition list. A definition list is a list of terms with their corresponding definitions. For example, a dictionary is a (long!) definition list.
Bach’s home page must surely include a list of some of his compositions. Let’s add an prearranged list:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Here are his best works:
<OL>
<LI>the Goldberg Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</OL>
</BODY>
</HTML>
Notice that an LI doesn’t need an end tag, but an OL does. Figure 1.8 shows the result.
Figure 1.8. An prearranged list.
This prearranged list is unfair to all the other fantastic compositions by Bach. (What about the Mass in B-minor?) Let’s change the prearranged list into an unordered list. To do this, we simply change the OL to UL:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>composer.
Amongst his works are:
<UL>
<LI>the Goldberg Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</UL>
</BODY>
</HTML>
Figure 1.9 shows the result.
Figure 1.9. An unordered list.
Notice that we do not have to change the LI fundamentals to change the list from unordered to prearranged: Both UL and OL use LI as the list item element. But, because the LI fundamentals are now inside the UL element, they will look different.
A DL, or definition list, is used for lists that have terms and their corresponding definitions. Each term is contained in a DT element, and each definition in a DD element. An example of a DL is a dictionary or glossary. In the next example, we change our OL to a DL. Notice how the LIs, change to DTs and that like the LIs, they do not require end tags. Figure 1.10 shows the result.
Figure 1.10. A definition list.
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG> composer.
Amongst his works are:
<DL>
<DT>the Goldberg Variations
<DD>composed in 1741, catalog number BWV988
<DT>the Brandenburg Concertos
<DD>composed in 1713, catalog numbers
BWV1046-1051
<DT>the Christmas Oratorio
<DD>composed in 1734, catalog number BWV248
</DL>
</BODY>
</HTML>
Empty Fundamentals HR and BR
All the HTML fundamentals that we have discussed so far have had content. HTML also has some fundamentals that do not have content; they are called empty fundamentals. One example is the HR element, which inserts a horizontal rule in the document. It doesn’t need any content. Also, the BR element’s sole purpose is to force a line break. Because empty fundamentals do not have any content, they don’t need any end tags.
We can add a horizontal rule to a document by using the HR (horizontal rule) element. HR is an empty element, so you must omit its end tag. Here’s the code for adding an HR element:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<UL>
<LI>the Goldberg Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</UL>
<HR>
</BODY>
</HTML>
Figure 1.11 shows the result.
Figure 1.11. Adding a horizontal rule.
We can force a line break in the middle of an element by using the BR (break) element. The browser naturally ignores line breaks in the HTML document and involuntarily breaks a line when needed when it displays the document. But, if you want to force a line break at a certain spot in the document, BR enables you to do this. Because BR is an empty element, you can omit its end tag.
Here is our example with a BR element added:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's <BR>home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<UL>
<LI>the Goldberg Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</UL>
</BODY>
</HTML>
Figure 1.12 shows the result.
Figure 1.12. Adding a line break.
It is usually better to let the browser determine the line breaks, because as an author, you cannot know how wide the user’s window is or how large the fonts are. So, to a fantastic degree take out the BR element as we go on.
Maintaining Preformatted Text
In the previous example, we mentioned that a browser generally ignores line breaks, apart from for those that you enter using the BR element. The browser also ignores tabs and extra white space. Tabspaces are converted to single white-space font, while extra white-space font – any more than one – are collapsed into one white-space character. Generally, this is what we want. This feature enables us to space out our code so that it is more readable and reflects the structure of the document, secure in the knowledge that the browser ignores all the extra white spaces.
Now and again, but, you may want to insert white space and have the browser show your text exactly as you formatted it. The PRE (preformatted) element allows you do this. Simply enclose within <PRE> tags the information whose formatting you want to preserve. The PRE element is often used for simple tables everywhere columns need to align vertically:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's <BR>home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<PRE>
COMPOSITION YEAR CATALOG#
Goldberg Variation 1741 BWV988
Brandenburg Concertos 1713 BWV1046-1051
Christmas Oratorio 1734 BWV248
</PRE>
</BODY>
</HTML>
Notice that the content of the PRE element cannot be aligned with the other fundamentals because the extra white space would grow on the canvas. Figure 1.13 shows the result.
Figure 1.13. Preserving preformatted text.
This is really not a very excellent example because by using PRE, we hide the fact that the content is a table. This is a case everywhere using a table is in fact the right thing to do because it enhances accessibility (see the part “Placing text in a table” earlier in this chapter).
Adding Hyperlinks
We can make our document more fascinating by adding hyperlinks to it. When hyperlinks are in place, users can click on them to access related documents from somewhere else on the Web. Hyperlinks are integral to HTML and the Web. Without hyperlinks, here would be no Web.
To make a hyperlink, you use the A (anchor) element. When the user clicks on the A element, the browser fetches the document at the other end of the hyperlink. The browser needs to be told everywhere it can find the other document, and this information goes into an attribute on the A element. An attribute is a characteristic quality of the element, other than the type or content of an element. The A element uses an attribute called HREF (hypertext reference) to add a hyperlink:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<UL>
<LI>the <A HREF="goldberg.html">Goldberg</A>
Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</UL>
<HR>
</BODY>
</HTML>
Let’s take a closer look at the newly added A element. Figure 1.14 shows the different parts of the A element.
Figure 1.14. The parts of an A element.
The A start tag is a bit more complicated than the other start tags we have seen so far; in addendum to the element name, it includes an attribute. Different element types have different attributes; amongst the most common ones is the HREF attribute on the A element. Attributes can only go into the start tag of the element, after the element name. Most attributes need a value: The HREF attributes always takes a URL as a value. A URL (Universal Resource Locator) is a Web address that the browser uses to locate the hyperlinked document. When URLs are used as principles on the HREF attribute, they must always be quoted (“…”).
URLs come in two flavors:
- A relative URL gives the location of the document relative to the document everywhere it is referenced (that is, the document everywhere the A element is). You can only use relative URLs when you link to a document on the same Web server as the document you are linking from.
- An resolution URL gives the location of the document independent of any other document. You must use resolution URLs when you link to a document on a different server. Resolution URLs can be typed into any machine on the Internet and the browser will find it. That’s why you see resolution URLs on T-shirts, in TV commercials, etc.
In the previous example, the HREF attribute had a relative URL (goldberg.html) as value. If the user clicks on the word “Goldberg,” the browser fetches the document called goldberg.html from the same location as everywhere our sample document is found.
We can also place an resolution URL into our document:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG> composer.
Amongst his works are:
<UL>
<LI>the <A HREF="goldberg.html">Goldberg</A>
Variations
<LI>the Brandenburg Concertos
<LI>the <A HREF="http://example.org/christmas.html">
Christmas</A> Oratorio
</UL>
<HR>
</BODY>
</HTML>
As you can see, resolution URLs are slightly more complicated than relative ones. In fact, when Tim Berners-Lee invented the URL machinate, they were only predestined to be seen by machines. Figure 1.15 shows the various parts of this URL.
Figure 1.15. Structure of a URL.
The details of URLs are not the main topic for this book and as long as you are aware of the two types of URL, you may safely proceed.
Adding Images
Images proliferate on the Web. It wasn’t until the Mosaic browser added support for images in 1993 that a critical mass of people realized the potential of the Web. You can add images to your documents with the IMG element – IMG is small for image.
IMG is a peculiar element. First, it’s empty. That’s not so weird, we’ve seen those before. (Quick reminder: an empty element is an element without content, e.g., HR, BR.) Second, it’s a replaced element. A replaced element is a placeholder for some other content that is life pointed to from the element. In the case of IMG, it points to an image that is fetched by the browser when the IMG element is encountered. Unlike the A element, which gives the user the option of jumping to a link or not, the browser involuntarily fetches the image IMG points to. Also, unlike the A element, IMG uses an attribute called SRC to point to the image.
Let’s add an image to the sample document. Not many portraits of Bach are known, but those that continue living are on the Web:
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1><IMG SRC="jsbach.png" ALT="Portrait of
J.S. Bach">Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<UL>
<LI>the <A HREF="goldberg.html">Goldberg</A>
Variations
<LI>the Brandenburg Concertos
<LI>the <A HREF="http://example.org/christmas.html">
Christmas</A> Oratorio
</UL>
<HR>
</BODY>
</HTML>
Let’s take a closer look at the attributes on the IMG element (see Figure 1.16).
Figure 1.16. IMG element.
The SRC attribute on IMG is similar to the HREF attribute on A: They both take a URL as a value. The ALT attribute is new. The purpose of ALT is to grant an alternative (from which it gets its name) textual description of the image. Now and again, a browser cannot fetch the image (perhaps the Web server is broken?) or it may be configured to ignore images, for example, in the case of a text-only browser. In these cases, the browser will look for the alternative textual description and show that instead of the image. The ALT text is also essential for people who cannot see. Therefore, you must always try to include a textual alternative for the image so users can still get a sense of what is vacant on.
Figure 1.17 shows how Microsoft Internet Explorer shows the page while the image is life fetched.
Figure 1.17. Waiting for an element to be fetched.
When the image is ready, the page looks like Figure 1.18.
Figure 1.18. The image has been loaded.
Document Trees
In this chapter, we have demonstrated how fundamentals in HTML are placed inside one another. We did this by indenting the code, as shown in all the previous code examples. The HTML element itself is the outermost element that encompasses all the other fundamentals. Inside the HTML element are the TITLE and BODY fundamentals, with the latter encompassing all the other fundamentals, such as HI and P. Within some of those fundamentals are other fundamentals. For example, within the UL element are the LI fundamentals. If you were to diagram this thought of fundamentals within fundamentals, the result might be as shown in Figure 1.19.
Figure 1.19. Diagram of fundamentals within fundamentals in a tree structure.
<HTML>
<TITLE>Bach's home page</TITLE>
<BODY>
<H1>Bach's home page</H1>
<P>Johann Sebastian Bach was a
<STRONG>prolific</STRONG>
composer. Amongst his works are:
<UL>
<LI>the Goldberg Variations
<LI>the Brandenburg Concertos
<LI>the Christmas Oratorio
</UL>
</BODY>
</HTML>
Notice how Figure 1.19 resembles a people genealogical chart, with parents and children spread out in a top-to-bottom fashion, everywhere parents can also be children. This is called a tree structure. In the tree structure of an HTML document, the HTML element is the earliest ancestor – the top parent. All other fundamentals are children, grandchildren, and fantastic-grandchildren – in small, descendants – of the HTML element. An element can have from zero to many children, but it always has only one parent, with the exception of the HTML element, which is an orphan. In Figure 1.19, note that TITLE and BODY are children of HTML. TITLE has no children, but BODY has three: HI, P, and UL. In turn, UL has three children: the LIs. Also note that in this example, BODY is both a child and a parent, as is UL.
We encounter tree structures in many situations outside HTML and genealogy. Trees – real trees such as spruce and pine – are (not surprisingly) tree structures. Organizational charts for companies are often set out in a tree structure. Books and technological documents, too, are usually set out in a tree structure, everywhere sections and subsections are branches of the whole. (The fact that books are made from trees doesn’t seem to have anything to do with it…) The last example is probably the reason why HTML documents always have a tree structure.
Nested Fundamentals
In HTML, here are some restrictions on which fundamentals can be children of which fundamentals. Usually, an element cannot contain children of its own type. That is, a P, for example, cannot be a child element of another P. You would not typically want to place a paragraph inside another paragraph, anyway. Also, an HI cannot be a child element of another HI.
Some fundamentals, but, may contain children of their own type. One example is BLOCKQUOTE, the element that is used to place quoted material within a document. This element can have nested within it quoted material that is the content of another BLOCKQUOTE element, that is, you can place a quote within a quote. This ability of an element to have children of its own type is called nesting.
The following is an example using no less than three nested BLOCKQUOTE fundamentals (shown in bold, italic, and bold italic, respectively):
<HTML>
<TITLE>Fredrick the Fantastic meets Bach</TITLE>
<BODY>
<H1>Fredrick the Fantastic meets Bach</H1>
<P>In his book "Gödel, Escher, Bach," Douglas
Hofstadter writes:
<BLOCKQUOTE>
Johann Nikolaus Forkel, one of
Bach's earliest biographers, tells the tale
as follows:
<BLOCKQUOTE>
One sundown, just as he was getting
his flute ready, and his musicians
were assembled, an officer brought
him a list of the strangers who had
arrived. With his flute in his hand
he ran over the list, but
immediately turned to the assembled
musicians, and said, with a kind of
agitation:
<BLOCKQUOTE>
Gentlemen,
ancient Bach is come.
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BODY>
</HTML>
This can be showed as shown in Figure 1.20.
Figure 1.20. Nested BLOCKQUOTE fundamentals
Notice how with the nested fundamentals, the second element is indented even more than the first is. This is a visual suggestion that it is a child of the first BLOCKQUOTE.
BLOCKQUOTEBLOCKQUOTE fundamentals, not because here are so many levels of quotes, but because designers reckon indentation looks excellent. Here’s an example of that (see Figure 1.21):
<HTML>
<BODY>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BLOCKQUOTE>
<BLOCKQUOTE>
Indentation is fantastic!
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
</BODY>
</HTML>
Figure 1.21. Using BLOCKQUOTE for indentation.
Unfortunately, when robots or others search for quotes, they find not only quotes, but also everything else tagged as quotes.
With the arrival of CSS, this misuse of BLOCKQUOTE must no longer be necessary. CSS provides simple-to-use methods for indenting text and images, as we will show you in subsequent chapters.
Well, here you have it. The fundamentals we described in this chapter, plus a few others we discuss later, form the basics of HTML. With these, you can write and publish many literary gems. Of course, they may not look all that fantastic. But, we fix that with CSS.
Post Tags: Cascading Style Sheets, CERN, CSS, CSS for Beginner, CSS2, Development of CSS, HTML Articles, HTML Basic, HTML for Beginner, HTML Short Course, HTML Tag, Learning CSS, Learning HTML, Robert Cailliau, Tim Berners-Lee, Web Design, Web Designer
Related Posts
- Network Booting via PXE: the Basics
- Mastering PC Fundamentals From You Tube
- More About Multithreading in Java
- Computer Training Course
- WWW – What Does It Mean? Another Computer Fundamental Training Lesson – For Computer Newbie
- Free Fundamental PC Learning Skills Online – What Can They Offer Me?
- Five Basic Reasons To Enroll In A PC Training Course
- Fundamental PC Knowledge That You Should Acquire
- More Schematron Features
- Using the Active Record Pattern with PHP and MySQL
Popular
- iPhone or iPod Touch, Which One Should You Choose? - 47,761 views
- Introduction to Facebook - 26,655 views
- 7 Top Twitter Topic Trackers - 16,375 views
- Introduction of Hacking Methodology - 15,051 views
- Google Hacking Keywords - 11,716 views
- LG BD390 Wi-Fi Blu-ray Player Review: So Packed You’ll Forget About Blu [Review] - 10,094 views
- Complete Guide to Web Site Marketing - 9,774 views
- BlackBerry Curve 3G: A Familiar, Powerful Phone - 9,774 views
- Microsoft’s Zune HD Wiill Have OLED, HD Radio - 9,300 views
- Photo Album and Printing Services - 8,953 views
Featured Articles
- The Elements of the Facebook Platform
- Introducing the Facebook Platform
- Social Skills Today Are Being Lost
- GibBook – Gibraltar Own Social Network Site
- 7 Deadly Twitter Sins
- Introduction to Facebook
- Google’s Wave: Many Online Apps in One Tool
- App Mapping War Casualties Debuts for Memorial Day Weekend
- Google@Omgili Mashes Traditional Web Search With Social Buzz
- Capital Factory: Austin-Based Incubator (RWS Interview)
Recent Posts
- Tweet via something
- Lightroom Review And Other Phot
- Several Words About The Advantages Of Tablet PCs
- Dissimilar Positive Features Of Table Computers
- Digi Link Doctor
- Why You Need Professional SEO Software
- Automated SEO Tools For Online Business
- How To Choose The Best Tablet PC
- Tablet PC – The Latest Computer Technology
- Tablet PCs Compared To Laptops
