Interactive Media Design Industry Practice

Industry Practice 1

Analysis

When given a Commissioned job you need to analyse what is needed from you by following these steps:

1. Objectives and Goals – The first thing you need to find out is what your client wants from their new design. Is this a redesign or reworking of an existing site, or is it a completely new design? Do they already have solid ideas for what they want their site to do or are their ideas more vague?

2. Budget and Schedule – Budget can be a touchy subject for some clients. A lot of clients feel like if they share their budget with you before you give them a quote, you’ll overcharge them or charge them the maximum amount for the least amount of money.

3. Target Audience – Whom are your clients trying to reach? A website designed for teenagers is going to look and work a bit differently than one designed for corporate decision-makers. Ask your client who they want to appeal to with their website right from the beginning.

4. Project Scope – Not every project is as in-depth as every other. Some clients want a completely custom solution. Others just want you to adapt an existing template or other design. Some clients want an entire commerce site with a shopping cart, while others just want a bar

5. Available Materials – Does your client already have a logo, brochure, product photos, or other materials that would be useful to your design?

6. Overall Style – Getting a sense of what your client wants in terms of style is vital. They may have a grunge design in mind when you’re picturing something clean and modern (or vice versa). Most clients have very distinct likes and dislikes. But they’re not always good at expressing what their tastes are.

7. Definite “Do Not’s” – At least as telling as what a client likes and wants is what they definitely do not want. Some clients hate certain features. Some clients don’t want an ecommerce site, or a three-column layout, or a slideshow. Getting an idea of what your client doesn’t want can save you from wasting time designing features your clients will then reject.

