Skip to content
Archwarden
Go back
Site In Progress

Archwarden — Security Portfolio Site

Skills AstroTypeScriptTailwind CSSCloudflare Pages

Archwarden — from blueprint to build

Why I Built This

A GitHub profile is fine for showing code. It’s not great for showing how you think.

I wanted somewhere to put my work that a normal person could actually read — not just another repo full of markdown files that only make sense if you already know the field. Writeups, project documentation, methodology notes — the kind of thing I was searching for when I was starting out and kept coming up empty.

That’s the point of this site. I’m not trying to position myself as an expert. I’m further along the path than some people, and I’m trying to leave useful markers for those coming behind me, the same way others did for me. The people I’m trying to help aren’t hiring managers — they’re people earlier in the same process I’m going through right now.

At the same time, this is a living record of where I am and where I’m going. I’m hoping it gives a more honest picture of my skills and how they’re developing than any resume could.


Stack

Built on Astro with Tailwind CSS, deployed on Cloudflare Pages.

The choice was deliberate — static site means fast load times, no server to maintain, and free hosting. Astro’s content collections give me a proper structure for writeups, projects, and methodology docs without needing a CMS. Everything lives in markdown files in a git repo.


Customization

I started from AstroPaper as a base and rebuilt it significantly. There are a lot of security portfolios that are clearly AstroPaper with a different name in the config — I didn’t want that.

The changes weren’t cosmetic for the sake of it. A wider content layout makes writeups easier to read. The HTB writeup collection with difficulty and OS filtering makes it actually useful to navigate. The methodology section is something I built specifically because I couldn’t find good structured methodology references when I was studying — so I’m building the thing I wished existed.

The color scheme, branding, and layout are all custom. It should look like mine, not like a template.


What’s On It


What’s Next

This site grows as I do. Boxes get added as I complete them. Projects get documented as I build them. The methodology section gets deeper as my understanding does.

It’s not finished. It’s not supposed to be.



Previous
CPTS Pentest Methodology