I build Websites

Your website is often the first contact with your business. It should show what you do, make important information easy to find, and give people a clear reason to get in touch.

Whether you’re starting a new website or working with one that already exists, I can help. That might mean building something from scratch, improving an existing site, adding new functionality, or fixing parts that have become difficult to maintain.

The approach depends on what your business needs. Sometimes a few focused changes are enough, while other projects need a new foundation.

Performance, accessibility, responsive design, and web standards are part of the work from the start. The result is a site that works well today and stays manageable as your business changes.

Websites I build

Every website has a job to do. I choose the design, technology, and level of complexity around that job and what makes sense for your business. Some projects need a simple, low-maintenance site. Others benefit from custom functionality and more involved interactions.

  1. Dynamic websites

    Dynamic websites make sense when content, users, or data change regularly. I use them for things like CMS-driven sites, member areas, customer portals, and web applications where the website needs to respond to what’s happening.

    • PHP
    • Tempest
    • Kirby
    • Laravel

  2. Static sites

    Static sites are a good fit when content doesn’t need to change on every request. They are fast, reliable, and straightforward to host, which makes them a good choice for marketing sites, documentation, and blogs that should stay easy to maintain.

    • Jekyll
    • Next.js
    • Nuxt.js
    • Zola

  3. Landing pages

    A landing page gives a specific offer, product, or campaign a clear place to live. I keep the page focused on what visitors need to know and make sure the important actions are easy to find and measure.

    • SEO
    • E-Commerce
    • Analytics

A good website should make things easier for your business and the people using it. It should load quickly, work across devices, and remain easy to change when things move on. I keep those things in mind from the beginning, so the website can stay useful long after it goes live.

I also build Backends

The visible part of a website is only one piece of the system. I build the backends that handle things like content, orders, payments, users, and data.

That might mean a CMS you can manage yourself, an e-commerce backend, or a custom system that connects your website to the tools you already use. I keep these systems reliable, understandable, and maintainable as they grow.

See how I build backends

Best Practices

A website should work well for the people using it and the people maintaining it. I build with web standards, responsive design, accessibility, and performance in mind from the beginning. These choices make a site easier to use, more consistent across devices, and easier to maintain over time.

  1. Web Standards

    Web standards give browsers a common way to understand and display a website. Following them makes websites more predictable, easier to maintain, and more likely to work well across browsers and devices.

    • HTML
    • CSS
    • JavaScript
    • DOM

  2. Responsive Design

    People use websites on screens of all sizes and with different input methods. I build layouts that adapt to those differences, so the content remains readable, useful, and easy to use whether someone is on a phone, tablet, or desktop.

    • Images
    • Typography
    • Media

  3. Accessibility

    Accessibility makes a website usable by more people, including people who use assistive technologies. Semantic HTML, keyboard navigation, readable content, and clear interactions are some of the basics I consider when building a site.

    • Semantics
    • WCAG
    • WAI-ARIA

Good technical decisions tend to disappear into the finished website. Pages load when they should, content works on different screens, and people can use the site without having to think about how it was built. That makes the website more useful today and gives you a better foundation for whatever comes next.

I also build Stores

An online shop has to fit the way your business actually works. I build shops around your products, customers, and workflow, with the parts you need for payments, shipping, inventory, and order management.

The result should be straightforward to run and reliable when customers are ready to buy. I can also connect the shop to the other tools your business already uses.

See how I build online shops

Interactive Websites

Some websites need more than pages and links. Interactive features can make complex information easier to understand, guide people through a process, or simply make a site more pleasant to use. I build these interactions with the technology that fits the project, keeping them fast, reliable, and maintainable.

  1. Web Components

    Web Components provide a way to build reusable interface elements that work without depending on a specific framework. They can be useful for design systems, embedded widgets, and components that need to live across different websites or applications.

    • Shadow-DOM
    • Templates
    • Slots
    • Scoped Styles

  2. React

    React is useful when a website starts behaving more like an application. I use it for interfaces with complex interactions, shared components, and client-side functionality that would be difficult to manage with simpler approaches.

    See how I use React

    • Components
    • JSX
    • State Management
    • Routing
    • Client-Side Rendering

  3. Vue, Astro & More

    There are plenty of good tools for building websites, and the most popular one isn’t always the right one. I also work with Vue, Svelte, Astro, and other frameworks when they make sense for the project.

    • Vue
    • Svelte
    • Astro

The technology should support the experience rather than become the experience. Sometimes a few carefully built interactions are enough. Other projects need a larger application underneath. I choose the simplest approach that gives the website the behaviour it needs and can still be looked after later.

Let’s build your website

Starting a new website, improving an existing one, or trying to fix something that’s getting in the way? Tell me what you have in mind.

You don’t need a technical brief. A rough idea, a specific problem, or a website that’s causing you trouble is enough to start a conversation.

Tell me about your project

Photo of Tobias Tom