Ongoing project
Portfolio website
lukemedia.dev
A static website for sharing my personal projects, live since October 2026.
Goal
This site shares projects I pursue outside work to practice designing, building, and testing software. The first version was a homepage, one page of notes per project, and a custom 404 page. It needed to read well on a phone and stay simple enough for me to learn from and change.
Decisions
Plain HTML and CSS
The site is text, links, and a layout that adapts to screen width. Plain HTML and CSS cover that without a build step, framework, database, or browser JavaScript, so every file can be read directly. The tradeoff is that the header and footer are repeated on each page. A static site generator becomes worth considering if the number of project pages grows.
Cloudflare hosting
I had Codex compare the free plans from Cloudflare and Vercel. Either would host a static site for $0. I chose Cloudflare because the lukemedia.dev domain is already registered there, which keeps the domain and hosting in one account.
Previewing each change before it goes live
Each change goes on its own Git branch. Cloudflare builds a preview of that branch, and the change reaches lukemedia.dev only after I merge the pull request on GitHub.
Purple accents
Purple is my favorite color, so I used it for the site's accents. Codex checked the text colors against the WCAG minimum contrast ratio of 4.5:1.
One project list with status tags
I tried separate sections for ongoing and completed projects, but the split repeated each status tag and left the completed section empty. Projects now share one list, each tagged with its status. Ongoing and in-progress projects come first, newest start date first, then completed projects, newest finish date first.
My role first, and no screenshots in the project list
Portfolio sites often put the person's role near the top, where readers see it first, so mine sits above the headline. I left screenshots out of the project list because my first projects wouldn't all have useful images, and a list where only some entries have one looks inconsistent. Photos go on project pages instead, where they show something a reader can't otherwise see, such as the server hardware.
A public repository for the code, and a private one for my working history
I make changes and keep my working notes in a private repository, which has the more frequent updates and my personal history. A separate public repository holds a copy of the site's code, and this site links to it.
My work and AI assistance
What I did
- Defined the site's purpose and audience.
- Created the GitHub repository, reviewed potential layouts, and chose the color scheme.
- Reviewed the wording in a Google Doc, left comments, and approved the first revision of the text.
- Added the site icon, which is a drawing of my cats (thanks for the drawing, Fern!), and updated its links on all three pages.
- Reviewed the layout drafts, chose which changes to keep, and edited the HTML myself.
- Changed the homepage headline, and adjusted the Projects heading's spacing and alignment in the CSS.
- Styled the Linux server page's photo in CSS.
- Committed, pushed, and merged each change through pull requests.
- Tested the live site and its 404 page on my phone and desktop.
How I used AI tools
- Had Codex research hosting options.
- Used Codex to generate the HTML, CSS, and a local preview server, then had it revise the layout from my feedback.
- Had Codex apply my approved wording and run local checks.
- Gave Codex the log from a failed preview build and had it find the fix.
- Had Cursor draft an alternative version of the wording. The site's first headline came from that draft.
- Used Cursor to build the layout drafts and copy the version I edited and approved into the site.
- Had Codex review other portfolio sites for common practices.
- Used Claude to review the site's wording against my writing guide, apply the edits I chose, and draft the Linux home server page from my notes.
Each entry in the update log says who made that change, so the balance between my code and generated code shows there as it shifts. My own code changes so far are the site icon update, the HTML edits in the October 19 layout revision, and some HTML and CSS changes in both the October 24 and 25 revisions.
Checks
The latest result for each kind of check. Checks for each change are in the update log.
| Check | Last checked | Result |
|---|---|---|
| Links and missing-page responses | Me, Oct 27 | Passed |
| Security headers in the local preview | Claude, Oct 27 | Passed |
| Layout on phone widths (320px and 375px) and several desktop widths | Me and Claude, Oct 27 | Passed |
| Keyboard skip link and text contrast (4.5:1 minimum) | Claude, Oct 27 | Passed |
| Cloudflare branch preview on phone and desktop | Me, Oct 27 | Worked |
| Live site and 404 page on phone and desktop | Me, Oct 27 | Worked |
The full check record is kept in my private working repository.
Update log
Pull request numbers refer to my private working repository.
-
Page titles and a server update
Page titles and link previews now show "lukemedia.dev" instead of my "Luke Wood", and the server page's description says "my" instead of "Luke Wood's" (third person is silly anyway). I widened the Projects caption so it shouldn't wrap onto a fourth line, and the server page now records the memory upgrade and the new power supply. I made the title, description, and caption changes myself (PR #8).
Checked: Claude checked the skip link, security headers, and text contrast locally. I checked links, the 404 page, and phone and desktop widths in my local preview, and the Cloudflare branch preview on my phone and desktop.
-
Linux home server page
A project page for my Linux home server, with a photo of the hardware, and a card for it on the homepage. I supplied the facts, my notes, and the photo, and Claude drafted the page. I styled the photo in CSS myself: margins that inset it from the text, a width that resizes with the page, a 1px border with slightly rounded corners, and a smaller, muted caption. I also set the order of the project list, with ongoing and in-progress projects before completed ones, each group newest first, and centered the Projects heading with its caption. I reviewed the result and made final edits myself (PR #7).
Checked: Claude checked the links, the 404 page, phone widths, the skip link, security headers, and text contrast locally. I checked phone widths and the 404 page in my local preview, and the Cloudflare branch preview on my desktop.
-
Homepage headline and wording revision
I changed the homepage headline to "Personal projects and what I'm learning", removed the "Selected work" label above the Projects heading, and adjusted the spacing at the top of the project section in the CSS until it looked right. Claude reviewed the site's wording against my writing guide and applied the edits I chose from its suggestions. I reviewed the result and made further edits myself (PR #6).
Checked: Claude checked the links, the 404 page, phone widths, the skip link, security headers, and text contrast locally. I tested the local site, its 404 page, and the Cloudflare branch preview on my desktop.
-
Layout and wording revision
A new layout that fits both ongoing and completed projects, with my role on the homepage, LinkedIn links, and a link to the public code repository. Cursor built the draft, and I chose which changes to keep and edited the HTML (PRs #4 and #5).
Checked: I reviewed the draft in my browser. Cursor checked the links, the 404 page, phone widths, and the skip link locally.
-
Wording revision, full name, and site icon
I reviewed the site's wording in a Google Doc, and Codex applied the text I approved. The header now uses my full name, and I added the cats icon. The first preview build for this change failed because the Cloudflare configuration was missing a required
previewssetting. I supplied the build log, Codex found the fix in Cloudflare's documentation, and I committed it and merged the change (PR #2).Checked: Codex matched the pages against the approved document and confirmed they fit a 320px screen. After publishing, I tested the live site on my phone and desktop, and Codex confirmed the changes on lukemedia.dev.
-
First version published
The homepage, these notes, and the 404 page. Codex generated the HTML and CSS from my goals and layout choices, and Cursor drafted part of the wording, including the headline. I merged the result (PR #1) and published it at lukemedia.dev.
Checked: Codex checked the links, missing-page responses, security headers, phone widths (320px and 375px), the skip link, and text contrast locally on October 11. After publishing, Codex confirmed the live pages loaded at lukemedia.dev and matched the merged files.
Planned next
- Add a project page for my next project, a progress tree and small mod for me and a friend on my Minecraft server.
- Work through a free online HTML and CSS course, such as W3Schools, to understand this site's code better and see how far what I've learned already takes me.
- Do more of the hands-on work in future changes myself, as I did with the photo CSS.