This portfolio

The tools behind the site got easier to use for creating tracking links and sharing a file map, with nothing visible to visitors.

The site had nothing for a search engine or a link preview to work with, and that has been put right.

• You can now share a link to the site and get a card with a title, description and image, where before it was a bare URL.
• Search engines can now index the site through a sitemap and structured data, so it shows up properly in results instead of as a bare domain.
• Fixed a mistyped address showing a silent copy of the homepage instead of a not-found page, and the build log skipping some days.

None of this changed anything on the site; it was internal work on how the update log gets put together, plus one documentation correction.

None of this changes an app you use; it is tooling behind the update log, with two August days re-published to match.

• Work on a shared building block now appears under the app it was made for, where before it could be filed under the wrong project.
• A project’s first entry now reads as a launch announcement introducing the thing, rather than a list of changes to something you’ve never seen.

The homepage now carries writing beside projects, which its opening line had promised since it was written.

• You can now see the newest writing posts on the homepage under Projects, so you reach them without opening the header menu.
• New posts appear there on their own once published, and the section hides when nothing is live, so no empty heading ever shows.
• The internal deploy dashboard now tracks the model-comparison tool and can deploy it with one button, where before that meant running commands by hand.

Anecdote’s case study is now published on the site, where before it was finished but hidden from readers.

• The case study opens with four phone screenshots and a before-and-after diagram, so you can see the app rather than only read about it.
• Its entries in the update log now link through to the case study, where before they had no page to open.
• The agentic-coding article now links an open-source tool you can use to map your own setup, so you can build one yourself.
• Fixed the header logo sitting off-centre on phones, and a link in the article that pointed at the wrong page.

The portfolio now has somewhere to publish written pieces, and the first one has gone live.

• A new writing section now sits in the top navigation, so the site has a home for articles alongside the projects and update log.
• The first article looks back at four months of building nine web apps with AI, written for people who haven’t tried these tools.
• The article is built around an interactive map you can drag, zoom into and click to open the real file behind any node.
• Clicking a file name in the text walks the map open to that exact file, so you see the real thing instead of a description.
• You can open the map full screen, which gives a crowded diagram room to breathe, most useful on a phone.
• A contents list near the top lets you jump straight to the map or the getting-started steps without scrolling the whole piece.
• Fixed a page that lurched when clicking into the map, a header that overflowed on phones, cramped tables, dim map-panel text, and choppy map animation.

The site’s navigation labels and the animation about how these updates get written both got attention.

• The build log is now called “What’s new” in the nav, on cards and project pages, so you know there’s something fresh to read.
• The header’s first link now reads “Projects” instead of “Work”, matching the built projects it sends you to.
• The updates page now opens with “What I’ve been building”, which stays true on a quiet week where “day by day” overpromised.
• The animation’s collect scene now shows real snippets of commits, file paths and diary lines flying into the file, instead of plain labels sliding in.
• The closing counter now shows the true total of entries written, dated to the newest one, instead of a number typed months ago.
• Fixed a scroll cue arriving late on the first scene, an opening that flew past too fast, and several uneven motion and ordering glitches.

The animation showing how the build log writes itself got a round of polish, along with the log page around it.

• Reading only the headings over the animation now walks you through the whole process in order, from your first instruction to the entry going live.
• The animation is easier to follow, with a slower opening scene, a scroll cue that appears partway through each scene, and larger headings on phones.
• Text under each entry on the log page is now brighter and more open, matching the rest of the site, so it no longer looks faded.
• Fixed a repeated intro fact, boxes jumping as text typed on phones, the scroll cue overlapping content, a wrong example app name, an overstated publishing line, and a sentence on the about page pointing at nobody.

The portfolio case study now shows how these build log entries get written without anyone typing them.

• A new section explains the agent that turns logged prompts, session notes and commit messages into a daily entry, so you can see how the log stays current.
• An animation plays through a single day, showing its commits, prompts and notes come together into one entry.
• The build log page now says up front that an agent writes it, and links to the fuller explanation.
• Mentions of the build log in the case study are now clickable, so you can jump straight to the page or the section.

Days spent setting up new tooling, like a skill, rule or hook, now appear in the build log, where before they were skipped.

The public build log on this site had an accuracy pass.

• Removed fourteen entries that described planning or repeated a change already listed, so the log only covers work that actually shipped.
• New entries for the planner, storymap and portfolio went up, covering the latest round of work across those projects.

Most of the day went into the public build log on this site.

• You can now read the build log back to late April 2026, so the record covers the projects from close to their earliest days.
• Removed several entries that misdescribed the work, including ones claiming sign-in was slow and that the build had no automated security checks.

On a phone, the case-study carousel now shows the edge of the next screenshot, so visitors can tell it swipes instead of seeing one static frame.

The homepage and the log page each picked up a small, visible change.

• The homepage build log card now shows five recent entries instead of ten, so it no longer dwarfs the other cards and the full log stays in reach.
• The log now covers more past days, including late June, so there is more of the project history to read.

Most of the work went on the header, the site’s colours, and making contact and the build log easier to find.

• The header now carries Work, Log and About links and a LinkedIn icon, so you can reach any part of the site directly.
• The D logo mark now sits in the header and the browser-tab icon turned forest green, so the whole site shares one colour.
• The build log now lists projects that will never get a full write-up, named but not clickable, so you see all the work rather than a third of it.
• The about page and every footer now show an email, so you can get in touch without scrolling a long page or leaving the site.
• Each project’s build log now leads with its newest entry, so you land on where the work is now instead of its first day.
• The build log updates itself each day and its history reaches back to 10 July, so the page stays current on its own.
• Build log entries now show just the commit count, dropping a time range that made short sessions look like a full day at the desk.
• Fixed the header links reading too dim and clashing in colour, and the about-page contact line breaking awkwardly on phones.

Most of today went on the portfolio itself: a new build log, and the case study pages.

• The site now lists each day of work across projects on a new build log page, and a daily job keeps it current on its own.
• The planner and storymap case studies now show sharper, larger screenshots, so the detail is readable instead of soft or cramped.
• The planner case study’s text-message example now looks like a real phone conversation, so it reads as a genuine screenshot rather than a mock-up.
• The the-weekly case study is now hidden from the public site, while its writing stays in the repository for later.
• Fixed case study lists that showed no bullet points, screenshots that looked dimmed, a gap beneath phone-frame images, and cramped homepage spacing and text.

Most of today was case study polish, with time set aside to plan a new build log for the site.

• The storymap case study now shows real captures of the grid and a card being dragged between release stages, instead of placeholder blocks.
• The live link on each case study now reads Try it, and storymap repeats it lower down where you’d most want to open the app.
• The site header now slides away as you scroll down and returns as you scroll up, giving small screens more room to read.
• On phones the app screenshots now fill the screen with a peek of the next one, so they’re easier to read and swipe.
• Started planning an automated build log that turns each day’s commits into a plain-language note about what changed for you.
• Fixed off-centre carousel captions, a controls row that shifted between slides, cluttered tags above case study titles, and inconsistent title dividers.

Most of the day reworked the site’s colours and the look of the homepage cards.

• Highlights across the site, from badges to links to buttons, are now forest green instead of purple, a look that read as AI-generated.
• Homepage project cards no longer show tag chips, giving each card larger, clearer artwork in the freed-up space.
• The diagrams on the storymap case study were re-tinted to match the new green, so the page reads as one palette.

The deploy buttons on the versions dashboard now show a run’s true outcome when you return to the tab, where before they could spin forever on a phone after the deployment had already finished.

The deploy button on the versions dashboard was misbehaving in three related ways at once.

• Fixed a deploy that fired twice per click, re-fired when you returned to the tab, and a success tick that rarely showed.

The images at the top of the case studies got attention, both the phone carousel and the framed screenshots.

• Each app screenshot in the planner case study now carries a caption, so you can see what screen it shows.
• You can now tap a side screen in the carousel to centre it, and the active screen stands out from the rest.
• The screenshots now stay sharp on high-resolution displays, where before they looked soft in the wide layout.
• One dashboard screenshot now sits in a browser frame showing its web address, so it reads as a real deployed page.
• You can now tap a screenshot to open it full size and inspect the detail, which was unreadable on a phone before.
• Screen readers now announce which screenshot is showing as the carousel moves between them.
• Fixed carousel dots too small to tap on a phone, and controls that gave screen readers a misleading structure.

The backend behind the site gained detailed timing records, so a slow response can now be pinned to the step that caused it.

A research day for a future writing post, plus this site’s share of the monitoring rollout.

• The workspace’s git history and diaries were mined into six tables recording when each tool arrived, why, and whether it survived or was retired.
• The site’s hand-rolled visitor analytics was replaced by the shared workspace package, so the site and the apps now share one wiring.
• The admin pages’ calls out to GitHub are now timed, so a slow version check or deploy poll shows where the time went.

A deploy still running could be wrongly marked failed if you stepped away for over 15 minutes, which no longer happens.

The versions dashboard deploy button no longer shows a false failure or a stuck spinner when you return long after starting a deploy.

The project dashboard now refreshes on every deploy again, and the Polymarket project appears where a wrong setting had hidden it.

The dashboard for tracking and deploying each project’s versions got a round of fixes and polish.

