-
Notifications
You must be signed in to change notification settings - Fork 562
Publish documentation #1755
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@renehernandez Hey! Thanks for suggestion. But I'm still on hold for this. I believe we don't even have enough love and content in our documentation yet. Let's add more content and publish it in a versioned way only after we are confident that we do have enough love and human resource to maintain it in a meaningful way. |
One thing that I forgot to mention and I think is the main benefit of docs, is that it makes it easy to search, while right now, I have to look at the readme and each file individually on the docs folder. And the documentation size shouldn't matter that much to decide whether we should automate and publish helmfile docs. IMO, I believe that the sooner we start the better. Example: I am building a small utility appfile and I have already published the docs at https://renehernandez.github.io/appfile |
@mumoshu This is an example of how the documentation would look like as a first step: https://renehernandez.github.io/helmfile I know that you don't want to dedicate resources to this for now, but if still makes sense I can open the initial PR that would deploy this automatically |
@renehernandez Maybe it's worth trying then...? I have no experience with Is there any mature alternative to |
@mumoshu Yes, I am OK with taking a leading role on this part of the system. I'll get you a PR by tomorrow |
Of that I am not aware, unfortunately |
I missed this one. I am using a golang script to generate the CLI reference for |
I want to propose publishing versioned docs of helmfiles. A solution such as:
latest
pointing to the most recent tag)would be a great starting place.
Would there be any other requirements out of the box? Otherwise, I can start working on a PR for the implementation
The text was updated successfully, but these errors were encountered: