Intro to Website Technologies - Revision history

Bsandberg: Bsandberg moved page Websites 101 to Intro to Website Technologies: Clarification, consistency

2013-11-02T04:08:12Z

Bsandberg moved page Websites 101 to Intro to Website Technologies: Clarification, consistency

Bsandberg: braindump

2013-11-02T03:50:00Z

braindump

Bsandberg: fixed order list wiki-markup

2013-09-12T22:21:41Z

fixed order list wiki-markup

Bsandberg: fixed numerical bullets

2013-09-12T22:15:29Z

fixed numerical bullets

Bsandberg: Added a link for WHOIS

2013-08-09T07:35:10Z

Added a link for WHOIS

Bsandberg: URL syntax

2013-08-09T07:21:09Z

URL syntax

Bsandberg: See Also

2013-08-09T06:49:46Z

Bsandberg: Get yer links right

2013-08-09T06:44:06Z

Get yer links right

Bsandberg: More updates, not even sure what....

2013-08-09T06:40:01Z

More updates, not even sure what....

Bsandberg: Filling in the blanks...

2013-08-09T06:37:03Z

Filling in the blanks...

@@ Line 2: / Line 2: @@
 = Domain Names =
-Domain names are perhaps the most familiar aspect of websites. Whether it is [http://www.freegeek.org/ FreeGeek.org] or [http://www.linux.com Linux.com], these are memorable names which we can use to identify the websites found at those locations.
+Domain names are perhaps the most familiar aspect of websites. Whether it is [http://www.freegeek.org/ FreeGeek.org] or [http://www.linux.com Linux.com], these are memorable names which we can use to locate and contact an individual server on the internet.
 == Registration ==
-One 'registers' a domain name, by choosing a registrar, finding an available domain name, and paying an annual fee for that domain name.
+One 'registers' a domain name, by choosing an ICANN registrar, finding an available domain name, and paying an annual fee for that domain name.
 Some notable registrars are:
@@ Line 13: / Line 13: @@
 == WHOIS ==
-Every domain name must have certain contact information available.  This is called the WHOIS registry (or database). It is public information, and many registrars sell 'privacy listing' services to hide your contact info and thus prevent spam.
+Every domain name's owner must provide certain contact information for what is called the WHOIS registry (or database). It is public information, and many registrars sell 'privacy listing' services to hide your contact info and thus prevent spam.
 [http://www.whois.net/ Whois.net, a free WHOIS service]
@@ Line 40: / Line 40: @@
 #: Last, comes the fragment identifier, or more commonly, an anchor. This allows us to point the user to a specific point in a document. One example might be, a long webpage with the contents of a book; there is a table of contents near the start, and clicking on 'Chapter 3' will cause the webpage to scroll down to chapter 3. It is added on to the end of a URL, like this; #chapter3
-= Servers & Hosting =
+= Products & Services  =
-= Software & Websites =
+= Server Software =
-= Services & Products =
+= Hosting =
-= Social Media =
+= Tools =
+== Browser Inspector ==
-= Browser Inspector =
+== Text Editor ==
 = See Also =

@@ Line 25: / Line 25: @@
 URLs are not read in a left-to-right fashion, as many might expect -- instead, the domain name is processed first, to determine which server we wish to connect to.  Next comes the protocol used to communicate, and the path to a resource we're requesting.  Finally, there can also be optional query strings, or anchors.
-. TLD
+# TLD
-The TLD is the first part of a domain name to be used. Each country controls the domains within their TLD, so those systems must be contacted to resolve the next step.
+#: The TLD is the first part of a domain name to be used. Each country controls the domains within their TLD, so those systems must be contacted to resolve the next step.
+# Domain
-. Domain
+#: The domain name is perhaps the most recognizable part of a URL. Using DNS, the domain name is resolved to an IP address.
-The domain name is perhaps the most recognizable part of a URL. Using DNS, the domain name is resolved to an IP address.
+# Subdomain
+#: Next, the subdomain is resolved to yet another IP address.
-. Subdomain
+# Protocol
-Next, the subdomain is resolved to yet another IP address.
+#: Now, with the IP address of the desired server, we must contact that server.  The protocol (http://) is how that communication should be conducted. This could be analogous to spoken language.
+# Path
-. Protocol
+#: Once a communication protocol has been established, we can make our actual request for a resource on that server. Often, this is an HTML document or at image, but it could be just about anything.
-Now, with the IP address of the desired server, we must contact that server.  The protocol (http://) is how that communication should be conducted. This could be analogous to spoken language.
+# Query String
+#: The query string is how we can pass information to the server, to help it respond to our request. Perhaps a webpage will display a certificate; it will need a name to display. By adding a question mark to the end of a URL, and separating each piece of data with an ampersand, we can provide this information, like so; ?first_name=John&last_name=Doe
-. Path
+# Fragment Identifier
-Once a communication protocol has been established, we can make our actual request for a resource on that server. Often, this is an HTML document or at image, but it could be just about anything.
+#: Last, comes the fragment identifier, or more commonly, an anchor. This allows us to point the user to a specific point in a document. One example might be, a long webpage with the contents of a book; there is a table of contents near the start, and clicking on 'Chapter 3' will cause the webpage to scroll down to chapter 3. It is added on to the end of a URL, like this; #chapter3
 = Servers & Hosting =

@@ Line 25: / Line 25: @@
 URLs are not read in a left-to-right fashion, as many might expect -- instead, the domain name is processed first, to determine which server we wish to connect to.  Next comes the protocol used to communicate, and the path to a resource we're requesting.  Finally, there can also be optional query strings, or anchors.
-# TLD
+. TLD
 The TLD is the first part of a domain name to be used. Each country controls the domains within their TLD, so those systems must be contacted to resolve the next step.
-# Domain
+. Domain
 The domain name is perhaps the most recognizable part of a URL. Using DNS, the domain name is resolved to an IP address.
-# Subdomain
+. Subdomain
 Next, the subdomain is resolved to yet another IP address.
-# Protocol
+. Protocol
 Now, with the IP address of the desired server, we must contact that server.  The protocol (http://) is how that communication should be conducted. This could be analogous to spoken language.
-# Path
+. Path
 Once a communication protocol has been established, we can make our actual request for a resource on that server. Often, this is an HTML document or at image, but it could be just about anything.
-# Query String
+. Query String
 The query string is how we can pass information to the server, to help it respond to our request. Perhaps a webpage will display a certificate; it will need a name to display. By adding a question mark to the end of a URL, and separating each piece of data with an ampersand, we can provide this information, like so; ?first_name=John&last_name=Doe
-# Fragment Identifier
+. Fragment Identifier
 Last, comes the fragment identifier, or more commonly, an anchor. This allows us to point the user to a specific point in a document. One example might be, a long webpage with the contents of a book; there is a table of contents near the start, and clicking on 'Chapter 3' will cause the webpage to scroll down to chapter 3. It is added on to the end of a URL, like this; #chapter3

@@ Line 14: / Line 14: @@
 == WHOIS ==
 Every domain name must have certain contact information available.  This is called the WHOIS registry (or database). It is public information, and many registrars sell 'privacy listing' services to hide your contact info and thus prevent spam.
 == Top-Level Domains ==

@@ Line 16: / Line 16: @@
 == Top-Level Domains ==
-Top-Level Domains, or TLDs, are the technical term for the ".com" part of a domain name. While the traditional TLDs are still available, each country has been assigned a two-letter country code, such as ".us" or ".uk" -- each country controls domains in their TLD, and set prices as they see fit.
+Top-Level Domains, or TLDs, are the technical term for the ".com" part of a domain name. While the generic TLDs are still available, each country has been assigned a two-letter country code, such as ".us" or ".uk" -- each country controls domains in their TLD, and set prices as they see fit.
 = URL Structure =
 # TLD
 # Domain
 # Subdomain
 # Protocol
 # Path
 # Query String
 # Fragment Identifier
 = Servers & Hosting =

← Older revision	Revision as of 04:08, 2 November 2013
(No difference)

@@ Line 36: / Line 36: @@
 = Browser Inspector =
 [[Category: Current Classes]]
 [[Category: Classes]]

@@ Line 2: / Line 2: @@
 = Domain Names =
-Domain names are perhaps the most familiar aspect of websites. Whether it is [[FreeGeek.org]] or [[Linux.com]], these are memorable names which we can use to identify the websites found at those locations.
+Domain names are perhaps the most familiar aspect of websites. Whether it is [http://www.freegeek.org/ FreeGeek.org] or [http://www.linux.com Linux.com], these are memorable names which we can use to identify the websites found at those locations.
 == Registration ==
@@ Line 8: / Line 8: @@
 Some notable registrars are:
-* Enom
+* [http://www.enom.com/ Enom]
-* Network Solutions
+* [http://www.networksolutions.com/ Network Solutions]
-* GoDaddy
+* [http://www.godaddy.com/ GoDaddy]
 == WHOIS ==

@@ Line 1: / Line 1: @@
-* URL structure
+The purpose of this class is to provide a broad overview of the technical components required to have a website.
 = Domain Names =
-Domain names are perhaps the most familiar aspect of websites. Whether it is FreeGeek.org or Linux.com, these are memorable names which we can use to identify the websites found at those locations.
+Domain names are perhaps the most familiar aspect of websites. Whether it is [[FreeGeek.org]] or [[Linux.com]], these are memorable names which we can use to identify the websites found at those locations.
 == Registration ==