Swapping out the i18n component


I’m in the process of implementing Project Fluent across some TypeScript and Python projects, and now I turn to the main website, which is naturally made with Hugo.

I see that Hugo has good i18n support via go-i18n, but I would like to share messages and common composable messages across all the projects, so I’m looking into the viability of swapping out go-i18n for a Project Fluent package - so far, I’ve found GitHub - lus/fluent.go: A pure Go implementation of Project Fluent.

Has anyone ever done a swap like this? I don’t know how much of a cross-cutting change it would be, or if the change would be relatively small.