Dynamic URLs from API and translated
Unanswered
Siamese Crocodile posted this in #help-forum
Siamese CrocodileOP
Hello to all,
We are doing a study to use Next JS in our next project, but talking to the team, they tell us that they are not sure if it would be viable to have all the URLS in the API (to use a CMS in the back), that Next takes the urls from the API and manages them in multiple languages. Of course, if a new url is created in the API, the page is generated in Next. Example from the back:
from API (both urls are the same but translated, and linked with alternate):
- /articles/running-next-english
- /articles/usando-next-espanol
It seems that the main problem lies in the translation of the slugs in each language, which a priori should be in a static file in Next.
What experiences have you had with this? What key points can we have to solve it? Thanks
We are doing a study to use Next JS in our next project, but talking to the team, they tell us that they are not sure if it would be viable to have all the URLS in the API (to use a CMS in the back), that Next takes the urls from the API and manages them in multiple languages. Of course, if a new url is created in the API, the page is generated in Next. Example from the back:
from API (both urls are the same but translated, and linked with alternate):
- /articles/running-next-english
- /articles/usando-next-espanol
It seems that the main problem lies in the translation of the slugs in each language, which a priori should be in a static file in Next.
What experiences have you had with this? What key points can we have to solve it? Thanks