oliverbenns.com

oliverbenns.com is the GitHub repository behind Oliver Benns's personal portfolio website, built as a static site and archived in two past implementations: one self-built in Go and one using Gatsby.

What is oliverbenns.com?

This repository hosts the source code for Oliver Benns's personal website, a portfolio designed to present his work and online identity. The project is tagged on GitHub with the topics golang, portfolio, static-site, and static-site-generator, and has collected 51 stars. The page itself functions as a minimal README that redirects visitors to the last commit of two historical versions: a self-built Go implementation and a Gatsby-based implementation.

Key Features

• Self-built Go version — A prior iteration of the site was built from scratch in Go, with the final commit linked directly in the README for reference.
• Gatsby version — Another historical version used the Gatsby static site generator, and its last commit is also linked in the README.
• Static site approach — Repository topics (static-site, static-site-generator) indicate the site is output as a static website, giving fast page loads and simple hosting.
• Portfolio focus — The site is explicitly a portfolio, suggesting it showcases projects, skills, or professional experience.
• Public GitHub repository — Anyone can browse the source history, compare the two implementations, or fork the code, subject to whatever license applies (not stated on this page).
• Personal domain — The repository name matches oliverbenns.com, indicating the site is deployed under the author's personal domain.

Who is it for?

The site is primarily for Oliver Benns to display his work to potential employers, clients, or collaborators. For other developers, the repository serves as a reference for a personal portfolio structure and for comparing a hand-written Go static site generator with a Gatsby-based one.

Use cases

• Developers studying static site generation: examine the Go code in the historical commit to see how a site can be generated without a framework.
• Gatsby learners: review the archived Gatsby implementation to see how pages and components were organized for a portfolio.
• Portfolio builders: use the repository as a starting point for creating a personal portfolio with a similar static-site approach.