Skip to content
All work

First KodeGo build · 2021

DigiLife Magazine

My first project at KodeGo: a magazine and digital-services site in plain HTML, CSS and JavaScript, with a page per section and a page per writer.

Role
Design and front-end
Stack
HTMLCSSJavaScript
Live
mark123jesper.github.io/digi-life-magazine
Source
GitHub
The DigiLife Magazine home page

01What the build involved

01

Six pages, no build step

Home, business, lifestyle, sports, about us and contact us are six separate HTML files sharing a main stylesheet and adding their own — business.css, lifestyle.css, sports.css. No framework, no bundler, no npm: the folder opens in a browser and works. Making the same navigation, footer and card rhythm behave across six files by hand is where I first felt the cost of repetition, and why componentisation made sense later.

02

A front page made of parts

The home page is a masthead, a category dropdown, a social bar and a grid of article cards that drop into their sections. Categories that were not part of the assignment stayed as placeholders in the menu rather than pretending to be pages, and every section got its own accent so the sections read apart at a glance.

03

A page per writer

The site had three authors, so it got three author pages — francis.html, mark.html and jonaadres.html — with a short bio and a portrait. Nobody asked for them. They were the first time I built something because a site felt unfinished without it, which is roughly the instinct the rest of this portfolio runs on.

02What it left behind

Outcome

Six section pages and three author pages, live on GitHub Pages, each section with its own stylesheet on top of a shared one and no build step anywhere. It was the first project I shipped end to end, and the first where I added pages nobody asked for because the site felt unfinished without them.

Another pass

Six hand-copied headers are the lesson. One templating pass — even a static one — would have paid for itself the first time the navigation changed, and the section stylesheets bought less than they cost. I would also design the narrow layout first: the mobile version of each page was an afterthought here.

03Inside the product

Each section kept its own stylesheet on top of the shared one, so the business page could carry an accent and a card rhythm the sports page did not.
Six hand-built pages with the same masthead, dropdown and footer — and no build step between editing a file and seeing it in the browser.

Click any screenshot to view it full size

Next case study

(dot)Logix

A group build for a fictional web-development studio: a scroll-driven Bootstrap front end with a full-screen sidebar menu, a preloader and SASS partials compiled into one stylesheet.