About

What this site is

This is a bilingual informational guide for applicants and sponsors preparing for U.S. permanent residence in English and Spanish. It maps all 48 immigrant-visa pathways. Today, 46 pathways have at least one supported personalized checklist path, 1 pathway has planning guidance only, and 1 pathway is orientation only. Checklist support depends on the exact green card path, processing context, and, for consular cases, sometimes the interview post. The goal is to help a first-time reader understand what is supported today, what still needs to be verified, and when a licensed attorney is the right next step.

Maintainer

The site is maintained by a single maintainer working from a public repository. The maintainer owns the content roadmap, the review schedule, and the intake for feedback. Contributions from other contributors are welcome through the public issue tracker and pull-request process, but the final decision about what ships on the public site sits with the maintainer. This is the same model recorded in the repository's maintained-source policy, which explicitly identifies the official upstream repository as the canonical maintained source and lists the maintainer's responsibilities for review, source referencing, changelog notes, and issue tracking.

How sources are reviewed

Every checklist rule, document guide, and process explanation is traced to a source or an approved editorial policy. Every content surface carries a last-reviewed date so readers can see how fresh the review is, and uncertain pages can be flagged for re-review when source material changes. Statements are classified into a small set of categories. Official requirement, official recommendation, common practical advice, anecdotal field note, and legal nuance requiring caution. So readers can tell at a glance how much weight a given line should carry. This classification model comes from the project's trust-and-safety policy and is applied consistently across surfaces. The source review model deliberately separates official requirements from practical advice and avoids publishing unsupported legal interpretations as settled guidance.

How feedback is escalated

If you notice something that looks wrong or out of date, the feedback form is the most direct channel: feedback submissions land in a private inbox readable only by the maintainer, with a 90-day retention window described on the Privacy page. From there, the maintainer triages submissions against the statement-class framework: a correction to an official requirement is prioritized over a style note, a high-risk topic (criminal history, waivers, inadmissibility, custody or adoption edge cases, medical inadmissibility, document unavailability exceptions) is explicitly limited and/or routed to a prompt for professional help rather than silently rewritten, and source changes create review tasks that are logged for a later re-review pass. Issues can also be raised through the repository's public issue tracker if you would rather leave a public trail than use the form.

Forks and mirrors

Because the subject matter can change and mistakes can have real consequences, readers should be able to tell which version is the maintained canonical source. Forks and mirrors are welcome, but fork maintainers are asked to clearly identify themselves as unofficial unless they are the official upstream, disclose modifications, disclose the date of their latest review, avoid implying official status, and preserve the disclaimers and attributions required by the project's licenses. The suggested notice for a fork is: "This is an unofficial fork of the project. Verify important requirements against the official upstream and relevant government sources." The full fork expectations live in the maintained-source policy file in the repository.

Project repository and corrections

This is an open-source educational project maintained by a single volunteer maintainer who is not an attorney and does not provide legal advice. The project mirrors public U.S. government instructions and other publicly verifiable sources, and the maintainer is the only person who reviews and ships content changes.

If you spot something wrong, missing, or out of date, please open an issue on the public tracker so the correction is logged in the open. The site feedback form is also available for less public reports.

• Source code on GitHub (https://github.com/NovaRagnarok/GreenCardGuide)
• Report a correction or open an issue (https://github.com/NovaRagnarok/GreenCardGuide/issues)