Add docs for maintainers and enforce hugo version #7
Conversation
melissawm
commented
Sep 17, 2024
melissawm
commented
- Make sure the site builds with the scientific python hugo theme
- Draft documentation for maintainers
- Also creates .gitignore
- Make sure the site builds with the scientific python hugo theme - Draft documentation for maintainers - Also creates .gitignore
|
Expand on the fact that we have an extra layer of indirection throught the repos at scientific-python-translations org. |
|
Also, the Create translations PR targets the scientific-python-translations repos, NOT the final website repos (this is only true for NumPy.org) |
|
|
||
| ## Setting up a language switcher | ||
|
|
||
| This work is in progress - follow (issue #) for details. |
There was a problem hiding this comment.
We should create an issue to update folks on how this is going.
There was a problem hiding this comment.
Thanks @melissawm. I made some suggestions for the part about hiding duplicates, and the description for how to resolve merge conflicts.
Co-authored-by: Albert Steppi <[email protected]>
Co-authored-by: Albert Steppi <[email protected]>
…nslations.github.io into add-docs
|
I think this is good to merge. |
|
Hi @goanpeca - would you take a look if you have some time? I think you would be the ideal reviewer as you are now onboarding into this process. Thank you! |
There was a problem hiding this comment.
I am not sure what it is, but I found this a bit hard to follow, it almost feels like set actual steps needed by maintainers are intermingled with a lot of implementation/caveat details about Crowdin and how the integration is managed.
Though, I do not have a concrete proposal as to how to improve the docs right now, perhaps keep a TLD;R or summary of what maintainers actually need to do and then refer to the rest of the content as an extended guide?
|
Ok - I've tried reorganizing a bit to make the steps clearer and the information about crowdin internals less intrusive. |
