How Jag Journey, LLC designs, builds, tests and ships its own software, and the principles behind each decision.
100 posts
Every new capability raises the same question: build it ourselves, reuse something we already have or rely on a provider. Here is the reasoning we use...
Adding dark mode at the end of a project is painful. Here is how designing with color tokens from the start makes both modes readable, consistent and...
Passwords, keys and session data have a way of leaking into places nobody intended. Here are the habits we use to keep secrets where they belong.
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...
Documentation that lives far from the code goes stale quickly. Here is how we organize docs inside each project so they stay current, findable and use...
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...
Plans include limits on things like websites, storage and categories. Here is how we enforce them clearly, with notices instead of silent failures and...
Our team uses AI for internal work, and customers use AI features in their own accounts. Here is why those two worlds are kept apart in access, billin...
Animations can make a website feel alive, and they can make some people feel unwell. Here is how we design motion that respects the reduced motion set...
We never deploy by logging into a server and running commands. Every change travels through the same automated pipeline. Here is why that discipline m...