Closed jorgemoralespou closed 8 months ago
There are instructions for how to run the site locally and test your docs here: https://github.com/carvel-dev/carvel/tree/develop/site If that needs to be updated, then let us know!
That needs to be linked from the main README.md as otherwise, how would one know how to get to that specific folder? I guess that maybe it's obvious for hugo users or for carvel contributors, but not for anyone else.
Sounds like a great idea, what say you @microwavables ?
This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.
Moving over my comment from the issue i opened, https://github.com/carvel-dev/carvel/issues/683, which is a duplicate of this issue.
Consider updating the contributing guide, https://carvel.dev/shared/docs/latest/contributing/, or the Development guide to include information on contributing to docs. Or make a new page in this section for contributing to docs.
Some things to consider including:
This issue is being marked as stale due to a long period of inactivity and will be closed in 5 days if there is no response.
Describe the problem/challenge you have I was reading the kbld docs and there was something not very clear and @cppforlife asked me to contribute a better explanation. I went ahead and after some search in kbld project I came to understand that the docs are all in this repository. I then tried to find where the specific file to be changed was located, and after a lot of searching got to it https://github.com/carvel-dev/carvel/tree/develop/site/content/kbld/docs and then I didn't know what brancch of the docs to add the contribution, as it's a better explanation of a feature that already exists for a long time. Then I was wondering how I can test the changed docs, but there's no way to know how to test this site locally. So I have given up :-(
Describe the solution you'd like I would like a doc on the docs repo and how to contribute to the docs (and test locally before doing a PR).
Anything else you would like to add: :-(