Make docs.zarhus.com adhere to specific Zarhus releases

[DaniilKl]

Currently Zarhus Docs does not relate to any versions/releases/revisions of Zarhus components (e.g. Zarhus OS), looking more like notes than a documentation with a specific purpose. This causes guides reproducibility problems and bad user experience.

I think this issue might be related to a bigger issue - Zarhus components releases absence. E.g. the develop zarhus/meta-zarhus branch has 161 commit vs 25 on main.

Because of this the Zarhus developers are starting to place their documentation in the code with the arguments like "the docs.zarhus.com are unstable because of bad versioning or reproduction". This could eventually cause docs.zarhus.com to be thrown away and forgotten.

[pietrushnic]

Zarhus's work needs to be tailored to the given platform with demos. For now, I think it would be challenging to maintain an abstract level, "Zarhus as a framework", from which you can build what you want. We should focus on target hardware platforms and demonstrate this with the public release of images that include clear KAS and a repo tag, showing how to obtain a picture that proves the demo. I have a clear vision of what it should look like.

Another problem we face is that we initially use multiple repositories for documentation. However, we should utilize a single private/public switch, and documentation should be organized in one place, with a clear decision on whether it should be visible to the public or not. Additionally, developers should focus more on documentation and include tests, which should always be part of the deliverables and not an afterthought.