What I Learned from Building a Site with Only HTML and CSS

Building this site at mischa-andriessen.com with only HTML and CSS started as a practical exercise in removing layers. Instead of reaching for a framework, component library or page builder, I wanted to see how far a clear document and a small stylesheet could carry a personal presence. The result is deliberately spare: a short landing page, generous space, readable type and photography that does the work of suggesting a life beyond the screen.

The constraint changed the way I planned. Every interactive idea had to justify its cost in bytes, maintenance and attention. A visitor should not wait for a framework to decide how the page looks, and the page should remain useful if a stylesheet fails. That resilience shaped the architecture: semantic HTML, one carefully organised CSS file and a handful of optimised images. It also made the experience quieter, which suited a personal domain more than a software demonstration.

Starting with the smallest useful promise

One of the first decisions was to define what the page actually needed to do. It had to identify me, explain the character of the site and offer a clear route into whatever came later. That sounds modest, but modest briefs are easier to honour. Each heading, sentence and photograph had to support one of those jobs rather than compete for attention.

Without a framework, the work became more deliberate. There was no component library quietly supplying spacing, buttons or a grid, so I had to name the recurring decisions myself. I used familiar HTML elements and wrote CSS rules around them, which kept the stylesheet readable and made later changes less risky. The code became part of the design process instead of a technical aftermath.

Starting small also created room for restraint. A single landing page can establish a voice through sentence length, image crops and the distance between elements before it needs a portfolio or blog. When those foundations felt right, extending the site felt like adding another room to a house rather than rebuilding the address. The initial simplicity was not an endpoint; it was a durable base.

HTML gives content a durable order

HTML is often treated as a delivery mechanism for styled components, yet it carries much of the meaning. A header, navigation list, main region and footer describe the page before any visual treatment is applied. Those elements give browsers, search engines and assistive technology a shared outline. On a small site, that outline is especially valuable because there are fewer visual cues to compensate for a confused structure.

Headings and landmarks also establish a reading path that remains intact on a narrow screen. I avoided choosing elements for their appearance when a more accurate tag existed. Lists contain lists, paragraphs handle extended writing, and buttons are reserved for actions. The visual result is simpler because the markup has already done much of the organising.

That order becomes even more important when the writing is personal. A guide to difficult family conversations depends on readers being able to distinguish setup, context and reflection without visual interference. A clear document lets the stylesheet support that sequence with line length, spacing and links rather than disguising it. Good HTML therefore made the editorial voice feel more direct.

CSS carries the visual voice

Once the structure was stable, CSS could carry the visual voice without taking control of the content. I began with a small type scale, measured line length and generous line height, using a system font stack so familiar letters appeared without a download. Responsive adjustments followed the reading experience rather than a list of device widths. The aim was a page that felt composed on a wide monitor and remained calm on a phone.

Whitespace was treated as active material. A broad outer margin separated the content from the browser, while smaller, consistent gaps showed which ideas belonged together. I avoided decorative containers where a heading and paragraph already established a relationship. This reduced the number of visible edges and made the page easier to scan. It also gave the photography enough silence to register as an image rather than another block of interface.

Colour came from a neutral base with one restrained accent, while text remained dark enough to sustain comfortable reading. Photography was selected for mood and subject rather than placed behind gradients or crowded with captions. Native image dimensions, aspect ratios and object fitting prevented layout shifts without a script. The page gained character from proportion and material choices, not from visual effects competing for attention.

Speed changed what I valued

Performance became a design material once the dependency count fell away. A static page needs no runtime to reveal its main content, and its layout does not depend on data arriving from another service. That made speed an immediate benefit of the simpler architecture. It also made me more conscious of every remote font, image and analysis script, because each one introduced another party to the loading process.

That calculation became the basis of my load time notes: once I removed the framework and reduced the visual system, the page’s priorities became visible. Typography, spacing and one carefully chosen image mattered more than a large bundle of decorative tooling. The lesson was not to chase a perfect score, but to spend network and attention only where it improved the visit.

Images needed particular care. The main photograph loaded normally, while images below the fold used native lazy loading. Explicit dimensions and responsive source information helped the browser select a suitable file. Modern formats reduced weight, with familiar fallbacks included in the markup. The CSS was compressed and checked for unused rules, keeping the critical path small enough that the page felt immediate on an ordinary Australian mobile connection.

Accessibility belongs in the first draft

Accessibility became easier to manage when it was part of the first draft. Semantic HTML supplied much of the basic structure, while visible keyboard focus, a skip link and generous touch targets handled movement and navigation. Colour contrast was checked before the palette felt final, since a restrained design is no excuse for faint text or links that disappear into photographs.

Text resizing and zoom were treated as normal conditions rather than edge cases. Relative units, flexible containers and wrapping content allowed the layout to adapt without clipping sentences. Where movement appeared, the reduced-motion preference could disable it. These details protect people using different devices and settings, but they also make the underlying page more robust.

A clear contact route, descriptive link text and meaningful alternative text complete the practical work. Alternative text explains the purpose of a photograph rather than repeating what can already be seen. Link text identifies its destination, avoiding vague words such as “click here”. Testing the site with a keyboard and then enlarging it on a phone exposed issues that a quick visual review had missed, revealing that accessibility and convenience often point toward the same solution.

Australian realities shaped the decisions

Australian context sharpened several choices. In Melbourne and Sydney, many readers move between apartments, trains, trams and cafés while checking a phone one-handed. That rhythm favours a page that loads quickly, keeps controls reachable and does not hide essential information behind a gesture. A long scroll can suit a quiet personal site, but a visitor may abandon it between a station platform and the next service.

Connection patterns also vary. The NBN reaches most Australian premises, but the technology available ranges by location and some households still rely on mobile data or older fixed-line services. A static page is a sensible default for that mixed network. The same reasoning matters in the local market, where independent retailers, studios, tradespeople and cafés often need one reliable page more than a feature-heavy platform.

Privacy and communication rules keep the static approach relevant. The Privacy Act 1988 and Australian Privacy Principles matter to many Australian organisations, so a page that collects no behavioural data or unnecessary details has less to govern. The Spam Act 2003 shapes how any later email list is introduced and used. Public-facing services must also meet accessibility obligations under laws such as the Disability Discrimination Act 1992, and Australian government practice has made WCAG 2.2 AA a practical benchmark.

Keeping the door open for change

A personal domain should be able to grow without becoming dependent on a complicated publishing system. HTML gives future pages a consistent foundation, while CSS can absorb new layouts and visual adjustments. Adding a project, essay or photography series does not require changing the underlying idea. The site can become more substantial while retaining the speed and clarity of its first version.

Keeping the code understandable matters as much as keeping the appearance controlled. Small stylesheets, consistent naming and a few reusable custom properties make revisions easier to trace. Comments explain unusual decisions without turning the file into a manual. The absence of JavaScript also removes a layer of accidental complexity, leaving behaviour that can be understood by reading the page source.

The finished site is less a monument than a working set of principles. It should load promptly, remain readable at different sizes, reveal its structure to assistive technology and leave enough space for the person behind it. Restraint proved to be an active decision rather than an absence of design, and HTML and CSS provided enough tools to make that decision visible in every line and photograph.