Development Resources
The source code is stored in a git repository at GNOME's git database. Anyone can clone it using the following command:
git clone https://gitlab.gnome.org/GNOME/gnome-documents.git
Alternatively, you can download tarball archives of earlier Documents releases.
Development in Documents is tracked using GNOME's issue tracker. Search the bug tracker for any issues or feature requests you may have. Feel free to work on fixing any bug filed against Documents. If you are a newcomer, you can find some easy bugs to get started with in this list.
Documents's design space
Documents follows a design-based approach for new features. This design space is where the current iteration of the designs can be found.
Documents is written in Gjs (GNOME Javascript) and follows the general GJS style guide conventions. A must read if you are unfamiliar with GJS. GJS is an introspected language - for more information about how introspected languages work, check the GObject Introspection Project.
API Reference for GJS (Glib, GTK+3 etc):
This is an auto-generated API based on the corresponding C API found at GNOME Developer Center. It can be searched via Google (and other search engines) for convenience.
Evince View Library Reference Manual
Documents is based on libevince and the above link is the Evince's public API.
Documents Developers
Most contributors to Documents hang out at #documents on irc.gnome.org. Contributors, users and developers are more than welcome to direct any questions about Documents there. Currently Documents is being developed by:
Christopher Davis (brainblasted) Documents maintainer
Documents was previously developed by:
Debarshi Ray (rishi) Former Documents maintainer
Cosimo Cecchi (cosimoc) Former Documents developer
Alessandro Bono (abono) Former Documents developer
Pranav Kant (pranavk) Former Google Summer of Code student