You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: unify the projects experience and editorial artwork #3922
As a visitor considering Devantler Tech, I want one coherent projects page and subject-specific journal imagery, so I can understand the real work without switching into inconsistent layouts.
Evidence and hypothesis
The maintainer reports that Active and Completed Projects look less polished than Projects and have floating-navigation problems. Browser inspection confirms that the legacy pages use a three-column documentation layout with a taller header, while Projects uses the shared business layout. Journal covers currently mix unrelated visual styles. A single curated catalogue and consistent editorial artwork should make browsing clearer without implying a large team or paid client history.
Acceptance Criteria
One EN/DA Projects page contains the public portfolio, family examples and clearly labelled earlier research; old active/completed URLs still reach the relevant material.
The projects experience uses the shared business header/footer and behaves correctly while scrolling on desktop and mobile in light/dark/system modes.
Existing portfolio drift checks still guard every tracked product and workflow; no technical source material is silently lost.
Journal/project cover illustrations match the green/charcoal theme and their subjects; authentic portrait, product screenshots and factual diagrams remain available, with asset provenance recorded.
RED/GREEN regression tests, production build and browser visitor paths pass; exact-head review and CI pass before merge; live publication is verified.
Success proxy: the catalogue is navigable from one page, legacy routes resolve, covers load without layout shift, and no header overlap or horizontal overflow is observed during named desktop/mobile paths. Validate at delivery; retain human aesthetic judgment rather than claiming conversion improvements. Scope: one website visual repair, medium. No new products, checkout, business/legal facts, or changes to company follow-up #3917.
PR #3923 is MERGED at evaluated head 0b8d0ce9714752d4664597e5baf133961ccd01de; squash commit cc6a4a7b409670dc3914e8deeae2a63770ff0028 has a verified signature. This issue closed through the merge. Publish Pages run 37583136071 completed successfully at that exact merge commit, including both build and deployment. The deployed website source tree matches the reviewed head.
Live verification completed on 2026-10-07:
English Projects and Danish Projects provide one shared catalogue with the technical portfolio and clearly labelled earlier research. Both legacy Active/Completed routes reach the relevant section; actual browser checks also preserved old heading and encoded KSail fragments and opened the matching disclosure.
Journal serves all 14 subject-specific cover illustrations. Ten delivered artwork assets, including responsive project derivatives, were byte-compared with the artifact from the successful Pages run and matched. Responsive image verification used the deployed CI artifact, not a local macOS encoder build.
The authentic founder portrait, KSail product capture, research diagram, thesis and CV links remain available. Illustrations are labelled as illustrations, with recorded provenance. No customer, company or contact facts were invented.
Desktop and 390 × 844 mobile browser paths passed. Danish Dark mode persisted into Journal; the header stayed at viewport top after scrolling, with no horizontal overflow. Light persisted across navigation and System remained selected as the automatic preference.
Introductory prices remain website DKK 2,995 with optional hosting from 99/month, small app 7,995 with 299/month, and web service 4,995 with 199/month. Additional scope and costs remain subject to an agreed quote.
RED/GREEN regression checks, production build, theme tests and all ten affected suites passed. The substantive exact-head review is 5438528181; the legacy-fragment finding was fixed and resolved. All current-head workflow runs settled green before the normal head-pinned merge. The helper's internal code-quality completeness stayed UNVERIFIED/UNKNOWN, not declared complete; fresh CLEAN state and normal GitHub merge enforcement were used without an admin bypass.
All five acceptance criteria are verified. These checks establish delivery and named browsing behaviour, not conversion improvements or a substitute for human aesthetic judgment. Company/contact follow-up #3917 remains OPEN.
Activity
devantler commentedon Oct 7, 2026
Verified live delivery
PR #3923 is MERGED at evaluated head
0b8d0ce9714752d4664597e5baf133961ccd01de; squash commitcc6a4a7b409670dc3914e8deeae2a63770ff0028has a verified signature. This issue closed through the merge. Publish Pages run 37583136071 completed successfully at that exact merge commit, including both build and deployment. The deployed website source tree matches the reviewed head.Live verification completed on 2026-10-07:
RED/GREEN regression checks, production build, theme tests and all ten affected suites passed. The substantive exact-head review is 5438528181; the legacy-fragment finding was fixed and resolved. All current-head workflow runs settled green before the normal head-pinned merge. The helper's internal code-quality completeness stayed UNVERIFIED/UNKNOWN, not declared complete; fresh CLEAN state and normal GitHub merge enforcement were used without an admin bypass.
All five acceptance criteria are verified. These checks establish delivery and named browsing behaviour, not conversion improvements or a substitute for human aesthetic judgment. Company/contact follow-up #3917 remains OPEN.