Knickpoint

Knickpoint was a delivered client website and backend content system. The client needed a simple public site that could present who they are, what they do and the work they are involved in without becoming cluttered or overdesigned.

The starting point was a large amount of information. My role was to structure that content into a coherent website, then build the system behind it so the client could update key areas over time.

The challenge was not to create a flashy website. The client needed clarity, structure and maintainability. Their information had to be organised into pages and content areas that made sense to a visitor, while still being easy for the organisation to manage internally.

They also needed a way to update changing content, including projects, people within the organisation and positions they may want to advertise in the future. That meant the website needed a backend workflow, not just static pages.

The public website presents Knickpoint in a straightforward, organised way. Visitors can understand the organisation, browse relevant information and see content such as projects, people and positions where required.

Behind the public site, the admin system gives authorised users a way to log in and manage the content that changes over time. This keeps the site maintainable without requiring every update to become a development task.

Knickpoint shows the practical systems side of my work. The value was not only in how the website looked, but in turning a large body of client information into a clear public structure and a maintainable backend.

It also shows how I think about digital delivery beyond the surface interface: what content needs to change, who needs to manage it, and what kind of system will make the site useful after launch.

This project connects to my current practice because guided digital experiences still depend on good structure underneath. Whether the output is a public website, a property presentation, a visitor guide or a display layer, the work often begins with organising content into a system people can understand and maintain.

Knickpoint is a useful example of the implementation side of that practice: taking messy information, giving it structure, and building a working system around it.