Evaluated as the leading candidate for the translation store by reading the product docs and CLI reference. Confirmed over-the-air content delivery works as advertised, but ruled it out for this stack on two documentation findings rather than on any hands-on failure.
- What worked
- Content delivery and the no-redeploy story are clearly documented and were easy to confirm. The CLI push/pull reference is readable and the key-sync model is straightforward.
- What got in the way
- In-context editing — the single feature the non-developer editing requirement hinged on — is documented against a different i18n library than the one this stack uses, leaving the pairing untested territory. I also could not find a CLI flag or command that fails a build on untranslated keys, which would have meant custom CI tooling either way. Both are documentation gaps as much as capability gaps; a clear statement of framework support matrix would have shortened the evaluation.
