Portfolio website
This project revolves around my personal portfolio website: a place where I bring together my work, working methods, and technical decisions. Not just to showcase end results, but to provide context — why I make certain choices, how I approach projects, and the role I play within them.
Project info
- Start
- October 2025
- End
- January 0001
- Complexity
- 4 / 10
- [[Team size]]
- 1
- Type
- Hobby Portfolio
- [[Stack]]
- C# Javascript HTML & CSS SQL ASP.NET Core RazorPages Bootstrap GIT Umbraco
- [[Live]]
- https://bartvanderburg.nl
- [[Source]]
- https://github.com/Bart023/PortfolioWebsite.Static
Goal and Motivation
The goal of this website is to give a clear and honest view of how I work. I want to show what I build, but more importantly how and why. This includes code examples, architectural decisions, and the trade-offs that come with them.
In addition, this project was a deliberate choice to gain hands-on experience with Umbraco, within a setup that remains easy to extend. New projects and content should be simple to add without sacrificing technical control.
Technical Stack
The website is built using Umbraco CMS in combination with ASP.NET Core Razor Pages. Because I already had experience with Razor Pages, I was able to become productive quickly and focus on structure, reusable components, and consistent styling.
For the front end, I opted for a lightweight setup using Bootstrap along with custom CSS and JavaScript. No unnecessary frameworks, but enough flexibility to create a clean and accessible UI. Interactive elements are intentionally kept simple to keep the code readable and maintainable.
Hosting and Static Generation
For hosting, I chose a static approach. The Umbraco site is converted locally into a static website, with all pages and assets generated automatically. This allows the site to be hosted entirely for free, without compromising performance or stability.
To support this workflow, I built a simple local static host that starts alongside Umbraco and immediately serves the generated files. This makes it easy to test changes quickly and iterate efficiently.
Architecture and Code Quality
The architecture is intentionally kept simple. The project contains little complex business logic and largely follows the patterns prescribed by Umbraco. This provides clarity and encourages structured decision-making without introducing unnecessary complexity.
The focus was on a clear content structure, reusable block components, consistent naming, and clean Razor views. Below, I provide insight into the project setup through several images. To give a concrete impression of my code style and way of working, I also include a few code examples, demonstrating how I approach structure, separation of concerns, and readability.