Rather than computing automatically, this would allow for key-based translations to be passed in:
<Chunk contentKey="home.greeting">{t('home.greeting')}</Chunk>I still recommend letting the content itself become the key, but this helps disambiguate when strings are the same but in different contexts (e.g. Sign Up buttons on different product plans)
Rather than computing automatically, this would allow for key-based translations to be passed in:
I still recommend letting the content itself become the key, but this helps disambiguate when strings are the same but in different contexts (e.g.
Sign Upbuttons on different product plans)