[discussion]: Addition of Harbor CLI Side Documentation

[NucleoFusion]

Topic

For Harbor CLI to move out of Sandbox into Incubation, a major part of it is the addition of documentation to the Harbor Organization Docs.
A problem that occurs with this is that Harbor uses Hugo, which builds static files which cannot be change, Harbor releases happen approximately bi-annually.

To accomodate this, I suggest keeping a CLI-side documentation, not as grand, but up-to-date. So even when our releases are weekly/monthly users can have an updated documentation. Instead of the outdated one that harbor keeps.

And we can just add a tag/mention, on the harbor docs saying, Hey, for more up-to-date docs, have a look at

@bupd @Vad1mo @qcserestipy would appreciate your thoughts

[bupd]

We have man pages which has accurate information

If people create issues followkng the outdated docs we can update it when needed it just needs a redeployment in netlify - much simple

But for now focus too much on nitty gritty details on updating and introducing a drastic change which will again pushback the timelines.

First let's add it to the website. Once we add it there we can change it.

Adding has real org complexity

[qcserestipy]

I agree with @NucleoFusion that it could be handy that the CLI docs are updated more frequently, especially if the harbor-cli releases are moving faster than the harbor ones. But I also agree with @bupd that there is much of complextiy to push this through at first. I guess this issue is a good reminder for us to work on a more automated docs deploy to the harbor website when necessary.

[NucleoFusion]

We can circle back after Harbor has the CLI Docs merged. But I do think, having something simple (as we already have the docs in md) should be considered down the line.
But I agree that for now, priority should be the harbor website docs