• You can now dismiss a failed deploy, and a successful one clears itself, so the next deploy needs no page reload.
• After a deploy finishes, its version row now updates on its own, so you can confirm the new build landed without clicking Refresh.
• The Refresh button now pulls fresh data instead of the cached copy, and shows how long ago the table was last updated.
• Fixed a URL shortener row missing its link, version cells stuck loading forever, a jumpy usage chart on load, and a ‘1 days ago’ label.

New reading landed on the portfolio, led by the storymap project.

• You can now read the full case study on the storymap backlog tool, covering why it was built and the decisions behind how it works.
• You can now read a transcript where an automated browser check caught a styling bug, showing how the workflow spots problems.
• Fixed uneven spacing around diagrams and code blocks inside case study pages.

The story-mapping tool I built for my own projects now has its own spot on the portfolio.

• You can now find Storymap among the projects on the homepage, so the tool sits alongside the rest of the work.
• Its card opens a short page explaining what Storymap is, with a link to try it live at storymap.dylanmagorhampel.com.

The homepage and the case-study pages got a pass over both their visuals and their writing.

• Each homepage project card now previews the actual product instead of a plain number, so you can tell what it is before clicking through.
• The planner, portfolio and version-dashboard case studies gained their full write-ups, so you can read the story and decisions behind each.
• Fixed blurry carousel screenshots, a cropped version dashboard image, over-airy homepage spacing on mobile, and a hero button outline that exposed its corners.

The project pages got most of the attention, on the images and the way out to each live app.

• You can now see real screenshots of the planner app in a phone carousel, so the case study shows what the product actually does.
• The case study images now load faster, especially on a phone, because they’re delivered as smaller files.
• Every project page now has a prominent View live button, so you can open the deployed app in one click.
• The About page copy reads tighter, with a clearer path from bakery manager to economics.
• Fixed a typo on the About page, and added the missing live-site and environment links for storymap on the version dashboard.

The portfolio got a cleanup pass on a few things that weren’t displaying properly.

• Fixed a phone-screenshot carousel that left its last frame off-centre, a project-link heading shown in the wrong small font, and a missing browser-tab icon.

The portfolio filled in the pages that were still placeholders.

• You can now read the full Remind me later case study, from the problem it solves to how its reminders and weekly review work.
• The About page now tells a personal story of my work and side projects, replacing the single placeholder paragraph that was there before.
• Each next-project link now shows a one-line description, so you know what the next case study covers before clicking through.
• Your browser tab now shows a custom gradient icon instead of the default Astro rocket the site came with.
• The anecdote project is no longer listed, because it is still being built and not ready to show.
• Case study cards now use an arrow beside the title as the click cue, dropping the separate “Read case study” link.
• Fixed a misaligned featured-card label, a screenshot carousel clipped on the right, homepage text stopping short of the page edges, and a faint next-project heading.

The deploy buttons on the site’s admin dashboard got most of the attention.

• The deploy button now clears once a deploy finishes, where before it could show Deploying forever even though the deploy had already succeeded.
• A deploy in progress now survives a reload or tab close, so returning shows it still running instead of a button you might fire twice.
• A deploy you started in another browser or on another device now appears on the dashboard, so you don’t launch the same one twice.
• Opening the production deploy confirmation is now instant, where before it reloaded every project’s status and flashed the whole dashboard.
• The deploy button is now a compact icon tucked on each row, so more of the dashboard fits on screen without scrolling.
• Fixed a featured project card that flickered a purple-blue gradient on hover, and a broken about link on the homepage.

A round of visual polish on the homepage, plus some housekeeping on the admin side.

• Featured project cards now match the others at rest, and a gradient ring appears and rotates when you hover, drawing the eye to them.
• The version dashboard now tracks Storymap, so you can tell at a glance whether its live and preview sites run the latest code.

Most of the work went into the version dashboard, the internal page that tracks deploys across every project.

• The production deploy dialog now refreshes when it opens, so it shows the latest commit instead of what master looked like when the page loaded.
• The preview branch picker now lists a branch pushed in the last minute, which caching could previously hide.
• When the preview branch list fails to load, the dialog now shows what went wrong, rather than only a bare error code.
• The dashboard no longer serves stale data from your browser cache, so a page refresh always shows the current deploy state.
• Fixed a preview branch picker that errored, an off-centre deploy dialog, and a deploy status that wrongly showed Failed after a tab regained focus.

The versions dashboard used to only show which version was live where; now it can trigger deploys too.

• You can now start a deploy for any project from a button on its row, instead of opening GitHub and running the workflow by hand.
• For a preview deploy, you pick from recent branches that touched the project, so you don’t have to recall a branch name.
• A production deploy shows the commit and how far it is ahead of what’s live before you confirm, so you don’t ship the wrong thing.
• The deploy buttons only appear after you sign in, so nobody browsing the page can trigger a deploy.
• A new bar shows the GitHub Actions minutes you’ve used this month, coloured by where the month is heading, so an overrun warns you early.
• Fixed a usage bar that over-counted across months, a branch picker that failed to load, off-centre dialogs, and deploy buttons frozen on “deploying”.

