How to Contribute to or Report Issues with OpenDyslexic

You can contribute to OpenDyslexic in two main ways: report bugs or request features through the project's source repository, or get involved with the design work itself. The font is developed in Glyphs.app, and its source is hosted on the Hackers.town Forgejo instance. The OpenDyslexic site explicitly invites help "by sharing bugs or requests," so issue reporting is the intended first step for most contributors. For general contact, the site lists Mastodon and a support email address.

Report a Bug or Request a Feature

The site does not publish a step-by-step issue template, so the exact menu labels and form fields on the Forgejo instance aren't documented here. What is confirmed is where the work lives and what kind of feedback is wanted.

What to prepare before you file

A useful report gives the maintainer enough to reproduce the problem. For a typeface, that typically means:

• The font file and version you installed (the site notes recent builds are added to Itch.io, and a "new release" was announced in its news feed).
• Where the problem appears — e.g., a specific glyph, a diacritic, spacing, or rendering in a particular app, ebook reader, or browser.
• Your environment — operating system and the application used, since rendering can differ between them.
• A screenshot or sample text showing the issue, if possible.

Where to submit it

1. Go to the Hackers.town Forgejo instance referenced on the OpenDyslexic site.
2. Locate the OpenDyslexic source repository there.
3. Open a new issue describing the bug or request, using the details above.

Expected result: your report becomes a tracked item the maintainer can review alongside other work. Because the site frames this as "sharing bugs or requests," a clear, reproducible description is the main thing you control.

Common sticking points

• No public issue template is documented. If the repository's issue form asks for fields you don't recognize, fill in what you can and put the rest in the description.
• Version drift. If you downloaded from Itch.io some time ago, check whether a newer build exists before reporting — the issue may already be fixed.
• Rendering vs. font bugs. A problem that appears in only one app may be a rendering issue rather than a defect in the font itself; note the app so the maintainer can judge.

Contribute to the Design Work

If you want to help beyond reporting, the site states that work on OpenDyslexic is done using Glyphs.app and that the source is hosted on the Hackers.town Forgejo instance. That means design contributions run through the same repository.

Practical conditions to check before starting:

• You need Glyphs.app to work with the source files as the project does.
• Coordinate before large changes. The site doesn't describe a contribution workflow, so opening an issue or contacting the maintainer first avoids duplicated or conflicting work.
• Respect the license. OpenDyslexic uses the SIL-OFL license, which permits personal, business, educational, commercial, book, ebook reader, application, and website use. If you plan to redistribute a modified version, review the SIL-OFL terms — the site grants broad use but does not spell out modification-and-redistribution rules in detail.

Reach the Maintainer Directly

For questions that aren't bugs — licensing clarifications, donation alternatives, or general contact — the site provides:

Donations are optional; the site states there are no mandatory fees and that you can download and use OpenDyslexic for free.

A Quick Decision Guide

• You found a rendering or glyph problem → file an issue on the Hackers.town Forgejo repository with version, environment, and a sample.
• You have an idea for a new feature or glyph → same place, framed as a request; check recent news first in case it's already planned.
• You want to edit the font itself → use Glyphs.app and work from the hosted source, coordinating with the maintainer.
• You just want to support the project → donate via Itch.io or Patreon, or subscribe; all optional.
• You need a direct answer → use the Mastodon or support email listed on the site.