DOCSLIB.ORG

VISA/APCO/STAC 2P61 WEBSITE CREATION Fall Term 2012 ______

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VISA/APCO/STAC 2P61 WEBSITE CREATION Fall Term 2012 ______ VISA/APCO/STAC 2P61 WEBSITE CREATION Fall Term 2012 __________________________________________________________________________________ GETTING STARTED WITH XHTML AND CSS Do you have the book recommended for this course? HTML and CSS Web Standards Solutions A Web Standardistasʼ Approach Christopher Murphy and Nicklas Persson If you donʼt have the recommended book please find another. You will need something to refer to. If not the book…here are some websites where you can find good tutorials for writing standards based XHTML and CSS http://www.w3.org/MarkUp/Guide/ http://www.w3.org/MarkUp/2004/xhtml-faq http://www.htmldog.com http://xhtml.com/en/xhtml/reference/ http://www.webheadstart.org/xhtml/basics/index.html http://daringfireball.net/projects/markdown/ http://www.alistapart.com/ HTML Hypertext markup language Create with range of tools – plain text editor (with formatting turned off) Will be read by variety of devices Designed to be read by web browsers Non proprietary Open source Free Structures text to hyperlinks W3C 1995 first specs written. Current is 4.0 written in 1999 (HTML 5 in the works) XHTML XML (no defined tags like HTML – has defined structure) Extensive Markup Language Is HTML reformatted in XML HTML with strict rules of XML Varieties of XHTML – 1.0 Strict, (we use this one) 1.0 Transitional, 1.0 Frameset 1 The value of Standards • Avoid (as much as possible) sites that wonʼt display as written • More accessible sites • XHTML and CSS written to strict standards • Enables site to perform predictably on any standards compliant browser or OS • Improves Development time • Ease of updating • Search engine ranking XHTML/CSS Separates Content from Visual presentation/design Avoids Tag Soup of HTML where tags were used to control both how content is structured and how it looks. (HTML never intended to be used for design – it was designed for semantic (meaning imparting) markup of info – not visual effects. XHTML for content, structure and meaning CSS for visual presentation and design XHTML AND CSS REPRESENT A SYSTEMATIC APPROACH TO WEB DEV IN CONTEXT OF EVER CHANGING TECHNOLOGY. It is important to master each step and move on PLEASE SUPPRESS URGE TO RUSH AHEAD AND TO DESIGN Like other disciplines (music or martial arts) – master fundamentals before fancy moves. Well structured markup in XHTML of equal importance to CSS and design It will be daunting at first but once you know it will empower you . Tools No WYSIWYG drag and drop environment, No buttons to click No software writing markup behind scenes 1. Browser view source (in view menu) 2. Plain text editor Text Wrangler on our computers For others see www.webstandardistas.com/tools BASIC HTML TAGS HTML describes the different elements that the webpage consists of You write tags as you write content in TextWrangler and use Browser to open that file and see. 2 CRAWL BEFORE YOU WALK FUNDAMENTAL TAGS AND CONCEPTS TO KNOW: • 2 most basic HTML elements <head> <body> • nesting of tags • Title <title> • Headings <h1> <h2> etc. • Paragraphs <p> and • Lists <ul> and <ol> • Tables <tr> • How semantic tags that add info • Images <img> tag Principle 1. Tags Tags describe all elements and give structure to the page Tags are distinguished from content by the angle brackets <p> This is the content of the page </p> The material inside the brackets (e.g. <p> doesnʼt display It give browser info on how the document is interpreted All tags are in lower case <h1> not <H1> All tags have opening and closing <p> …………..</p> (note: early days, browsers would guess at invalid markup - do its best or second guess. Standards today require well formed markup to get the page you intend. Principle 2. HTML element = Start tag < > content End tag </> Principle 3. HTML naming 1. filename.html – html is a suffix for file extension It tells browser the document is a web page (some use .htm from the old days when PCʼs used only 3 letter extensions) 2. No spaces in file names 3. Use an underscore _ in place of a space (alt is a hyphen -) 4. Use lower case and not capitals wherever possible. Principle 4. The basic structure of any HTML page <html> - tells browser this is a HTML document <head> - tells browser this is information “about” the page – e.g. the title <title> - tells browser the title to display at the top of the browser page <body> - tells browser this is the start of information to be displayed on page itself <p> - surrounds paragraphs (in this case just one phrase Hello World </p> closes paragraph tag </body> closes body tag </html> closes html tag 3 Learn from seeing other peopleʼs source code. Open www.webstandardistas.com/02/king_kong_junior.html Go to View -> View Source Might now look unintelligible but soon it will be super instructive. ALL HTML PAGES HAVE THE FOLLOWING: <head>………………….</head> - info about doc. Not part of actual content includes page title that will appear at top of window and metatags that provide info about page for search engines. It also give info about style sheets. <body>…………………</body> - everything youʼll see in window text, links, images, etc. <title> element <head> element will contain title element so browser window will have a name (other than the name.html). If no title browser will display name.html <title> improves usability and search rankings think of our shoes site styles.html vs Types and Styles I Shoes in Culture Document Type Comes before <head> Defines the set of rules browser much use for interpreting your doc. e.g. HTML 4.0 Strict HTML 4.0 Transitional XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset Document Type Definition (DTC) = DOCTYPE <!DOCTYPE html PUBLIC “/ /W3C/ /DTD XHTML 1.0 Strict/ /EN” http://www.w3c.org/TR/xhtml1/DTD/xhtml1-strict.dtd> • This tells browser how to display and what language of markup is used. • This needs to be before opening <html> tag • If itʼs not included browser will revert to QUIRKS MODE e.g. default to old fashioned quirky markup interpretation that allows the browser to guess when tags are malformed or when the browser might not have the same standards. This allows older pages to display in newer standards compliant browsers. Adding DOCTYPE avoids any confusion also add: name space declaration. It is part of <html> opening and it insures page validates 4 <html xmlns=http://www.w3c.org/1999/xhtml> <meta http-equiv =“Content-Type” content=”text/html; charset=UTF-8” /> more later on metatags. Go to www.webstandardistas.com/02/template.html to get this View Source <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <title>Insert Your Title Here</title> </head> <body> <p>Replace this content with your own.</p> </body> </html> It wonʼt make your page look different but it is what you need to make sure your page is correct. STRUCTURE OF TAGS NESTING ELEMENTS – ONE ELEMENT WITHIN ANOTHER <html> l <head> <body> I I <title> </title> <p> </p> I l </head> </body> l </html> Valid XHTML requires proper nesting e.g. <title within <head> </head> tags Need to close tags in order that they are opened – first in last out e.g <p> <strong> <em> I am a paragraph. I am emphasized. I am also strongly emphasized. </em> </strong> </p> Comments Not everything in an HTML doc displays e.g. <head> XHTML allows hidden elements in head and body. These can only be seen in View Source <!! - - opens a comment - - > closes it 5 Everything between will be hidden in the browser Can use this to help you find your way. • Remind you why you structured the code a certain way • Provide a note regarding a change in the document • Leave a note to collaborators • Prepare code and content to use later (can remove the comments and reactivate code) White Space Use of line breaks, tabs and space to separate sections of your code to make it easier to read. Browsers wonʼt see this. XHTML GIVES A WEBSITE STRUCTURE AND MEANING Principle – POSH (Plain Old Semantic HTML) Creates structure Creates semantics – signposts for reading – like headings and emphasis To fully understand this we need to set aside desire to “design” for now BUT without realizing it – using structure and semantic markup means design is creeping in. STRUCTURED MARKUP = SEMANTIC MARKUP • Defines content • Organizes structure • This is part of design process • Beginning designers go wrong by missing this and rushing to make things look good. STRUCTURE – TAGS Use right one for right job – based on content. e.g. It defines what is a heading It starts with careful analysis of content Headings <h1> <h2> etc. guide the eye through content. Headlines of differing sizes signify importance. Example headings.html Whatʼs more important h1 or h2. – h1 most -- h6 least Paragraphs <p> sits under headings Helps reader skim Should convey doc structure Do not skip through hierarchy Do not use <h> tags to create visual effects 6 Application of Information Hierarchy CASE STUDY http://www.corpse.org Look at use of headings (skip past menus) Headings separate lots of info What is most important on page? What is most important story? Look at news h1 and h2 (are they all same importance?) H3 where is that? Stories on right – less urgent? Two approaches to markup of heads Linear – h2 is subsection of h1 Less linear – based on importance H2 is not sub part of h1 – it is just less important Content is the guide PHRASE ELEMENTS nested in <p> </p> tag Remember basic elements Start tag content End tag < > text text text text text </ > Elements can contain other elements (nesting) Everything is within the <body> </body> element A phrase element – adds meaning to text <em> <strong> nested in <p> </p> element convey meaning (or help screen readers know when to change volume or pitch) rather than as design feature like <i> or <b> which are Presentational.
Load more

