Whats the best practice to use strapi also for static content management

Discussions
1

I am using strapi more from a perspective of a cms but i found the translate features (including localazy) interesting also for static content. By that i mean all the texts that are found on button captions and so on. I could think of using repeatable components but the backend interface for it in practise is not very productive. It would need an ui that would allow to overview and edit all entries without accordion effects and such. Is there a better way?

2

I dont understand exactly what you want to achieve.

However maybe you just want to consider a simple translations-SingleType with a JSON-Field.
en:

{
"loginBtnLabel":"Login",
"logoutBtnLabel":"Logout",
...
}

and if your site is visited in another language the translations-JSON of this language is fetched & used?