Insights on e-commerce, web development and digital solutions
Here you find our articles about online shops, websites and web tech. We explain new rules, tools and good ways of working. You can filter the articles by topic. At the top of an article you find a short version in plain words. Ask us if something is still not clear.
After 31 December 2026, the PHP project no longer publishes security fixes for PHP 8.2 (php.net). This guide shows how WordPress websites and WordPress shops can move to PHP 8.3 or 8.4 before the end of the year: inventory, compatibility check, staging test and switch.
Stolen credentials from other providers’ leaks run against your login form, spread across many addresses and at ordinary speed. What counting per account achieves, where the block list check applies, what a second factor devalues and which response path holds after a takeover.
Almost every grown shop has one account that may do everything. What a role cut along the actual tasks looks like, which rights belong apart and what happens on the day an account leaves.
More than half of all web traffic now comes from machines. A shop that does not separate collectors from customers ends up throttling the wrong requests.
Ransomware and human error hit every shop. This guide shows how tested 3-2-1 backups, defined RTO/RPO targets and a documented recovery plan form a resilient contingency plan – and how disaster recovery differs from monitoring.
A shop's largest attack surface is not the frontend, it is the build. How supply chain attacks via npm and Composer actually unfold, and which measures catch them beforehand.
As soon as a shop gets an AI advisor, a new attack surface opens up: language models do not separate instruction from data. What that means in practice and which layers hold.
The Cyber Resilience Act affects everyone placing products with digital elements on the EU market. The reporting duty has applied since 11 Sep 2026, CE marking and SBOM follow from 11 Dec 2027. What online shops should do now.
From 2026 all 64 new PCI DSS 4.x requirements are binding. Script management, MFA and tokenization for online shops, implemented pragmatically.
Larger targets, terms explained, input help, clear focus, no time limits
You decide which optional data processing to allow.
Our anonymous reach measurement runs without cookies and without IP storage, including campaign parameters in links – we do not ask for consent for it because none is legally required.
Strictly required: language preference, core site functions and storing your cookie choice. Without these the site does not work. Settings you choose yourself (light/dark appearance, accessibility) are kept in your browser's local storage only once you choose them; "Reset" in the accessibility settings removes them.
Records your interactions (clicks, scrolling, inputs) pseudonymously so we can spot usability issues. Form field inputs are masked automatically before storage; your IP address is not saved with the recording. Served from our own domain, no external tool. Opt-in, revocable any time.