Analysis: What is our current developer experience
This is a summary of important documentation for GNOME Developers and other parties. It constitutes the current GNOME Developer Documentation. See also this blog post.
- The Application Development Overview (gtk-devel-docs) (unknown maintainer)
- The C API Reference (generated by gtk-doc from GTK+)
- Getting started with GTK+ 3 in C, (maintained by @matthiasc in the GTK+ repository)
- A list of various Guides (from the HowDoI pages in the GNOME wiki) (**unknown maintainer **)
- The Human Interface Guidelines (maintained by @aday in gtk-devel-docs)
- Devhelp provides API reference (maintained by @swilmet)
- Builder (API reference, Auto-completion..) (maintained by @chergert)
- A PDF book on the GTK/Glib platform (maintained by @swilmet).
- Video tutorials on GObject (made by @chergert)
- Video tutorial on GTK+ 3 (made by @bastianilso).
- The Newcomer guide: How to contribute to GNOME's Apps (maintained by @csoriano and @bastianilso)
- The PyGObject website (maintained by @creiter)
- Introduction to Python and GTK+ 3 (maintained by sebp)
- The PyGObject API Reference (maintained by @creiter)
- Builder docs (maintained by @chergert)
- Javascript API Reference (maintained by @ptomato)
- Rust API Reference (maintained by @GuillaumeGomez)
- Rust bindings other binding documentation (maintained by @GuillaumeGomez)
- FreeDesktop API and Documentation (unknown maintainer)
- Application distribution, fx Flatpak (maintained by Flatpak team)
- The GNOME and GTK+ tags on Stackoverflow. (unknown maintainer)
TODO
- Evaluate which are important for our audiences and for the Developer Center
- Find out who is maintaining existing the documentation sources (or if they are at all).
- Make a plan for maintaining documentation sources which currently have no assigned maintainers.
- Do you have additional suggestions to important sources?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information