HTML5与CSS3入门指南：打造高效网站

需积分: 9 130 浏览量更新于2024-07-16 收藏 11.31MB PDF 举报

"Foundation HTML5 with CSS3: A Comprehensive Guide for Beginners and Experts" 本书名为《Foundation HTML5 with CSS3》，是一本针对HTML5和CSS3的英文专业教程，配以详细目录，旨在帮助读者从零开始构建网页，同时也适合有一定基础的网络开发者深入学习。作者和技术审稿人共同呈现了丰富的内容，让读者在快速上手的同时，理解和掌握这些核心技术和概念。第1章"Getting Started"引导读者步入Web开发的世界，首先会介绍互联网和万维网的基本原理，帮助读者理解其背景与重要性。即使对于已经熟悉网络环境的人来说，这一章也提供了必要的术语和概念概述，确保后续章节的学习更加顺畅。接下来的章节涵盖HTML5的基础知识，如第2章"HTML and CSS Basics"，深入讲解这两种语言的基础语法和结构，使读者能够构建网页的基本元素和样式。第3章"Document Structure"探讨文档的组织方式，强调良好的文档结构对网站性能和用户体验的重要性。第4章至第8章分别关注内容构造、媒体嵌入、链接网络、创建表格以及表单和应用程序的组装。每章都逐步提升技能层次，帮助读者构建功能丰富的网页，并与用户进行互动。第9章"Page Layout with CSS"专门研究如何使用CSS来控制页面布局，实现响应式设计，适应不同设备的屏幕尺寸。而第10章"Putting it All Together"则是将前面学到的知识整合应用，通过实例展示如何完成一个完整的项目。最后，附录的索引提供了全书内容的快速检索，方便读者查找所需的主题和知识点。无论你是初次接触HTML5和CSS3的新手，还是希望巩固并扩展现有技能的开发者，《Foundation HTML5 with CSS3》都是一份不可或缺的参考资料。书中深入浅出的讲解和实用案例，将帮助你建立起坚实的Web开发基础。

Getting Started

Figure 1-2. The W3C Markup Validation Service

The W3C validator can automatically analyze your markup and display any errors it encounters so you can

correct them. It will also display validation warnings, which are simply cautions about issues you might

want to address but are not quite as severe as errors; warnings can be ignored if you have good reason to

do so, but errors are flaws that really must be fixed. When no errors are found, you’ll see a joyful banner

declaring that your document is valid. A document that is valid and correctly assembled according to the

rules of the language is said to be well-formed. Other validation tools are also available—both online and

offline—that can help you check your documents.

CSS also needs to be authored in accordance with the specifications, and the W3C offers a similar CSS