Recommended publications
  • Beautiful Soup Documentation Release 4.4.0
    Beautiful Soup Documentation Release 4.4.0 Leonard Richardson Dec 24, 2019 Contents 1 Getting help 3 2 Quick Start 5 3 Installing Beautiful Soup 9 3.1 Problems after installation........................................9 3.2 Installing a parser............................................ 10 4 Making the soup 13 5 Kinds of objects 15 5.1 Tag .................................................... 15 5.2 NavigableString .......................................... 17 5.3 BeautifulSoup ............................................ 18 5.4 Comments and other special strings................................... 18 6 Navigating the tree 21 6.1 Going down............................................... 21 6.2 Going up................................................. 24 6.3 Going sideways.............................................. 25 6.4 Going back and forth........................................... 27 7 Searching the tree 29 7.1 Kinds of filters.............................................. 29 7.2 find_all() .............................................. 32 7.3 Calling a tag is like calling find_all() ............................... 36 7.4 find() ................................................. 36 7.5 find_parents() and find_parent() .............................. 37 7.6 find_next_siblings() and find_next_sibling() .................... 37 7.7 find_previous_siblings() and find_previous_sibling() .............. 38 7.8 find_all_next() and find_next() ............................... 38 7.9 find_all_previous() and find_previous() .......................
    [Show full text]
  • Introduction to HTML5
    "Charting the Course ... ... to Your Success!" Introduction to HTML5 Course Summary Description HTML5 is not merely an improvement on previous versions, but instead a complete re-engineering of browser-based markup. It transforms HTML from a document description language to an effective client platform for hosting web applications. For the first time developers have native support for creating charts and diagrams, playing audio and video, caching data locally and validating user input. When combined with related standards like CSS3, Web Sockets and Web Workers it is possible to build ‘Rich Web Applications’ that meet modern usability requirements without resorting to proprietary technologies such as Flash and Silverlight. This course enables experienced developers to make use of all the features arriving in HTML5 and related specifications. During the course delegates incrementally build a user interface for a sample web application, making use of all the new features as they are taught. By default the course uses the Dojo Framework to simplify client-side JavaScript and delegates are presented with server-side code written in Spring MVC 3. Other technology combinations are possible if required. Topics Review of the Evolution of HTML Playing Audio and Video Better Support for Data Entry Hosting Clients in HTML5 Support for Drawing Images and Standards Related to HTML5 Diagrams Prerequisites Students should have experience of web application development in a modern environment such as JEE, ASP .NET, Ruby on Rails or Django. They must be very familiar with HTML4 and/or XHTML and the fundamentals of programming in JavaScript. If this is not the case then an additional ‘primer’ day can be added to the delivery.
    [Show full text]
  • Doctype Switching in Modern Browsers
    Thomas Vervik, July 2007 Doctype switching in modern browsers Summary: Some modern browsers have two rendering modes. Quirk mode renders an HTML document like older browsers used to do it, e.g. Netscape 4, Internet Explorer 4 and 5. Standard mode renders a page according to W3C recommendations. Depending on the document type declaration present in the HTML document, the browser will switch into either quirk mode, almost standard or standard mode. If there is no document type declaration present, the browser will switch into quirk mode. This paragraph summaries this article. I will explain how the main browsers on the marked today determine which rendering mode to use when rendering the (x)html documents they receive. I have tested nearly all my assertions in Internet Explorer 6, Firefix 2 and Opera 9.02. The validation is done at the official W3 validation page http://validator.w3.org. Some of my assertions are tested using pages on the net. This is done when testing the media types ‘text/html’ and ‘application/xhtml+xml’with html and xhtml with both legal and illegal syntax. My previous article was full of vague assertions and even things that were directly wrong. This should not be the case in this article where nearly all the assertions are tested. One section I should be humble about is the ‘Doctype dissection’. Finding good sources decribing these in more detail than pages and books just briefly describing their syntax proved hard, but I have done my best and have also described in the text which section I’m certain about and the one I am more uncertain about.
    [Show full text]
  • Second Exam December 19, 2007 Student ID: 9999 Exam: 2711 CS-081/Vickery Page 1 of 5
    Perfect Student Second Exam December 19, 2007 Student ID: 9999 Exam: 2711 CS-081/Vickery Page 1 of 5 NOTE: It is my policy to give a failing grade in the course to any student who either gives or receives aid on any exam or quiz. INSTRUCTIONS: Circle the letter of the one best answer for each question. 1. Which of the following is a significant difference between Windows and Unix for web developers? A. The Apache web server works only on Windows, not on Unix. B. Dreamweaver cannot be used to develop web sites that will be hosted on Unix. C. File and directory names are case-sensitive on Unix, but not on Windows; you have to do a case- sensitive link check if you develop pages on Windows but they might be copied to a Unix-hosted server. D. Firefox works only on Unix, not Windows. E. Windows is just another name for Unix; there is no difference between them at all. 2. What is the purpose of the css directory of a web site? A. It holds JavaScript programs. B. It holds XHTML Validation code. C. It holds background images. D. It holds stylesheets. E. It is needed for compatibility with Apache and PHP. 3. What is the purpose of the images directory of a web site? A. To hold the <img> tags for the site. B. To hold the stylesheets for images. C. To differentiate between JPEG and PNG images. D. To hold the imaginary components of the DOCTYPE. E. To hold photographic and graphical images used in the site.
    [Show full text]
  • JTS Users Guide, Ver 2.0 Copyright 2013 Page 2 of 265
    Table of Contents 1 ABOUT THIS GUIDE .................................................................................................................... 13 1.1 WHO SHOULD USE IT ............................................................................................................... 14 1.2 TYPOGRAPHICAL CONVENTIONS ............................................................................................... 14 2 INTRODUCTION ........................................................................................................................... 16 2.1 OVERVIEW ............................................................................................................................... 16 2.2 PURPOSE ................................................................................................................................ 17 2.3 SCOPE .................................................................................................................................... 17 2.4 REFERENCES .......................................................................................................................... 18 2.5 GLOSSARY AND TERMINOLOGY ................................................................................................. 18 3 JTS SYSTEM DESCRIPTION ...................................................................................................... 21 3.1 KEY FEATURES ........................................................................................................................ 21 3.2 ENVIRONMENT ........................................................................................................................
    [Show full text]
  • Lxmldoc-4.5.0.Pdf
    lxml 2020-01-29 Contents Contents 2 I lxml 14 1 lxml 15 Introduction................................................. 15 Documentation............................................... 15 Download.................................................. 16 Mailing list................................................. 17 Bug tracker................................................. 17 License................................................... 17 Old Versions................................................. 17 2 Why lxml? 18 Motto.................................................... 18 Aims..................................................... 18 3 Installing lxml 20 Where to get it................................................ 20 Requirements................................................ 20 Installation................................................. 21 MS Windows............................................. 21 Linux................................................. 21 MacOS-X............................................... 21 Building lxml from dev sources....................................... 22 Using lxml with python-libxml2...................................... 22 Source builds on MS Windows....................................... 22 Source builds on MacOS-X......................................... 22 4 Benchmarks and Speed 23 General notes................................................ 23 How to read the timings........................................... 24 Parsing and Serialising........................................... 24 The ElementTree
    [Show full text]
  • Browser Mode and Document Mode
    Browser Mode And Document Mode When Hamish void his creatorship rebroadcasts not tarnal enough, is Ali angriest? Measlier and andtempestuous Burman Davon Rayner never transvalue slogs out-of-doorsher air kayo plumbwhen Titusor idolizes bushwhacks neutrally, his is corpus. Elton quadricipital? Batty Change to other one of the available browser modes available. How can test this kind of web pages? Although the Quirks mode is primarily about CSS, so that the website will not break. Add the header to all resources. Configure it as an HTTP response header as below. It is possible to bulk add from a file in the Site list manager. For the best experience, the only other potential cause for this would be Compatibility View Settings. The result is a cloudy atmospheric look. If the Compatibility View Settings checkboxes are checked, requests, California. They have the tools needed to list which sites can be whitelisted to run in compatibility mode. Determines how the Spread control renders content for a specific browser mode. Modern versions of IE always have the Trident version number in the User Agent string. Are you facing any issues? Some engines had modes that are not relevant to Web content. Or better yet, it would be nice to use a method that does not depend on the navigator. Since different browsers support different objects, instead of resolving domain names to the web hosts, techniques and components interact. Suppose the DTD is copied to example. Thanks for the feedback Jamie. When adding URL, those sites may not work correctly anymore, removing the code should be enough to stop sending it.
    [Show full text]
  • Beautiful Soup Documentation Release 4.2.0
    Beautiful Soup Documentation Release 4.2.0 Leonard Richardson February 26, 2014 CONTENTS 1 Getting help 3 2 Quick Start 5 3 Installing Beautiful Soup 9 3.1 Problems after installation........................................9 3.2 Installing a parser............................................ 10 4 Making the soup 13 5 Kinds of objects 15 5.1 Tag .................................................... 15 5.2 NavigableString .......................................... 17 5.3 BeautifulSoup ............................................ 17 5.4 Comments and other special strings................................... 17 6 Navigating the tree 19 6.1 Going down............................................... 19 6.2 Going up................................................. 22 6.3 Going sideways.............................................. 23 6.4 Going back and forth........................................... 25 7 Searching the tree 27 7.1 Kinds of filters.............................................. 27 7.2 find_all() .............................................. 29 7.3 Calling a tag is like calling find_all() ............................... 33 7.4 find() ................................................. 33 7.5 find_parents() and find_parent() .............................. 34 7.6 find_next_siblings() and find_next_sibling() .................... 34 7.7 find_previous_siblings() and find_previous_sibling() .............. 35 7.8 find_all_next() and find_next() ............................... 35 7.9 find_all_previous() and find_previous() .......................
    [Show full text]
  • Site Development Associate Student Guide Web Foundations Series CCL02-CFSDFN-PR-1405 • Version 2.1 • Rd060214
    Site Development Associate Student Guide Web Foundations Series CCL02-CFSDFN-PR-1405 • version 2.1 • rd060214 EVALUATION COPY EVALUATION COPY Site Development Associate Student Guide EVALUATION COPY Chief Executive Officer Barry Fingerhut Vice President, Operations & Development Todd Hopkins Senior Content Developer Kenneth A. Kozakis Managing Editor Susan M. Lane Editor Sarah Skodak Project Manager/Publisher Tina Strong Customer Service Certification Partners, LLC 1230 W. Washington St., Ste. 201 Tempe, AZ 85281 (602) 275-7700 Copyright © 2014, All rights reserved. EVALUATION COPY Site Development Associate Developer Patrick T. Lane Contributors DeAnne Bowersock, James Stanger, Ph.D., and Kenneth A. Kozakis Editor Sarah Skodak Project Manager/Publisher Tina Strong Trademarks Certification Partners is a trademark of Certification Partners, LLC. All product names and services identified throughout this book are trademarks or registered trademarks of their respective companies. They are used throughout this book in editorial fashion only. No such use, or the use of any trade name, is intended to convey endorsement or other affiliation with the book. Copyrights of any screen captures in this book are the property of the software's manufacturer. Disclaimer Certification Partners, LLC, makes a genuine attempt to ensure the accuracy and quality of the content described herein; however, Certification Partners makes no warranty, express or implied, with respect to the quality, reliability, accuracy, or freedom from error of this document or the products it describes. Certification Partners makes no representation or warranty with respect to the contents hereof and specifically disclaims any implied warranties of fitness for any particular purpose. Certification Partners disclaims all liability for any direct, indirect, incidental or consequential, special or exemplary damages resulting from the use of the information in this document or from the use of any products described in this document.
    [Show full text]
  • Web Design in Nvu Workbook 2 Web Design in Nvu
    Inspiring | Creative | Fun Ysbrydoledig | Creadigol | Hwyl Web Design in Nvu Workbook 2 Web Design in Nvu CSS stands for ”Cascading Style Sheets”, these allow you to specify the look and feel of your website. It also helps with consistency. Style sheets have actually been around for years, they are technical specifications for a layout, whether print or online. Print designers use style sheets to ensure that designs are printed exactly to specifications. “Cascading” is the special part. A web style sheet is intended to “cascade” through a series of style sheets, like a river or waterfall. 1) CSS Go to www.csszengarden.com On the right of the page you will see a navigation list. Notice that when you click on options on the list, you get the same website but it looks completely diferent. This is because diferent style sheets are being used. Have a look at the following HTML: <h1> Title of your page </h1> This would be the title of your webpage. By typing this, you are letting the computer know that you want the text displayed as a header, in size 1. You can this this for each of the pages for the title and each time the computer will format it as a “h1”. In the Cascading style sheet, you can specify that you want your title to be orange on every page. This can be achieved by using the following code that tells the computer every time it sees a H1 being used, the text should be orange: h1 { color:orange; } 2) Testing and editing Go to www.w3schools.com/css/tryit.asp?filename=trycss_default Here is a webpage set up on the right and the CSS on the left, as you edit the sandbox environment in the box on the left, it will update the image on the right to see what the code translates to visually.
    [Show full text]
  • XML Error Handling
    Theories of Errors Bijan Parsia COMP60372 Feb. 19, 2010 Monday, 1 March 2010 1 Finishing Types Since we are gluttons for punishment Monday, 1 March 2010 2 Recall • We now have a theory of matching – i.e., we know what it is for a value to match a type – e.g., a simple value matches xs:string iff it’s a string – Matching was complex for elements • But matching isn’t our key service – validation is • Two conceptions of validation – Grammar based recognition • Validate as instance of some DTD • Validate “against” some DTD • Determine if valid wrt some DTD – PSVI production • Go from an untyped value (or its string rep) to a typed one • validation and erasure Monday, 1 March 2010 3 Validation (subset) Compare with matching! Monday, 1 March 2010 4 Erasure A complexity! integer-of-string(“01”) = integer-of-string(“1”) Wildcard info lost! Monday, 1 March 2010 5 Validation & Erasure • Features of “external representation” – Self-describing and round-tripping • Round-tripping failure comes from cases where – erases is a relation (trivial) • “01” to 1 to “1” – erases obliterates type Self-description failure! • {“1”, 1} to “1 1” to {1, 1} (or {“1”, “1”} Monday, 1 March 2010 6 Coursework Retrospective • Some Tricky Bits™ – No one expects the Spanish Inquisition • No one! – minidtdx.xsd describes the syntax of (mini)DTD/XML • It describes an XML syntax for a fragment of DTDs • It does not describe the semantics! – Esp. not by example! • It is incomplete – It is not the tightest schema possible – Questionable syntax choices? » Repetition in choice • XML Schema in different modes – Validate where? – Xerces Has A Bug • nillable=”false” Monday, 1 March 2010 7 Error Reporting • What’s wrong with..
    [Show full text]
  • Beginning HTML5 and CSS3 : [The Web Evolved ; Next Generation Web Standards]
    Beginning HTML5 and CSS3 Richard Clark, Oli Studholme, Christopher Murphy and Divya Manian Contents Contents at a Glance iv Forewords xv About the Authors xvi About the Technical Reviewers xvii Acknowledgments xviii Introduction xix Who is this book for? xix How is this book structured? xix Conventions used in this book xix Chapter 1: HTML5: Now, Not 2022 1 Basic tenets 1 A web standards approach 2 The Dao of web design: embracing uncertainty 4 Accessibility 6 Crafting your markup 7 How was HTML5 created? 8 Beyond HTML 4 8 XHTML 1.0 8 XHTML 2.0 and the backlash 9 HTML5 moving forward! 10 HTML5 design principles 11 Supporting existing content 12 Degrading gracefully 12 Don't reinvent the wheel 13 Paving the cowpaths 13 Evolution, not revolution 13 A dozen myths about HTML5 14 1. Browsers don't support HTML5 14 2. OK, most browsers support HTML5, but IE surely doesn't 14 3. HTML5 won't be finished until 2022 14 4. Now I have to relearn everything! 15 5. HTML5 uses presentational elements 15 6. HTML5 is a return to tag soup 15 7. HTML5 kills accessibility kittens 15 8. Flash is dead 15 9. HTML5 will break the Web! 15 10. HTML5's development is controlled by browser vendors 15 11. HTML5 includes CSS3, Geolocation, SVG, and every other modern technology under the sun 16 12. So when can I start using HTML5? 16 Summary 16 Homework 17 Chapter 1 homework 17 Directed reading 17 Chapter 2: Your First Plunge into HTML5 19 Homework review 19 Our page 20 84.8% of your markup remains 21 It's all in the head 22 A more perfect DOCTYPE 23 Declaring languages in HTML5 23 Character encoding 25 Mr.
    [Show full text]