We're hiring! Check out open positions
Image of Humanforce



The Humanforce team had just undergone an extensive process to modify their static website into a WordPress site. The project had proved to be a frustrating experience and communication with the development agency was slowing the project down, leading to poor results. 

Their team approached Clean Commit in August 2021 for help getting the rest of their website developed. They had opted to build each page individually and replace the existing website. We don’t recommend this approach normally because it creates a great deal of overhead effort and expenses but in Humanforce’s case, this approach made sense.

In addition to developing the rest of their website pages, we needed to provide an easier way to create new landing pages, modify existing content and keep the website updated without having to get us on the phone. No business wants to rely on a developer to make simple changes, and honestly, no developer wants that either.

About a month into the project we took over the design as well as handling the development, initially to improve the responsiveness of the site but it’s almost always more efficient and easier to manage design and development within one team. 

The Humanforce project is currently ongoing but quickly reaching its conclusion. The site is will most likely continue to evolve as Humanforce identify areas of the design and content that can be optimised to drive results.

Know how

  • PM
  • Web Design
  • WordPress Development





Check it out

Content: Visit website


Picking up the pieces

The most challenging aspect of this project was picking up a half-finished WordPress website that was built with some questionable approaches. 

Working on another developer’s code is never easy, especially if they’ve used unnecessary libraries and their architectural decision was hard to understand. The Humanforce website was a combination of two different development teams’ efforts; the new homepage and the legacy website. We needed to rebuild the homepage using a more dynamic block-based page builder, and continue to rebuild the remaining pages, all while keeping the website up and running.

To avoid the new stylesheet overtaking the legacy site’s look and feel, we wrote a bit of logic to dynamically pick the stylesheet based on which template the page was running. The old content would load the old stylesheet, and the new template would load the new and improved styles. 

On the design side of the project, as we picked up the Figma project it was clear the target ratio was poorly chosen and was going to cause headaches. The frame width was 1280px wide which is somewhere between a small laptop and tablet. A width this small meant that anytime the site was viewed on a larger device (i.e. a desktop), there were very large empty side margins. 

Even though the wide margins aren’t a look we would have picked from the outset, they didn’t end up impacting the site’s overall appearance too badly. The biggest change to resolve this problem was removing any designed elements that half-overlapped the edge of the screen.

Clean Commit's completed work project image
Clean Commit's completed work project image
Clean Commit's completed work project image
Clean Commit's completed work project image

Have an idea you want to discuss?

We’re based in Canberra, Australia and we LOVE working with locals… but we work with clients all around the world.

From the U.S. to the U.K. From Norway to New Zealand. Where there’s a problem to solve, we’ll be there!