Migrate Help/Developer to RST?
This is somewhat related to https://gitlab.gnome.org/Infrastructure/wiki-web/-/issues/31, but it is logistically separate.
Right now GNOME Help and GNOME Developer use a somewhat opaque content-management system, and in particular outside of the API reference a lot of documentation is ambiguously out of date. I suggested porting the GNOME Wiki to a Gitlab backend, and for similar reasons it might make sense to port GNOME Help and GNOME Developer to the backend (presumably ReadTheDocs/ReStructuredText) already used by docs.gtk.org.
In addition to docs.gtk.org, other existing RST docs that would make sense to have under a single roof include The Python GTK+ 3 Tutorial, PyGObject, and the Rust-Gtk4 Book. Maybe these would make more sense at docs.gtk.org—like Gtk 4 is—but I don't know if this is the right issue tracker for that. Indeed, the PyGtk 2.0 documentation currently lives at developer.gnome.org, and it would probably be better at docs.gtk.org, alongside everything else Gtk (though obviously it should be marked as deprecated at this point).
While having everything under a single roof (with a common Gitlab backend, split among the relevant project repositories) would just make life easier in the first place, the main advantage ReadTheDocs/RST format offers over the existing help.gnome.org and developer.gnome.org is that the underlying engine is under active development, so using it gives you various "freebie" features, such as including more adaptive layouts, adaptive (Dark Mode) CSS, ePub exports, etc.
One aside—which I emphasized on my other issue—is that any migration should include redirects for any changed URLs, in order to prevent external linkrot.
I personally like writing documentation, and if the GNOME documentation were more straightforward to contribute to, I would be much more inclined to actually do so.