I recommend using this package: https://github.com/spatie/laravel-translatable?spm=5aebb161.2ef5001f.0.0.5fb8c921cBCCGc. I think it is the best one that fits your problem.

If you prefer not to use the package or if you want more control, I would create a separate table for translations. This is particularly useful if your application has a lot of dynamic content and you need to handle translations in a more structured way. For static content or less frequent changes, translating it on the frontend could also be a viable option.

For example, I worked on a project where I had to manage data translations, and due to technical needs and limited traffic, I chose to create a separate table. This approach worked well because it allowed me to easily scale the translations and ensure the data was structured properly.