Implementation Checklist
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • : Function ereg() is deprecated in /home/bfactory/public_html/includes/file.inc on line 644.
  • warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in /home/bfactory/public_html/themes/bwf/node-flexinode-8.tpl.php on line 147.
How to ensure your design turns into reality…

You should set realistic deadlines to collect and write your content and photographs. Use direct response style copy writing to make your content attractive, interesting and have an objective or reason for writing it. This will normally to either inform or persuade your visitor to take action in some form or other.

Use all your design information to create handover packs for your graphic designer and your developers. It is essential that you format the information in a clear and unambiguous manner.

When you have the graphic design, you can now begin to develop your website.

1) Collect content (text and images) with realistic deadlines

Set implementation phases if all the content cannot be collected at once.

2) Take steps to start collecting content using Direct Response Style

Make sure all your content follows a consistent pattern such as that below:

  • Page title
  • Headline (article header or first paragraph)
  • Body (promise, benefits, consequences)
  • Summary
  • Proof (case studies, photographs, testimonials)
  • Call to action

3) Create a design handover pack for the graphic designer

This will contain your wireframe layout design for each page style, the menus, the colours and some example content.

4) Review and snag the graphic design from your designer and make sure you are completely happy with it

5) Create a style guide document with the help of your graphic designer

This will include fonts, font sizes, colours, indentation rules, column widths, menu styling etc.

6) Create a design handover pack for the web developer

This will contain the graphic design template, the style guide, and the content including text and images.

7) Generate a snag list using your design documents as a measure of quality control

The last 5% of effort that goes into designing and developing a website will be the most important in terms of overall quality, functionality and aesthetics. If you don’t perform full QC (quality control) testing on your website, you will end up with a poor quality end product.

Use your design documents as a means to measure the state of the developed site. For this reason, it is essential that you handle inevitable development issues in such a way that any design decisions are made by you and not the developers, and are documented.

If your design proves to be difficult to follow or appears to have missing information, the last thing you want is someone to interpret your requirements and produce something completely different.

Summary
Ensure your design is clear and unambiguous before handing it to the developers. During development, always keep on top of any design changes and keep the documentation up to date. The quality of the final result will be down to the design and how well you control any variations from the design.
Further Info
Register for the FREE '7 Week Blueprint to Success' email course:
Name:
Email: