<?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"
	>

<channel>
	<title>CK Web Development</title>
	<atom:link href="http://www.ckwebdev.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ckwebdev.com</link>
	<description>Web Solutions provider based in Portland, Oregon</description>
	<pubDate>Thu, 04 Dec 2008 21:21:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>Website Development Process</title>
		<link>http://www.ckwebdev.com/2008/12/website-development-process/</link>
		<comments>http://www.ckwebdev.com/2008/12/website-development-process/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 21:15:30 +0000</pubDate>
		<dc:creator>Christie</dc:creator>
		
		<category><![CDATA[Article]]></category>

		<category><![CDATA[web development]]></category>

		<guid isPermaLink="false">http://www.ckwebdev.com/?p=43</guid>
		<description><![CDATA[The following article is for non-techies who want to know what to expect during the development of their website. (This article draws a bit on the ideas presented in this here. Many thanks to the author.)
The website development process includes six steps:

Gathering Information
Planning
Design
Development
Delivery and Testing
Maintenance

Each step is outlined below.
Step 1: Gathering Information
The first step in [...]]]></description>
			<content:encoded><![CDATA[<p><em>The following article is for non-techies who want to know what to expect during the development of their website. (This article draws a bit on the ideas presented in this <a href="http://www.idesignstudios.com/blog/web-design/phases-web-design-development-process/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.idesignstudios.com');" target="_blank">here</a>. Many thanks to the author.)</em></p>
<p>The website development process includes six steps:</p>
<ol>
<li>Gathering Information</li>
<li>Planning</li>
<li>Design</li>
<li>Development</li>
<li>Delivery and Testing</li>
<li>Maintenance</li>
</ol>
<p>Each step is outlined below.</p>
<h3>Step 1: Gathering Information</h3>
<p>The first step in the web site development process is to gather information about the operation of your business and specific needs for a website (or website improvement).<br />
The following should be discussed before any work is started: objective, specific goals, target audience, content, budget, and technical constraints.</p>
<h4>Objective</h4>
<p>What is the purpose of the site? Are you disseminating information? Selling a product? Creating community? Providing a service?</p>
<h4>Specific Goals</h4>
<p>What are the specific goals of the site? The general goal of most sites is to either generate revenue or disseminate information. While it’s important to start with a general set of goals, it’s also important to set specific ones along the they way. For example, one goal for a site could be to increase member signups by 20% in the first year. Or increase donations by 50%. Or have 20,000 unique visitors in the first year.</p>
<h4>Target Audience</h4>
<p>Who is the ideal audience for your site? The answer to this question greatly affects design and development decisions for your site, so it’s important to be as specific as possible. Come up with as many demographic details possible. Sometimes your website will cater to more than one target audience.</p>
<h4>Content</h4>
<p>What type of content will your audience be looking for on your site? And in what form? Text, pdf, audio, video, podcasts are all valid options. How often will they expect new content? Who will generate this content?</p>
<h4>Budget</h4>
<p>What is the realistic budget for your website? It’s important to begin your project with a frank evaluation of available budget. Often there are solutions to fit nearly every reasonable budget. The budget should make allowance for: initial design and development, monthly hosting costs, on-going maintenance, and future development.</p>
<h4>Technical Constraints</h4>
<p>Are there any existing technical constraints with which your website will need to function? Perhaps you have an existing database from which your website will need to get information. Or, you are setting up an eCommerce site and you have a merchant account and shipping account that you need the site to utilize.</p>
<h4>Step 2: Planning</h4>
<p>The second step in the web development process is to take all the information gathered in Step 1 and plan your site. Planning your site includes three steps: determining requirements, writing a site plan, and choosing technology.</p>
<h4>Determine Requirements</h4>
<p>Your website requirements are the needs of your website translated into specific functionality. And, as such, your requirements become a set of tasks for your website developer. Some example requirements are:</p>
<ul>
<li> ability for a non-technical person to add, update and delete site content.</li>
<li> content on site must be categorized into four different sections.</li>
<li> site must have members-only area that is password-protected.</li>
<li> ability for a non-technical person to approve member requests and update member information.</li>
<li> site must by able to process payments using my PayPal account.</li>
</ul>
<p>Your requirements list can be as short or as long as you deem necessary, but should be as complete as possible. Think of your requirements as the checklist that you’ll use when checking your final website to ensure that everything has been completed.</p>
<h4>Write a Site Map</h4>
<p>Your site map is the org chart of your website’s content. It should include the names of all main and any subcategories, as well as a short description of the specific content belonging to each category.</p>
<p>This document is essential to the development of your site’s structure and navigation and should be included in your requirements list.</p>
<h4>Choose Your Technology</h4>
<p>After your requirements have been outlined and your site map developed, you will then be able to work with your developer to choose the technology for your website. This includes, but is not limited to choosing your: hosting plan, web server software, database software and programming language.</p>
<h3>Step 3: Design</h3>
<p>It is during this step that the look and feel of your website is developed. The target audience is a key factor when designing your site. During this phase, any existing graphic elements such as logo and color scheme are incorporated into the design of the site.</p>
<h4>Initial Comps</h4>
<p>A designer will typically create a set of mockups, which will then be presented to you in the form of jpeg or png files that you can easily view on your computer or through a web browser. Usually mockups include at least the homepage for your site and possibly a sub page or two.</p>
<p>You will then pick your favorite, provide specific feedback and the designer will go back to work.</p>
<h4>Revised Comps</h4>
<p>Based on your feedback, the designer will continue working on a single design and make improvements and refinements based on your feedback. At this stage, the designer will likely provide another set of mockups for you to review. If no subpages were included in the initial comps, they should be included now.</p>
<h4>Prototypes</h4>
<p>Once the design is nearly finalized, the designer may elect to provide an html prototype of the layout. This prototype is usually a couple of static html pages that you’ll be able to interact with.</p>
<h4>Final Design</h4>
<p>The above steps continue until a final design is decided upon. Then the design, usually in the form of a layered Photoshop or Illustrator file is handed over for development and implementation.</p>
<h3>Step 4: Development</h3>
<p>There are two main phases of development, front-end development and back-end development, which can overlap or even occur simultaneously.<br />
Front-end and back-end development can be performed by the same person, but are often performed by two different individuals.</p>
<p>Not all projects require a back-end developer. Many software packages (like ExpressionEngine or Wordpress) can provide a complete website without additional custom programming.</p>
<h4>Front-end Development</h4>
<p>Front-end development concerns the conversion of the final design to html layouts with the associated css, javascript and images. A complete layout should be provided for each unique page template. I.e., for a simple blog site this would include: home page, article page, and the archives page.</p>
<p>The layouts should also be developed according to current web standards and look consistent across major browsers (Internet Explorer 7, FireFox 3, Opera and Safari).<br />
Sometimes front-end development also includes the integration of these html layouts with a content management system (CMS), eCommerce, or other website management tool.</p>
<h4>Back-end Development</h4>
<p>Back-end development concerns the “behind-the-scenes” programming necessary to make your website do what you want it to do.<br />
This involves programming in a language like PHP or C#, and, often, setting up and querying a database like MySQL or Oracle.</p>
<p>For the most part, you only need a back-end developer if you would like to customize the functionality of your content management or eCommerce system (or create your own from scratch).</p>
<h3>Step 5: Testing and Delivery</h3>
<p>Testing is crucial to the web development process and can occur in a few different steps.</p>
<h4>Internal Testing</h4>
<p>Internal testing is done as a part of development. Sites are tested for errors and against the requirements document before being released to you. Once the site is in good working order (e.g., “beta” version), it is presented to you for review and feedback.</p>
<h4>Client Testing</h4>
<p>A functional website is presented to you for review and feedback. Any requirements not yet implemented are outlined along with an estimated time to completion. At this stage you report any bugs you encounter as well as any requirements that have not been implemented according to your requirements.</p>
<h4>Final Acceptance</h4>
<p>Development, internal testing and client testing continue until the final product is reached and you are happy with the way your site looks and functions.</p>
<h3>Delivery</h3>
<p>Once you have accepted your final website it is delivered to you, with installation instructions, or deployed to your server or webhost (depending on what was decided during requirements development).</p>
<h3>Step 6: Maintenance</h3>
<p>Maintenance of your site includes both updating its content and adding new features. Sometimes other maintenance issues can arise as you attract visitors to your site.</p>
<p>If you’ve elected to include a content management system as part of your website, you will probably be able to maintain basic content yourself. That is, you’ll be able to add new pages, and edit and delete old ones. Otherwise, you may need to learn how to edit html yourself, or continue to work with your website developer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ckwebdev.com/2008/12/website-development-process/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Transferring a Domain from GoDaddy</title>
		<link>http://www.ckwebdev.com/2008/08/transferring-a-domain-from-godaddy/</link>
		<comments>http://www.ckwebdev.com/2008/08/transferring-a-domain-from-godaddy/#comments</comments>
		<pubDate>Thu, 21 Aug 2008 16:55:51 +0000</pubDate>
		<dc:creator>Christie</dc:creator>
		
		<category><![CDATA[Misc]]></category>

		<category><![CDATA[Tutorial]]></category>

		<category><![CDATA[domains]]></category>

		<category><![CDATA[howto]]></category>

		<category><![CDATA[registrar]]></category>

		<guid isPermaLink="false">http://ckwebdev.ck-macbook.local/?p=38</guid>
		<description><![CDATA[After some consideration and research, I have decided to slowly start switching my registered domains from GoDaddy to Gandi.net. I won’t go into all the reasons why not to use GoDaddy, though their cluttered interface and constant up selling are reasons enough. For plenty of information about GoDaddy and other registrars, check out NoDaddy.
Gandi is [...]]]></description>
			<content:encoded><![CDATA[<p>After some consideration and research, I have decided to slowly start switching my registered domains from GoDaddy to <a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.gandi.net');" href="http://www.gandi.net/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.gandi.net');">Gandi.net</a>. I won’t go into all the reasons why not to use GoDaddy, though their cluttered interface and constant up selling are reasons enough. For plenty of information about GoDaddy and other registrars, check out <a onclick="javascript:pageTracker._trackPageview('/outbound/article/nodaddy.com');" href="http://nodaddy.com/" onclick="javascript:pageTracker._trackPageview('/outbound/article/nodaddy.com');">NoDaddy</a>.</p>
<p>Gandi is a French company. Their website is in English and French and they register all kinds of domains, including the usual top-level domains as well as .us, .name, etc. Domains are $15/year plus VAT, transfers are $12/each plus VAT. I did not see a discount for multi-year registrations. They do offer a reseller service.</p>
<p>I chose Gandi because their user-friendly policies. For example, Section 1 of their <a onclick="javascript:pageTracker._trackPageview('/outbound/article/www.gandi.net');" href="http://www.gandi.net/contracts/en/g1/pdf/" onclick="javascript:pageTracker._trackPageview('/outbound/article/www.gandi.net');">Domain Name Registration</a> agreement says “Section 1–You are the owner of the domain name.” Plus their prices are reasonable, they offer full DNS control and their interface is uncluttered and for the most part easy to use (some translations are a little odd, however).</p>
<p>I’ve now registered two new domains with and transfered two using Gandi and have been pleased with the results. One transfer failed at first, but I emailed support and they resolved the issue within 24 hours.</p>
<p>Transferring domains from one registrar to another can be a problematic process. But it doesn’t have to be.</p>
<p>Below is the procedure I followed to transfer my domains away from GoDaddy without troubles:</p>
<ol>
<li>Make sure each of the following is set to off:
<ul>
<li> Privacy</li>
<li>Business Registration</li>
<li>Domain Ownership Protection</li>
</ul>
</li>
<li>Turn privacy/private registration off.</li>
<li>Make sure whois info is correct. This includes the owner, admin and technical contact. It is critical that these email addresses be accurate and accessible. Both your new registrar and GoDaddy will need to send emails to this account.</li>
<li>Unlock the domain from the GoDaddy control panel.</li>
<li>Request an authorization code from GoDaddy. This code will be emailed to your admin/technical contact.</li>
<li>Go to your new registrar and initiate the transfer process. You will need to provide the domain name to be transfer and the authorization code provided by GoDaddy.</li>
<li>The new registrar will send  you an email asking you to accept or deny the transfer request. Follow the directions in the email to accept the request.</li>
<li>After a bit of time GoDaddy will send you an email saying they have received the transfer request. This email might say you do not need to do anything to accept the transfer. <strong>This is not the case, see step 9 below.</strong></li>
<li>Go to the GoDaddy control panel and click on “Pending Transfers.” Accept the transfer.</li>
<li>Wait for the new registrar to complete the transfer.</li>
</ol>
<p>Your nameserver information will be transfer from your existing host to your new host. Or, at least it was when I transfered to Gandi. I was able to complete the above process in one day for most of my domains.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ckwebdev.com/2008/08/transferring-a-domain-from-godaddy/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://www.ckwebdev.com/2008/07/hello-world/</link>
		<comments>http://www.ckwebdev.com/2008/07/hello-world/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 16:23:33 +0000</pubDate>
		<dc:creator>Christie</dc:creator>
		
		<category><![CDATA[Misc]]></category>

		<guid isPermaLink="false">http://ckwebdev.ck-macbook.local/?p=1</guid>
		<description><![CDATA[Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
]]></description>
			<content:encoded><![CDATA[<p>Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ckwebdev.com/2008/07/hello-world/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
