A community reference for atheists & anyone deconstructing their faith
Contribute

This resource gets better when people like you add to it

This isn't one person's project — it's a shared reference for atheists, ex-believers, and anyone working through doubts about their faith. If you've ever wished a verse, an argument, or a whole topic was covered here, you can put it here. No credentials needed: if you can open a passage and check a fact, you can contribute.

Ways to help

Suggest

A verse or topic that's missing

Know a passage that belongs on the slavery shelf or the distasteful shelf? A creationist claim that keeps coming up and deserves a prepared answer? Open an issue with the reference and a line on why it matters, and it can be added in the same format as the existing cards.

Correct

Fix an error

Accuracy is the whole point of a reference like this. If a date, half-life, brain-size range, translation note or summary is wrong or misleading, file a correction — ideally with a source — and it will be fixed. Corrections are the most valuable contributions there are.

Propose

A whole new section

The problem of evil? Bible contradictions, prophecy claims, flood geology, church–state history? If a topic deserves its own page, propose it in an issue — outline the key claims and the best sources, and it can grow into a section the whole community can use.

Build

Contribute code or content directly

Comfortable with GitLab? Fork the repository and open a merge request. New cards, better wording, extra sources, accessibility fixes — direct contributions are welcome, and the repository is where every change is reviewed and tracked.

What is GitLab, and why do we use it?

What it is. GitLab is a free website for storing and collaborating on a project's files. Every page, style and script of this site lives there in a repository, which keeps a full history of every change: who made it, when, and why. It also has an issue tracker (a public to-do and discussion list) and merge requests (proposed changes that get reviewed before they go live). It is also where this site is published, using GitLab Pages.

Why we use it.

  • Every change is traceable. For a reference whose whole point is accuracy, anyone can see exactly what changed and why, and any mistake can be undone.
  • Nothing goes live unreviewed. Suggestions arrive as issues or merge requests, and maintainers check the sources before anything is published.
  • It is open. Anyone can read the content, the discussion and the history, and anyone can copy the project or propose changes to it. It isn't tied to one person's computer or inbox.
  • It is free and does the whole job. The same service stores the files, tracks suggestions, runs the automatic checks and publishes the site, so there is nothing extra to pay for or maintain.

Why an account is needed. Posting an issue or proposing a change attaches it to a named account. That lets maintainers reply to you and notifies you when someone answers, credits your work (under a handle if you prefer), and makes spam and drive-by vandalism much easier to deal with than anonymous posting would. Reading the site and the repository never needs an account. Signing up is free, takes a couple of minutes, and doesn't need your real name: a handle and an email address are enough.

Prefer not to sign up? Use the email option below instead. It creates an issue for you without an account.

How it works on GitLab

New to GitLab? The easy path is an issue:

1 · Go to the repository and open the Issues tab.
2 · Click New issue and say what you'd add or fix — the verse reference, the claim, or the new topic, in your own words.
3 · That's it. Maintainers and other contributors can pick it up, discuss it, and turn it into an update.

Want to make the change yourself? Fork the repo, make your edit, and open a merge request describing what you changed and why. Every merge request is reviewed before it merges, so don't worry about getting the format perfect — a clear change with a good source beats a polished one without.

Fix a typo or add a card in the browser, no install needed. Open index.html in the repository, click Edit → Edit single file (or the Web IDE), make your change, and choose Commit changes with a new branch. GitLab then offers to open the merge request for you. The contributing guide has copy-paste templates for each kind of card.

Pseudonyms are fine. You can contribute under a handle, and you'll be credited by that handle or not at all, whichever you prefer.

No GitLab account? Just send an email. Write to contact-project+heretixlive-heretix-live-debate-reference-88173583-issue-@incoming.gitlab.com with the verse, claim or correction and a source if you have one. It becomes a private issue that maintainers can read and reply to, and no account is needed. Maintainers will be able to see the email address you send from, so use one you're comfortable with.

What makes a good contribution

Don't have a GitLab account? Creating one is free, and an issue takes about two minutes. Or skip the account and email it in. Every suggestion is read — this page exists because people kept asking good questions.