pull down to refresh

Couldn't agree more, we're using i18n for providing language agnostic components, it is a difficult tradeoff to centralise all translations or keep them at the component level. But both options are provided in the template as it currently is.
Happy to hear you way on localisation as heavy as we do, providing user language matching content is a way to make a difference 🚀
ahh nice. did not know about i18n. looks interesting. From a user perspective, it is nice to have localization centralized. In Grav, you get one txt file with all strings in it (quite easy to translate after that. Where it becomes tricky is in localizing urls/images/categories/tags/labels etc. This is not solved very good in grav.
reply