Closed jarrodmillman closed 3 months ago
Name | Link |
---|---|
Latest commit | 9297cec160c63c4d436f95eefde443aafb7eb353 |
Latest deploy log | https://app.netlify.com/sites/numpy-org/deploys/65f03882327e9c000812c4b5 |
Deploy Preview | https://deploy-preview-734--numpy-org.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
That sounds reasonable to me. I'll defer to @steppi here, since he knows better what the impact on translation machinery is.
That sounds reasonable to me. I'll defer to @steppi here, since he knows better what the impact on translation machinery is.
From my understanding, we can resync Crowdin by closing its pull request and letting it re-open another one, so I think it should be fine.
@steppi @rgommers For the outstanding translations, you need to turn the team page (e.g.,
content/pt/teams.md
) into a bundle (e.g.,content/pt/teams/index.md
):Once you commit that, you will have the following directory structure
Then in
content/pt/teams/index.md
changeto
All the translations will share the same toml files (i.e., the one in
content/en/teams
):FYI, this has nothing to do with the fact that it is the default language. Hugo first looks in each translation's own bundle. If it doesn't find the resouce in the translation's own bundle, it will look in another translation's bundle. If there are mutliple options, hugo will choose the translation with greatest respective
Weight
.Finally, as mentioned in #733, after the next release we will need to rename
grid1
togrid
.