Blogs
Articles on the decisions that actually shape a project — architecture, cost, delivery and the trade-offs behind them.
The single most common commercial mistake in a replatform is losing the URLs that already bring in traffic. A redirect map is cheap insurance.
Drupal has a strong security team and a predictable advisory process. The risk on most sites is not the platform, it is that nobody is watching the advisories.
A meaningful share of cloud spend on a typical estate is recoverable without changing the architecture at all. Start there.
Four measures describe delivery performance well. They are useful for finding constraints and harmful when used to compare teams.
Software people use all day has different requirements from software people use occasionally. Optimising for the wrong one makes experts slower.
Suites get abandoned when they are slow, flaky or testing the wrong level. A deliberate strategy prevents all three.
A PWA avoids app store distribution and gives one codebase. It also gives up some platform capability. Here is how the trade actually falls.
Drupal handles translation better than most content platforms, but the decisions you make in the first week determine whether adding a language later is easy or painful.
Both are mature and both are capable. The decision should follow how structured your content is, how complex your permissions are, and who has to maintain it in three years.
Users judge an app in the first few seconds. Startup time, scroll smoothness and battery drain are what they actually notice.
Governance is largely about being able to explain what a system does, on what data, with what oversight, and to evidence it.
Complete rewrites fail at a high rate. Incremental strangulation delivers value earlier and carries far less risk.
Technical SEO is mostly about making a site easy to crawl, easy to understand and fast. None of it is exotic and most of it is done once.
A slow Drupal site is usually slow for a small number of identifiable reasons. Measure before you cache, and cache at the right layer.
Kubernetes is excellent at problems many organisations do not have. Here is a straight test for whether you are one of the ones that does.
Credentials in repositories remain one of the most common causes of breach, and it is one of the most preventable.
