Build Phase and Content Entry

Site build and content entry is the business end of the website development process. After all of the planning and design, we now build up the site. Signing off on design is the dependency that must be met before me move onto build.

In this phase we will:

1. Build the website – includes building the theme and also any custom coding or integrations.
2. Enter the site content – This includes creating the site structure and entering the content to the pages and posts.
3. QA test and fix – Conduct our own internal testing and perform fixes as necessary.

Development Site

We build the website on a development server, referred to as the “dev site” or “staging server”. The dev site is “hidden” from search engines and can only be navigated to via a unique URL. Typically we provide access to the dev site for UAT (user acceptance testing) at around 80% build completion.

Steps in Build Phase / Content Entry Phase

1. Build the Theme (Curata) – Build of the page templates that make up the website theme, in line with the designs.
2. Custom Coding or integrations (Curata) – If your site includes any custom coding or integrations with other systems, these will be implemented now.
3. Enter Content (Curata) – We add content to the site in line with sitemap and signed off copywriting. (Amount of content entry is as per the proposal, additional content entry to be done by client.)
4. QA Testing and Bug Fixes (Curata) – We conduct our own rigorous QA testing regime and correct any issues that arise. This includes cross browser/device/platform testing. “Bugs” are normal during any build. We identify them, and fix them.
5. User Acceptance Testing (Client) – We provide you access to the development site to review and feedback any final issues, or sign off.
6. Final Fixes (Curata) – This is the final round of fixes before Go Live. Final fixes at this point are typically minimal. It is not an opportunity to make additional feature requests.
7. Sign Off (Client) – “Sign Off to Deploy” is your confirmation that the site is built in line with the designs and functional specification. At this point you confirm the site is complete and giveCurata the “green light” to make the site Live.
8. Go Live (Curata) – Curata makes the technical changes to severs/domain records in order to publish the new site to the web, (make it “live”).

Review Tips

The purpose of UAT or “client review” is your opportunity to review the site in line with the design, sitemap and any functional notes for the theme functionality.

• Review against the page template designs
• Review against the sitemap
• Try the site in a few different browser/your mobile device
• When feeding back issues, be as descriptive as possible. Include: URL’s, Screenshots, descriptions. Browser/OS details. I.e. as much detail as possible to assist us to rectify the issue as quickly as possible. Please feedback issues on Basecamp.

Training

We will also conduct the training session for your website during the build phase, usually toward the end of the build, on the dev site, prior to Go Live. This enables you to have the skills to update your site from the point of Go Live onwards.

Post Go Live Bug Fixes

Although we test rigorously pre go live, it’s possible that some minor bugs may surface after the site is deployed. Curata will performa any bug fixes required in line with the warranty period. Fixes are limited to functionality in line with the designs/specifications.