Add documentation for micro-manager installation

[erikscheurer]

The first release of the micro-manager is coming up, adding information on installation on the website would be ideal.
However, as the micro manager is not directly a language binding or an adapter, I am not sure where to put the information. The two options I see are with the provided adapters or in the installation tab under the language bindings.

[uekerman]

IMO, this should go under "tools" and only be linked. The actual content should be in the micro-manager repo. Similarly to e.g. the OpenFOAM adapter.

[MakisH]

Why no branch for the micro-manager here?
I guess the workflow is failing because the pages don't yet exist in the default branch (main): https://github.com/precice/micro-manager/tree/main/docs

       Subproject: imported/openfoam-adapter/docs
      Adding pages: README.md, openfoam-support.md, config.md, get.md, extend.md
         Tutorials: No subproject found at imported/micro-manager/docs
        Subproject: imported/micro-manager/docs
                    ------------------------------------------------
      Jekyll 4.2.2   Please append `--trace` to the `build` command 
                     for any additional information or backtrace. 
                    ------------------------------------------------
/home/runner/work/precice.github.io/precice.github.io/website/_plugins/subprojects.rb:22:in `block in generate': No subproject found at imported/micro-manager/docs (RuntimeError)

[IshaanDesai]

Thanks for noticing this! The website building still fails, but this was definitely an issue.

[MakisH]

I don't know, but I am confused by this line:

Tutorials: No subproject found at imported/micro-manager/docs

Where should the Tutorials: come from?

[erikscheurer]

The pipeline fails because the micro-manager submodule is imported at this commit for some reason and not at develop as specified in .gitmodules.
Any ideas why this is the case?

[IshaanDesai]

The pipeline fails because the micro-manager submodule is imported at this commit for some reason and not at develop as specified in .gitmodules. Any ideas why this is the case?

Perhaps @MakisH has a clue.

[erikscheurer]

Ah it was already described in the README :)
So as I understand, git submodules can't follow a branch but only save a current commit. And therefore every time we update the documentation, we have to open a PR here right?

[MakisH]

So as I understand, git submodules can't follow a branch but only save a current commit.

Correct.

And therefore every time we update the documentation, we have to open a PR here right?

Almost... The website points to specific submodule commits, but triggering this workflow on the website repository updates the submodules. This is done automatically by workflows in each of the source repositories, with such a workflow. You actually should add a similar file here as well.