The guides I send to clients before kick-off, made public.
Why neither REST-only nor GraphQL-only is the right call for an enterprise multi-locale CMS site, and how to split by concern instead. Includes the circular-reference problem on full REST payloads, the bundle cost of GraphQL on the client, the decision matrix per call site, the unified fetcher, granular cache tags, the block-as-fragment pattern, locale fallback in one round trip, Live Preview survival, Server Actions for CMA writes, the Algolia Sync API exception, and the migration sequence.
How digital consultancies operate, how they price, and where Danish clients typically overpay.
The questions that reveal whether an agency understands your needs and whether their proposal is realistic.
Cut through the hype: which technical choices have real business impact and which are just buzzwords.
What every technical specification should include to prevent scope creep, miscommunication, and budget overruns.
A step-by-step framework for comparing proposals, identifying red flags, and making informed vendor decisions.
Beyond the initial quote: maintenance, hosting, scaling, and the true total cost of ownership.
How to structure your CMS so marketers can add tracking events without developer intervention. Save tens of thousands in ongoing costs.
Most CMS implementations let authors paste raw URLs. The day someone renames a slug, half your navigation silently 404s. The model that makes that impossible — with a Contentful walkthrough.
The performance gap closed. The native-features gap closed. Why most product apps should default to Expo — and the cases where native still wins.