You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the enhancement you'd like
I was unfamiliar with localization markup within {% schema %} tags and it is used throughout the Dawn sections (e.g. "name": "t:sections.main-product.name") . I'm still unsure how the t: markup really works.
Please let me know if this documentation is located elsewhere and I just wasn't able to find it. (google-fu doesn't play so nicely with colons 😔)
Describe alternatives you've considered
I would also consider updating the readme to include a statement regarding Dawns approach to localization. Many developers won't have the need or resources to build out locale files for new sections and it would be nice to recognize that Dawn is maybe not the best example or at least won't reflect lots of real world use cases in this regard.
Additional context/screenshots
n/a
The text was updated successfully, but these errors were encountered:
Describe the enhancement you'd like
I was unfamiliar with localization markup within
{% schema %}
tags and it is used throughout the Dawn sections (e.g."name": "t:sections.main-product.name"
) . I'm still unsure how thet:
markup really works.I'd like to see better documentation of the localization in the sections documentation here: https://shopify.dev/themes/architecture/sections/section-schema#locales and for the examples to reference how Dawn approaches localization.
Please let me know if this documentation is located elsewhere and I just wasn't able to find it. (google-fu doesn't play so nicely with colons 😔)
Describe alternatives you've considered
I would also consider updating the readme to include a statement regarding Dawns approach to localization. Many developers won't have the need or resources to build out locale files for new sections and it would be nice to recognize that Dawn is maybe not the best example or at least won't reflect lots of real world use cases in this regard.
Additional context/screenshots
n/a
The text was updated successfully, but these errors were encountered: