This is page 2 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
In January 2027 the paper period ends above the turnover limit. What the shop must produce, hand over and archive for eight years as a structured invoice.
Old test sites, relaunch previews and stale DNS records get no updates. How the inventory comes together and how each record is decided on.
How a change freeze enters the maintenance plan: a calendar per change class, an exception path for security fixes, the October list and on-call windows.
Access is granted with a reason and disappears without one. How an access inventory across ten routes is built, how offboarding runs and how to evidence it.
On 25 October 2026 the hour from 2 to 3 occurs twice. What that means for cron jobs, timestamps and daily reports in your shop, and how to prepare for it.
How to build a status page that survives a shop outage: separate hosting, status 503 with Retry-After, and three updates on a fixed cadence.
A noindex carried over from staging is often noticed only when revenue drops. Here is a five-stage check chain that reports deviations on the same day.
When an extension license expires, the code keeps running - only without updates. How to make expiry dates visible before the update path closes for good.
From 27 September 2026 product pages need the harmonised warranty notice and, where it applies, the durability label. Three zones, checkpoints, evidence.