Skip to content

Website Design

I have been building and operating websites since the late 1990s. Over that time, the technologies, platforms, and conventions have changed repeatedly, but the underlying concerns have remained largely the same: clarity, maintainability, and respect for the people responsible for keeping a site running.

This page summarizes that work by pattern and intent rather than by exhaustive inventory.

How this work evolved

My earliest web work involved hand-authored HTML sites, often maintained over long periods with incremental change. As content management systems and frameworks became more common, I worked with a variety of platforms where they made sense, while remaining cautious about unnecessary complexity.

In more recent years, I have gravitated toward static-site approaches and documentation-oriented tooling when the goal is durability, clarity, and low operational overhead.

Across all of these phases, I was typically responsible not just for initial development, but for long-term operation: hosting, updates, content changes, and eventual retirement.

Patterns of work

Rather than treating websites as one-off deliverables, I tend to approach them as systems with lifecycles. Common patterns include:

  • Long-lived personal or organizational sites maintained over many years
  • Sites that prioritize content stability over frequent redesign
  • Small, purpose-built sites that do one thing well
  • Documentation- and reference-oriented sites
  • Sites operated directly by their owners rather than handed off to agencies

In many cases, I served simultaneously as site owner, administrator, designer, and content editor, which reinforced a bias toward simplicity and maintainability.

Representative examples

A small number of sites illustrate these patterns particularly well:

  • OmegaTower.com
    A long-running personal and technical home that has evolved across multiple generations of tooling and content.

  • NGRStudio.com
    An artist-focused site emphasizing longevity, direct ownership, and minimal dependency on external platforms.

  • Danukoria.OmegaTower.com
    A long-running fictional world project where published stories are constrained by a formal, systems-oriented canon defining institutions, authority, and continuity.

  • RefuseForResearch.OmegaTower.com
    A project site supporting a long-running operational system rather than promotional content.

These examples are representative rather than exhaustive.

Role emphasis

Across most of this work, my role extended beyond visual design. I was commonly responsible for:

  • Information architecture and content structure
  • Hosting and operational maintenance
  • Theme or layout implementation where needed
  • Content editing and long-term updates
  • Migration between platforms as requirements changed

Visual aesthetics were treated as important but secondary to clarity, accessibility, and sustainability.

Historical record

Over time, this work has included dozens of sites across personal, organizational, and project contexts. Many of those sites are no longer active, and some were intentionally retired when their purpose was complete.

A complete historical list exists, but is maintained separately as reference rather than as part of this profile.