BrontëHF — Client portfolio website

Case snapshot

Problem

Turn Brontë’s visual direction and project material into a finished site they could update without editing code.

My role

Implementation, responsive refinement, CMS integration, and technical delivery.

What I changed

Translated the supplied visual direction into responsive editorial layouts.
Separated project content from code with an editor-friendly CMS.
Automated linting, building, and auditing before deployment.

Result

A complete live portfolio with public authorship credit and a publishing workflow Brontë can use directly.

A designer needed faithful technical delivery

Brontë supplied the visual direction and project material. My responsibility was to turn that direction into a reliable, responsive public portfolio without claiming authorship of the design.

The site had to remain Brontë’s to operate

A finished portfolio was not enough if every content update required a developer. The content model and release path had to support direct editing without making the front end feel like a template.

The quiet technical choices mattered most

I used Astro for a fast, low-JavaScript front end, Decap CMS for project and page editing, and GitHub Actions to check each release. Components preserve the editorial system while content stays independent.

The result is visible in the public site

The live site includes Home, Projects, About, Contact, a CV, detailed project pages, responsive layouts, and a public “Site by Hamish Burke” credit.

Good delivery keeps the client in focus

The strongest part of this work is not a flashy framework decision. It is that the implementation supports Brontë’s work, authorship, and ability to keep the portfolio current.