The dashboard that tracks which version of each project is live got attention on how it loads.

• Cells still loading now show a shimmer placeholder sized to the final content, so the page no longer jumps as each one fills in.
• The first load now shows seven placeholder rows instead of a centred loading message, so the table’s shape appears straight away.
• You can now start a preview deploy straight from the dashboard, beside the production deploy link, where before only production was one click away.

Most of the work went into the internal dashboard that shows which projects have code waiting to be deployed.

• Projects now appear on the dashboard immediately, with each status filling in as it’s ready, so the page is usable before every check finishes.
• A project with code waiting to deploy now shows how long it’s been waiting, so recent gaps stand apart from ones left for days.
• Projects whose deployed and latest code have split now stand out more than ones with small differences, so the serious cases catch the eye.
• Fixed the dashboard intermittently failing to load entirely, and a removed link returning a raw error rather than a clear message.

The project pages got most of the attention.

• You can now read the Anecdote case study: why an achievement tracker that interviews you was worth building, and how it reused existing app foundations.
• You can now read how this portfolio itself was built as a product, from its mock-first design workflow to the shared design token system.
• Design iteration links inside the case studies now stay on this site, instead of sending you off to a separate hosting domain.
• Made the site header shorter on phones, freeing up screen space that a taller bar had been eating on small viewports.

Most of the work went into getting the portfolio ready to share as a first public version.

• A new case study covers the version-status project from idea to live, with an architecture diagram and a link to the running dashboard.
• The homepage now leads with Anecdote and Remind me later as featured projects, and drops two entries that had no write-up yet.
• Featured project cards now carry a gradient border and a FEATURED tag, so the projects worth reading first stand out.
• The header now has a LinkedIn button, so you can connect in one click instead of hunting for a contact link.
• On a phone, the interactive demos in case studies now open in a tap-to-expand full-height sheet, instead of cramping into the page.
• A new privacy page explains what the site records and how to opt out of analytics.
• Fixed hard-to-read faint text, a dead header menu button, an oversized gap under case-study headers, and blank cells on the live status dashboard.

Most of the day went to fleshing out The Weekly’s case study and sharpening the look of the rest of the site.

• The Weekly case study now shows how its recipe data was scraped from Coles, with a diagram, so the build story is concrete.
• It now opens with a real screenshot of the app mid-selection, replacing a plain gradient placeholder that showed nothing of the product.
• The Weekly’s homepage card now carries a large ‘01’ numeral mark, giving the project grid more visual identity.
• Case study section headings now use larger serif type, so telling a section from a subsection while reading is easier.
• Project cards now carry short editorial tags about each project, instead of a raw list of framework names, so each card’s point lands faster.
• Homepage section labels like ‘Selected work’ and ‘About’ are now proper headings, giving the page a clearer structure.
• Case study pages now show how many iterations a project went through, so the effort behind it is visible up front.
• Embedded app previews now sit in a cleaner line-drawn phone frame, replacing an older frame with a fake browser bar.
• A new dashboard shows which version of each project is live across production, preview and the main branch, so lagging ones stand out.
• Renamed the ‘Shipped’ label to ‘Done-ish’, fixed a LinkedIn link that led nowhere, made a diagram caption readable, and tidied a mismatched link style.

The Weekly’s case study got most of the attention, with a couple of tidy-ups elsewhere on the site.

• You can now toggle between the first rough version of The Weekly and the polished final one, both running live, to see how it changed.
• Every case study now shows a dated timeline of its milestones, so you can follow how the project progressed instead of only seeing the result.
• The next-project link at the end of a case study is now a card, easier to spot and click as you keep browsing.
• On the homepage, the whole of each case study card is now a click target, so a tap anywhere opens it.

Most of the work was words and layout, on the homepage and the-weekly case study.

• The homepage now describes the day job and the side projects in plain words, instead of the boastful placeholder text that was there before.
• The the-weekly case study now lays out the app’s design across three versions, each with a short note on what changed and why.
• Fixed case study dates to show the day and not just the month, and evened up the left and right page margins.

The Weekly is a meal planner Dylan built to try Claude Code, and its portfolio case study now reads in full.

• The Weekly picks a week of supermarket meals, prints the recipes, and fills a real Coles trolley, all in about two minutes.
• The write-up explains why it stayed frontend-only, using a trolley link Coles already published for its shoppable recipe partnerships.
• It ends on the surprise that the whole app was built in four days without Dylan writing or reading a single line of code.

The tooling that deploys the site was missing a program it relies on to run, and that program was added.

You can now open the anecdote design explorer directly on the portfolio, where before it loaded through a third-party proxy with caching problems.