docs: Merge all documentation into a single one
These changes allow to build all SWH documentations (developmment, system administration and user) using a single sphinx-build command, meaning they are now merged into a single one with shared index of references.
Development documentation is now rooted to docs/devel, user one to docs/user and sysadmin one to docs/sysadm so a good amount of files were moved.
A couple of configuration files and makefiles were updated to reflect that change and the building / cleaning processes were made more reliable.
Calling make in root directory of swh-docs will execute the development build of the documentation in a tox environment while calling make in docs folder will use the current virtualenv.
It remains possible to build each documentation in a standalone way by calling make in their root directory.
Related to #4496 (closed)
Merge request reports
Activity
changed milestone to %Bootstrap user documentation on docs.s.o
assigned to @anlambert
added 1 commit
- 8956f0c7 - docs: Merge all documentation into a single one (WIP)
added 1 commit
- 74ea1152 - docs: Merge all documentations into a single one
added 1 commit
- be771362 - docs: Merge all documentations into a single one
1 #!/usr/bin/env python3 2 # -*- coding: utf-8 -*- 3 # 1 # Copyright (C) 2017-2022 The Software Heritage developers changed this line in version 8 of the diff
mentioned in merge request swh/infra/ci-cd/swh-jenkins-jobs!154 (merged)
Thanks a lot for this work!
There's a few intersphinx links left to the swh-sysadm separate docs build, may be worth cleaning them up directly (grep for
swh-sysadm:
).I don't think the transition will break any links, as long as we publish this new documentation at the root of https://docs.softwareheritage.org/ (which was our intention? See discussion in swh/infra/ci-cd/swh-jenkins-jobs!154 (merged))
There's a few intersphinx links left to the swh-sysadm separate docs build, may be worth cleaning them up directly (grep for
swh-sysadm:
).Thanks for spotting, there is also a couple of
swh-devel
ones to remove.I don't think the transition will break any links, as long as we publish this new documentation at the root of https://docs.softwareheritage.org/ (which was our intention? See discussion in swh/infra/ci-cd/swh-jenkins-jobs!154 (merged))
That would be ideal indeed to not break the current links or we could redirect to docs.swh.org/sphinx/devel/* ?
That would be ideal indeed to not break the current links or we could redirect to docs.swh.org/sphinx/devel/* ?
I'm not fond of the idea of adding an implementation detail (
/sphinx/
) to the canonical path of all our documentation, and I don't foresee any blockers to pointing docs.softwareheritage.org directly to the new root of the built documentation.Is removing the target option in jenkins job conf swh/infra/ci-cd/swh-jenkins-jobs!154 (diffs) is sufficient to upload at the root ?
Ah, and the question I asked on IRC:
The TOC on the left column of the devel main page https://jenkins.softwareheritage.org/job/DDOC/job/builds/25/SWH_20Documentation/devel/index.html is pretty empty; would it be possible to give it one more level of toctree?
enabled an automatic merge when the pipeline for 64e03f5e succeeds
mentioned in commit swh/infra/puppet/puppet-swh-site@4be7726b