Why I prefer a static site over a dynamic CMS
This website is deliberately small. It uses restrained typography, generous whitespace, a modest palette and photographs that have room to breathe. That approach extends to the machinery underneath the pages. Instead of asking visitors to pass through a content management system, a database and a collection of extensions, I prefer a set of plain files that can be opened, inspected and served with very little fuss.
For a personal presence, that choice feels unusually direct. Writing is a core part of the process, publishing is occasional, and the content changes slowly enough that an editorial dashboard can create more overhead than value. The aim is to offer pages that load quickly, remain easy to maintain and stay visually consistent as the site grows.
A dynamic CMS is a sensible tool when many people need to publish, when content changes several times a day, or when a site includes accounts, payments and complex catalogues. It trades a little simplicity for convenience at the point of editing. For a small personal domain, I am happy to make a few deliberate choices in a text editor and deploy the result. The benefits are predictable performance, a smaller attack surface, easier backups and hosting costs that do not expand when traffic rises.
That preference is practical rather than ideological. A static build still needs design, writing, accessibility checks and sensible deployment habits. A CMS still needs security updates, database care and attention to how extensions affect performance. The right question is which set of responsibilities suits the site in front of you, rather than which architecture sounds more professional.
Speed that does not depend on a dashboard
A static page can be as simple as an HTML document, a stylesheet and a few images. There is no database query before a visitor reaches the title, and no PHP process assembling the page on every request. Files can be delivered from a CDN edge close to the visitor, while unchanged assets remain cached for days or weeks. The result is less waiting between tapping a link and seeing the words.
Australian connections make that distinction relevant. A household in Sydney or Melbourne may have an excellent NBN service, yet shared connections, congested Wi-Fi and mobile coverage can still interrupt a visit to the train. In regional Australia, fixed-wireless and satellite services offer useful access, but their real-world speeds vary with location and demand. A light page is considerate of these conditions, particularly when someone is checking a reference while travelling or waiting for a connection to recover.
A CMS introduces additional work before the page appears. Themes may load fonts and scripts from other providers; plugins can query APIs; caching may have to be configured properly. Some of those features are valuable on a large publication, but on a quiet personal site they add weight without improving the reading. Keeping the delivery path short gives the content priority and makes a broken third-party service less likely to spoil the whole experience.
Simplicity is a form of maintenance
Files are wonderfully durable. An HTML page, a stylesheet and an image remain meaningful when the fashionable framework, hosting dashboard or publishing platform has changed. I can copy them to another host, read them without special software and keep versions in a private repository. A Git history also records why a page changed, which turns publishing into a controlled, reversible action rather than a sequence of clicks whose consequences are hidden.
The CMS advantage becomes clearer in a busy newsroom or membership organisation. Editors may need scheduled publication, role-based permissions, revision comparisons and content that arrives through structured feeds. WordPress is a familiar choice in the Australian small-business market, where agencies often maintain client sites through plugin updates and support retainers. My concern is that convenience often arrives with recurring costs: subscriptions, plugin licences, specialist maintenance and the risk of an unattended update causing trouble.
A static site asks for fewer moving parts, although it does not eliminate technical work. Images still need sensible dimensions, headings still need a logical order, and links still need testing. Those checks are direct and mostly repeatable. I keep a small deployment routine, use relative asset paths where practical and lean on system fonts where they suit the design. A restrained page can then remain restrained in the browser as well as on the screen.
Publishing should feel calm, not busy
The publishing rhythm matters as much as the architecture. I want a calm process in which a thought becomes a note, the note becomes a finished page, and the finished page goes live without a flurry of administrative activity. I keep my productivity guide close to the publishing routine because it captures the broader approach: reduce competing demands, keep useful material close at hand and make the next action obvious. For this site, that means writing locally, checking the rendered page and publishing a small set of files.
A CMS tends to put editing tools permanently within reach. That can be helpful, but it can also make every visit to the dashboard feel like work. The blank post editor, revision history and notification settings can compete for attention with the actual writing. With a file-based workflow, the browser tab used for drafting can be closed when the session ends. There is still discipline involved, yet the tool recedes once the page has been prepared.
This approach suits a site built around selected writing, photographs and small notes rather than constant conversation. Comments, if included, can be handled by a separate service with clear moderation rules. A contact form can point to a form processor without turning every public page into a full application. The boundary stays visible: the reading experience is static, while the few interactive parts are chosen deliberately and kept independent.
Ownership, privacy and the Australian context
Ownership becomes clearer when a site is made of portable pieces. The domain is rented, and any hosting arrangement can change, but the source files remain available. Exporting content from a CMS is usually possible, yet exports may need cleaning, remapping or conversion before they resemble the published site. With my own files, a move can be as straightforward as copying a directory, updating a deployment setting and checking that paths still resolve.
Australia's privacy framework adds a useful reason to collect less. The Privacy Act 1988 and the Australian Privacy Principles govern the handling of personal information in many Australian organisations, with the applicable rules depending on the organisation and its activities. A static reading page can avoid behavioural tracking, advertising identifiers and unnecessary comment accounts. Those choices reduce exposure, although they are not a substitute for a privacy policy or sound advice when information is genuinely collected.
Commercial email and contact forms deserve the same attention. The Spam Act 2003 sets consent and identification requirements for many commercial electronic messages, and people should have a straightforward way to stop receiving them. A static site does not automatically satisfy those duties. It can, however, keep the contact mechanism simple, send messages from a monitored business address and avoid hidden tracking in the form flow. Less machinery makes review easier, not unnecessary.
Where a dynamic CMS still makes sense
There are projects for which I would choose a CMS without hesitation. A large online shop needs a changing inventory, discount rules, payment connections and order management. A community site may need member profiles and moderation tools. A newsroom may need many editors working at once. In each case, the publishing system supports the underlying job, and removing it would merely push complexity into awkward workarounds.
Australian consumers add practical requirements to that picture. Product pages need clear prices in Australian dollars, accurate availability and information that supports purchases under the Australian Consumer Law. A capable commerce platform can connect stock, GST treatment, shipping and payment records more efficiently than manually rebuilt catalogue files. If the business changes prices or stock every hour, a CMS-backed catalogue is not merely convenient; it can prevent customers from seeing information that has already expired.
For this personal domain, those demands are absent. The content is sparse, the images are selected rather than continuously replaced, and there is no team that needs a shared editorial interface. That is why my personal site is built from a quiet, static foundation. It keeps the public side predictable, preserves ownership of the work and leaves enough energy for the writing and visual judgment that give the site its character. The restraint is the feature, not an interim state waiting to become a larger platform.