Start planning

With the informations gathered in the first phase (requirements phase), it’s time to create a structured plan of your project. We define the components of the product, the relations between them, workflows, navigational system, homepage structure and content pages.

This is a stage where the end-user (your potential customer) experience is taking into account and web design and web development process meets for the first time.

Creating technical specifications for the project, requires a breakdown of it's objectives and a definition process for existing requirements and restrictions.

describe in detail what information will be provided in the pages of the website and how they will be presented. For example, if one of the objectives of a website is "providing link references on a specific topic", then, these technical specifications should specify: which are these references, which are URL addresses, how many such addresses will be included in a page, and so on.

A technical specification must identify all the resources required to achieve the objectives: links, graphics files, audio or video files and other items that needs to be included: forms, image maps, scripts. Also, the specifications should specify, also, the items that will not be included in the page (if any). For example, you can specify not to use some HTML extensions, or forms, files that exceed a certain size.

At a glance, a quality website that provides valuable information in an attractive way and communicates coherently the 'subject' exposed, is not achieved by chance. Without an detailed overview of the issues set out in the planning phase, the chances of achieving a good quality web site are minimal.
If we start the web design and web development process directly, without going through the planning stage, what we can get together is just a pile of pages without coherence, often poorly connected with an unclear and poorly structured content.