35 posts
Sending messages people did not ask for damages trust and breaks rules. Here is how our platform treats consent, unsubscribes and suppression as featu...
Testing payments is essential, and mixing test transactions with real ones is dangerous. Here is how we keep test and live money clearly separated.
Saving the wrong change should never mean losing the right version. Here is how revision history works for pages and blog posts in our platform.
Images, documents and exports are some of the most personal data a customer stores. Here is how our media library keeps every file in the right accoun...
The same logo gets uploaded again and again. Here is how a simple file fingerprint keeps media libraries tidy without ever mixing one customer's files...
Slow work like sending email or resizing images happens in the background, long after the request ends. Here is how our jobs carry the right customer...
When a website moves to our platform, every image, font and file comes with it. Here is why we never leave a page depending on the old host, and how w...
When records come from another system, keeping their original identifiers makes imports safe to repeat and relationships possible to rebuild. Here is...
Imports change a lot of data at once, so we never start one without a verified recovery point. Here is how the automatic backup step works and why it...
In a platform where one person can belong to several customer accounts, a simple list of users can leak names across accounts. Here is the pattern we...
A payment that never reaches the accounting records creates work and risk later. Here is how our payment flows connect to the books from the very firs...