Imagine going to a new grocery store and not having a clue where anything is. There are signs, but they’re vague and confusing. Maybe they’re so obscure you don’t notice them at all. Would that make for a good first impression? If you’re anything...Read more.
Every organization has a story. Somewhere along the line, a spark inspired someone to challenge the status quo, and that idea was tempered by milestones to forge the business we see today. What better way to celebrate that history than to put it on...Read more.
Information architecture and page hierarchy can make or break you. Your interface should be designed with your end goals in mind. Website visitors arrive with many levels of literacy, attention spans and 'will' to figure out how to use your website...Read more.
Not to toot our own horn, but I think we make wireframes that are pretty good...and unique. We include some basic design elements to help clients get a clearer idea of what the final product is actually going to look like. This is unusual since...Read more.
Imagine going to a new grocery store and not having a clue where anything is. There are signs, but they’re vague and confusing. Maybe they’re so obscure you don’t notice them at all. Would that make for a good first impression? If you’re anything like us, you wouldn’t make a return visit anytime soon.
Now shift that scenario from a store to a website.
The same principles apply. If the navigation isn’t clear and inviting, chances are, you won’t bookmark it to visit again—or worse, you’ll leave without exploring any further. So, what can be done to save our own websites from this fictional fate? Let’s take a look at six organizations with an abundance of navigational inspiration.
EarthJustice uses color-coded horizontal navigation to differentiate informational tabs from calls-to-action. Upon hover, second and tertiary levels drop down in easy to follow menus.
Headlands Center for the Arts also color codes their horizontal navigation, but instead it’s upon hover, where secondary levels are highlighted.
The Bill & Melinda Gates Foundation uses a minimalist approach by containing its navigation within a menu symbol in the upper left corner. Once clicked, vertical categories appear on the left side with dropdown arrows to expose further sublevels.
3. Comedy Central
Comedy Central has a horizontal navigation that changes color and drops down upon hover, displaying alphabetized secondary menus.
AIGA differentiates itself by dropping a semi-transparent gradient over the content, upon hovering over its horizontal navigation. Visitors can focus on navigational options, while still viewing the page they landed on.
This larger full screen overlay is responsive friendly, and gives you the ability to tuck away your main navigation items while still giving them full attention when called upon. A little bit more intense than the AIGA example, but another well designed and engaging option.
Every organization has a story. Somewhere along the line, a spark inspired someone to challenge the status quo, and that idea was tempered by milestones to forge the business we see today. What better way to celebrate that history than to put it on display?
Your audience wants to connect with you. They want to relate and invest in your success. But to do so, you have to let them in on the narrative. That’s why timelines are so popular in web design right now. With a few clicks, audiences are able to see an organization’s impact through solid, qualitative facts that stick with them. When executed properly, they might even encourage your visitors to become part of your future—but how?
Don’t worry. We’ve searched far and wide for seven of the best tips and examples to inspire you.
Information architecture and page hierarchy can make or break you. Your interface should be designed with your end goals in mind.
Website visitors arrive with many levels of literacy, attention spans and 'will' to figure out how to use your website. If they are not able to find what they are looking for quickly, you've lost them. Start by defining the goals of your page, and what journey you want users to take:
Identify the "who" (stakeholders and target audience). Who is reading the content you are presenting? What do they need to know in 1 sentence.
Identify the "why" (your goals). Why do they need to know this information, giving them a line of context is helpful.
Identify the "how" (functional website requirements). How are they going to accomplish what they came to your site to do. (eg. 'Welcome to site 'X' you are hear to learn about 'Y.' You should learn about 'Y' so that you can accomplish 'Z.' Here are the steps you need to take to accomplish 'Z.')
By setting clear expectations for your users from the start, they will not get lost or confused in their process through your website.
The following is a short list of page elements and a few best practices too make your website's pages easier to read and digest.
1. Effective Headings & Sub-headings
Pages are typically divided into sections and sub-sections.
Each section is usually started with a heading.
Use headings in a hierarchical way.
The hierarchy of headings is limited to five starting with H2 - the most important - and finishing with H6 - the least important.
You should use them in the following way:
The page heading - the title of the page - is always formatted as an H2. It is the only heading on the page that should use this setting.
Use H3 for sub-headings
Use H4 for sub-headings within a subsection that is started with an H3
Use H5 and H6 for subheadings within sections
Align all headings and subheadings to the left as a general rule, unless the design of your website is mobile first and all your headings are centered....either way...
Use sentence case for all heading and sub-headings. Sentence case is the standard approach to using upper and lower case letters, mainly in titles and headings. It is the most legible for all levels of readers and gives them a visual queue that something is a heading (since each word has a capital letter).
2. Succinct Paragraphs
Paragraphs are single blocks of text which flow from left to right, often running to more than one line, and have a single blank line above and below.
Lower literacy readers need chunking, so if it going to take you more than 2 normal length sentences to make your point, consider editing.
All paragraphs should be aligned to the left (the default alignment). Avoid aligning paragraphs to the center or right unless you have designed a site that has intro sections of text that are centered. If you do, only have 1 sentence centered, as a rule it is more difficult to read since English readers are used to reading left to right.
Keep your text short and to the point.
Use bulleted lists with plenty of space between items—this helps slower readers absorb your information more effectively.
3. Text formatting
Within text, there are a number of options available to emphasize text:
Use italics sparingly. It is ok to use for publication titles of course, but large amounts of italicized text is very hard to read online.
Use bold sparingly. For clear emphasis of an idea or sub-heading, it is great, but large amounts again are very hard to read. Plus, you can't emphasis everything!
Use color very sparingly. Excessive use of a different color, for example red, makes it very quickly lose effect and again is just hard to read. If you must highlight an important point in a different color, limit it to as few words as possible and do not make it a habit.
Use all capitals sparingly. Excessive use of capitals can get very annoying very quickly and should be reserved for special cases. Words in all capitals are very difficult to read online and often feels as though you are shouting at someone.
Note: ALL CAPS are a great use case for buttons, main navigation items, and other situations where a single word is used.
Do not underline. As a rule, you should NEVER underline because most browsers make links appear underlined. If you underline text that is not a link, it will only confuse your site visitors.
If you are not a designer, or have not had a designer create a styleguide for you, as a rule, the settings for any table should be as follows: Cell padding = 5; Cell spacing = 0.
Text within cells should be vertically aligned to the top of the cell. This makes it the easiest for people to read the contents of your table by keeping the text from running into itself or floating at random heights within your table (depending on the length of your text).
Not to toot our own horn, but I think we make wireframes that are pretty good...and unique. We include some basic design elements to help clients get a clearer idea of what the final product is actually going to look like. This is unusual since wireframes are mostly used to get a general sense of layout, content, functionality requirements, and heirarchy. Typically, you are not talking about fonts, line weight, use of images, (ie. the visual language) at this stage in a website build.
So, why do we do it this way? Well, we have found that wireframes can be a difficult thing for clients to conceptualize. They understand that this stage is when we are determining the heirarchy of their information and the general placement of content and "calls to action," but if there are not more specific layout details, sometimes it is hard to "see where this is going." Over time, we have gotten more and more detailed with our wireframes so that the final products look more like a grayscale version of the website to be, rather than a simple content map.
Here are some tips if you want to construct a wireframe the Rootid way:
Research. Make sure before you get started that you have looked at websites (ideally with your client) that have similar layout and functionality as what they are interested in. Talk about use of menus, column widths, call to actions, any highlight areas, use of motion, video or imagery done in interesting ways. This intake conversation is probably the most important step. It saves a lot of time down the road if you already know your clients' leanings. Also, we tend to use this as an opportunity to get input from as many stakeholders as possible. By using a nice google spreadsheet with some prompting questions, you can get multiple people's input (and often consensus) before you actually talk.
Start with the Home page, but build with your simplest page (and responsive design rules) in mind. Since we are a mobile first/agile development shop, we build websites beginning with the most basic page layout first and then work toward the more complex elements. However, as a designer, since I am doing the opposite, and I need to be gathering "love it" and "hate it" information as I go. I present 2-3 different Home page layouts in the first round that show not only options in terms of page heirarchy, but also font choice, shape of boxes (ie. are there a lot of rectangular elements vs. rounded edges vs. circles), and size of content pieces. The more options you show now will help move the design phase along more quickly later.
New round = more detail...but be careful not to go too crazy. You do not want to lock youself or your design team into a corner that stifles their creativity later. Keep your wireframes lite and agile. In some of the early iterations I did of these more designed wireframes, I got too into using lots of shades of gray and no textures. Once I entered the design phase, I would find it really hard to invision different home page design options because I had made too many decisions already.
Note: As an agile design/development shop, we have the benefit of designing and building side-by-side so this system of wireframe creation is also much more effecient than if you need to take a more siloed approach where you are passing things off to someone else once they are complete.