Easy-to-follow video tutorials help you learn software, creative, and business skills.Become a member
In this chapter, we are going to take what we've learned about HTML5 syntax and the new structural elements and apply it in creating and designing our own HTML5 document. Now, before we get into any of the code of the document itself, I want to talk about the process of planning and structuring your documents. And I am really just going to talk about my own workflow. It's not any better than anybody else's, but hopefully you can take some things out of my own workflow, adapt it to yours, and use it for the planning and structuring of your own HTML5 documents.
Okay, so the first place that I start before I begin any type of pencil sketches or wireframes or anything else, I start with content, and the reason for that is I'm really concerned about how devices are going to access my content, not only now, but also in the future. So even if I don't know every single piece of content that's going to be on the page, I will probably have a good idea. So I'll sit down and I'll just sort of list all those different pieces of content and sort of quantify them. That allows me to really start thinking about the document structure and thinking about how that content needs to relate to each other.
So what I want do is show you the content for the page that we're going to be designing. Now, the page that we are going to do is the Explore California Trail Guide page, and it's going to be one of the pages that focus on a single trail review, in this case the Northridge loop. So looking at the content that we are going to have on this page, we are going to have obviously some site navigation, some branding and identity content, a trail review-- it's going to be our Northridge trail review. We have some user-submitted reviews, so users on the page can go ahead and submit their own trail reviews.
We have some trail facts, also advertising, a little small advertising area, and then some content information, some legal information that's pretty typical of most pages that you are going to be working with. So what this does is it really helps me think about what's going on the page, where that content needs to be located, and in the case, in terms of thinking of it in terms of HTML5, which semantic elements we are going to use to represent that content. And in terms of thinking of the document outline that's going to be generated, remember, what we have learned in the last chapter about the HTML5 outlining algorithm, how our document outline needs to be structured based on that algorithm. So that really sort of leads me to thinking about the outline.
So what I have done is I have put together the outline that I want my document to generate. So if I go ahead and hold this up, we are going to start with the Explore California Trail Guide to identify what the page is and the contents of the page. We are going to have our main page navigation following very closely after that. Then we are going to have a section on trail reviews. So this is just a whole section of trail reviews, and in this case, we are looking at one individual trail review. We are going to be looking at the Ojai trails region, and the trail that we are going to be looking at is the Northridge loop.
After that, this article has several sections, including skill level, surface materials, things like that. At the very end of that, notice that we have a section here for comments. So this is a situation where users can go ahead and comment on the review and sort of add their two cents if you will. We are going to have a section on those rider reviews that we talked about. Those are user-submitted reviews. We are going to have two of those. Now here's an interesting part of document outline: notice that we have Ojai trail facts sandwiched in between two of those reviews. So obviously, Ojai trail facts is not a rider review, so we are going to have to put a lot of thought into how that information relates to each other and which semantic tags we are going to use to sort of describe the relationship there.
And then at the very end, we have the advertising section, this "Want to take a tour?" So you may have noticed that the contact information and the legal disclaimer information are left off of this document outline. The purpose of this document outline is not to sit there and list every single piece of content that's going to be in your file. The purpose of generating this outline is thinking about the semantic structural elements that you are going to be using on the page and what type of outline that's going to generate for assistive devices and assistive technologies and search engines and things like that.
So there are certain pieces of information that you might want leave off, and in this case, that's certainly one of them. Now, this process to me makes creating wireframes and thumbnail sketches and designs a lot easier, because now I have the relationship between my content. I have the content that we are going to be focusing on more than anything else identified as well. So it really actually helps the remainder of my process. It's a step you definitely want to think about taking. Okay, so armed with this outline, I can now begin to wireframe my content.
I can start identifying which structural elements, which semantic elements we are going to use for the various sections of the page, and we are going to take a look at that in our next movie.
Get unlimited access to all courses for just $25/month.Become a member