builder¶A class (inheriting from Builder) that takes| www.sphinx-doc.org
Cross-references¶| www.sphinx-doc.org
Writing your pyproject.toml#| packaging.python.org
At this year’s GUADEC, I made a proposal: that the GNOME project should migrate its documentation from wiki.gnome.org to other locations, and then disable its wiki. This blog post describes the proposal in more detail, in order to receive feedback from the wider community.| Form and Function
Who writes the developer documentation for your product? During the early days of my tech career, I worked on a database replication product at IBM. My immediate team had developers and testers but not a single technical writer. I can speak for myself when I say that I never bothered to know who keeps writing the lengthy and complex documentation for every release. Since then, many companies in tech (including companies like IBM) have taken a modern approach to documentation. This “moderniz...| Dewan's Blog
A look into the tech and tools used by Winterbloom| blog.thea.codes
A completely incomplete guide to packaging a Python module and sharing it with the world on PyPI.| Hynek Schlawack
Short post on making minimal changes to derivations in nixpkgs at a project level using callPackage() along with GH-Actions for deployment of sphinx documentation. Background As part of my work on the Symengine documentation1, I had originally thought of leveraging nix for reproducible builds for each of the language bindings with GH-Actions. There exists a derivation in the upstream package repository, but it was outdated (v6.0.0 instead of v6.0.1) 2.| rgoswami.me