[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fY1LfTsW7SLzVTqgqheEzF_dpbJKjzgb_NaatM6DKsvc":3},{"id":4,"title":5,"teaser":6,"body":7,"slug":8,"date":9,"tags":10},"031d1f3a-1dec-4fa9-a4fc-0419f463fc42","Five Pushes to madsnorgaard.net Over Two Days","A detailed look at five incremental commits to madsnorgaard.net over two days, including feature branch work fixing lightbox control overlaps and the value of frequent, focused pushes.","I made five separate pushes to the madsnorgaard.net repository between yesterday and today - a burst of iterative work that represents the kind of incremental development rhythm I fall into when refining interface behavior and fixing edge cases. The commits span both the main branch and a feature branch focused on lightbox controls, with the most recent push landing at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002Ffac289a74d7a...aa47ec29beb9\">aa47ec29 on main\u003C\u002Fa>.\n\n\u003Ch2>What the commit history shows\u003C\u002Fh2>\n\n\u003Cp>The sequence of pushes tells a story of focused iteration. The earliest commit in this batch moved main from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002F032f5c3d1034...af9b17840cbb\">032f5c3d to af9b1784\u003C\u002Fa>. That was followed by a push from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002Faf9b17840cbb...ffd8a1494fdc\">af9b1784 to ffd8a149\u003C\u002Fa>, then another from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002Fffd8a1494fdc...fac289a74d7a\">ffd8a149 to fac289a7\u003C\u002Fa>, and finally the most recent push from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002Ffac289a74d7a...aa47ec29beb9\">fac289a7 to aa47ec29\u003C\u002Fa>.\u003C\u002Fp>\n\n\u003Cp>In parallel, I worked on a feature branch called fix\u002Flightbox-controls-overlap. That branch received its own push, moving from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fmadsnorgaard\u002Fmadsnorgaard.net\u002Fcompare\u002F32e6ad9c126a...b33077c3fa58\">32e6ad9c to b33077c3\u003C\u002Fa>. The branch name is descriptive - this was work to address an interface issue where lightbox navigation controls were visually colliding with other UI elements.\u003C\u002Fp>\n\n\u003Ch2>Why this pattern matters\u003C\u002Fh2>\n\n\u003Cp>When I am deep in interface refinement work, I push frequently. Each commit represents a small, testable change - a CSS adjustment, a layout tweak, a touch event handler fix. This approach keeps the change surface small and makes it easier to isolate what broke if something goes wrong. It also means the commit history becomes a readable log of problem-solving steps rather than a monolithic \"fixed everything\" commit that obscures the actual work.\u003C\u002Fp>\n\n\u003Cp>The feature branch for lightbox controls suggests I was working on a specific interaction problem that needed focused attention before merging back to main. Lightbox controls - the previous\u002Fnext buttons, close icons, and navigation hints - need careful positioning to avoid overlapping with image content or viewport edges, especially on mobile devices where screen real estate is constrained. A branch dedicated to this problem indicates it was thorny enough to warrant isolation from other ongoing work.\u003C\u002Fp>\n\n\u003Ch2>The technical context\u003C\u002Fh2>\n\n\u003Cp>This site runs on Nuxt 3 with a Drupal 11 headless backend. The frontend handles all presentation logic, including image galleries and lightbox behavior. When I work on UI components like lightboxes, the changes are typically scoped to Vue components, CSS modules, and sometimes composables that manage state or interaction logic.\u003C\u002Fp>\n\n\u003Cp>The five pushes over two days suggest I was testing variations, deploying to a preview environment, observing behavior across different viewport sizes, and iterating based on what I saw. This is how interface work progresses - not in single perfect commits, but through cycles of adjustment and validation.\u003C\u002Fp>\n\n\u003Cp>These commits represent maintenance work that does not announce itself but keeps the site functioning as intended. The kind of work that matters most when you are the only person responsible for every layer of the stack.\u003C\u002Fp>","five-pushes-madsnorgaardnet-over-two-days","2026-06-20T19:55:42+00:00",[]]