(Text from http://www.webdesignerdepot.com/2011/03/7-basics-to-create-a-good-design-brief/)

Client communication

Communicating effectively with your clients is key to the success of your projects and the structure of your freelance business. The process of communication begins before the client even agrees to have you work on their project, and it should remain as a constant throughout your entire relationship. When a client expresses their needs and wants, you should convey concern, attentiveness, and assurance. You will need to understand that there are clients with whom you can minimize communication as their not interested in updates every single hour of the day, while others want you to hold their hands throughout the entire design process. Know which clients deserve what amount of attention and degree of communication.

Save the sales pitch for a different niche like automobile sales. Your clients will more than likely help you equip yourself with the right tools to “sell” them, if you listen. A client’s project has everything to do with what they need, what they represent, what type of customers they’re trying to reach, and less about you. For this reason, it is very important that you listen carefully to the details they provide. This will help you do your best, not your average on the job. While you’re listening or reading what your client’s saying, make sure you have something in hand that will allow you to take notes. That way you can regurgitate your clients needs in your own words for better understanding.

If you’re working with various clients at a time, then you know how difficult it can be to keep mental records of every word, document, and suggestions sent by a client. This is why it is important to fuel effective communication by having some sort of system in place. Developing your own system for keeping track of communication isn’t the most difficult of tasks. It can be as easy as having a separate folder on your desktop for every client containing all of his or her emails, notes, and suggestions.

A large majority of clients you’ll come across have very little knowledge of the various elements it takes to design a website. Most of them know what they want, they just don’t know how to turn it into a successful website or illustration. Apart from the chatty clients, there will be times that you’ll find yourself working with one that doesn’t have much to say or suggest. This is where you get them involved. Try to give them a summarized idea of what you need from them in order to produce the best possible work. You can devise a quick list of what’s expected of them and send it over. That way they can feed you the correct information all at once, rather then you having to call them a hundred times to figure out what they want. This is where collaboration meets communication.

If you decide to go ahead and give your input, make sure you can explain why you’re giving that advice. Many times a client will want you to add or make changes to things that you don’t think will be effective for the scope of the project at hand. This is where it’s important to demonstrate to them why it is they should take into consideration your advice. Always remember to cover your bases. This is far more effective then designing your own concept only to find out it has been rejected.

Using good examples compliments effective communication. Sometimes explaining a concept or suggestion just doesn’t cut it through email or on the phone. When this happens clients will appreciate you much more if you can provide real examples. Consequently, you’ll end up clearing up a lot of confusion and misunderstanding. For example, if you wish to nest specific elements in various locations throughout the layout, it would be an ideal choice for you to send them a wireframe of how you plan on structuring the site.

(Text from http://webdesignledger.com/tips/tips-for-effective-communication-with-your-clients)

Creative thinking skills

Idea generation starts with the problem list from the planning phase. This is the anchor for creative thinking because it provides clear targets for designers and engineers to shoot for. The best marksmen in the world will not do very well without a clearly labelled bull’s-eye to shoot at. To make your targets clear, print out the list of user problems you’re trying to solve. Post it in the hallway for the entire team to see. Scotch tape a copy next to your monitor. Make it so everyone that is expected to contribute will have intimate knowledge of the project goals, from your executives to your entire engineering team. Never hide your goals. You want as much support for them as you can get throughout your organization. Strive to make the design or user experience goals align well with the overall business and project goals (or vice versa).

Creativity is elusive. It’s hard for people to be creative because they are told to. The more pressure you put on people to be creative, the less creative they become. Some people are naturally creative when under pressure, while others work best through introspection, and time left alone in their office. As a project manager or designer, you have to find the right way to build in support for creativity. That starts with understanding the people on your team, or if you’re working alone, understanding yourself. When are they most creative? What inspires their best work? What kind of environment do they work best in?

Brainstorming meetings are a common exercise for generating ideas, but few know how to organize and run them well. Often personalities don’t mix in the right way for these kinds of meetings to be effective. Some people are just not open enough in-group settings to listen to new ideas, or to share their potentially embarrassing ideas with others. These sessions tend to work best when there is an experienced leader or organizer, who knows how to facilitate a session. Someone has to be responsible for keeping the meeting focused, but open enough that many ideas are presented and discussed. Brainstorming is most effective with small groups. This improves the comfort level of participants, since with fewer people in the room; there is much less personal risk. People are more comfortable making jokes or taking chances, and the interaction becomes more intimate. Thinking can progress at a faster rate because people know each other better, and can communicate more effectively.

One definition for creativity is the diligent exploration of interesting alternatives. By investing energy into trying out different possible approaches, you improve your understanding of the problem, and get closer to a reasonable solution. People that are considered creative are almost always the ones who can consider the widest range of different ideas, and who have the courage to try many of them out. Like Picasso with painting, you never know when you’ll have your moments of brilliance, but the more time you spend working with designs and creating alternatives, the better the odds that it will come through in your work. The ability to generate alternatives comes from intuition, but is amplified by experience. The more website navigation models you have studied, the wider the range of ideas you can pull from when designing a specific navigation system from scratch. The more usability studies you’ve watched, the better your sense for matching different kinds of designs with different kinds of users. Like any craft, you learn by doing, observing the results, and trying again. With a design of any complexity, there are so many subtleties that have to be considered that you cannot easily predict the value of an approach until you try it out. This is why sketches and rough mock-ups are essential to any form of design. Combined with usability engineering techniques, a designer can get information on the value of an approach with a fairly small time investment.

The greatest asset during idea generation, besides the ideas themselves, is time. Since production code is not being written, the only thing you have the potential to waste is your schedule. The time in a project for idea generation should be scheduled and tracked. A rule of thumb is to divide the time planned for idea generation into thirds: 1/3 for open idea generation, 1/3rd for narrowing down to 3 to 5 approaches, and 1/3rd for drilling down into the one or two best approaches. So if you have 3 weeks for this phase, each third would be a weeklong. The range of ideas explored should feel like a funnel, starting off wide, and narrowing as you go along. By the 2/3rd mark, you should have sketches or prototypes of at least 3 to 5 different designs. The rest of the time should be dedicated to exploring the best approaches in the usability lab, getting feedback from key people in your organization, and preparing to make a recommendation and presentation if necessary.

He work culture you are working in, there are many different ways to structure your time and divide the labour. Software and web engineering practices vary widely from organization to organization, and it follows that the approaches used for planning and integrating design vary as well. In all cases, everyone should be clear on the answers to the following questions. Any reasonable design process has clear answers to them, and any reasonably good design team should have complete awareness of the answers.

It’s the role of the project leader, or design process owner, to define and communicate the answers to these questions:

  • What are our business / project / strategic goals?
  • What user problems are we trying to solve? (How do these fit with the business / strategic goals?)
  • How much time do we have? How will we divide that time into planning, idea generation, development, and testing?
  • What is the output of the idea generation phase? Pictures? Prototype? Specifications?
  • How many usability studies will we have time for during idea generation? After?
  • During development, how much room do we have to make tweaks and adjustments? How final does the specification need to be?
  • How will we communicate our designs to engineering? When wills this happen?
  • How are design decisions made? Who needs to be involved?
  • Who manages the schedule? Design? Engineering? Business? Project manager?
  • Will there be a design review meeting? Who makes final decisions?

(Text from http://scottberkun.com/essays/15-critical-thinking-in-web-and-interface-design-part-2/)

Creative problem solving tools

Creative Problem Solving is a proven method for approaching a problem or a challenge in an imaginative and innovative way. It’s a tool that helps people re-define the problems they face, come up with breakthrough ideas and then take action on these new ideas. It’s broken down into 3 stages:

  • Explore the challenge
  • Generate Ideas
  • Prepare for action

cps_process

Explore the Challenge consists of 3 points which need to be looked at. These are Objective finding, Fact-finding and problem finding. Objective finding can be a wish or a goal. Fact-finding is the review of all the data the persists in the situation at hand and Problem finding explores the facts and data to find all the problems and challenges inherent in the situation, and all the opportunities they represent.

Generate Ideas is where you explore ideas that are possible solutions and have the most fun. It’s also where you need to stretch to make connections, take risks, and try new combinations to find potentially innovative solutions.

Prepare for action consists of 2 sections, which are Solution finding and Acceptance finding. First, try to strengthen and improve the best ideas generated. Next, generate the criteria that need to be considered to evaluate the ideas for success. Apply that criteria to the top ideas and decide which are most likely to solve the redefined problem. The best idea needs to meet criteria that make it actionable before it becomes the solution. Look at who’s responsible, what has to be done by when, and what resources are available in order to realize this idea as a full-fledged, activated solution.

(Text From http://www.creativeeducationfoundation.org/our-process/what-is-cps)

Planning Techniques

So many articles explain how to design interfaces, design graphics and deal with clients. But one step in the Web development process is often skipped over or forgotten altogether: content planning. Sometimes called information architecture, or IA planning, this step doesn’t find a home easily in many people’s workflow. But rushing on to programming and pushing pixels makes for content that looks shoehorned rather than fully integrated and will only require late-game revisions.

(Text from http://www.smashingmagazine.com/2010/03/17/starting-out-organized-website-content-planning-the-right-way/)

Layout

For a website that will require a lot of content, the design will have to be specifically designed around that content. It will need to be a part of the design phase. In other web designs, filler content is sufficient while the client is getting content put together, and this is because many content areas in a design can be flexible in text length. However, with a content-heavy design, with so many content pieces on a page, it can be incredibly helpful to know how long blurbs, introductions, or other pieces of static content are. Also, if there were variables pieces of content, it would be helpful to know the average size of those pieces.

It’s nice to break the grid every once in awhile, or allow variation within a grid system. This is what can make web design fun and interesting. With content-heavy web design, though, there’s not a lot of room for variety. With possibly a few minor exceptions to your creativity, for content-heavy design, use a grid, and keep to it. Organize margins and padding in detail within the design process, and plan ahead of time for the size of each content area.

From a purely aesthetic design perspective, content-heavy design takes a different route in this way as well. Organizing a webpage through hierarchy, rhythm, and order, and defining functional design is a major part, as it is heavily stressed throughout this article and many more like it. Colour and shape, though, have a lot to do with it too. While many aesthetic design choices are best for content-heavy design, many are also good for the functional part of the design too. In a way, they complement each other.

There is a mix between serif and sans serif fonts, font colour, size, and style. A completely unique font is used for the main headlines. While typography can bring interest to a design, especially one with primarily text only, it can also serve an essential purpose in hierarchy, repetition, and design organization. Where will the reader look next? If all the type of the page were much the same, it would be difficult to know. However, with intelligently designed headlines, we do know where to look. With so much type on the page, it can easily become difficult to read and focus on one piece of content. Smart typography will embrace vertical rhythm, correctly planned content widths, and adequate whitespace for easily legibility of one piece of content in a sea of text.

(Text from http://www.onextrapixel.com/2011/02/23/planning-for-a-content-heavy-web-design/)

Information architecture

There is no one right way to plan the architecture for a website. Depending on the size of the website, you might use all of these techniques. They’re not opposed or mutually exclusive—just different means to similar ends.

When picking your method of architecture planning, consider these things:

  • How big is the website?
    The sheer size of some websites makes some of these methods cumbersome or impossible.
  • What type of website is it?
    The card-sorting method, for example, is perfect for e-commerce websites but overkill for blogs.
  • Who is your client?
    The less Web-savvy the client, the more elaborate your descriptions and plans will have to be. If your client understands websites, then you can be a bit more brief (but not too brief!).
  • Consider your workflow.
    Try out all of the ideas, and then pick a lightweight, simple process that you and your clients can understand. If you find yourself filling in information that isn’t useful or illustrative, then you’ve gone off track. Adopting a process that allows you to do the bare minimum is good in this case.

A few tips on architecture planning:

  • Organize content according to user needs, not an organizational chart or how the client structures their company.
  • Give pages clear and succinct names.
  • Be sympathetic. Think of your typical users, called personas, and imagine them navigating the website. What would they be looking for?
  • Consider creating auxiliary way-finding pages. These pages would lie beyond the main navigation of your website and structure various pages according to specific user needs.
  • If you can’t succinctly explain why a page would be useful to someone, omit it.
  • Plan the architecture around the content. Don’t write content to fit the architecture.
  • When dealing with clients, especially clients at large companies with many departments, keeping egos in check can be tough. Keep everyone on point with constant reminders of the true goals of the website.
  • Not everything has to be a page. Use your hierarchy of content as a guide. Some items might work better as an FAQ entry or as sidebar content. Make sure your architecture-planning method does not blind you to this.

(Text From http://www.smashingmagazine.com/2010/03/17/starting-out-organized-website-content-planning-the-right-way/)

Workflow

We know that a great website relies on all parts working in harmony. To achieve this, you have to start on the right foot at the beginning of the project. You need an organizational system that does the following things:

  • Allows you to organize deliverables from various media;
  • Lets you rapidly make changes when needed (it’s called planning for a reason: things change!)
  • Helps you collaborate with all stakeholders;
  • Shows how the project is developing and what’s left to do;
  • Ideally launches you into the actual design and building phase.

(Text From http://www.smashingmagazine.com/2010/03/17/starting-out-organized-website-content-planning-the-right-way/)

As designers we don’t commonly think in terms of structure. Unfortunately this can cause problems in design projects both personal and freelance as organizational issues rise up and bubble through our artwork.

Fortunately there are some changes you can make to your routine that can help to straighten out project work. Granted the setup may be different based on differing operating systems and per-project conditions, but the core ideas will help you implement a much better organizational scheme during your work.

documentation-folder

The first major step is to organize and split up your core files. We can use a freelance web design project as an example here and list out what we’d be working with. To start there will be PSD/AI files for graphics, links and resources for inspiration and also the HTML/CSS/JS files.

documentation-file

Another useful item here would be a .txt file containing any and all useful information. I use this as a type of documentation and could be even more advanced if necessary (Word or Excel Spreadsheet). I will include links to websites with similar designs or elements I want to work with in my site, or just future notes to myself on the project. This saves time during the development process since I don’t need to write all the code from scratch. These are just a few ideas to get you started but documentation really has no limits – it’s solely in place as a resource for you, the designer.

(Text from http://speckyboy.com/2010/09/28/professional-structure-and-documentation-in-web-design/)

Deadlines

Having a website designed and developed is a two way process. Even for the most basic website, the client needs to put in as much work and effort as the agency who puts it all together and makes it work. At least they need to if they want to get what they expect from their website. A website is not a product you can just buy off the shelf. Once this concept is understood, both clients and companies can work together to deliver. And so we can conclude that at the heart of making this process work well is communication.

From a web design agency’s perspective, managing multiple projects and a large team can be tricky. Be sure not to take on more work than you can handle. It’s always best to let new clients know you’re busy and have to start their project a bit later – they are more likely to appreciate the fact you are able to manage your workload and it looks good to say that you are busy so chances are they will be happy to wait so that they can work with you.

  • Create a detailed specification of project and speak to the lead designer and lead developer to find out accurate timeframes for the work, considering other projects. Be clear and give estimate dates, explain the reasoning.
  • Split the project into phases and ask the client for feedback at each phase to ensure you are on the right path, listen to what they want and what their expectations are, some clients will trust your advice and decisions more than others.
  • During the project, make sure you show the client the work you have done and report on progress – if the scope changes at all; notify them of the effect on the estimated deadline and costs. 
  • Don’t make excuses – explain exactly when you will be working on the project, what you have achieved during the time, where the problems are and how long they may take to resolve. Be honest and open, even when you are late or delayed.
  • Surprise your client and deliver earlier (by giving yourself extra days on the deadline).

As a client, the first step is ensuring you select a company who can communicate well with you and who has an understanding of what you want from your website. Stay away if a company is not asking you questions, has not provided you with a specification or scope of work showing exactly what they are going to deliver. This includes information about the number of pages, what will be on each page, how the back end (content management system) will work and what you will be able to do on it.

  • Don’t expect an exact launch date from the day the work on your website starts. It’s difficult to predict how long work will take, but make sure you’re given estimation for work and a timeframes on different phases (e.g. for branding and home page design, further page designs, development work, testing).
  • Be prepared to get involved – you will need to provide feedback on designs, and provide content and images as appropriate. If you decide you want something to be changed or added from what was originally discussed, talk to the company and assess the impact this will have on the cost and timescale of the project.
  • Respect the fact that it’s difficult for you to know how long different parts of your project will take. One simple change may look very easy to change, but actually when it comes to the coding of it it’s pretty complicated and may takes hours rather than 5 minutes.
  • Give feedback at each stage. A conversation with your company may be the best form of communication at this stage to ensure they understand you and you understand them.

(Text from http://www.whichwebdesigncompany.com/blog/?p=211)

Management tools

Many Web design companies start out offering their services left and right and everything is pretty much handled via email. It’s a direct and cheap way of keeping our clients in the loop regarding their project status. Quickly though, clients will ask for changes, revisions, clients get lost and don’t answer and retake the issue weeks later. In the meantime, you may have accidentally deleted the email of things you had pending and you have no way of recovering the info that client deemed as “utmost importance” or probably, months after finishing the Web design project the client asks you how many visitors has the site made since launching the Website and you have to put a monkey face and explain to the client pretty much that you forgot to install Google Analytics or some site statistic software.

A project management tool is the glue that a bonds task, deadlines, files, reminders, and discussions, all in one. Email isn’t designed to do this though it can. An email is just a tool to communicate between two or more individuals, but never to organize a project. You can certainly do this, but this requires manual labour on your behalf, like filtering emails, setting reminders on them, sorting out files on a folder and setting deadlines on each task you create manually via your email client (if it supports it).

(Text from http://www.webmentor.cr/en/project-management-tool-for-web-design-projects/)

Here are 3 examples from Vibe themes blog.

1. Asana: It is a Free Web based Project Management, Bug Tracking and Task Management app. It is free unto a team of 30 members and is compatible on smart phones. The best feature of this app is that its lighting fast and is bundled with keyboard shortcuts. The modern look and feel, clubbed with useful features as labelling, commenting, setting up goals, milestones, releases, creating sprints, backlog, converting features into tasks with deadlines, follow projects and maintaining notes make it one of my personal choice for project management. It is an app made for small designers to big companies. Click here to see Demo Video for Asana project management.

2. Cohuman: Cohuman is more of a task management and collaborative tool rather a complete project management system. This web app focuses on group projects where people can get connected and start working on tasks under projects. The main advantage with this tool is that it creates a priority score for tasks that allow the system to automatically re-prioritize tasks. This way you only have to focus on your limited set of work. Cohuman is powerfully integrated with Google docs/apps and easy task creation just by sending mail. It supports mobile phones as well, so for collaborative projects this tool is definitely in the list. It is an app for Designers and group of collaborative designers. Click here to see more about Cohuman Management tool.

3. Trello: Trello is again more of a tracking tool which can track who is doing what? Rather than a complete project management. Though on the brighter side, it is a tool which you can use for everything including organizing events, sales and client management, bug tracking and just about everything which requires a collaborative effort. The USP of this is that it deals in tasks as cards, where in each card is a new task. With this approach it becomes very easy to monitor who is doing what and how much % work is remaining. It also has some cool features as commenting, voting, labelling, check listing and notifications. It is a powerful, yet simple tool and if have a small team then it is a great tool to start with. Click here to learn more about Trello.

(Text from http://www.vibethemes.com/best-free-project-management-tools-for-web-developers-in-2012/)

Documentation skills

Documenting your work can be useful for communicating ideas to a client while in process and is essential to build a portfolio for your business.

Purpose

Whether you are having a site built by scratch or doing a redesign of your existing site, it is really important to examine the reasons you have a website at all. Sound obvious? It isn’t. If you look at your own favourite sites, you will find that they serve many different purposes. For a graphics team like Ratio7 to build you exactly what you want and need for your business’s website, you need to explore the various types of sites and determine which one suits your business goals. A site may have several purposes at once.

  • Informational – This is a site that tells a potential customer or visitor what your business is, where it’s located, its hours, how to contact you and maybe a bit more. These sites are fast and easy to construct and usually only involve a page or two.
  • Educates – a site like Wikipedia or Grammar Girl with information on everything or just on grammar and writing. Or it could be a health site with information on conditions or illnesses.
  • Inspirational – They provide you with stories and photography and music on various topics like personal development, spirituality, psychology and new age practices.

There are more Purposes to build or create a website to what you wish to use it for. You can find more information at Ratio7.

(Text from http://www.ratio7.com/blog/whats-your-websites-purpose/)

Content

Content is one of the most important parts of design and development as it is what will attract people to your website. Content can be in a huge range of formats, from text, animation, move and games. Below are a few examples:

  • Instagram – It’s a fast, beautiful and fun way to share your photos with friends and family. Snap a picture, choose a filter to transform its look and feel, and then post to Instagram. Share to Facebook, Twitter, and Tumblr too – it’s as easy as pie. It’s photo sharing, reinvented.
  • Twitterfeed – Feeds the last posts published in a blog via the RSS feed to Twitter, Facebook, and LinkedIn.
  • Vimeo – Vimeo makes it easy to upload the videos you take. We adore many different kinds of file formats and give you great tools so you can make sure your videos look amazing. We even support HD!
  • Timeline – “Beautifully crafted timelines that are easy, and intuitive to use.” Timeline is also great for pulling in media from different sources. It has built in support for pulling in Tweets and media from Twitter, YouTube, Flicker, Vimeo, Google Maps and SoundCloud. 

(Text from http://mikepetroff.com/2012/05/10/huge-list-100-of-web-social-media-and-content-tools/)

Script

A script is a small bit of code that enables web browsers to do something rather than just displaying static results. Scripts are used in web design to create dynamic pages and DHTML. The most commonly used scripting language in web design is JavaScript, but many developers also write scripts in ActiveX.

(Text from http://webdesign.about.com/od/dhtmlglossary/g/script-definition.htm)

Technical Language

In the web design industry, you will encounter some language that is specialised for web design and development. For illustration of this, below is a short list of a few of those technical words:

ASP – Abbreviation for “Active Server Pages”. ASP is a server-side scripting language. ASP commands are embedded within HTML documents (with .asp extension) to provide dynamic content. ASP is often supported by web hosts using a NT server.

CGI – Abbreviation for “Common Gateway Interface”. This is an interface standard which provides a method of executing a server-side program (script) from a web site to generate a web page with dynamic content. Scripts conforming to this standard may be written in any programming language that produces an executable file, but are most often written in Perl, Python, C, C++, or TCL.

SSL – Abbreviation for Secure Sockets Layer. SSL is a transaction security standard that provides data encryption, server authentication, and message integrity. SSL is usually used on sites that accept credit card numbers or other private information.

You can find more at http://www.greenwebdesign.com/Glossary-Of-Technical-Terms.htm.

Reference
http://www.webdesignerdepot.com/2011/03/7-basics-to-create-a-good-design-brief/ (Accessed April 2013)
http://webdesignledger.com/tips/tips-for-effective-communication-with-your-clients (Accessed April 2013)
http://scottberkun.com/essays/15-critical-thinking-in-web-and-interface-design-part-2/ (Accessed April 2013)
http://www.creativeeducationfoundation.org/our-process/what-is-cps (Accessed April 2013
http://www.smashingmagazine.com/2010/03/17/starting-out-organized-website-content-planning-the-right-way/ (Accessed April 2013)
http://www.onextrapixel.com/2011/02/23/planning-for-a-content-heavy-web-design/ (Accessed April 2013)
http://www.smashingmagazine.com/2010/03/17/starting-out-organized-website-content-planning-the-right-way/ (Accessed April 2013)
http://www.whichwebdesigncompany.com/blog/?p=211 (Accessed April 2013)
http://www.webmentor.cr/en/project-management-tool-for-web-design-projects/ (Accessed April 2013)
http://www.vibethemes.com/best-free-project-management-tools-for-web-developers-in-2012/ (Accessed April 2013)
 http://speckyboy.com/2010/09/28/professional-structure-and-documentation-in-web-design/ (Accessed May 2013)
 http://www.ratio7.com/blog/whats-your-websites-purpose/ (Accessed May 2013)
 http://mikepetroff.com/2012/05/10/huge-list-100-of-web-social-media-and-content-tools/ (Accessed May 2013)
http://webdesign.about.com/od/dhtmlglossary/g/script-definition.htm (Accessed May 2013) 
http://www.greenwebdesign.com/Glossary-Of-Technical-Terms.htm (Accessed May 2013)
 
 
 

Leave a comment