Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
Notes de l'éditeur
Introduction:Who I amWhere I workTalk about wordpress
No RelationShare a passion for what we loveWe want to share that passion with everyone around usin hopes that they will love it as much as we doWhen sharing new/exciting or a little different its sometimes met with hesitation
People have an innate fear of trying something newThey love what they are comfortable with. Even if it is something that is just a little different on the surface But on the inside it’s the same thing we’ve been using all alongCan I please see a show of hands for how many of you haven’t used HTML5? (Look around, these are all the people that are using HTML5 and just don’t know it yet) That’s what we will talk about today.
Important to know where something comes from to know where its going. HTML4 specification was published in 1999 only revision to that spec was XHTML1. XHTML1 was identical to HTML4, except it took on the strict syntax of XML. Where as HTML had plenty of freedom in how they wrote their elements and attributes, xhtml would require authors to follow the rules. At this time no new tags were introduced.W3C Felt HTML4 was the last HTML and began work on XHTML2Although the names were similar they were completely different. XHTML2 would not be backwards compatible with existing html or any other web content. It would be a pure language unburdened by its history. It was a disaster. In 2004 a small group of representatives from Apple, Opera, and Mozilla proposied the idea of extending HTML4 to allow the creation of web apps. It was rejectedThey then started a group called WHATWG ( Web hypertext application techonlogy working group ) and began crafting their own version of HTML, HTML5 In 2006 the W3C who had made little traction with XHTML2 decided to unify with WHATWG and begin working together on HTML5The general fear at this time was that this would mean a return to sloppy markup, but its quite the opposite.
The beaten path. If there is a widespread way of doing something (even if its not the best) it should be part of the spec
Doctype reduce charactersNo more DTD’sHTML is HTML now, not 4 or 5
Added en for lang support on html5 devicesNo more need for decade old xmlns reference
Content type is understoodUTF8 is standard
No need for text/cssBrowser knows it’s a style sheet
No need for type or language the browser knows that script is javascript
Lets have some real fun, but first what do we need to support these tags?
Google SHIV Uses document.create to create elements. Set new html5 elements to display block so the take on div like formatting.By default, block-level elements begin on new lines.Generally, block-level elements may contain inline elements and other block-level elements. Inherent in this structural distinction is the idea that block elements create "larger" structures than inline elements.
Header of a page Or header of a sectionOr header of an article
Group together thematically-related contentIt’s a lot like a div, but it has semantic meaning after all div is a division of contentAlways as yourself if all of the content is related, 80/20 rule.
This is your content area, articles can have sections, headers, footers, whatever makes sense! You can also wrap article around links to content.
Multiple navs
Aside is a sidebar but not in terms of location, instead in terms of content. Its tangentially related content Its much like a pull quoteContent dictates the tag NOT location! Get ready for micro formats
Time is a great micro format, Semantic ways of marking up content that is read by a device, crawler or software. Remember that the end result is to accurately represent the time you are displaying.
This is relative new and not necessarily HTML5 but a great piece of SEO juice especially for wordpress bloggers. Links to yourself and links to other articles you write will be index and picked up. Google has openly said that they will start to feature bloggers in search results based on these types of inter linking
Lets build a simple page
Confusion around the timeline ‘When will it be ready’ 2022 has been mentioned as being the time where we will get a proposed recommendation. That means it will have 2 complete implementations, but this is an unlikely goal and depends on the browsers all making full use of itThe date that really matters is 2012, this is the date that HTML5 will become a candidate recommendation, meaning little change so browser makers no longer need worry about much change. But to us that isnt even that relevant. What we care about is what browsers are supporting it today. It will never be fully ready to use, instead start to use parts of the spec while browsers start to support it. HTML5 isnt a brand new language, its an evolution if you currently use HTML to build websites you are already using HTML5.
