Article
Building a small Angular portfolio
This site began with a modest goal: keep a public record of the work, decisions, and abandoned directions that are still worth remembering.
Why Angular?
Angular is more framework than a small portfolio strictly needs. It is also the framework I use professionally, so the surrounding concepts are familiar and the site remains pleasant to change. For a personal project, familiarity can be a perfectly reasonable architectural choice.
Static by design
The application is prerendered during ng build. Visitors receive ordinary static files, while the source can still use Angular components and routing.
- The homepage introduces the site and lists the available writing.
- Each article or project has a direct URL that can be bookmarked and shared.
- Shared components keep typography and navigation consistent.
Deployment without a server
A GitHub Actions workflow builds the application whenever the main branch changes. GitHub Pages publishes the generated files, and the custom domain points readers to that deployment.
The goal is not to make a small website feel like a large application. The goal is to use familiar tools without making the final result complicated.
What comes next
The useful part starts after the infrastructure disappears into the background: replacing sample entries with honest accounts of what each project attempted, what worked, and why the work eventually stopped.