Where to Get Involved with Gradia or Find Its Documentation

Gradia's official site links directly to four resources for users and contributors: GitHub for code, a localization page for translations, documentation for usage help, and Flathub and Snap Store for installation. If you want to contribute code, translate the app, read the docs, or just install it, one of these entry points covers it.

The official entry points

The Gradia homepage lists these destinations under its "Get Involved" section:

The site describes Gradia as free and open-source software licensed under GPLv3, and states that contributions are welcome.

Contributing code via GitHub

GitHub is the place for code contributions. The site points there for source access and contribution work, though the homepage itself doesn't spell out a branching model, review process, or issue labels — you'll need to check the repository's own README and contribution guidelines once you're there.

A practical first step: browse open issues before writing code, so your change matches what maintainers actually want. For anything non-trivial, opening an issue to discuss the approach first is the usual convention for GPLv3 projects of this kind.

Contributing translations

Localization is listed as a separate entry point, which means translation work is handled outside the main code repository. If you want to help translate Gradia, follow the Localization link from the homepage rather than opening a pull request against the source directly — the site treats these as distinct workflows.

Reading the documentation

The Docs link is the official reference for how to use Gradia. Since the site's own description is brief — it helps you "beautify, annotate, and share screenshots seamlessly on Linux" — the documentation is where you'd go for actual usage detail. The homepage does not reproduce that content, so treat the Docs page as the authoritative source rather than third-party summaries.

Installing Gradia

Two distribution channels are offered:

• Flathub — install as a Flatpak
• Snap Store — install as a Snap

Both are linked from the homepage. Which one to use depends on which packaging system your distribution already supports; the site doesn't rank them or state a preference. Note that the homepage gives no pricing information for either store listing, so check the individual store pages if cost matters to you.

What the site does not cover

The homepage is a landing page, not a manual. It doesn't include system requirements, a feature list, version history, or a contribution workflow. For any of those, go to the linked Docs or GitHub repository. The only firm facts stated on the page itself are the GPLv3 license, the free and open-source status, and the five linked destinations above.