Languages & tooling
Purpose-built compilers, REPLs, and workflows that compile to 6502 but feel modern.
Why we exist
Atari development shouldn’t feel like archaeology. The Foundry keeps the signal strong by pairing modern structure with hardware-first thinking: structured languages, schematics and build guides, verified ATR/ROM releases, and community support channels that stay archived.
What we build
Documentation & wiki
Markdown-first docs mirrored to GitHub Pages with schematics, tutorials, and grammar references.
Hardware projects
Cartridges, interface boards, test rigs, and BOMs with wiring diagrams and faceplate artwork.
Download vault
Verified ATRs, cassette masters, and ROMs with checksums, duplication notes, and compatibility callouts.
Community ops
GitHub Issues, Discord hooks, and build threads so fixes, feature requests, and lessons stay searchable.
Guiding principles
- Respect the hardware. Everything is tested on stock Atari machines and common emulators before shipping.
- Keep sources readable. Docs, examples, and code live in the repo so you inherit full history.
- Stay explicit. We avoid magic tooling in favor of flows you can replicate on your own gear.
- Leave a trail. Issues, build logs, and releases stay public so future builders can follow along.
How we partner
- Everything we ship is static-export friendly—ideal for GitHub Pages and retro web mirrors.
- Projects arrive with checklists, scripts, and duplication guides so you can reproduce results.
- Support flows through the same repo you already use, keeping conversations attached to code.
- When a product needs more depth, it gets its own page, docs, and vault slot.
Milestones
- 2024 – Prototype new language tooling and ship early REPL builds to friends running stock 800XLs.
- 2025 – Stand up AtariFoundry.com with mirrored docs, GitHub Issue integration, and the download vault.
- 2026 – Add hardware projects (diagnostic cartridges, interface boards) and open up public Discord support.
Operating signals
- Docs and specs originate as Markdown in the repo—no hidden wikis or locked formats.
- Automation scripts produce ATRs, ROMs, and audio masters with checksums baked in.
- Each release is paired with diagnostic tools so you can verify your hardware after flashing.
- We publish errata posts whenever new learnings surface from GitHub Issues or the Discord.
Want to collaborate?
Builders, BBS sysops, musicians, and hardware hackers are all welcome. Fork the docs, open an issue, or drop into the Discord to sync up. If you’ve got an Atari-ready workflow that belongs in the Foundry, let’s talk.
About the founder
I’m Rick Collette. I started on Atari hardware in 1978—first a 2600, then a 400, then an 800XL, and eventually just about every other 8-bit Atari. I accidentally dialed into a modem, found a copy of AMIS, hacked it to pieces, and ran a BBS until 1994. Atari Foundry is my way of giving today’s builders the tooling I always wanted.
Connect with me on LinkedIn or drop a note on GitHub.
Keep the signal alive.
Whether you’re writing new code, flashing cartridges, or scanning schematics, Atari Foundry is the hub. Grab the latest download or sync with support—we’ll keep the neon on.