You can get a website – out of the box – and start publishing content. However, with every project there comes a time when you want to deliver more functionality, or custom content, and for that we need to develop custom solutions to deliver what you need.
Building websites is what we've done for a decade. We will recommend an appropriate technology for your project, plan it out, and start building.In medicine prognosis without diagnosis is malpractice – same with website development
We have the combined skills to apply a variety of tools to suit your job. We can recommend an appropriate solution for your project and we will continue to offer you solutions during and after the job if something catches our eye and we think it would be the right fit for you.
All code is tested throughout the development process to ensure the website works consistently on iOS and Android on phones and tablets plus laptops and desktops on both Apple and Windows.
Over the last decade we've refined a solid development process to reduce risk (for you and us) increase quality. You can read more about our Website Development Best Practices, meanwhile here's a summary:
The first stage of development is planning. Call me old school but we can work out a lot of stuff with pen and paper before we start writing any code. “Measure twice, cut once,” as the chippies say.
We need to fully understand your processes fully – to the point where our team can perform the entire process without you.
We create sets of "tasks" that a user would perform and rewite them as a User Story. This means we can think about the functionality as a user rather than the technical requirements. Once we have all the User Stories we can create the technical tasks to complete the User Story.
We create clickable mockups (mockups focussed on content and process over design). Clickable mockups allow us to thoroughly resolve any new business processes or workflows before a line of code is written.
Once we've resolved the functionality then we can apply the design to the mockups. Again, we've resolved all the look and functionality before we've written any code.
Now we know what's required we can plan and schedule the project using Agile methodology. Tasks are grouped into Sprints which are short focussed periods usually a few weeks long. At the end of the Sprint we report back what’s been completed before planning the next Sprint.
We use Atlassian Jira and Confluence to keep track of all tasks, issues and docuemntation. This means all your project information is securely stored in one place so we're all on the same page.
Projects are developed on local (inhouse) servers. They are tested and moved to a Staging Server. On the Staging Server you can log in and test the functionality as if it was a live site. Once everything is working as planned we "push" the changes to the Production Server. The Production Server is the Live system.
We use a Software Version Control system (called Git) so we can manage the development process from different developers and servers. This allows us to monitor the development process and quickly identify any issues.