Knowledge
Plain-language guides for people who run websites and the people who build them, written from what we do every day. Start with the basics, grow what works, or go deep into how things are built.
Start
For anyone who owns a website.
Out of stock product pages: what to show instead of a dead end
What an out of stock product page can still do: lead times, alternatives, restock notices, and how to handle discontinued and made-to-order items.
Who owns your domain? What to do when it is in someone else's account
Check who really controls your domain, DNS, hosting and website accounts, what to request from a former developer, and what to do if it is not yours.
A DIY website usability test: hand over your site and say nothing
Run a simple website usability test in an hour: whom to ask, how to pick three tasks, how to watch without helping, and how to turn notes into fixes.
How to install WordPress
How to install WordPress step by step: what you need first, the installation in about fifteen minutes, and ten things to set up right afterwards.
Grow
For marketing, sales and operations teams.
What an automation is really worth once things go wrong
A worked example for calculating the true value of an automation: exceptions, checking, maintenance, net time saved, break-even and when to keep a person.
Fewer website enquiries, better ones: reading a quieter contact form
Clear prices and answers can cut form submissions while qualified enquiries and won deals hold. How to measure enquiry quality, workload and outcomes.
Outdated translations: when the German page promises more than the English one
How delivery terms, specifications and service promises drift apart on a multilingual website, and how to assign owners, flag stale pages and audit them.
Why B2B customers order by email when you have built them a shop
Find out why B2B customers order by email, sort a month of order emails by reason, and decide which features your shop needs and what stays personal.
Build
For developers, product owners and IT.
AI assistants and document permissions: who may get the answer?
How to design an internal AI assistant that respects document permissions: checks at retrieval time, permission sync, caches, revocation and leak tests.
Missed payment webhooks: the payment succeeded, the shop never heard
How to build a shop that survives lost, late and duplicate payment webhooks: durable processing, idempotency, signature checks and reconciliation.
Caching customer-specific prices: when a fast site shows the wrong price
How page caching can show customer-specific prices to the wrong person, which HTTP headers prevent it, and how to test it with two customer accounts.
In preparation
- The European Accessibility Act for small and medium companies, in plain words
- Migrating a website without losing rankings: the checklist we use
- Privacy-first analytics: what you can measure without a consent banner
Have a question we should answer here?
A person answers within one working day. No obligation.