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
{{ message }}
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
Rather than including different .md or .html files for page content as translate files (thus duplicating markup) would it be possible to separate out different .yml files for each of the pages while still referencing them as such: {% t page.home.section.hero.buttons.new-chart %}
Thank you for your work on this!
The text was updated successfully, but these errors were encountered:
Hi @aulneau, currently the plugin only searches for translations that exist into a single YAML file for each language, for example en.yml for English and pt.yml for Portuguese.
You can avoid duplicating markup by creating HTML layouts, and your .md files should have the minimum markdown markup possible.
You can avoid markup redundancy by removing markup from .md and placing them into HTML layouts and includes. Try using the YAML files for small strings and .md files only for long texts.
If I could see your site, maybe I could help more.
Hello!
Rather than including different
.md
or.html
files for page content as translate files (thus duplicating markup) would it be possible to separate out different.yml
files for each of the pages while still referencing them as such:{% t page.home.section.hero.buttons.new-chart %}
Thank you for your work on this!
The text was updated successfully, but these errors were encountered: