<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>HTML.co.uk &#187; contract</title>
	<atom:link href="http://www.html.co.uk/tag/contract/feed" rel="self" type="application/rss+xml" />
	<link>http://www.html.co.uk</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 06 Jan 2010 12:45:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Creating a Design Brief along with the Design Contract</title>
		<link>http://www.html.co.uk/160/creating-a-design-brief-along-with-the-design-contract.html</link>
		<comments>http://www.html.co.uk/160/creating-a-design-brief-along-with-the-design-contract.html#comments</comments>
		<pubDate>Wed, 20 May 2009 17:05:42 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[General Website Information]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[design brief]]></category>
		<category><![CDATA[freelance]]></category>
		<category><![CDATA[guidelines]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[website building]]></category>

		<guid isPermaLink="false">http://www.html.co.uk/?p=160</guid>
		<description><![CDATA[A design brief is nothing but a written document that is used to describe all the features and scope of the project’s design. This documents is jointly developed by the client and the by the Web designer. ]]></description>
			<content:encoded><![CDATA[<p class="blogtext">A design brief is nothing but a written document that is used to describe all the features and scope of the project’s design. This documents is jointly developed by the client and the by the Web designer.   <span id="more-160"></span> </p>
<p class="blogtext"> This is not particularly intended to be to be the entire description of the actual designs. It just briefs the goals and objectives of the work that has to be done and they are also designed in such a way that it includes the terms and conditions of the work.   </p>
<p class="blogtext">What is the need of Design Brief?<br />
For any process of large designs, design briefs must be part of the work’s planning stage. They are pretty useful for both the client and for the designer as they provide the roadmap for the goals that has to be achieved.
 </p>
<p class="blogtext"> Where to start the building of this design brief?<br />
You as a Freelance Web designer, you will be the instigator for any design brief. While the project client will have the better idea on what he/she will require from their website just beyond making money or else to get more page views. So it is entirely upto the client on project planning and client interviews.
</p>
<p class="blogtext"> What should be mentioned in a design brief?<br />
Mostly, the design briefs has to include the objective and goals that has to be achieved and also the deadlines or contractual or billing issues. So you have to include some of the things such as:
</p>
<p class="blogtext">Site’s goals and objectives<br />
Site’s overview<br />
Entire description of the objectives and goals of the site<br />
If there is a redesign, you have to have the description of the objectives and goals of the project.
 </p>
<p class="blogtext">Site Audience<br />
The typical description of the audiences that they are trying to attract towards them<br />
Age<br />
Gender<br />
Employment<br />
Interests
 </p>
<p class="blogtext"> Where the site will be used?<br />
At home with slow connection or high connection<br />
In the office<br />
On PDA’s or on the cell phones<br />
On a CDROM<br />
Over a kiosk<br />
Scope of the project<br />
Type of technology that will be required for the project:<br />
Redesign or full site build<br />
HTML development<br />
Ajax development or JavaScript<br />
CSS development<br />
ColdFusion, PHP or ASP<br />
In which language the CGIs are written?<br />
Ecommerce storefront<br />
Flash<br />
Content type of both the designer and the client<br />
Text<br />
Graphics: logos, animation, icons, photos and illustrations<br />
Video<br />
Sound<br />
Localization of above mentioned<br />
Design aspects<br />
Creative design<br />
Conceptual design<br />
Typography<br />
Layout<br />
Colours
</p>
<p class="blogtext">Details of the contract<br />
 It has to include the project’s details and also include:<br />
Pricing: be specific or general for the need that will be required by the client and make sure the client understands for what he is paying for<br />
Schedule: include the dates of content due and approval dates. Also you have to include the deadline dates as well.<br />
Billing: the date for the invoices and also when the late fees will be assessed.<br />
Copyright: who will own the entire copyright of any design, content etc?
 </p>
<p class="blogtext">
]]></content:encoded>
			<wfw:commentRss>http://www.html.co.uk/160/creating-a-design-brief-along-with-the-design-contract.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Help for Writing a Great Web Design Contract</title>
		<link>http://www.html.co.uk/158/help-for-writing-a-great-web-design-contract.html</link>
		<comments>http://www.html.co.uk/158/help-for-writing-a-great-web-design-contract.html#comments</comments>
		<pubDate>Sun, 17 May 2009 15:17:19 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[General Website Information]]></category>
		<category><![CDATA[advice]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[credit]]></category>
		<category><![CDATA[freelance]]></category>
		<category><![CDATA[layout]]></category>
		<category><![CDATA[payment]]></category>
		<category><![CDATA[plan]]></category>
		<category><![CDATA[project dates]]></category>
		<category><![CDATA[schedule]]></category>
		<category><![CDATA[wed design]]></category>

		<guid isPermaLink="false">http://www.html.co.uk/?p=158</guid>
		<description><![CDATA[Description of the work or scope of the work. Initially, most of the people think that they will know this automatically, but as go on with the work, you will come to know that most of the clients do not have any idea. Clients think that they know what they need but in reality, they do not have most of the clues.]]></description>
			<content:encoded><![CDATA[<p class="blogtext"><strong>Description of the work or scope of the work</strong><br />
Initially, most of the people think that they will know this automatically, but as go on with the work, you will come to know that most of the clients do not have any idea. Clients think that they know what they need but in reality, they do not have most of the clues. The idea is not to plan the entire course of the work, but to acknowledge that the time that you’re working on is very much valuable and the client have to meet the expenses of the plan that you will be drawing up. Whether or not you have to make your client agree to that and you have to draw up the work contract. The contract should include the scope of the work that you’re doing. The contract should include<br />
<span id="more-158"></span></p>
<p class="blogtext">Number of pages that has to be built<br />
Number of scripts or the CGIs or the programs that has to be built<br />
Number of graphics that has to be created<br />
Total amount of content that has to be written<br />
The margin of error that has occurred<br />
Make sure that the client agrees to the contract and then make the move towards the work that has to be done.</p>
<p class="blogtext"><strong>Project dates</strong><br />
A contract which is good includes dates. It will be pretty tempting to leave this upto the client and all of the clients will want the site to be fixed. Most of the clients will forget about the dates as they will get busy with other works. So you have to include the dates. Some of the dates that has to be included are<br />
Due date of the signed contract<br />
Starting date of the work<br />
Designs or the plans completed<br />
Approval of the designs and plans by the client<br />
Due dates of the client<br />
Designer milestone releases<br />
Dates of invoices<br />
Competition date of the site<br />
Due dates of the clients review<br />
Updates date<br />
Client’s final review<br />
Launching date</p>
<p class="blogtext"><strong>Payment</strong><br />
You should not only include the project’s cost but also how much have to be invoiced. You have to take some percent of the project cost as the deposit and will thus ensure that the client is pretty serious about the work and will definitely give you some amount of cash for the work to move ahead.</p>
<p class="blogtext"><strong>Revisions</strong><br />
Mostly, clients will always want to make some of the changes in the project. So if you include number of revisions in your contract, you will not be in the trouble of sticking in to the never ending work of revising the work.</p>
<p class="blogtext"><strong>Source files and copyright</strong><br />
The contract that you have done should include and mainly specify the entire copyright of the content, graphics, designs, programs and the multimedia and also you have to specify of who owns the rights of source files. The source files include<br />
Images<br />
Multimedia<br />
Scripts and programs<br />
Design of the website<br />
Content written for the site</p>
<p class="blogtext"><strong>Credits</strong><br />
Along with the files rights, you should also specify the on how you will be credited for that wok that you have done. So you have to mainly specify<br />
Where will be the credit displayed?<br />
How the credit will be done<br />
For what things you will be credited</p>
]]></content:encoded>
			<wfw:commentRss>http://www.html.co.uk/158/help-for-writing-a-great-web-design-contract.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a Design Brief for your Contract</title>
		<link>http://www.html.co.uk/153/create-a-design-brief-for-your-contract.html</link>
		<comments>http://www.html.co.uk/153/create-a-design-brief-for-your-contract.html#comments</comments>
		<pubDate>Sat, 25 Apr 2009 20:50:45 +0000</pubDate>
		<dc:creator>Editor</dc:creator>
				<category><![CDATA[General Website Information]]></category>
		<category><![CDATA[advice]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[design brief]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://www.html.co.uk/?p=153</guid>
		<description><![CDATA[What do you mean by design brief?]]></description>
			<content:encoded><![CDATA[<p class="blogtext">What do you mean by design brief?<span id="more-153"></span></p>
<p class="blogtext">This Design Brief is nothing but a document that is written to describe the features and scopes of a particular project. This Design Brief is jointly developed by both the web designer and the client.  </p>
<p class="blogtext">This design brief is not planned to be just a description of the genuine design. In words we can tell that the look and feel is not accurately defined in a particular Design Brief but instead a design brief will outline the objectives and goals of that website and also provides details on how they will be able to meet. Most of the Design Briefs are used in Conjunction along with a contract in order to define the terms of a web design profession. </p>
<p class="blogtext">Why to build a design brief?</p>
<p class="blogtext">This Design Briefs must be the part of that particular planning stage of any big design process. These Design brief are useful for both the client and designer because they provide a roadmap for both of theirs objectives and goals of their site. Designers will know on what to be focused on and also clients will know on what has to be achieved.</p>
<p class="blogtext">Where and when to start building a Design Brief</p>
<p class="blogtext">If you are a freelance web designer, now you will be the instigator of any Design Brief. It is also possible that even client will have lot better ideas of what he wants from their website beyond on “How to Make Money Online” or else &#8220;Get More Page Views” but most of the clients do not have so. So it is entirely up to the client’s interviews and also the project planning. So do the client interview in an efficient way. </p>
<p class="blogtext">What the matter should be there in a Design Brief?</p>
<p class="blogtext">All the Design briefs should contain information regarding on what is the project objectives and goals and as well as the deadlines and also the billing or else the contractual issues. </p>
<p class="blogtext">Some of the Site objectives and goals</p>
<p class="blogtext">Overview of the website as a total thing<br />
Descriptions of the objective and goal<br />
Explanation of the objectives and goals and of the project </p>
<p class="blogtext">Website’s audience<br />
An explanation of the typical members they are trying to draw.<br />
Gender<br />
Age<br />
Employment<br />
Interests<br />
Where should be the site particularly is used:<br />
At home over slow connection or high speed connection<br />
At an office<br />
On PDA’s or cell phones<br />
On a CDROM or over a kiosk </p>
<p class="blogtext">Scope of the project<br />
The technology required for the project:<br />
Redesign or full site build?<br />
Development of HTML<br />
Development of Ajax or JavaScript<br />
Development of CSS<br />
ColdFusion, ASP, PHP or any other server related technology<br />
Flash<br />
Ecommerce storefront<br />
Content of both the clients and the designer<br />
Text</p>
]]></content:encoded>
			<wfw:commentRss>http://www.html.co.uk/153/create-a-design-brief-for-your-contract.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