validation service (http://jigsaw.w3.org/css-validator/) to check your CSS files for problems.

Most web browsers are still able to interpret and render invalid documents, but only because they’ve been

designed to compensate for minor errors. Valid, well-formed documents are much more stable, and you

won’t have to depend on a browser’s built-in error handling to display them correctly.

Chapter 1

Hosting Your Web Site

You can save all of your work locally on your own computer, but when it’s time to make it available to the

World Wide Web, you need to move those files to a web server. You have a few hosting options if you’re

building your own website:

 Using web space provided by your ISP: An Internet service provider (ISP) is the company that

connects you to the Internet. Many service providers offer a limited amount of web space where

you can host your own site. Ask your ISP whether web space is included with your service

contract and how you can use it.

 Using free web space: Many companies provide free web hosting, though “free” is a relative term

because free web hosts are usually supplemented by advertising. If you’re not bothered by such

ads appearing on your website, free hosting may be a quick solution to getting your files online.

 Paying for web hosting: Perhaps the best option is to purchase service from a company that

specializes in hosting websites. Many offer hosting packages for as little as $10 (US) per month

and include more robust features than free hosting or ISP hosting provides (such as e-mail

service, server-side scripting, and databases). Research your options, and choose a host that

can meet your needs.

If you opt for paid web hosting, you’ll also need to purchase and register a unique domain name to be your

site’s address on the Web. Some hosting companies offer domain registration as an included service (and

some domain registrars also offer hosting services), but securing a domain and securing a host are usually

two separate processes.

We won’t go into all the particulars of registering a domain and getting your site online with a web host.

After all, this is still the first chapter, and numerous resources online can provide more information. To

learn more about hosting your websites when the time comes, just visit your favorite search engine and

have a look around for information about “web hosting basics” or some similar phrase. One good place to

start is the Wikipedia entry about web hosting service (http://en.wikipedia.org/wiki/Web_hosting),

which offers a fairly detailed introduction to set you on your way.

Introducing the URL

Every file or document available on the Web resides at a unique address called a Uniform Resource

Locator (URL). The term Uniform Resource Identifier (URI) is sometimes used interchangeably with URL,

though URI is a more general term; a URL is a type of URI. We’ll be using the term URL in this book to

discuss addressed file locations. It’s this address that allows a web-connected device to locate a specific

file on a specific server in order to download and display it to the user (or employ it for some other

purpose; not all files on the Web are meant to be displayed).

Getting Started

The Components of a URL

A web URL follows a standard form that can be broken down into a few key parts, diagrammed in Figure

1-3. Each segment of the URL communicates specific information to both the client and the server.

http://www.example.com/examples/example.html

Protocol Hostname Path

Name Extension

File

Prefix Domain

Figure 1-3. The components of a URL

The protocol indicates one of a few different sets of rules that dictate the movement of data over the

Internet. The Web uses HyperText Transfer Protocol (HTTP), the standard protocol used for transmitting

hypertext-encoded data from one computer to another. The protocol is separated from the rest of the URL

by a colon and two forward slashes (://).

A hostname is the name of the site from which the browser will retrieve the file. The web server’s true

address is a unique numeric Internet Protocol (IP) address, and every computer connected to the Internet

has one. IP addresses look something like “66.211.109.45,” which isn’t very easy on the eyes and is

certainly a challenge to remember. A domain name is a more memorable alias that directs Internet traffic

to an IP address. Many web hostnames feature a domain prefix, further naming the particular server being

accessed (especially when there are multiple servers within a single domain), though that prefix is

frequently optional. A prefix can be almost any short text label, but “www” is traditional. It’s possible for

another entire website to exist separately within a domain under a different prefix, known as a subdomain.

A hostname will also feature a domain suffix (sometimes called an extension) to indicate the domain’s

category, such as “.com” for a U.S. commercial domain, “.edu” for a U.S. educational institution, or “.co.uk”

for a commercial website in the United Kingdom. Every country also has its own domain extension, and

you’ll often see URLs that indicate a country of origin but not any particular category.

The path specifies the directory on the web server that holds the requested document, just as you save

files in different virtual folders on your own computer. Files on a web server may be stored in

subdirectories—folders within folders—and each directory in the path is separated by a forward slash (/).

This path is the route a client will follow to reach the ultimate destination file. The top-level directory of a

website (the one that contains all other files and directories) is called the site root directory and doesn’t

appear in the URL.

The specific file to retrieve is identified by its file name and extension. You can give your files just about

any name you want, and a file extension indicates what type of file it is. An HTML (or XHTML) document

will have an extension of .html or .htm (the shorter version is used on some servers that support only

three-letter file extensions). CSS files use the .css extension, JavaScript files use .js, and so forth. Web

Chapter 1

servers are configured to recognize these extensions and handle the files appropriately, processing

different types of files in different ways.

You won’t see a file name and extension in every URL you encounter. Most web servers are configured to

automatically locate a specially named file when a directory is requested without a specified file name.

This could be the file called index.html, default.html, or some other name, depending on the way the

server has been set up. Indeed, most of the various parts of the URL may be optional depending on the

particular server configuration.

The URL is the instrument that allows you to build links to other parts of the Web, including other parts of

your own site. You’ll use URLs extensively in the HTML and CSS you author, which is why we’ve spent so

much time exploring them in this first chapter.

Absolute and Relative URLs

A URL can take either of two forms when it points to a resource elsewhere within the same site. An

absolute URL is one that includes the full string, including the protocol and hostname, leaving no question

as to where that resource is found on the Web. You’ll use an absolute URL when you link to a site or file

outside your own site’s domain, though internal URLs can also be absolute.

A relative URL is one that points to a resource within the same site by referencing only the path and/or file,

omitting the protocol and hostname because those can be safely assumed. It might look something like

this:

examples/chapter1/example.html

If the destination file is kept within the same directory as the file where the URL occurs, the path can be

assumed as well so only the file name and extension are required, like so:

example.html

If the destination is in a directory above the source file, you can indicate that relative path with two dots

and a slash (../), instructing the browser to go up one level to find the resource. Each occurrence of ../

indicates one up-level directive, so a URL pointing two directories upwards might look like this:

../../example.html

Almost all web servers are configured to interpret a leading slash in a relative URL as the site root

directory, so URLs can be “site root relative,” showing the full path from the site root down:

/examples/chapter1/example.html

Lastly, if the destination is a directory rather than a specific file, only the path is needed:

/examples/chapter1/

剩余423页未读，继续阅读

lizikunzk

粉丝: 0
资源: 8

HTML5与CSS3入门指南：打造高效网站

Foundation Website Creation with HTML5, CSS3, and JavaScript 无水印原版pdf

HTML5.and.CSS3.Building.Responsive.Websites.pdf

FoundationWebsiteCreationWithHTML5CSS3AndJavascript.pdf 英文原版

ebook-flutter-revolution.pdf

FoundationHTML5WithCSS3.pdf 英文原版

[JavaScript] 网站设计基础教程 (HTML5, CSS3, JavaScript 实现) (英文版)

JQuery In Action.PDF

Manning jQuery in Action.pdf

Flask By Example.pdf 最新 原版

Web Applications Development with Microsoft(Exame70-547)

最新资源

Flask By Example.pdf 最新原版