-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create application docs with moin, publish by loading to readthedocs #1656
Comments
If the goal is publishing docs to readthedocs, using sphinx might be the simpler and well-established approach. |
yes (and no :-) ). I would undestand if this could be a correct tool-chain to create documentation:
but for what I've unserstand I can export from moinmoin and import it directly to Readthedocs. avoiding Sphinx. Is it? Renato |
Editing files with an editor in a git repo and editing wikipages in a browser are two different workflows, and depending on who your users are, will feel comfortable to them or not. |
ok, |
I would like to know if this is the way the 2 SW collaborate or am I wrong |
This is A way the two CAN (or COULD) collaborate. Obviously one can be used without the other one. |
of course...but coul be that the scenario? (moin2 collect doc and RTD publish it in various format)? |
The effort to keep the docs uptodate increases by version and time. When building the docs on rtfd you can use there parts of moin to convert to rst and extend the formats for writings in the sphinx framework. |
still not clear... |
When you make the installation and develop doc and usage doc with the wiki, why do you want to use RTD? Usually I ask developers on a PR to update also the docs in the repo. Writing docs is usually part of the development process. When you move the whole doc maintaining process to the wiki, then it is usually not the developer who changes it. |
@ReimanBauer. So you are telling that I can build docs using a repo (i.e GIT) and directly RTD, without a wiki. But i.e. if I would start a chain where everybody (developer and normal employ) could write doc not just for program documentation, I could manage the "fishing" of docs by a wiki and paste the result to RTD that can produce more kind of docs. |
A possible approach:
The text was updated successfully, but these errors were encountered: