Skip to content
Snippets Groups Projects
  1. Feb 23, 2023
    • Jérémy Bobbio (Lunar)'s avatar
      Update “Code review” for GitLab · 895f2092
      Jérémy Bobbio (Lunar) authored
      Now we have switched to GitLab, code review is done via merge requests.
      Update the process to the new terminology and provided tools.
      
      Let’s also move the `patch-submission` ref from the obsolete Phabricator
      page to the one about GitLab.
      
      Related to #4732
      895f2092
  2. Feb 22, 2023
    • Jérémy Bobbio (Lunar)'s avatar
      Update Git style guide for GitLab · 8b396dc3
      Jérémy Bobbio (Lunar) authored
      As we have switched from Phabricator to GitLab, we now point at GitLab
      documentation on how to automatically link and close issues from
      commit messages.
      
      Improvements on the section about commit messages are thrown in for good
      measure.
      
      Related to #4732
      8b396dc3
  3. Feb 20, 2023
  4. Feb 16, 2023
  5. Feb 13, 2023
  6. Feb 01, 2023
    • Jérémy Bobbio (Lunar)'s avatar
      Restore a link to the API reference in Development section · f13f1620
      Jérémy Bobbio (Lunar) authored
      Suggested by @zack: “it's useful to have it on top (because a lot people
      use docs.s.o for that, at least now), but it also belongs to devel doc,
      so people will look for it on the left as well”
      f13f1620
    • Jérémy Bobbio (Lunar)'s avatar
      Switch to PyData Sphinx theme · b37d4ff8
      Jérémy Bobbio (Lunar) authored
      After merging various parts of Software Heritage documentation in a
      single Sphinx instance, the navigation using the Read The Docs theme
      became seriously cumbersome.
      
      We switch to PyData Sphinx theme: a clean, Bootstrap-based Sphinx theme
      by and for the PyData community. For details, please refer to:
      https://pydata-sphinx-theme.readthedocs.io/
      
      One major upside is that by default supports three level of navigation:
      
      - top-level parts in the header bar (for us, they would refer to
        `devel`, `sysadm` and `user`)
      - a left sidebar for sections in the current part,
      - a right sidebar for the contents of the current page.
      
      This maps really well to our hierarchy.
      
      Some changes made to better navigate the various parts of our
      navigation:
      
      - Rename “Development Documentation” to just “Development”.
      - Rename “Sysadmin Documentation” to just “Infrastructure”.
      - Rename “User Documentation” to just “Usage”.
      - Promote the API reference from Development to the top-level.
      
      Some other improvements to better benefit the new theme:
      
      - Replace the vertical logo with the horizontal one to better fit the
        header.
      - Add links to GitLab, PyPI and status.s.o to the header.
      - Remove the unused Alegreya font.
      b37d4ff8
    • vlorentz's avatar
      8ddbe45f
  7. Jan 23, 2023
    • vlorentz's avatar
      Remove second-level headings from the dev doc + hide TOC · edda8b3a
      vlorentz authored and vlorentz's avatar vlorentz committed
      The only two titles at the second level were 'Important documentation links'
      and 'Content', which look weird and are not very useful.
      
      And this level prevented headings inside package documentation from being
      shown in the TOC at all, which means the TOC couldn't be used to navigate
      within a package's documentation.
      edda8b3a
  8. Jan 13, 2023
    • Antoine Lambert's avatar
    • Antoine Lambert's avatar
      docs: Merge all documentations into a single one · 0e55968d
      Antoine Lambert authored
      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.
      
      Closes #4496
      0e55968d
Loading