Community

Orchard is built in the open. The fastest way to get unstuck, share a project, or change where the language goes is to show up and say something. Here is where the conversation happens.

Where to go

Getting help

If you are stuck, the forum is the right first stop. A good question includes what you tried, the agent or snippet in question, and the exact output from orch check or orch run. Other people read these threads later, so a clear question that gets a clear answer helps more than just you.

Helping out

You do not need to be a compiler engineer to make Orchard better. Answer a question in the forum, write up something you figured out, file a precise bug, or send a documentation fix. If you want to work on the language itself, the contributing guide walks through building from source and opening a pull request.

Be decent. Everyone here was new to this once. Read the code of conduct before you post. It is short, and it is enforced.