How the work is going
What is already in LocalesFS, and the pieces that are still ahead.
LocalesFS started as a place to keep translation keys, languages, and files together. The recent work has been about making that loop usable for a team, and for the scripts that ship the product.
You can create a project, import JSON, YAML, CSV, PO, and properties files, edit strings, and export them again. A project token, or a signed-in API call, can pull a bundle for an app. Glossary terms and review tasks already live in the workspace.
The API now covers the part a release pipeline needs. You can create and update keys, subscribe to signed webhooks, and ask for a QA report before you ship. The checks look for empty strings, missing languages, placeholder drift, and text that is longer than the key allows. You can also open a review task and add a teammate by email.
The site follows the color scheme of the device. Pro and Enterprise billing goes through Stripe. Bring your own model key when you want drafts billed to your provider instead of a shared pool.
What is still ahead is the quieter tooling: translation memory, branches, and a style guide. Those are not in the product yet. The path that works today is the one above: keys in, a review, a QA check, then an export.