Vulnerability notes, site pentests and audits
Recent vulnerabilities in plain language, and how a website pentest and a security audit work for companies.
A short visual identity: why a site and a build need it
A chaotic look cuts trust before the offer is read. A short guide saves colour arguments during layout.
A site and 1C: what to synchronise first
Products, prices, stock and orders do not have to travel in the first export. The source of truth is better named before the exchange.
An account area: which paths to put in at the start
An account area breaks when every future role is put into the first version. At the start one finished path is enough.
Desktop software: when a browser is no longer enough
A warehouse, offline work and hardware often live more stably in a workstation program than in yet another web admin.
A PWA or a store app: how not to choose by fashion
An installable page covers part of the job without a store. A store is needed when the path does not live without it.
Support after launch: why "handed over and forgotten" breaks a site
After release, browsers change, edge cases appear and dependencies receive fixes. Without an owner the site ages in silence.
A redesign without losing leads
A new homepage should not take the phone, the form and the old ad links with it. Traffic after launch is measured, not celebrated.
A site in two languages: how not to create duplicates in the index
A "translate this page" widget is not a second version of the site. You need addresses, a link between them and living text.
Development and cybersecurity in one team
Two contractors argue about whose hole sits on the seam. One release calendar removes that seam.
What site maintenance includes, and what is already a new task
A support pack breaks when a new section is quietly placed inside it. The boundary is better written before the first argument.