Stringtale

The client asked for a "quick" text update. It's just a tiny tweak to some static text.

Static text is content that doesn’t change often, like button labels or error messages. It’s usually managed in the code, not in a CMS, because it’s faster and simpler that way. Or at least, it’s supposed to be.

The dev dropped everything, switched projects, loaded the codebase, and made the edit. However, the client’s instructions weren’t clear, and a typo slipped in. The update went live.

An hour later, the client called. Furious. "This isn’t what I asked for!" They demanded it be fixed immediately. The developer switched projects again, updated, and redeployed. The client was annoyed, and the developer was upset about switching work twice.

By the time it was resolved, the afternoon was gone. All for a "simple" update.

Over the years, we tried everything to avoid these headaches: CMS setups, i18n files, separate JSON files, and shared text docs. Nothing worked smoothly.

We decided it was time to fix this. For good. That’s when we started building Stringtale.