Determining how to organize your web site is no easy task. Finding the right structure for your site can take quite a bit of research and trial and error. To find that right fit you need to understand information architecture and choose the right method for you.
Essentially, information architecture tells you where certain parts of your site should go. This includes in your home page, your navigation and on the various other pages throughout your site. The key to information architecture is that it is not about design per se, meaning something that is pleasing to the eye to view. It is more a matter of where content should be on a page, as well as links and other pages on your site. It is a matter of structure for your site.
Information architecture can work as a type of storytelling. It is an effective way of reaching your users through their emotions and drawing them in with your content. It is more than just making a page appear orderly and neat. A variety of methods exist behind information architecture, and here are just a few to get you started.
The theory behind organization schemes is you categorize your content based on the way you want each piece to relate to the other. Two different types of organization schemes exist: exact organization schemes and subjective organization schemes. Determining which one is the right one for you depends on the type of content involved.
Subjective organization schemes take information and put it into categories that are specifically defined by a field or organization. They are less than specific and more open than exact organization schemes, but they can be difficult to design from the start. The reason for this difficulty is that a subjective organization scheme needs to get into the mind of the user to organize the content. However, that process is far from easy, and it takes stepping into the user’s state of mind to see it from his or her point of view. Once you understand and can draft a user mental model, you should be able to arrange the content in a manner that is the most effective in reaching the user. Unlike the black and white organization method of exact organization, subjective draws relationships and connections between pieces of content. The following are a few examples of subjective schemes.
Not all content schemes need to be so black and white, one type or another. Hybrid schemes are available, and many sites take advantage of this possibility to create the best information architecture method possible. Choosing one scheme, exact or subject, can be helpful in that it keeps the organization simple for the user. However, one size might not fit all, and if there is conflict between designers as to which scheme is best, creating a mix or hybrid of two can be helpful. The problem with this tactic can be if it is not properly done, users may become confused when attempting to find content. If you are not 100 percent sure what you are doing and prefer to keep things more basic, sticking to one scheme over another might be best for your site. If you are not sure, seek the advice of experts.
Organization structures are similar to organization schemes, and one would assume they would actually be the same thing based upon their titles alone. However, organization structures take content and arrange it based upon the relationship users define between different pieces of content. Users can predict the location of content based upon the actual structure itself. Three different types of organization structures exist: hierarchical, sequential and matrix structures. Developers can use one structure alone, but many will take all three and morph them into the right structure for their site.
Think of a hierarchical structure as a sort of family tree. Like a family tree, you start with one idea and branch out from there. This type of organization is similar to a parent/child relationship between the different content. You can also organization content in a hub and spoke structure, as well. Regardless of which hierarchical theme you use, the point of this type of structure is users take one broad idea and narrow down their search as they seek more detailed information.
Family tree structures look like what you would see when constructing a family tree. You might also consider them to look like a structure of an office. You have a manager, and the tree then branches down from there. One large idea is broken down into two, and then those two different related by yet separate topics are broken down into even more subtopics relating solely to the subtopic above them. As you get more and more detailed, the branches break out more.
However, in a hub-and-spoke structure, you have one main idea and like spokes on a bicycle, subtopics break out from that one idea. They are all related but yet separate. One subtopic does not branch out from the other, and they are more equal, so to speak. But since they are connected to the one main topic at the center of the all, they are all related in some way. A hub-and-spoke hierarchical structure can be a bit more free form than a family tree type of hierarchy.
Sequential structures arrange the content in a step-by-step process. How do you get from Point A to Point B? You start at one location and go through the path created by the web developer. Prior to coming up with this structure, the web developer needs to research and create the most logical steps that would make sense in the sequence chosen. One example of what a sequential structure looks like is what you would see when a user is trying to purchase something. You select the item, click on checkout from your cart, enter in your content information, enter the payment information and then click submit. A logical step-by-step theme takes you to the end result you desire, purchasing that specific item. Another example is when a user is taking a course online. You do not jump from one piece of content to another. Rather you view the content from point A to your end result, but you do this in a process designed by the developer. When creating this structure, the developer is assuming that an ideal ordering of content is the most effective way to consume the content posted.
No, you will not pick a blue or red pill with a matrix structure, nor will you be guided by Keanu Reaves. A matrix structure, however, gives users the power. Through these types of structures, content is arranged and linked in more than one way. It depends on how the user decides to view the content as to what the organization will be. The idea is actually more complex than it sounds, however. Matrix structures rely on hypertext or HTML to make this type of organization possible. One user might choose different topics to access in order to navigate through the content, while another user might get to the same place but through a radically different process than the first user. It all depends on that specific user’s methodology.
A content inventory includes a list of all content on your site. This content does not just include written content but also images, applications, and data. To get an accurate inventory you need to assess each piece of content you have. You need to have a good understanding of what you have on your site and where it is, as well as where it should be.
So where do you start? Developers should consider several questions would pulling a content inventory.
You have your goals and your scope. It is now time to start. However, how do you even go about starting off? Before you get too far, you will need to accumulate certain pieces of data for each piece of the site’s content. It can depend on what your goals are, but several standard pieces are traditionally collected in content inventories. You will need the following:
Sometimes you can utilize a content management system or web crawler to get this information. Once this information is pulled, it can be then exported into a spreadsheet, allowing the information to be sorted easily.
Once all of that data is pulled, you will need someone to manually go through each piece of information and assessment. This process is definitely not one for the faint of heart and needs to be done by someone who is detail-oriented and understands the process. How you go about doing this depends on those goals and your scope listed. These initial goals will set the type of assessment that is performed on the data once it is pulled.
A lot can be done through a convent inventory. The goals and scopes help establish this. Audits can help site developers track what pages on your site should be eliminated, what pages need to be edited, what gaps in content need to be filled, and whether content needs to be moved.
You should also consider adding columns for purposes of your editorial review. If something is being fact-checked, changed, or modified, use these columns to monitor progress.
Your site has been inventoried. Now what? One purpose of a content inventory is to maintain a site navigational model. It gives you a base from which to start for a complete overhaul of the navigational model of the site. It can be used as a duplicate of the copy deck. If content is being overhauled, the developer can use the inventory to help guide them when rebuilding the page.
Several reasons do exist for create a content inventory.
Several of these reasons include:
You should normally inventory when you are the first stages of your site redesign. You may also choose to inventory when preparing for a content management system migration. A content inventory can also be part of site maintenance on an ongoing basis.
Content inventories are not a small project by any means. Just hearing the words can strike fear in the strongest of web developers. They can be time consuming, monotonous and never ending. Many developers see them as pointless for sites that are updated frequently. Once you create an inventory, if your site is constantly being updated, your inventory can quickly be outdated. What does that mean? Time to do another inventory, of course! Who is excited?
One last information architecture method is wireframing. Wireframing looks at a page’s interface, focusing on the space allocated on the site and where content is listed based on priorities and functionalities. Wireframes are not interested in the actual design, color style or graphics on a site. Rather, wireframes are focused on the content and functionality of the page. This method helps create relationships between the templates on a web site.
Wireframes are useful for several different reasons. As a developer, you may only have one of these reasons, or you may require all. The following include just a few:
This prioritization of content can help determine how much space should be given to one item over the other and where is best to locate that item.
Wireframes help you determine where certain navigation and content elements of your site will be on your page. Keep in mind that wireframes are not about appearances or visual design so try not to go overboard. Here are a few tips for creating wireframes:
A wireframe includes many different elements. Like a content inventory, what elements are included can depend heavily on the type of site. However, traditionally certain elements are considered fairly standard. They include:
Because web sites can differ in so many ways, so can wireframes. In fact, different types of wireframes exist. The differences can include the way they are produced to what detail they convey. Two different types of wireframes are commonly used depending on these differences, and these are the low-fidelity wireframe and high-fidelity wireframe.
The hierarchical method may take an approach of breaking content out from the top to the bottom, but the database model takes the opposite approach. In a database model, content is organized from the bottom on up. The links within the meta data in the site is what controls the database model. As opposed to other schemes or models, the database model tends to be more dynamic and offers more search capabilities and advanced filtering for the user.
In addition to information architecture methods, your team may also need to utilize site diagrams to prepare an image of the hierarchy of information and communicate your organizational concepts to the web team as well as related stakeholders. It is important to communicate as a team throughout the project and to show the process from brainstorming to planning the actual document from a blueprint to a site.
The site diagram can be a hierarchical organization chart, which is a more simple use of a diagram, or it can be an informative map showing the layout of the site, including information and user experiences. Essentially it really depends on how detailed your team needs to be in communicating throughout the process.
What should be included on a site diagram? It depends on the detail and maturity of the diagram, but many diagrams—include:
The process of site diagram creation can range from simple to involved. Certain diagrams are conceptual, and the purpose of these are to communicate to the team at a more general level. As the project progresses, a more complex blueprint site diagram might be more appropriate to communicate to not only the clients and stakeholders but to also serve as a guide to the edifice of the user interface as well as the site directories or files.
Site diagrams can be created through a variety of drawing software, such as Adobe Illustrator. However more specific programs can be utilized for more specialized diagrams, such as OmniGraffle, ConceptDraw or Microsoft Visio. If you are not sure which software is for you, seek the advice of experts to get advice prior to trying out the product.
Simply creating a site’s architecture is not enough. You need to make sure that the structure is not only effective for the here and now but is also sustainable. As time passes, different aspects and the content of the site, the architecture will need to be modified for that. No one wants their site to be static. Users will recognize when a site has not been updated in quite some time, and that will often keep users from continuing to come to your site, which will hurt you in terms of search algorithms. It goes without saying that, if your content is going to be evolving, so should your structure. Several things should be considered when creating a sustainable information architecture structure.
Creating a site is more than just producing the content. Simply producing content provides nothing if the user is not able to easily find it. Information architecture is the key to laying out and arranging the content so that users are able to find what they are looking for, which, you hope, is the content you are producing on your site. The key is finding the right structure for you, and that can depend on who your user is, the type of content you are producing, among other factors. Once you have found the right fit, make sure you are able to maintain and keep up with the structure. If you play your cards right, you will find that your site is able to withstand the test of time.
Create, edit, customize, and share visual sitemaps integrated with Google Analytics for easy discovery, planning, and collaboration.