Let me walk through an example sitemap process, so I can explain how to get from a list of content and functionality, remember the requirements we determined in the outline of scope phase, to a sitemap. So, here we have a bunch of content items, let's say this is for an E-commerce sites. The first step would be to sort these items into sections of related content. Now, we have things that belong to products and the shopping experience on the left. Items that belong to information about the company is collected in the middle, and information about contacting and visiting the company is on the right. We have a few other things like FAQs and the blog as standalone sections. Next, let's find some umbrella terms that can describe these content buckets that we created. Here we have Shop, FAQ, Shopping Carts, About, Blog and Contact. These labels will form the main navigation of the sites, the links that you'll find on top of every page. Note that we don't have a section that the credits and the privacy policy fit into. Well, these are pages that while they are important to be included, don't need to be accessed from the main navigation. So, let's decide to link to them in the footer of every page. Let's take another look at the Contact section. The last two items Directions and Opening Times could fit here. Visiting a store can be somewhat described as a form of contact, but it's not very precise, is it? Let's be more explicit and create another category. Now, we added a section called Visit, which will contain information for Directions and Opening Times. This new section will also stress that this online store also has a physical location, users will see the word visit right in the primary navigation. Okay, now let's look a little closer at all the content items we have and decide if we need actual pages for each. Here, I isolated all of the content notes that do not need their own page. The product description and images and customer reviews will live on the product pages. The About text will go on the About landing page, the Employee Directory will fit nicely on the Our Team page, contact info and social media links can be listed combined on the Contact page. We don't need sub-pages for the Visit page, we can list Directions and Opening Times on just one page. Okay, we cleaned up quite a bit by now, we are ready to build out the sitemap. We'll start with the main level items. They go across the top, but what about the order here? The order should make logical sense and also indicate importance. Having the shop first makes sense, but you might determine that it's more important to list the Visit section next and to move the About section towards the end. Also the FAQ are a little more important than the Blog, so we'll switch those and it's somewhat of a convention to list the Shopping Cart last. Speaking of the shopping cart, it's the only navigation link that has two words, let's be consistent and rename it to just Cart. There we go, our final main level navigation and now we add all of our secondary content we determined earlier. Here's everything that goes into the Shop category. Note that the Featured products and the Products sections, both link to Product Details and the icon for product details looks a little different. It's a page stack to indicates that there will be many different product detail pages. The same happens with the Blog Posts, there are many different Blog Posts that all link from the Blog landing page. Here are all the pages that need to go under the About section and here are all the different steps that the user will need to complete during the checkout process. Note that instead of using simple lines we have arrows to indicate the sequential order of these items. The user won't be able to advance to the billing info let's say, before they entered their shipping info, the arrows indicate that. Also there's a horizontal bar on the last arrow to indicate that once you reach the Order Confirmation page you can't go back to the Confirm Order page. We also have to account for the two items that we're adding to the footer. Since they will be on every single page we just list them separately on the bottom of our sitemap. Okay, we're almost done, there's only one little detail missing. In fact, it's actually not so little. We're missing an important page, can you spot which one? It's the page that most people will land on when they visit the site. The Homepage and we'll indicate with lines that the Homepage links to all the other primary navigation items. So there you have it, a beautifully organized sitemap. Remember where we started, with a wild list of requirements. It took a little work to pare this down into a meaningful, logical and cohesive whole. In the next video, I will talk a little bit more about the different elements that make up a sitemap.