Information Architecture [IA] and the Global Site Map
Before you start pushing pixels you have to have a plan for your all your content, a map of how information is arranged and flows, in comes the site map or content map to the rescue. This allows us to logically organize and access all our information before we spend long hours designing and then coding our site. There’s nothing worse than spending hours getting a mockup just right and then realizing that you forgot an element, ugh! Omit this step at your own risk.
READING | Interact with Web Standars
- Chapter 6
IA DELIVERABLES
- Primary audience goals
- User type(s) or Persona(s)
- Content innovatory
- Competitive analysis
- Content strategy statement
- Content outline
- Content gap analysis
- Site map or diagram
- Page description
- Wireframes
WHAT IA IS NOT
- Project management
- Copywriting
- Usability testing
- Visual design
- Web Development
- Quality testing
QUESTIONS TO ANSWER
- What is the full URL path?
- What content will be displayed on each page, make a list.
- What content types will be displayed on each page?
- How is this page relevant in relation to other pages, think hierarchy
DOWNLOADS
2010 Newhouse Military complete project package | ZIP
RESOURCES
Information Architecture 101: Techniques and Best Practices | Link
Multi-level Site Map Example | Link
Phases of Website Creation
1) Client List of goals (e.g. target audience, user profiles, mission statement)
2) Developers take the list of goals and writes up a creative brief
3) Client/Designer develops a site map and wireframes
4) Client/Designer writes up style guide – a breakdown of the design elements in a specific way (color, fonts, etc). This will be used as reference to provide consistency.
5) Client/Designer writes the UI descriptive document – describes how each page element actually works, the functionality. This is another layer of planning to reduce ambiguity.
6) Client/Designer creates mockups for each page, in great detail, down to the padding and margins
7) Actual programming takes place
Developer/internal tests the site – make sure all the functionality works
9) Developer/Client review – back and forth sharing period to find any mistakes
10) Publish with a soft launch – “Alpha” Phase – within a non-public URL environment
11) Beta Phase – Final bug fixes.
12) Final launch
